From bullx's X account:

BullX operates on policy-based enclaves for all wallet-related actions. Wallets are stored in AWS CloudHSM modules, which are not accessible outside the enclaves.

All actions, including transaction signing and wallet generation, happen here. These policies are immutable and bound to each generated wallet. These include rules like:

• The PK can only be downloaded for 24 hours.
• Transfers are only possible between wallets within the user's account.
• Simulated trade transactions must end with expected balance changes.
• And more...

Neither the BullX team nor any associated entity, including the cloud provider, can perform actions or access the wallets. Only the code-signed enclaves can interact with the HSM.

The primary login is facilitated via Telegram APIs. Since BullX is a TG-based app, treat your TG account as equivalent to your wallet seed phrase.

From bullx's X account:

BullX operates on policy-based enclaves for all wallet-related actions. Wallets are stored in AWS CloudHSM modules, which are not accessible outside the enclaves.

All actions, including transaction signing and wallet generation, happen here. These policies are immutable and bound to each generated wallet. These include rules like:

• The PK can only be downloaded for 24 hours.
• Transfers are only possible between wallets within the user's account.
• Simulated trade transactions must end with expected balance changes.
• And more...

Neither the BullX team nor any associated entity, including the cloud provider, can perform actions or access the wallets. Only the code-signed enclaves can interact with the HSM.

The primary login is facilitated via Telegram APIs. Since BullX is a TG-based app, treat your TG account as equivalent to your wallet seed phrase.

Ref: https://x.com/bullx_io/status/1811838786780770771