Genesis and token supply model.

Launch review must make the initial chain facts explicit before deploy. The BaaS record stores the customer-visible profile even when the underlying generator or attached bundle owns the concrete genesis file.

Profile fields

chain_idHuman-readable chain identity used in BaaS records and launch review.

token_symbolNative token ticker shown to operators and integrators.

token_nameDisplay name for the native token.

token_decimalsDecimal precision for client-facing balances.

initial_supplyTotal initial allocation in base units. Must be an integer string from 1 to 9223372036854775807.

treasury_addressClient-controlled public treasury address.

genesis_hashSHA-256 hash of the generated or attached genesis.json when available.

Create network payload

POST /v1/networks
Authorization: Bearer <token>
Content-Type: application/json

{
  "name": "partner-testnet",
  "plan": "resilient_7",
  "environment": "testnet",
  "deployment_target": "local_fs",
  "consensus_mode": "private",
  "chain_id": "nabd-partner-testnet",
  "token_symbol": "NABD",
  "token_name": "NABD Token",
  "token_decimals": 6,
  "initial_supply": "5000000000000",
  "treasury_address": "NABD_TREASURY_001"
}

Integer bounds

On-chain balances, fees, and token supply use integer base units. The BaaS rejects decimals, separators, negative values, and values above signed 64-bit storage capacity: 9223372036854775807.

Genesis hash

For local bundles, the worker computes a SHA-256 hash of genesis.jsonafter provision/start/stop/destroy lifecycle jobs. A pending hash means the bundle has not been generated or attached yet.

Supply and treasury are product facts. Genesis hash is the deployment artifact fact. A launch is not review-complete until both sides are visible or explicitly pending.