Building on KXCO Armature

Step-by-step

1. 1

   Know the network

   Armature is EVM-compatible with QBFT proof-of-authority consensus, ~2s deterministic finality, and negligible gas. The native token is ARMR.

   Network     KXCO Armature
   Chain ID    1111111  (0x10F447)
   Currency    ARMR
   RPC (HTTP)  https://chain.kxco.ai/rpc
   REST API    https://chain.kxco.ai/api
   Explorer    https://chain.kxco.ai

2. 2

   Verify you can reach it

   A single JSON-RPC call confirms connectivity and the chain ID before you write any code.

   curl -s -X POST https://chain.kxco.ai/rpc \
     -H "Content-Type: application/json" \
     -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
   # → {"jsonrpc":"2.0","id":1,"result":"0x10f447"}   (0x10f447 = 1111111)

3. 3

   Connect with viem (or ethers)

   Define the chain once and point any EVM library at the RPC with your credential. Reads work immediately.

   import { createPublicClient, http, defineChain } from 'viem'
   
   export const armature = defineChain({
     id: 1111111,
     name: 'KXCO Armature',
     nativeCurrency: { name: 'ARMR', symbol: 'ARMR', decimals: 18 },
     rpcUrls: { default: { http: ['https://chain.kxco.ai/rpc'] } },
   })
   
   const client = createPublicClient({ chain: armature, transport: http() })
   console.log(await client.getBlockNumber())

4. 4

   Get a funded account

   Reads through the explorer and its API are open to everyone; the RPC takes a credential, and writes require a funded account on the permissioned chain. Contact KXCO to be provisioned, the licensed operator running the platform handles any KYC/eligibility at the application layer, not at the chain layer.

5. 5

   Deploy a contract with Hardhat or Foundry

   Add Armature as a network and deploy as you would on any EVM chain. Gas is negligible but not zero, the EIP-1559 base fee is a few wei, so query eth_gasPrice rather than sending gasPrice:0.

   // hardhat.config.js
   module.exports = {
     solidity: '0.8.24',
     networks: {
       armature: {
         url: 'https://chain.kxco.ai/rpc',
         chainId: 1111111,
         accounts: [process.env.PRIVATE_KEY],
       },
     },
   }
   
   // foundry: forge create --rpc-url https://chain.kxco.ai/rpc \
   //   --private-key $PRIVATE_KEY src/HelloWorld.sol:HelloWorld

6. 6

   Add post-quantum signing (optional)

   EVM transactions are signed with secp256k1. To make an action post-quantum-verifiable, sign an ML-DSA-87 or ML-DSA-65 intent off-chain with kxco-post-quantum; the KXCO relay submits it and every validator verifies the post-quantum signature on chain, in consensus, before the result is recorded. See the Quantum section for the full cryptographic coverage.

   npm install kxco-post-quantum   # ML-DSA-87 / ML-DSA-65 / SLH-DSA / ML-KEM-1024 / ML-KEM-768

What you get on Armature

A standard EVM developer experience on a permissioned, post-quantum-secured settlement layer.

Frequently asked