Smart contracts
Contract architecture, deployment addresses, ABIs, and audits.
Architecture
Each asset is a standard token (such as ERC-20 or SPL) per network; launch networks will be announced ahead of launch. Issuance and operations run under role-based administration, with administrative powers and their holders documented per product at launch. A price oracle publishes reference prices onchain for transparency. Balances or reference values adjust to reflect corporate actions under the published per-product policy — integrators should read a product's corporate-action mechanics before building on the token.
Deployment addresses
Addresses for each token and network will be published here at launch — token contracts (one per asset, per network) and the oracle contract. This registry will be the only authoritative source of TokenForce contract addresses.
ABIs & interfaces
The tokens expose standard token interfaces (such as ERC-20), so wallets, indexers, and protocols can integrate without bespoke interfaces. Reference data — ISIN, listing venue, reference price — is available via the oracle and the documentation reference feed. Published ABIs and a functional specification accompany the address registry at launch.
Audits & security
Independent third-party smart-contract audits are completed before mainnet launch, with dated reports published on this page. The upgrade policy — what can change, who can change it, and with what delay — is documented alongside the contracts. A security contact for vulnerability reports is published here at launch; good-faith research is welcomed.