Expand description
Private wallet service composition without browser-engine policy.
Structs§
- Native
HnsFinalize Notice - Durable native notice spanning TRANSFER submission through verified FINALIZE completion. It is derived from encrypted name workflows plus the current authenticated name state; a host cannot manufacture its lifecycle.
- Native
HnsName State Summary - Native
HnsName Summary - Bounded canonical name state returned only to trusted native callers. Derivations, owner outputs, proof bytes, and key material stay inside the HNS runtime; public state and the protocol-bounded resource may be shown by a first-party wallet UI without another database or chain scan.
- Native
HnsRead Bootstrap Passphrase - One consumable wallet passphrase supplied by a trusted process-local bootstrap composition. The allocation is zeroized on every return path and its diagnostics never expose the passphrase.
- Native
HnsRead Profile - Wallet-owned configuration for a future trusted native HNS read service.
- Native
HnsRead Profile Fence - Exact nonsecret active-profile fence supplied by the wallet-owned launch authority. Both fields must match before and after service construction.
- Native
HnsRead Profile Metadata - Secret-free authenticated metadata for one profile record or tombstone.
- Native
HnsValue Snapshot - One coherent, minimized full-runtime projection for trusted native UI. Chain/mempool bindings, coins, scripts, raw transactions, and keys remain inside the HNS runtime.
- Persistent
Control Runtime - Existing-database control plane used by the checked-in subprocess. It owns
no chain adapter or account selector and cannot move value. The same shared
store handle is installed in
ProviderCore, sowallet_lockclears the one decrypted record key used by both runtime control and permission state. - Persistent
HnsAccount Config - Trusted library inputs for the exact-existing-account HNS composition. The checked-in executable intentionally has no insecure CLI defaults for wallet/account selection, so product code must build the selector from the same shared store handle passed to the service.
- Persistent
HnsAccount Runtime - Concrete lifecycle runtime which can select and disclose only one exact authenticated pre-existing HNS account. Persisted value flags grant no capability here; synchronized reads and signing remain separate unavailable compositions.
- Persistent
HnsRead Config - Trusted library inputs for the synchronized HNS read composition. The runtime already owns the exact selector/store/backend join; the service accepts it only when its Arc-backed store authority is identical.
- Persistent
HnsRead Runtime - Product-composable HNS account runtime that performs one live, bounded reconciliation for every balance/history/receive/name result. Its exact- text name import is trusted-native only; it exposes no provider import, value, signing, module, marketplace, or settlement path.
- Persistent
HnsValue Config - Trusted product inputs for a full HNS runtime that was opened over the same unlocked store and then relocked before service construction.
- Persistent
HnsValue Runtime - Provider-capable HNS runtime with one exact account and one exact encrypted store authority. There is no alternate signing store or caller-selected wallet/account path.
- Persistent
Native HnsRead Config - Trusted native-launcher inputs for the concrete authenticated-loopback HNS read service. The expected account is configuration, not a caller-selected website identity: unlock re-authenticates the exact persisted account before any provider request can use it.
- Persistent
Shakedex Config - Trusted installed-product policy for Shakedex. Website callers cannot supply or override marketplace fee destinations or amounts.
- Profile
Backed Native HnsRead Runtime - Closed post-bootstrap runtime. Its wallet-operation implementation admits
exactly the six reads frozen by
hnsReadOperationsV1; mainnet/testnet/ regtest instances additionally admit the separate native-only authority- context request. Lifecycle, recovery, workflow, value, provider, and non-HNS module operations remain rejected. - Recovery
Profile Backed Native HnsRead Runtime - Closed recovery-only post-bootstrap runtime for an exact already-persisted
flagged account/profile. Its flags are identity facts only: this type
advertises no provider or value capability and admits only the six frozen
hnsReadOperationsV1wallet reads. - Stored
Native HnsRead Profile - One authenticated encrypted active profile revision returned after exact account reauthentication.
- Trusted
Native HnsValue Action - Opaque, single-owner permit proving that the exact native value action was prepared and its canonical summary validated. Private fields prevent a downstream embedding from manufacturing an execute-only shortcut.
- Unavailable
Runtime - Wallet
Service - One process-local service generation. Construction rotates both the service and wallet session identifiers and starts with no authority handles, approvals, replay entries, rate windows, request IDs, or event cursors. The supplied state store remains the sole source of permission records and tombstone generations.
Enums§
- Loaded
Native HnsRead Profile - Complete result of inspecting the encrypted singleton namespace.
- Native
HnsFinalize Notice Phase - Native
HnsName Ownership Status - Native
HnsName Resource Status - Native
HnsRead Bootstrap Error - Failure from the private profile-backed native-read composition.
- Native
HnsRead Profile Error - Native
HnsRead Profile State - Persistent
Shakescape Transport - Transport policy for the native Shakescape board.
- Service
Error
Constants§
- MAX_
JAVASCRIPT_ SAFE_ INTEGER - MAX_
PROVIDER_ HNS_ READ_ ITEMS - MAX_
SEEN_ REQUEST_ IDS - MAX_
SERVICE_ PENDING_ APPROVALS - NATIVE_
HNS_ READ_ PROFILE_ ID - The only record identifier admitted in the native HNS read-profile namespace.
- NATIVE_
HNS_ READ_ PROFILE_ SCHEMA_ VERSION - Authenticated-record schema for the native HNS read profile.
- NATIVE_
HNS_ SEND_ PRE_ BROADCAST_ RETRY_ MESSAGE - A native HNS send failed before it could be authorized, signed, or handed to the peer broadcaster. The approval is discarded and the caller must obtain a fresh authenticated snapshot before preparing another send.
- TRUSTED_
NATIVE_ HNS_ VALUE_ ORIGIN - Reserved origin commitment used only by the installed native value UI. It is deliberately a valid loopback origin so the existing encrypted approval records retain one canonical origin encoding, but it never grants or stands in for browser-engine authority.
Traits§
- Service
Runtime - Execution boundary supplied by a wallet composition. Runtime method support is checked independently from the closed provider vocabulary, and value or browser capability is never inferred merely because protocol source exists.
Functions§
- load_
native_ hns_ read_ profile - Inspect the single encrypted profile state after wallet unlock. Active profiles reauthenticate their exact account; tombstones return only secret-free revision metadata and absent state remains distinguishable.
- provision_
native_ hns_ read_ profile - Create, rotate, or re-provision the single encrypted native-read profile.
- revoke_
native_ hns_ read_ profile - Compare-and-swap the active profile into a persistent tombstone. The tombstone retains the monotonically increasing revision and update time so later re-provisioning cannot create a revision ABA. This changes future startup configuration only; a future product must separately terminate or revision-revalidate any already-running service before claiming revocation.
Type Aliases§
- Persistent
Native HnsRead Runtime - Concrete non-value read runtime used by a separately trusted native browser launcher. Browser-engine authority and artifact admission remain outside this crate and are never inferred from constructing this type.