Protocol

Contract & status reference

Detailed status definitions, signing rules and published API capabilities.

Buying one stock and holding an index are different products

They differ in what you hold, who custodies it, and how you get out. The interface never blurs the two.

Difference	Buy it directlytoken in your wallet	Hold an indexvault shares
What you hold	The bStock token itself, at its own contract address.	ERC-20 shares of a vault that holds the basket.
Custody	Your wallet. Nothing of ours touches it after the swap.	A non-custodial contract. No platform wallet holds user assets.
How you exit	Sell it back through the same route, whenever a route exists.	Redeem in kind, pro rata: you receive the underlying tokens, not cash.
Issuer restrictions	Apply to you directly. A freeze stops your transfer.	Apply per leg. One restricted leg reverts the whole redemption.
Price you act on	An executable quote with a deadline and a minimum output.	A fixed-block preview. It is not a promise of execution.
Rebalancing	Yours to do. We hold no position and send no instruction.	Only through a reviewed recipe, under governance, within fixed limits.
Choose it when	You want one name, and you want the token in hand.	You want a theme in one position, with the weights checked by contract.

What stays the same in both

The asset is identified by chain id and address, never by symbol. The same evidence chain admitted it. The issuer can freeze or restrict either path, and neither promises you can exit.

What is open today

Execution depends on the path: index shares require a registered vault’s current chain-specific capability; direct buying requires an executable route and measured depth. Configured addresses, test evidence and production permission are separate.

Verification status

Source and code provenance. It says nothing about whether an asset may be used.

Testnet technical status · DISCOVERED	Imported as a candidate from an archived source. Nothing is confirmed yet.
Testnet technical status · SOURCE_REVIEW	The issuer document is under review.
Testnet technical status · ONCHAIN_VERIFIED	Onchain capability evidence was recorded at a fixed block.
Testnet technical status · VERIFIED	Source and onchain evidence were both reviewed and approved independently.
Testnet technical status · REVOKED	A previous approval was withdrawn. Treat this asset as unverified.

Operation permission

Whether an asset may be used, and in which direction. It is decided independently from verification.

Display only	May be displayed only. No new exposure and no fund use.
Active	Operation is permitted under the registry's current rules.
Exit only	No new exposure. Existing exposure may be exited.
Paused	Affected exits are disallowed as well. Expect operations to fail.
Revoked	Terminal. No new exposure; exit only if the token itself still permits transfer.

Why the two are separate

An asset can be fully source-verified and still be display-only, and a previously active asset can be paused without its evidence changing. Collapsing the two states into one badge would hide the difference between "we checked the issuer document" and "you may build a fund with this".

Capability status

The API answers 503 CAPABILITY_UNAVAILABLE for a capability that is not implemented. This interface shows that as unavailable. It never substitutes an empty list, a zero balance or a successful transaction.

