Technical Manual: Device Linkage & Multi-Account Restrictions—A Technical Deep-Dive
Preface: Architectural Integrity
Our products and services are designed to provide high-performance Android applications and executable scripts (Lua) within a strictly regulated security environment. To maintain the Pentagruel ecosystem, we enforce a mandatory 1:1 device-to-account ratio.
This documentation provides an exhaustive analysis of the technical mechanisms, such as SSAID identifiers, used to prevent ecosystem abuse and ensure fair resource distribution.
I The Primary Identifier: Android ID (SSAID)
To establish a permanent link between a user and their hardware, the application queries the Settings.Secure.ANDROID_ID.
1. Persistence
This 64-bit number is persistent across application uninstalls and re-installs.
2. Bypass Resistance
Unlike temporary cache, a "fresh start" or clearing data will not reset this identifier.
3. Hardware Profile
Tied deeply to the hardware profile and signing key, creating a robust security anchor.
II The 1:1 Binding Logic: The "Stamping" Process
The Hydra backend serves as the authoritative registry. Upon the first successful login, the database "stamps" the device's SSAID onto the Pentagruel ID provided by the user.
Once linked, the backend rejects any AUTH_REQUEST where the incoming DeviceID does not match the registry.
> ❌ Error: This device is already linked to an account.
This error triggers if an authentication attempt is made from a mismatched hardware profile.
Ref: DEVICE LINK
III Anti-Abuse Rationale: Safeguarding the Ecosystem
Standard users are restricted to a 4h daily limit. Linkage prevents rotating through multiple free accounts to reset this temporal meter.
Acts as a "Hard Lock" against subscription sharing, preventing a single Premium account from being used across a "farm" of devices.
Even if credentials are stolen, the Self-Protection Protocol blocks access if the device ID does not match the "stamped" ID.
IV. Persistent State and Decoupling
Because the SSAID is tied to the hardware profile, it creates a highly Persistent State that resists standard reset methods.
⚠️ Factory Resets
Depending on the Android version and signing key, even a full factory reset may not be sufficient to decouple the link.
ℹ️ Manual Intervention
Decoupling typically requires manual intervention from the administration team to ensure the request is legitimate.