NFTs & native 8415
NFTs first. Native ownership, holder and settlement controls at a glance.
Beta 2.0
Your assets. Your say.
A familiar wallet with clear identity, ownership and approval boundaries.
Existing wallet
Find your wallet
Verify your identity to access your wallet.
Wallet login
Your private key stays in your wallet. Never paste a seed phrase or private key into this page.
You can keep several sign-in methods enabled for this account. Choosing one for this login does not disable the others.
Log in to view assets and history. Connecting an account alone is not login.
Wallet login
The public entry stays open. Assets, balances, holdings and history appear only after a verified wallet login. Choose a login method. Login grants no transaction authority; every transfer still needs your wallet approval.
Login lasts 15 minutes in this tab and ends on reload, logout, account or chain changes. Public blockchain records remain public. Local wallet login is a display lock. Account login methods require the configured same-origin authentication service; no private register API is introduced.
Register an ordinary wallet account
Verify your email, then prove control of your wallet. This creates an ordinary account only. No administrator access or transaction permission is granted.
Already have an account? Sign in first, then verify its email in account settings. Do not create a second account for the same wallet.
Leave both fields empty to start with registered-wallet login. An optional password must match and contain at least 12 characters. Never enter a wallet seed phrase or private key.
Account authentication settings
Choose what to set up or manage. Verification is requested only after you choose an operation.
Verify an already established method for this wallet to continue. Opening settings does not require an earlier login.
Sign in to view and manage this account’s methods. Local-only wallet login cannot manage server credentials.
Account password
Use at least 12 characters, at most 1024 UTF-8 bytes, and matching entries. Never enter a wallet seed phrase or private key. Saving signs out every account session.
This account has an authenticator. Enter its current code or one unused recovery code in the protected-changes field below, even if authenticator login is disabled.
Verify the reserved security answer and email code below before saving this password.
Account registration email
Changing a verified account email requires your reserved recovery verification and existing authenticator/recovery proof. The new email must also be verified.
This account’s sign-in methods
Select one or more bound methods. Keep at least one password, registered-wallet or hardware-CA method enabled. Changing authenticator access also needs its current code or a recovery code. Saving signs out all sessions.
Configured methods stay enabled independently. Adding an authenticator does not remove password, wallet or hardware-CA access.
First authenticator setup needs no old code. Scan the private QR code and verify a new code before activation.
Replacement requires a fresh independent login and an existing authenticator or recovery code. If both are lost, use the operator’s verified recovery process.
Set up an authenticator
Requires a password, registered-wallet or hardware-CA login within five minutes. A replacement also needs the current authenticator code or a saved recovery code. This is an alternative login method, not mandatory two-factor authentication.
Scan locally with your authenticator. Keep this code private; manual entry remains available.
Safety reset verification
Reserve and verify an email address and security answer before you need them. Email codes add reset verification; they do not log you in or replace independent identity and existing authenticator/recovery proof.
To change reserved details, verify the existing answer and email first. Then enter the new details below; the new email must also be verified.
Recovery verification uses the same verified account email. Change that identity only through account-email verification.
Use a private answer of at least 12 characters. Avoid facts others can guess. Do not enter a wallet seed phrase, private key or reused password.
Wallet and hardware-CA bindings use their verified registration or operator processes. This page never initializes the server or replaces its store key.
Save your recovery codes now
Each code works once. Store them somewhere private. Setup signed you out and revoked previous sessions. These codes are shown only once.
Native asset
ERC-8415Tradeable position
—
ownerOfConfirmed holder
—
—No asset read yet. Load an exact deployment and token ID.
NFT holdings
ERC-721 / ERC-1155
No NFT holding read yetUse an exact contract and token ID. No automatic discovery or external artwork.
Native settlement
Prepare a review before opening your wallet. Native controls remain testnet-only.
Cancellation closes a gap without admitting an entry or making an instant final.
Standalone account
Optional capabilityOwned-token deposit and unencumbered withdrawal require separate review.
ETH & tokens
No external-account balance read yet
Connection and deployment identity
Use a genuine wallet provider. No keys are imported. This native ERC-8415 panel enables testnets only.
Not connected
Standalone account
Projection readers and protocol settlement actions remain available independently. No responsibility controller or payment module is required.
Cross-token commitment and reference review
Compare up to 32 distinct token IDs on this deployment, with at most 2048 total entries per scan. A budget refusal produces no partial report. No collision found only applies to these tokens and reads, never the whole register. Registry locators are not resolved; sequential reads are not an atomic snapshot or transaction authority.
Protocol settlement
Prepare one ERC-8415 operation, review its authority and protocol checks, then explicitly continue in your own wallet. These are snapshots. An integrating contract should read holderAsOf, isFinalAsOf and openGapOf atomically inside the dependent transaction. A mined receipt is not protocol temporal finality.
Finalization is a permissionless proof relay. Only the contract verifies the proof under its verification profile; the wallet cannot verify legal identity or entitlement. Cancellation requires the recorded initiator after the deadline, closes only the contest, and makes no instant final.
No settlement reviewed
Settlement receipt and recovery
Unknown outcomes block another send across reloads. Never clear browser storage to bypass them. An explicit wallet cancellation requires a fresh review. Recover only from matching mined wallet activity; a different canonical same-nonce transaction can resolve the old intent without calling it successful. Two confirmations are a display threshold only.
No settlement journal loaded
Optional controlled account
External wallet account
Ethereum and Base, with Sepolia and Base Sepolia for rehearsal. ETH, ERC-20 tokens and standard ERC-721 / ERC-1155 NFTs remain in your existing external wallet account. No seed phrase, private key or standing agent permission is requested.
Not independently audited. Functional-testing Beta; real-asset acceptance remains outstanding. Agents prepare and check requests; you personally review, sign and submit in your wallet. ETH sends currently require an EOA recipient. No swaps, approvals or smart-account custody. ERC-20 transfers use explicit contract addresses and integer raw amounts; optional metadata never establishes token identity. Fee-on-transfer, rebasing and other nonstandard token economics are unsupported. An exact Transfer event is not a promise of economic value or future balance.
Not connected. Select Ethereum, Base or a supported testnet in your wallet first.
Technical fields, signed terms and token metadata below retain their original source values. UI language never changes transaction amounts or authorization.
No external-account execution performedPrepare a transfer
ERC-20 decimals are never assumed to be 18. Enter raw integer units. A formatted display is shown only when the contract supplies valid decimals. Always check the selected chain and contract address.
Or review a request prepared by your agent
Technical fields retain original values
No transfer reviewedYour receiving address
No receive address verified. Never send ETH to the 8415 controlled-account contract.Match the network with the sender. Never use the controlled-account contract.
Receipt and recovery
Unknown outcomes must stay saved. Never resend or clear browser storage to escape an unknown result. Check the same account in wallet activity; recover only with its exact matching mined transaction hash. A speed-up with the same intent can be recovered by its mined hash. A cancellation or different transaction clears this journal only with explicit canonical same-nonce proof; it never marks the original transfer successful. Missing hashes and unchanged nonces do not prove cancellation. Two confirmations are a display threshold, not economic or ERC-8415 finality.
No account journal loaded
Open NFT details
Use an exact contract and token ID. No automatic discovery or external artwork.
No NFT holding read yetLinked responsibilities
Completion needs both owner and admitted holder at the buyer occurrence or later. A completed prefix never becomes recallable again. Payment is optional and cannot authorize completion.
Amount and adapter come only from the reviewed consent. Reserve before switching to the seller for forwarding. After detachment, payment remains readable and withdrawable by leg ID; a missing payment record is not a completed responsibility.
Detached responsibility history
Load a public register export covering the full detached prefix. Every record must match the on-chain commitment; missing, changed or out-of-order records are refused. No registry locator is resolved. The 4 MiB file limit is a UI review budget, not a chain-lifetime limit.
Receive with informed acceptance
Load only public consent and its exact terms documents. No signature is loaded from a file or shown in this page.
No review prepared
After acceptance, select the selling wallet in your provider and reconnect before forwarding. The signature stays in this page's memory only and is cleared on reload.
Agent request inbox
An agent can prepare a public request for this selected testnet account. Its claimed name is not authenticated. Importing or reviewing never signs or sends. Every supported request needs your explicit review and a separate confirmation in your wallet.
This first integration supports controlled-account creation, deposit, unencumbered withdrawal, prefix completion and one accepted return hop. It does not grant allowances, import signatures, execute arbitrary calldata or enable unattended trading. Linked forwarding keeps its separate informed-consent flow above.
No agent request reviewed
Responsibility recovery and execution state
Connect the same wallet account, chain and deployment to inspect its saved operation. No automatic resend.
A submitted hash is not completion. Unknown outcomes block a second send. A refresh never automatically repeats a transaction.
No execution performed
Authorize an agent task
Review the complete bounded task once. A separate task grant lets the agent carry out in-scope work without asking you to approve each child operation.
Execution requires configured trusted adapters. The default candidate has none connected. Authorization, submission and a verified outcome are separate facts.
No tasks for this authenticated account and chain. A task prepared through the service will appear here.
Exact task and limits
Canonical task policy
Authorization saved. Continuation is blocked because a required execution or evidence integration is unavailable. No new transaction is being sent.
Verify this operation
Verification does not execute or resume this operation.
No unattempted reserved operation.
Task operation records
Transaction observation
Confirmation depth is only a chain observation. Protocol temporal finality and economic finality are not evaluated. Reorgs can change this result.
Saved observation records
Required execution integrations
Closing or signing out does not revoke an existing grant or undo a submitted request. Recheck this task after an interrupted response. Unknown transaction outcomes must be recovered, never resent.
First authenticator setup, replacement and sign-in method management belong in account settings. Only existing factors are required; task authorization does not change login methods.
Account authentication settings
Agent settings
Default ON (unlocked) · controls not connected. Saved settings have not been read.
Saved setting read for this wallet · operate this switch in sign-in method management.
Tenant avatar
Only in this browser, for this tenant and release profile. This does not change the platform logo or server tenant configuration.
Configured identity, read-only
Loading verified release profile…
Read result
Functional-testing Beta
Functional-testing Beta. Not independently audited. Native ERC-8415 protocol and responsibility controls remain testnet-only. External-account mainnet transfers require your own wallet confirmation; genuine-wallet and physical-device acceptance remains outstanding.