Asset Register Dev Portal
A wallet-gated companion to the Asset Register documentation. It hosts the seven tools you'll use most often when building on the Asset Register: namespace and schema creation, collection and asset management, webhook configuration, and SIWE token generation.
The portal lives at https://ar-docs.futureverse.app. All operations require a connected wallet — usually the wallet that owns the collection or schema you're about to operate on.
What is it
"Asset Register is a new ledger system that functions similarly to layer 2 distributed ledger technologies (DLTs). It has been designed with a primary focus on managing asset relationships. It brings a blockchain-like transaction experience but with off-chain DLT performance."
— ar-docs.futureverse.app
The dev portal is the operator-facing UI on top of this ledger. The conceptual reference for what's happening underneath is on the Asset Register introduction and Terminology pages.
Tools
- /namespace
- Create Namespace. A namespace groups schemas under a specific contextual domain (e.g.
fifa-world-cup-ai-league). You'll create one before registering schemas. - /schema
- Create Schemas. Define a specific asset or accessory and the linking relationships it can participate in. Schemas use SHACL shapes inside TTL files. See How to Schema for the underlying flow.
- /collections
- Manage Collections. View and manage collection schemas for the collections you own. Wallet-gated.
- /manage-assets
- Manage Assets. View and manage individual assets you own — links, metadata, schema bindings. Wallet-gated.
- /webhooks
- Manage Webhooks. Subscribe to Asset Register events and route them to your endpoint. The data model is described under Subscriptions.
- /siwe-generator
- SIWE Generator. Builds the Sign-In With Ethereum payload, prompts the wallet to sign, and outputs an
Authorization-header value you can paste into Postman/curl to call the admin endpoints. See Authentication for the auth model. - / (home)
- Tool index + portal home. Links to all the above plus external resources (GitHub, NPM, Rootscan, whitepaper).
Common workflow
- Connect wallet — the portal requires a wallet that owns the collections you'll act on.
- Generate a SIWE token at
/siwe-generatorand keep it in theAuthorizationheader for any admin calls (Postman, curl, etc.). - Create a namespace for your project at
/namespace. - Create schemas at
/schema, registering them under the namespace from step 3. - Bind a collection or token to a schema by visiting
/collections. The detailed flow is the Register Asset with Schema guide. - Configure webhooks at
/webhooksif you need event delivery to your service. - Operate on assets — issue ARTM transactions to update links. The library you'll use is
@futureverse/artm; the data structure is on the Asset Register Transaction page.
Related docs on this site
- Asset Register · Introduction — what the system is and why.
- Asset Register · How it works — concept-level explanation of links and trees.
- Asset Register · Authentication — SIWE for admin, wallet-signed transactions for asset updates.
- Asset Register · Asset Register Transaction — ARTM message format.
- Asset Register · Subscriptions — webhook payloads + acknowledgement protocol.
@futureverse/asset-register— core SDK that talks to the API.@futureverse/asset-register-react— React provider/hooks for the same.@futureverse/artm— ARTM codec.
API endpoints (production)
Production (Root + Ethereum mainnet): https://ar-api.futureverse.app/graphql
Staging (Porcini + Goerli): https://ar-api.futureverse.cloud/graphqlThese come from the Asset Register Getting Started page.