Arxium

How Arxium works

Asset rules run inside the chain’s execution, finality is signed by stake, and every claim the network makes comes with something you can check.

Block time
2 s
Finality
BFT, 2/3 of stake
Devnet validators
4
Smart contracts
Not yet

Life of a transfer

Five steps from your key to a final block.

  1. 1

    Sign locally

    Your key signs the action on your machine, bound to this chain's genesis hash.

  2. 2

    Submit

    The signed action goes to a node's RPC, through the gateway and your API key.

  3. 3

    Include

    The proposer whose turn it is puts it in the next block, every two seconds.

  4. 4

    Execute

    Every validator runs the same rules. A transfer that breaks them is dropped, with the reason recorded.

  5. 5

    Finalize

    Validators holding two thirds of stake sign the block. It can't be reversed after that.

The network, by the numbers

Devnet values. They change if the network does.

2 s
Block time
Blocks are produced on a fixed interval.
2/3
Of stake to finalize
A block is final once validators holding two thirds sign it.
4
Devnet validators
Finality keeps going with one validator down.
12 h
Dispute window
A dissenting validator can challenge a block's result before it settles.
1
Proposer per height
Rotating and known in advance, so a missed slot is provable.
ed25519
Signatures
Bound to the genesis hash so they can't be replayed elsewhere.

What the protocol gives you

  • Protocol compliance

    Eligibility, holder limits and jurisdiction rules belong to the asset. The chain refuses any transfer that breaks them.

  • Proof of execution

    Every validator's execution is attributable. A disagreement produces evidence anyone can verify, and the faulty validator is slashed.

  • Secure by design

    Modern cryptography and decentralized validation at the protocol level.

  • Private eligibility

    Holders prove they meet an asset's rules with zero-knowledge proofs. Their claims and country stay off the public record.

  • Room to grow

    One chain today. Issuers who need their own execution environment can get one when they ask for it.

Accounts with rules

A fixed menu enforced by the chain. There is no custom code to write or exploit.

Shared control
A multisig account needs a threshold of up to 16 keys to sign, checked on the chain.
Spending limits
Cap how much of an asset an account can send in a period of blocks.
Recipient allowlists
Restrict an account to a fixed list of addresses it may pay.
Key rotation
Change the owners without changing the address, balances or identity.

Identity without exposure

  • An attestor you trust verifies a person off-chain and records claims: KYC, AML, accredited investor and a country code.
  • The chain stores the claims and an opaque reference, never the documents.
  • Anyone can re-check an account's claims with a state proof, and a new grant replaces the old one completely.
  • Zero-knowledge proofs for private claims exist on devnet, with test-only keys.