SETTLEMENT

Abstract

Irium (IRM) is a mineable, settlement-first blockchain for escrow, agreements, and proof-based commerce. The live network already operates as an independent SHA-256d Proof-of-Work chain built from scratch in Rust with public mining, public explorer access, public pool infrastructure, and a fair-launch profile. Its broader direction is to extend that base layer toward trust-minimized commercial settlement built around objective rules, agreement anchoring, escrow-oriented outputs, timeout refunds, and proof-linked outcomes.

Implementation status: the base chain and infrastructure are live today; settlement primitives are in active development; objective proof automation and broader commercial tooling remain planned roadmap work.

1. Positioning

Most blockchains are framed primarily as payment systems. They move value from one address to another and treat the transfer itself as the finished job. Irium is being positioned around a narrower and more practical problem: how a public blockchain can support agreements, escrow, release conditions, refund logic, and objective settlement outcomes without turning consensus into subjective arbitration.

Core positioning:

  • Settlement-first blockchain rather than a generic transfer chain
  • Mineable and secured by public Proof-of-Work
  • Designed for escrow, agreements, and proof-based commerce
  • Rules-based and objective-only, not dependent on admin overrides

Preferred description: Irium (IRM) is a mineable, settlement-first blockchain for escrow, agreements, and proof-based commerce.

2. Why Payments Are Not Enough

Commercial coordination usually requires more than a transfer. OTC trades may need escrow release rules. Contractor payments may need milestone logic and holdbacks. Deposits and preorders may require refund handling and response windows. Business agreements may need defined proof paths and objective fallback outcomes if one side fails to perform or fails to respond.

A settlement-first blockchain is concerned with what happens before release, after timeout, at refund, or when a verifiable condition is met. That makes it different from a chain whose primary concern is only transferring units between addresses.

2.1 Example Use Cases

  • OTC escrow for safer peer-to-peer trading
  • Contractor and service payments with milestone-oriented release logic
  • Deposits and preorders with explicit refund paths
  • Milestone settlement for staged commercial payouts
  • Verifiable commercial agreements anchored to chain state

3. What Is Live Today

The current Irium network is already live as an independent SHA-256d Proof-of-Work blockchain. It is not a fork. It was built from scratch in Rust and launched with public mining rather than a private distribution model.

Live Base LayerStatus
Independent SHA-256d Proof-of-Work chainLive
Rust implementationLive
Public mining path and public poolLive
Explorer and mining calculatorLive
No premine, no ICO, no presale, no VC controlLive positioning / launch model
DNS-free bootstrap approachLive foundation
Resilient peer discovery and Sybil-resistant networkingLive foundation
Anchor checkpoints and light-client-oriented architectureLive foundation
On-chain metadata supportLive foundation

Mining remains important because miners secure the public base layer that the broader settlement narrative depends on.

4. Settlement Foundation In Development

The next layer of Irium’s direction is settlement infrastructure built on top of the live chain. This does not mean every settlement feature is already in production. It means the protocol and product direction are moving toward practical settlement primitives that remain compatible with objective-only consensus.

4.1 Active Direction

  • Agreement-hash anchoring
  • Native escrow / settlement output direction
  • Timeout refund logic
  • Basic commercial settlement primitives
  • Safer OTC escrow and simpler contractor/deposit flows

These items should be understood as in development unless explicitly described elsewhere as already live.

5. Objective-Only Consensus

Irium’s settlement direction depends on keeping consensus narrow, deterministic, and objective-only. The protocol should not become a general-purpose human dispute system. Subjective judgment, discretionary governance, and privileged override powers would conflict with the trust-minimized positioning the project is aiming for.

5.1 Public Principles

  • No admin keys
  • No override powers
  • No freeze or seizure mechanism
  • No centralized dispute authority in consensus
  • Rules-based, verifiable settlement paths only

Where signatures, attestors, proofs, or timeout behavior are used, they should remain explicit and technically verifiable rather than dependent on a privileged operator.

6. Roadmap Phases

Irium’s public messaging needs to distinguish clearly between what already exists, what is under active development, and what is still planned. The roadmap below follows that principle.

PhaseScopeStatus
Phase 1Core independent PoW foundation, Rust node, public explorer, public pool, calculator, fair-launch profile, resilient networkingLive
Phase 2Agreement anchoring, native escrow / settlement direction, timeout refunds, basic settlement primitivesIn Development
Phase 3Objective proof validation, approved attestors, no-response auto-settlement, milestone proofs and holdbacksPlanned
Phase 4Commercial templates, contractor and merchant flows, recurring invoice direction, reputation tooling, broader integration APIsPlanned

7. Closing Note

Irium is not abandoning mining, nor is it reducing the importance of the base chain. The point of the settlement-first positioning is to explain what that base layer is for. Mining secures the live public network. The broader settlement roadmap gives that network a clearer commercial purpose: trust-minimized outcomes, not just payments.