Safety Principles and Authorization Limits

Current safety baseline: verify user identity and read permitted public data. Live trade signing, broadcasting, order placement, and withdrawals stay closed under the product baseline. Connector-directory status, a browser-side Agent link, and an order preview map to listing, cache, and review.

Current safeguards

• The server verifies the Privy Bearer token. The Master address matches a wallet linked in the server-side profile.
• Public account data is an external observation.
• A funding observation records external evidence.
• Live orders, signing, broadcasting, and withdrawals stay closed; related requests return a rejection.
• AI output organizes information; account permissions stay in server-side policy.
• Composer’s NFT check opens Free-tier read-only quotes. A local test grant or custom mint is an eligibility cache.

Hyperliquid and ASTER

approveAgent and approveBuilderFee are marked connected after implementation, signing, and acceptance. ASTER appears in the connector directory. Trading authorization and order execution follow separate acceptance.

Security design in the proposal

The attached proposal recommends tool allowlists, approvals, idempotency, audit trails, limits, circuit breakers, and an independent signing boundary. Before write operations open, authorization scope, validation flow, and revocation will be defined, then accepted separately.

Status map

Users should independently assess the risks of digital-asset trading.