Skip to main content
Ankara Chain is open-source infrastructure for tokenizing real-world assets (RWAs) on-chain. Think of it as the Stripe for RWA tokenization in Africa — plug it into your existing Node.js or React app the same way you’d plug in a payments library, deploy pre-audited contracts under your own keys, and keep full control of your business logic. Whether you’re building a fractional farmland platform in Nigeria, a commodity receipt market in Ghana, or a diaspora investment product connecting Nairobi to London, Ankara Chain gives you the contract infrastructure so you can focus on your product.

EVM Quickstart

Deploy your first token on Polygon Amoy testnet in under 30 minutes — no Solidity required.

Stellar Quickstart

Deploy on Stellar Soroban testnet using the same SDK API as EVM chains.

Asset Templates

Six pre-audited asset classes: farmland, commodity, real estate, invoice, carbon credit, mining rights.

CLI Reference

The ankara CLI scaffolds projects, deploys contracts, and mints tokens from your terminal.

​
Architecture

Ankara Chain sits between raw blockchain protocols and your product. You own the business layer — Ankara Chain provides the contract infrastructure and the TypeScript SDK that wraps it. The contracts deploy to your chosen network under your deployer key — Ankara Chain never holds custody of your assets or your infrastructure. The SDK’s TokenFactory class is the primary entry point: it accepts an ethers.js Signer (EVM) or a Stellar secret key / Freighter wallet (Stellar), and exposes a unified deployFarmland(), deployCommodity(), deployRealEstate(), and similar methods regardless of which chain you target.

​
Why Ankara Chain?

Import @ankarachain/sdk into your existing Node.js or React app. There is no platform dependency, no managed service, and no vendor dashboard you must use. The contracts are yours — deployed to your chosen network under your deployer key. You can eject from the SDK entirely and interact with the deployed contracts directly via ethers.js or the Stellar SDK if you ever need to.
Asset schemas are designed around the realities of African markets: farmland parcels with GPS coordinates and soil classifications, commodity receipts tied to specific warehouses and inspection reports, mining rights linked to license numbers and concession areas. Identity hooks support BVN, NIN, Huduma Namba, and Ghana Card natively — not retrofitted from European KYC standards. Supported countries include Nigeria, Ghana, Kenya, and South Africa.
Ankara Chain provides the IIdentityVerifier interface and plugs it into the transfer layer of every deployed token. You decide which KYC provider backs it — Smile Identity, Persona, your own internal verification service, or nothing at all for permissionless deployments. Swapping your KYC provider never requires redeploying core contracts, because the verifier address is a configurable parameter, not compiled into the token logic.
The smart contracts and TypeScript SDK are MIT licensed. There is no proprietary runtime between your app and the chain. The optional dashboard is self-hosted, so you control infrastructure and keys end-to-end. The open-core model means you get the benefits of a maintained, audited library without any of the lock-in of a SaaS tokenization platform.

​
SDK Modules

Every module ships as part of the @ankarachain/sdk package and is MIT licensed unless noted.

​
Supported Chains

Testnet support is available for Polygon Amoy (polygon-amoy) and Stellar Testnet (stellar-testnet). Use these for development and staging before deploying to mainnet. The CLI defaults to polygon-amoy when you run ankara init.

​
License

Core SDK and smart contracts are MIT licensed. Built by PIE Drops Studio.