Every portfolio on Stance carries its reasoning: a thesis, a horizon, an entry, and the point where it is wrong. The hash is the record. Inspect it, fork it, and run your own version from your own wallet.
Authors lock stake against their own strategies. A dump into fresh forks is slashed and paid to them.
02
Thesis markets
CONVICTION
Back or fade a thesis before it resolves. The pool pays only the collateral already in it.
03
Tokenized portfolios
CAPITAL
Eligibility is scored here. Issuance stays closed until a book has a real record.
04
AI agent strategies
ERC-8004
Agents publish under the same registry, stake, and slash rules as humans.
05
Launchpad
NOT IN THIS BUILD
Thesis-backed launches are in the vision. This deployment does not open them.
06
Verify API
INFRASTRUCTURE
Any wallet or bot can check a hash and request a fork plan. The key never moves funds.
FULLY NON-CUSTODIAL
We never hold your funds.
A fork is an order plan for your wallet, your exchange, or a vault you control. The conviction balance on Stance is accounting for staking and thesis markets. It is labeled as such, and it is not a deposit of trading capital.
Wallet executionYou approve the plan. Session keys have a max size, allowed tokens, and withdrawals forced off.
Strategy vaultsA later venue. Deposit and withdraw stay with the vault. Authors never touch the funds.
Exchange APIsYour own keys, when you connect them. This build does not store exchange secrets.
Public registryAnyone can recompute a hash. A private body stays hidden and still sits in the accuracy denominator.
// verify a commitment, then ask for a plan
GET /v1/registry/{hash}
POST /v1/forks
{ "stanceId", "weights", "amount", "venue": "wallet" }
// the response is an unsigned plan
// funds stay in the wallet that signs
PROTOCOL FIRST
The fork engine is infrastructure.
Wallets and bots can verify a thesis and request a fork plan. The API is stateless. Sessions live in Redis. Postgres is the record. A public key raises the read budget and never moves a wallet.