Portfolio Registry
Canonical project identity, append-only release history, source commits, artifact hashes, and explicit lifecycle state.
Architecture Lab · Protocol V2
A working specification for project provenance, sponsored interaction, and evidence-driven reputation—designed to show the boundaries a Web3 systems architect is responsible for.
System primitives
Canonical project identity, append-only release history, source commits, artifact hashes, and explicit lifecycle state.
Structured architecture choices linked to real projects, with bounded options, EIP-712 relaying, and one response per account.
Idempotent ERC-1155 achievements for meaningful actions—kept separate from professional reputation and financial value.
Intended user flow
Read the context, system constraint, and credible implementation choices.
A relayer can sponsor the operation without custody or token approval.
The response, aggregate result, and optional passport update share one trace.
Flagship interaction
Evaluate account abstraction, trust, and protocol-lifecycle decisions using the same bounded data model implemented by the V2 contract.
Enter the workbenchHistorical system
The original HOMIE faucet, visitor book, project voting, and NFTs remain publicly inspectable as an earlier architecture generation.
Inspect the legacy system