Embedded wallets: transactions & session keys

​

What maps to what

​

Migration-specific behavior

• Nothing embedded-wallet-specific about signing. Pass the embedded walletAccount into the same signMessage() / transferAmount() / confirmTransaction() you’d use for any wallet — signMessage returns { signature }, transferAmount returns { transactionHash }, and confirmTransaction resolves once that hash confirms on-chain. The widget rendered the pending state; you now render it from those calls.
• Session keys are gone — use delegated access. The React SDK’s session-key approval screens (approve an app or agent to sign within limits) are replaced by delegated access: grant your backend the ability to sign for the wallet and let the user revoke it anytime. Build that flow from the delegated-access page, not a session-key screen.

​

Errors you now own

​

See also

• Transaction confirmation & simulation (Building UI) — the full sign, send, confirm, and simulate build
• Transactions & balance — reading balances and simulating before a send
• Embedded wallets: delegated access — where scoped session keys now live
• Embedded wallets: setup & creation — creating the wallet you sign with