Capability	Endpoint	State	Write signature
Asset registry directory	GET /v1/assets	Implemented	Read
Asset verification provenance	GET /v1/assets/{address}/verification	Implemented	Read
Archived official sources	GET /v1/assets/{address}/sources	Implemented	Read
Fixed-block token capability	GET /v1/assets/{address}/capabilities	Implemented	Read
Reference price publication	GET /v1/assets/{address}/pricing	ImplementedNeeds a licensed price feed; 503 until then	Read
Public address check	POST /v1/assets/verify	Implemented	Read
Wallet sign-in	POST /v1/auth/verify	Implemented	Read
Session and roles	GET /v1/auth/session	Implemented	Yes
Business write challenge	POST /v1/auth/operation-challenge	Implemented	Yes
Published strategy discovery	GET /v1/indexes	Implemented	Read
Strategy drafts	POST /v1/indexes	Implemented	Per-request signature
Strategy publication	POST /v1/indexes/{id}/publish	Implemented	Per-request signature
Read-only share link	GET /v1/indexes/by-slug/{slug}	Implemented	Read
Deterministic fact check	GET /v1/indexes/{id}/advisory	ImplementedNeeds a licensed price feed; 503 until then	Read
Historical backtest	GET /v1/indexes/{id}/backtest	ImplementedNeeds a licensed price feed; 503 until then	Read
Personal watchlist	GET /v1/me/watchlist	Implemented	Yes
Runtime chain and deployment capability	GET /v1/capabilities	Implemented	Read
Canonical testnet in-kind preview	GET /v1/funds/{id}/preview	ImplementedNeeds a deployed contract address	Read
Registered fund directory	GET /v1/funds	Implemented	Read
Fixed-block fund holdings	GET /v1/funds/{id}/holdings	ImplementedNeeds a canonical fixed-block snapshot; 503 until then	Read
Reference NAV	GET /v1/funds/{id}/nav	ImplementedNeeds a licensed price feed; 503 until then	Read
Sparse NAV history	GET /v1/funds/{id}/nav/history	ImplementedNeeds a licensed price feed; 503 until then	Read
Fund activity	GET /v1/funds/{id}/transactions	ImplementedNeeds a canonical fixed-block snapshot; 503 until then	Read
Wallet positions	GET /v1/portfolio	ImplementedNeeds a canonical fixed-block snapshot; 503 until then	Yes
Wallet activity	GET /v1/portfolio/transactions	ImplementedNeeds a canonical fixed-block snapshot; 503 until then	Yes
Transaction intents	POST /v1/transactions/intents	Implemented	Per-request signature
Asset review queue	GET /v1/admin/assets/pending	Implemented	Yes
Asset source review	POST /v1/admin/assets/{address}/review	Implemented	Per-request signature
Asset activation	POST /v1/admin/assets/{address}/activate	Implemented	Per-request signature
Restricted fund applications	POST /v1/fund-applications	Implemented	Per-request signature
Fund governance record	GET /v1/admin/funds/{id}/governance	Implemented	Yes
Legacy basket quote	GET /v1/quotes/basket	Not in contractNot declared in the contract; answers 503	Read
Basket buy quote	POST /v1/quotes/basket-buy	ImplementedNeeds an approved route provider; 503 by default, and a success is simulation only	Per-request signature
Basket sell quote	POST /v1/quotes/basket-sell	ImplementedNeeds an approved route provider; 503 by default, and a success is simulation only	Per-request signature
Vault deposit quote	POST /v1/quotes/vault-deposit	ImplementedNeeds an approved route provider; 503 by default, and a success is simulation only	Per-request signature
Vault redeem quote	POST /v1/quotes/vault-redeem	ImplementedNeeds an approved route provider; 503 by default, and a success is simulation only	Per-request signature

How a business write is authorized

A login session proves who you are; it does not authorize a change. Every write serializes its body once, hashes those exact bytes with SHA-256, asks the server for a one-time challenge bound to that method, path and hash, has the wallet sign the server's exact message, and then sends those same bytes with the nonce and signature. Changing one byte, the path or the method invalidates the signature.

A nonce that already succeeded cannot be reused, and the interface never silently creates the same record again. If a response is lost, the outcome is looked up by nonce before anything is retried.

What wallet sign-in means

Sign-in proves you control an address, using a message the server generated. It authorizes API calls for eight hours. It never authorizes a token transfer, an allowance or a fund operation, and it grants no reviewer or governor role.

How amounts are handled

Raw token quantities are integers, carried as BigInt or exact decimal strings. The interface performs no floating-point arithmetic on an amount, and it applies no multiplier until the contract publishes that multiplier's scale.

Risk and limits

No RPC endpoint configured

Onchain reads are disabled in this deployment. Wallet connection and sign-in still work, because they use your wallet's own provider.

Production transactions unavailable

Contract actions depend on the active chain’s deployment and launch gates. A configured testnet address does not enable production; check a fund page for its current testnet capability.

Mainnet production remains disabled. Testnet deployments and synthetic test assets do not satisfy production launch gates.
No price source, reference NAV or executable quote is published. A preview is never a quote promise.
Registry records imported from the seed are candidates. A candidate is not verified and is not tradable.
Tokenized stock issuers can restrict transfers. No interface here can guarantee that a restricted token can be exited.