Platform

Overview

How It Works

Beneficiary Identity

Policy Corridors

Deterministic Finality

Architecture

Security Model

Governance

Integration

Solutions

Corridors Overview

Institutional Overview

Pricing

All Scenarios

Humanitarian Impact Fund

Assurance

Technical Assurance

Verify Receipt

Receipt Example

Developers

Documentation

APIs & Bridges

Architecture Docs

Glossary

BID API

Company

About

Team

Partners

Roadmap

Investors

Contact

Blog

All Documentation

Schedule Consultation
← Back to Documentation
Specification v1.0 All Documentation →

Token Factory Specification

Zero-code token creation with configurable supply, distribution rules, and compliance corridors.

Specification JIL Sovereign February 2026

1. Overview

The JIL Token Factory enables institutions and projects to create custom tokens on the JIL network without writing smart contract code. Tokens inherit JIL's settlement integrity layer, identity binding, and compliance enforcement by default.

Every token created through the factory is automatically:

Identity-Bound

Linked to the creator's verified identity. Token issuance is traceable and attributable.

Compliance-Enforced

Transfers respect jurisdiction corridors, sanctions lists, and configurable policy rules.

Settlement-Integrated

Tokens settle through JIL's validator network with cryptographic finality receipts.

Audit-Ready

Full provenance trail from creation through every transfer, stored on-chain with timestamps.

2. Token Configuration

The following parameters are available during token creation:

Parameter Type Required Description
name string Required Token display name (max 64 characters)
symbol string Required Token ticker symbol (3-8 characters, uppercase)
decimals uint8 Optional Decimal precision (default: 18, range: 0-18)
totalSupply uint256 Required Fixed total supply minted at creation
mintable boolean Optional Whether additional tokens can be minted post-creation (default: false)
burnable boolean Optional Whether holders can burn their tokens (default: true)
transferRestrictions object Optional Jurisdiction corridors, whitelist mode, or open transfer
vestingSchedule object[] Optional Array of vesting tranches with cliff, duration, and beneficiary
complianceCorridor string[] Optional Allowed jurisdiction codes for transfers (e.g., ["US", "EU", "SG"])

3. Creation Flow

  1. Configure Token - Set name, symbol, supply, and optional parameters through the Token Factory UI or API.
  2. Identity Verification - Creator's wallet identity is verified against on-chain binding. Only verified wallets can create tokens.
  3. Policy Validation - The compliance engine validates the token configuration against jurisdiction requirements and platform rules.
  4. Token Deployment - The token contract is deployed to the JIL ledger with the specified parameters. A unique token ID is assigned.
  5. Initial Distribution - Total supply is minted to the creator's wallet. If vesting schedules are configured, vesting contracts are deployed automatically.
  6. Finality Receipt - A creation receipt is generated with validator signatures, recording the token's genesis on-chain.

4. Distribution Options

4.1 Direct Distribution

The creator manually transfers tokens to recipients. Each transfer goes through JIL's settlement flow with beneficiary verification and compliance checks.

4.2 Liquidity Bootstrapping Pool (LBP)

Tokens can be listed on JIL's DEX through a Liquidity Bootstrapping Pool. The LBP uses a declining price curve that starts high and decreases over time, enabling fair price discovery. See the LBP documentation for details.

4.3 Vesting Contracts

Configure automatic token release schedules with cliff periods and linear vesting. Vesting contracts are deployed alongside the token and enforce release schedules on-chain.

Vesting Parameter Description Default
cliff Time before any tokens unlock (seconds) 0
duration Total vesting period after cliff (seconds) Required if vesting enabled
beneficiary Wallet address receiving vested tokens Required
amount Number of tokens in this vesting tranche Required

5. Compliance Corridors

Token creators can restrict transfers to specific jurisdiction corridors. When a corridor is configured, all transfers are validated against the sender and recipient's jurisdiction before settlement proceeds.

Open Transfer

No jurisdiction restrictions. Tokens can be transferred between any verified wallets globally. Default mode.

Corridor-Restricted

Transfers limited to wallets in specified jurisdictions. Useful for securities tokens or region-specific utility tokens.

Whitelist Mode

Only pre-approved wallet addresses can receive tokens. Maximum control for private placements or internal tokens.

6. API Reference

6.1 Create Token

POST /v1/tokens/create
Content-Type: application/json
Authorization: Bearer {jwt}

{
  "name": "Example Token",
  "symbol": "EXT",
  "decimals": 18,
  "totalSupply": "1000000000000000000000000",
  "burnable": true,
  "mintable": false,
  "complianceCorridor": ["US", "EU", "SG", "CH"]
}

6.2 Get Token Info

GET /v1/tokens/{tokenId}
Authorization: Bearer {jwt}

Response:
{
  "tokenId": "tok_abc123",
  "name": "Example Token",
  "symbol": "EXT",
  "totalSupply": "1000000000000000000000000",
  "creator": "0x7Bcf...aBa2",
  "createdAt": "2026-02-24T12:00:00Z",
  "status": "active"
}

6.3 Transfer Token

POST /v1/tokens/{tokenId}/transfer
Content-Type: application/json
Authorization: Bearer {jwt}

{
  "to": "0x1234...5678",
  "amount": "1000000000000000000"
}

7. Limits and Constraints

Constraint Value
Max tokens per creator 100
Max symbol length 8 characters
Max name length 64 characters
Decimal range 0-18
Max vesting tranches 50 per token
Max compliance corridors All supported jurisdictions
Token creation fee 10 JIL (burned)