🔑

DreamNet x Dynamic

Server-Wallet Ready

DreamNet Partner Lab Microsite

Thesis

Onboarding human operators into Web3 agent networks is blocked by complex wallet setup. dreamnet-dynamic pairs Dynamic social auth for humans with backend-only Dynamic server wallets for agents, letting operators approve budgeted agent wallets, revoke permissions, and preserve receipt trails without ever exposing API keys in the browser.

Interactive Simulation Console

Onboard Agent Workforce

Log in via social accounts to automatically spin up a secure, non-custodial MPC wallet on-the-fly.

Awaiting social sign-in...

Agent Server Wallet Lane

Dynamic recommended server wallets for agent-only wallets. DreamNet keeps that API-token lane behind a backend policy gate and shows the judges a sandbox receipt today.

Backend-only secret
Backend Contract
✓DYNAMIC_API_TOKEN stays in a server route, Worker secret, or trusted job.
✓Human approval creates the wallet policy before any agent can spend.
✓Current policy cap: 15 USDC/day for 24 hours.
✓Revocation clears the active agent wallet policy and emits a receipt.
Provisioning Receipt
No active server wallet policy.
Provisioning creates a sandbox receipt with an agent id, policy cap, wallet address, allowed actions, and zero exposed credentials.

Integration Flow

1
Social Authenticate

The operator sign-ins via social login options like Google, Discord, Twitter, or GitHub.

2
MPC Wallet Mint

Dynamic SDK provisions a secure, non-custodial multi-party computation embedded wallet mapped to the session.

3
Session Key Settings

The operator configures temporary session key parameters, setting daily USDC limits and durations.

4
Bounded Delegation

The operator signs to delegate key permissions, allowing the child agent node to sign transactions within limits.

5
Server Wallet Lane

Agent-only wallets are created by a backend using Dynamic server wallets and API-key auth, never by exposing keys in the browser.

6
Receipt Trail

Every agent wallet action emits a receipt with policy, approval, wallet, and revocation state.

Server Wallet Boundary

✓Read DYNAMIC_API_TOKEN only inside a server route, Worker secret binding, or trusted job.
✓Never prefix the token with NEXT_PUBLIC_ and never import it into client components.
✓Create the agent server wallet after human approval, policy assignment, and budget selection.
✓Emit a receipt for create-wallet, assign-policy, propose-sign, approved-sign, and revoke-policy events.

Sponsor Integration Link

git clone https://github.com/BrandonDucar/dreamnet-dynamic.git

NotebookLM Briefing Prompt

Explain how dreamnet-dynamic uses Dynamic social auth for human operators, backend-only Dynamic server wallets for agent-only wallets, and receipt-gated policies so agents can act with budgets without exposing API tokens in the browser.