Evaluation

Use this page to decide whether the model fits, and as the list you and Cantor8 work through to launch. The behavior behind each line is in the page linked from it.

​

Confirm the model

​

What you deploy

Token App’s production profile is 2 CPU and 10 GiB requested, 4 CPU and 16 GiB limited, one replica, PostgreSQL 14 at a small size. Deployment.

​

What “launched” means

The sequence is Launch. It is done when all of these are true:

• The factory, the freeze configuration, and the instrument exist, created by your acceptance.
• The treasury mint delegation exists, so batch mint and mint-to-treasury have a standing consent.
• The Registry’s public metadata API lists the instrument.
• The observer was named in that acceptance.
• Token App is ready on /healthz, as one replica, with authentication on.
• A mint to the treasury is visible in Token App’s mint history and in the supply gauge.
• A wallet-style transfer between two parties completes through the public Registry.
• A pause and an unpause have gone through Token App, on a test network or a test instrument.
• Alerts exist for the monitor timestamp, mint and burn errors, ledger errors, and, if markers are on, lag and failed batches.

​

Bring this to the first working session

• the asset: what it represents, the ticker you want, and the decimals
• the network: public mainnet, a test network first, or a private synchronizer, and who should operate the validator
• who will hold the controlling party, and whether mint, pause, and rewards must be separate parties
• whether holders transfer the instrument, or it moves only by mint and burn
• whether you want featured-app rewards
• the compliance actions you must be able to take, and who in your organization approves them
• the target date, and whether a test-network rehearsal is in that date

​

What comes back

The keys that can act stay with you. The offer is a command you submit.