A verifiable career record for smart contract developers, built on Stellar.
Smart contract developers have no portable record of their work. GitHub portfolios are unverifiable — anyone can fork code and claim authorship. Resumes are claims without proof. And when capital flows through a contract, the question “who built this, and what's their track record?” has no good answer.
Every contract deployed to a public chain is cryptographically tied to the wallet that signed for it. That binding is unforgeable. Signet turns that binding into a career record: every contract a developer has shipped, the activity it's seen, the outcomes it's had — aggregated into one verifiable profile.
The Identity Registry is deployed and initialized on Stellar testnet, and handle-to-wallet bindings are claimed on-chain: a wallet owner authorizes a claim(handle, wallet) call, and Soroban requires a valid signature from that wallet's key, so no off-chain admin can mint an identity. Profiles at /p/{handle} and the /handles directory read those bindings live from the registry. Nothing is curated or seeded: a handle appears only once it is actually bound on-chain.
Every contract a wallet deploys is recorded on-chain with the account that signed the deploy. When one of your linked wallets deployed a contract, Signet gives it a page under your handle, /p/{handle}/contract/{address}, with its interface, generated docs, a diagram and its activity. Asking for a contract under a handle that did not deploy it is a 404, so nobody can put your work under their name, or theirs under yours.Signet checks its indexer's record of deployments first. A deployment without an indexer walks the wallet's history on Horizon instead.What it does not do:It attributes direct deployments only, not contracts created by a factory contract on your behalf.Without an indexer, only the most recent 400 operations of a wallet are searched, so an older deployment is not found.Upgrade history starts when indexing began: an upgrade made before Signet saw the contract does not appear.
signet dev runs a deployed contract on your own machine: it forks the contract's ledger state from a Soroban RPC, builds your changed source, and replays saved and real transactions against both versions, then shows what changed: return values, events, storage, authorisation and cost.Nothing executes on Signet's servers. The CLI and the simulator run where you run them, and your source never leaves your machine. The guide is docs/SANDBOX.md.
Published CLI. The signet CLI is built and documented in docs/CLI.md: linking the deploy wallet you ship contracts from to your claimed handle, and signet dev. It is not on npm yet, so for now it is built from source. Linking is the step that turns a claimed handle into an indexed profile: a handle claimed with a browser wallet points at an address that has usually deployed nothing.Indexer service. The indexer is built but not yet running against this deployment's database. Running it keeps profiles current with deployments and invocations as they happen.Reputation primitives. Peer attestations, outcome tracking (TVL handled, incidents, bug bounty payouts), and integrations with audit firms, grant programs, and hiring tools.The SDK on npm. The public API (/api/v1, documented at /docs/api) and @signet/sdk exist today, so a wallet, a grant application form or an insurance protocol can query a developer's record. Publishing the SDK to npm is next.
Stellar's institutional and RWA positioning means real, regulated capital flows through Soroban contracts — MoneyGram, Franklin Templeton, Circle. On chains where serious money is at stake, the question of who built a contract isn't academic. Signet makes that question answerable.