K256 Money

Your money, already yours.

Use the identity already protected by your device. There is no wallet to install and no recovery phrase to manage.

This application never receives your passkey.

Spendable

—

Checking finalized balance…

Mint: —
Program: —
Decimals: —
Total: —
Spendable: —
Frozen: —
Send support: —

Assets

Finalized balances

Checking finalized holdings…

Balances, mint addresses, token programs, decimals, and safety status come from finalized Solana state. Names, icons, prices, and spam labels are optional advisory metadata on Mainnet only.

Activity

Finalized

No recent activity yet.

Access & security

Protected

Device protectionPasskey
Recovery phraseNot needed
Eligible network feesChecking eligibility
Passkey or ownership key shared with this appNever

What else this ID can do

These protections appear only when an application needs them. There is nothing to configure for ordinary payments.

Open on another deviceApprove a new device while keeping the same address and balance.
Require more than one approvalAdd a second person or secure device for higher-assurance actions.
Approve limited app accessSet an exact amount, application, and expiry instead of giving away control.
Remove access safelyRevoke a device or permission without moving money or changing the ID.
Prove your ID to an applicationAuthorize an exact message without connecting a wallet or creating a transaction.

Controls & configuration

Progressive

Ordinary payments need no setup. This console shows what this application can request, what only the canonical K256 ID surface may change, and which policy extensions remain planned.

Last verified approvals: Recognize to verify
Last verified controllers: Recognize to verify
Last verified modules: Recognize to verify
Last verified role masks: Recognize to verify
Last verified policy version: Recognize to verify
Verified at: Recognize to verify

Recognition required for requestsYou can inspect deployment and capability boundaries now. Continue before asking K256 ID to authorize a message, payment, or call.

This deployment

Runtime configuration

Application: —
Network: —
Portfolio: —
Sponsorship: Loading eligibility

Application ID, network, finalized portfolio reads, optional sponsored receive-setup eligibility, and the registered reference call come from this deployment. Portfolio metadata never overrides finalized asset identity, decimals, or balances. Message purpose and bytes remain configurable. Exact and Guarded requests are pinned to the registered call; adapter-validated Verified requests must supply matching calls, guards, review, and an integration-owned semantic adapter.

Available in this app

Public hosted SDK

Ready here

Finalized portfolio

Read SOL and every indexed classic SPL or Token-2022 holding from finalized account bytes. Select an asset to send, inspect activity, or share the same receive address.

Ready here

Exact message

Approve an application-bound, purpose-bound message with the active policy. No Solana transaction is created.

Ready here

Execution assurances

Run this registered deployment's read-only reference call as Exact or Guarded, or supply an integration-owned semantic adapter and matching Verified calls.

Ready here

Permissionless technical review

Build an arbitrary compatible call batch. K256 derives the technical review from exact bytes and returns authorization only; it does not sponsor or submit the transaction.

Ready here

Existing Solana transaction

Inspect a legacy or v0 transaction, ignore its signatures, and learn whether its exact calls can be authorized through this K256 ID.

Owner-controlled identity and permissions

Canonical K256 ID

Applications may request a supported capability or open the relevant K256 ID control. Every authority change happens on the canonical K256 ID surface and requires the active policy. This application never receives the passkey or silently changes authority.

Devices and accessPair another passkey, remove access, and restore public recognition records.
Manage
Typed controllersWebAuthn P-256, native P-256, and explicit Solana Ed25519 controllers can govern the same ID.
Review
Approval policyRequest multiple controllers and threshold approvals without changing the ID address.
Review
Bounded app accessRequest an expiring session with exact program, account, asset, and spending limits; revoke it at any time.
Delayed actionsSchedule, inspect, execute, cancel, or clean up an exact policy change after its enforced delay.
Manage
Recovery helpersConfigure typed helpers, an exact approval threshold, and a fixed delay—or open a recovery for another K256 ID. Approval and lifecycle actions stay on the canonical K256 ID surface.
Manage
Recognition recoveryReconstruct the same ID from a passkey or restore its public recognition record without a seed phrase.
Manage

