Finance District Managed Wallet

Connect Finance District when your hive needs networks and wallet services beyond HivemindOS’s local Base, Robinhood Chain, and Solana wallets.

The connection adds:

• Balances and account activity across Ethereum, BSC, Arbitrum, Base, Solana, Bitcoin, and Sui.
• Token transfers on supported networks, including Bitcoin and Sui.
• Swaps where the connected service supports them.
• Discovery, deposits, withdrawals, positions, and redemption tracking for supported EVM yield opportunities.
• Message signing and paid x402 requests.
• Merchant project, settlement-wallet, staff, payment, and earnings management.
• Finance District UCP and ACP discovery, payment preparation, and settlement for published company products.
• Signed payment notifications with duplicate-delivery protection.

Finance District reports that wallet signing happens inside its protected signing service. HivemindOS does not receive or store the managed wallet’s private keys. This is a third-party account boundary: Finance District remains responsible for its custody, supported networks, asset availability, and service uptime.

Connect

1. Open More → Integrations → Connected tools.
2. Find Managed Wallet and choose Set up. Setup finishes in the same panel.
3. Enter your email and choose Sign in or Create account.
4. Enter the 8-digit code sent to your email.
5. Refresh the panel and confirm the account shows as connected.
6. To sell published company products to shopping agents, paste the Project Identify Token created in your Finance District payment console into Commerce access token. This extra credential is not required for wallet use.

The sign-in session is kept in your operating system’s protected credential store when that facility is available. If your system cannot provide protected credential storage, complete setup only on a machine you trust and review the warning shown by the wallet helper.

To remove the optional helper, disconnect the account in the same panel and choose Remove helper. You can reinstall and sign in again later.

Safe Agent Use

Account reads are available to authorized agents after connection. Anything that can move assets, trade, enter or exit yield, create a signature, make a paid request, or change live merchant settings follows a separate sequence:

1. The agent prepares the exact action and returns a review code that changes if any detail changes.
2. You review the account, network, asset, amount, destination, strategy, message, or merchant change.
3. You explicitly confirm the unchanged action.
4. HivemindOS records an idempotency receipt before submitting it.
5. A successful retry returns the saved receipt instead of submitting twice.

If the connected service does not return a clear result, HivemindOS marks the outcome for review and refuses an automatic retry. Check account activity, yield positions, or payment history before deciding what to do next.

Smart accounts appear only when the connected account actually reports them. HivemindOS does not show an unavailable deployment action.

Agent Checkout For Company Products

Published paid company products become discoverable to shopping agents through UCP and ACP as well as the existing x402 purchase flow after commerce access is saved. HivemindOS advertises Finance District’s current xyz.fd.prism_payment handler, asks Finance District to prepare payment options for the server-owned catalog price, and sends the signed payment credential back to Finance District for settlement. The buyer cannot replace the price, destination, network, or product identity in its checkout request.

Checkout sessions expire, bind payment to the unique session address and one published product, accept one unit per order, honor checkout idempotency keys, and store the successful result for safe replay. A repeated completion returns the existing order instead of settling again. A payment option not issued for that session is rejected before settlement. If a product is unpublished before payment, checkout stops.

To receive payment updates, add the payment-notification address shown in the Managed Wallet panel to your Finance District payment console, then paste the signing secret back into the same panel. HivemindOS verifies every notification before accepting it and records only bounded receipt metadata; wallet addresses from the notification are not retained in that receipt store.

The same panel can replace or remove the commerce access token and notification signing secret without disconnecting the wallet account.

Boundaries

• This is an optional third-party connection. Local HivemindOS wallets continue to work without it.
• Bitcoin and Sui support is limited to the operations returned by the connected service. Yield is limited to supported EVM networks.
• Merchant access-token creation stays in the provider’s own console so a one-time secret never passes through an agent tool.
• HivemindOS does not claim a smart-account deployment succeeded unless the connected account reports it.
• Do not paste recovery material, private keys, payment credentials, or signing secrets into chat, notes, screenshots, or support reports.