Developer Console

The Developer Console is available at /developer-console to approved Developer Preview organizations. Its identity and organization-membership controls are live; broader application, credential, webhook, usage, and sandbox controls remain governed by the current preview boundary.

Sign in with an organization wallet

Console access is wallet-first and non-custodial. Creating a preview organization requires an ownerWalletAddress; Torq creates that address as the first active organization owner. To sign in, the browser requests an origin-bound, short-lived challenge and the owner or member signs it with their own wallet. The challenge is not a transaction and does not move funds.

After verification, Torq sets a short-lived opaque HttpOnly, SameSite=Strict browser cookie. The token is never returned to browser code, written to local storage, persisted in a log, or stored in the database. The database contains only its hash. Each request rechecks the cookie hash, expiry, revocation, exact origin, organization state, member wallet, and active membership against Postgres-backed canonical state.

Membership and recovery

• Owners may add members and change roles or membership status.
• Admins may add Developers and Viewers; they cannot grant Owner or Admin access.
• Developers and Viewers have no membership-administration authority.
• Changing or suspending the last active owner is rejected.
• Changing a member's role or status revokes that member's active console sessions.

Before a sole owner loses access to its wallet, add a second active owner. Torq cannot reset, recover, impersonate, or bypass wallet ownership. This avoids a custodial recovery path and keeps organization authority with its members.

Organizations created before Console identity

An existing Developer Preview organization created before Console identity was introduced can claim its first and only initial owner once. Send POST /v1/console/owner-claim from a server using an existing secret developer key with applications:write, an Idempotency-Key, and the target walletAddress. The request is rejected if the organization is not in private preview or already has any Console member. Publishable browser keys cannot use this path.

This claim creates an active owner record; it does not create a browser session or bypass wallet verification. The claimed wallet must still complete the normal origin-bound signing challenge to use the Console. Store the secret key only in your server-side secret manager.

Preview controls

The rest of the Developer Console will provide:

• organizations and members
• test and live applications
• publishable and secret key creation, rotation, and revocation
• allowed browser origins
• granted scopes and quotas
• webhook endpoints, delivery attempts, DLQ state, and replay
• stream cursors and usage accounting
• sandbox wallets, fixtures, faucet quotas, reset, and reseed
• audit history

Secret values are shown once at creation. The console never displays stored key material because Torq persists hashes for developer keys and KMS ciphertext for webhook signing secrets.

Console identity and membership remain behind Developer Preview access controls. They do not enable public GA, production credentials, protocol governance, or emergency authority.