Open K256 ID controls

Policy modules and controller roles

Public SDK

The values above come from the latest independently verified hosted result in this tab. This app can inspect them, but it cannot change authority. Use the canonical K256 ID policy control to review any module, threshold, controller, or role change.

Recognized module kinds: —
Execute calls: —
Authorize messages: —
Manage policy: —
Manage sessions: —
All permissions: —

PolicyModuleKind · ROLE_PERMISSION_BITS · ALL_ROLE_PERMISSIONS · rolePermissionsForPolicy(...)

Review policy and roles in K256 ID

Request bounded app access

Choose the exact limits this application may use. K256 ID will show the complete request and the active policy must approve it. This application never receives your passkey or unrestricted control.

DurationMinutes, from 1 minute through 30 days Maximum SOL per actionLamports; use 0 for no SOL authority Maximum SOL totalLamports across the complete session

Allowed programsOne Solana program address per line, up to 8. This deployment begins with its registered reference program. Additional writable accountsOptional; one Solana account per line, up to 8. The scoped token account is included automatically. Allow one exact token accountSet a mint, token account, and hard per-action and total base-unit limits.

Executable integration builders

Public SDK

These forms call the shipped SDK in this browser. A valid plan is loaded into the same hosted Verified review used by an integration. K256 does not invent accounts, quotes, routes, or sponsor attestations: supply the exact real inputs your application obtained.

Verified native SOL payment

Verified classic token payment

Verified Jupiter v6 swap

The SDK verifies an exact caller-supplied Jupiter v6 instruction plus maximum input and minimum output. It does not choose a quote or route.

Inspect a Solana Pay request

Prepare token fee reimbursement

Paste one short-lived quote issued by the configured sponsor. The SDK validates its closed schema and expiry, then binds its exact token debit separately from sponsored SOL transport. The sponsor validates quote authenticity at submission; a quote alone never grants authority.

Existing transaction compatibilityThe interactive transaction inspector above classifies legacy and v0 messages and can load accepted calls into fresh K256 review.classifyInstructionRequest · prepareTransaction
Ready here
Solana Pay receive linksThe Money receive flow creates a canonical receive request after finalized account readiness.createSolanaPayReceiveRequest
Ready here

Token-2022 safety registry

Complete current registry

The example renders this list from the public SDK. A transfer is Guarded or Verified only when the mint, source, and destination contain exclusively closed-effect extensions and the onchain postconditions hold. Exact-only extensions remain available through a fresh human-present Exact request.

Guarded extensions: —
Exact-only extensions: —
Unknown or malformed: Rejected

Prepare a Verified Token-2022 payment

Enter the exact finalized mint, source, and destination. The public SDK reads all three accounts, classifies every extension, and opens the existing hosted review only when the transfer has closed, enforceable effects.

Exact only is not a weaker safety mode. It means K256 commits the complete call and requires fresh human approval, but does not claim closed-world transfer semantics. Unknown extension IDs, malformed layouts, incomplete account coverage, and unbounded effects fail closed.

Extension boundary

Not implemented

Future policy modulesRecurring permissions, sub-Vaults, institutional workflows, and post-quantum controller schemes remain planned. Controller roles, delayed actions, and delayed helper recovery are implemented on the canonical K256 ID surface.
Planned

Your money, already yours.

Assets

Activity

Access & security

What else this ID can do

Controls & configuration

This deployment

Available in this app

Finalized portfolio

Exact message

Execution assurances

Permissionless technical review

Existing Solana transaction

Owner-controlled identity and permissions

Policy modules and controller roles

Bounded access on this device

Executable integration builders

Token-2022 safety registry

Extension boundary

Where should it go?

Authorize an exact message

Authorize bounded Solana calls

Inspect an existing Solana transaction

Classification

Share your ID

Payment complete