Interactive protocol surface

Make the trade-off. Then inspect the state transition.

This workbench mirrors the reviewed V2 Solidity interface without pretending a local simulation is a mainnet transaction. Choose an architecture, attach a rationale, and inspect the contract-ready receipt.

Account architecture

ADR–001 · portfolio-protocol-v2

Contract-ready simulation

How should a public portfolio provide one-action Web3 interactions without turning account infrastructure into product friction?

Context

Visitors may arrive through email, a browser wallet, or an existing smart account. The application needs sponsored, legible actions while keeping the portfolio available without authentication.

Hard constraint

No visitor should claim a token, approve spending, or register the same identity across multiple contracts before expressing one useful signal.

Select the architecture you would ship01Managed smart accountUse a production account provider for onboarding, batching, recovery, and sponsorship.StrengthLowest interaction friction · Operationally mature · Fastest recovery pathCostProvider dependency · Less protocol code is owned02Custom modular accountOwn the complete account stack with validators, modules, bundler, and paymaster policy.StrengthMaximum architectural control · Deepest protocol demonstrationCostLarge security surface · High maintenance burden03Product + account labUse managed accounts for visitors and a custom standards-oriented account as an explicit exhibit.StrengthGood UX and technical depth · Clear production boundaryCostTwo integration paths · Requires disciplined documentation

Optional rationale0/280 · only the content hash enters the contract receipt

Architect's resolution

Use a managed ERC-4337 account for the product surface and keep the custom modular account as a separately inspectable engineering lab.

Hide operational complexity; expose architectural decisions.