Security

Know what
authorizes what.

Amethyst separates wallet authority, device trading authority, and exchange execution. That boundary reduces repeated prompts without giving an API key the ability to move funds.

Last updated August 26, 2026

Your wallet approves. Your device trades. Only your wallet moves funds.

The wallet

Your wallet controls the account address and approves enrollment and on-chain value movement. Depending on how you enter Amethyst, the wallet may be embedded through Privy or connected through WalletConnect. Amethyst does not turn the wallet's signing key into a PERPL API credential.

The device trading key

Amethyst generates a separate Ed25519 key on the device. Your wallet signs a PERPL EIP-712 enrollment payload, and the device key signs a proof-of-possession. The enrolled key has read and trade scope. Its private key is stored in the iOS Keychain and is not sent to Amethyst's website or PERPL.

It can

  • Authenticate signed PERPL account and history reads.
  • Subscribe to authenticated trading updates.
  • Place, cancel, and modify orders within the enrolled scope.

It cannot

  • Withdraw or transfer funds through PERPL's API-key surface.
  • Export or reveal the wallet's private key.
  • Guarantee a fill, execution price, protocol response, or network outcome.

Funding and withdrawals

Account creation, token approvals, deposits, withdrawals, and wallet-to-wallet sends are explicit wallet-authorized transactions. Amethyst presents the transaction intent and follows on-chain receipts, but it cannot reverse finalized blockchain activity.

Revocation and a lost device

The in-app revoke action asks PERPL to delete the active session key and then removes it locally. If server revocation cannot be confirmed, the local credential is still erased and the app directs you to PERPL's key-management page. From another device, use PERPL API key management to review and revoke enrolled keys.

Infrastructure boundaries

Amethyst depends on PERPL APIs and exchange contracts, Monad RPC providers, wallet providers, Privy for hosted identity/embedded wallet paths, and Reown for WalletConnect paths. Outages, incompatible changes, congestion, and provider policy can affect availability. Amethyst does not operate PERPL or control its liquidity.

Report a security issue

Do not include private keys, seed phrases, signatures, API credentials, or unredacted balances. DM @theamethystapp on X with the app version, network, steps, and redacted evidence.