Key concepts

These are the only ideas you need to use Taliware. Each one links to where it shows up.

Organization

A workspace for one product or company. It holds that product's API keys, team members, users, contracts, and assets, and keeps them completely separate from your other organizations.

Example: a startup with a photo app and a ticketing app would create two organizations.

Team member

Someone on your side who helps run the organization. Owners control billing and settings; developers can build and manage resources. Team members sign in to this dashboard.

User

One of your customers — a person who owns or approves digital assets. Users don't sign in to this dashboard; they use the Confida app on their phone. In the API, they're managed under /cl2c/user.

API key

A secret code your software sends with every request so Taliware knows which organization is asking. Treat it like a password:

Keep it on your server (in an environment variable), never in a website or mobile app.
Make separate keys for testing and production, and name them clearly.
If one leaks, delete it in API keys and create a new one.

Every request sends it in a header: x-api-key: <your key>.

The on-chain "home" your assets are issued from — think of it as a collection or a ledger that belongs to your organization. You create it once, deploy it (publish it to the blockchain), and then issue as many assets from it as you like.

Digital asset (NFT)

A single registered item: a photo, document, artwork, or certificate, along with its name, description, and owners. Technically it's an NFT, but you don't need to know that to use it.

An asset can have several owners, each with a percentage share. Shares must add up to 100%.

Asset status	What it means
`CREATED`	Registered. Waiting for every owner to approve.
`MINTED`	Every owner approved, and it's recorded on the blockchain.
`FAILED`	Something went wrong. Check the asset details or contact us.

Each owner also has their own approval status: PENDING until they respond, then CONFIRMED (approved), REJECTED, or EXPIRED.

Owner approval (Confida)

When you issue an asset, each owner gets a request in the Confida mobile app and approves it with a fingerprint or face scan. Only after every owner approves is the asset recorded on-chain. This is what makes the ownership record trustworthy. See Confida mobile app.

CRDB credits

Writing to a blockchain has a small cost. CRDB credits cover it, so you never deal with cryptocurrency directly.

Test CRDB (also called faucet) — free, for building and testing.
Live CRDB (also called mainnet) — paid, for real production use.

See CRDB tokens for prices and how to get them.

Test vs. live

Everything has a test version and a live version. Build and experiment on test (the testnet): it's free and nothing is permanent. Switch to live (the mainnet) when you launch. A contract's env field — TESTNET or MAINNET — decides which one it uses.

Managed vs. self-service

Every organization is in one of two modes. It decides who pays for blockchain activity.

	Managed	Self-service
Who pays	The organization owner, for everyone	Each user pays for their own
Good for	Most companies — you control the experience	Approved partners whose users manage their own credits
How to get it	The default	Request it in Settings; Taliware approves it

Certificate of authenticity

Every asset has a printable certificate that lists its owners and its blockchain record. Anyone with the link can check it's genuine. See Certificates of authenticity.