Materios is a Substrate-based Cardano partner chain that provides high-throughput certified data anchoring. A decentralized committee of attestors verifies data receipts via threshold signatures, and the certified receipts are then batched into Cardano mainnet transactions under metadata label 8746 for permanent settlement.

How does certification work?

Data submissions are certified by a committee of 10 attestors using a 2-of-10 threshold signature. Certification takes approximately 12 seconds end-to-end. Certified receipts are periodically batched and anchored to Cardano mainnet, giving applications sub-15-second receipt finality plus Cardano L1 settlement guarantees.

What is the dual token model?

Materios uses two tokens: tMATRA for staking and governance, and tMOTRA which is auto-generated from your tMATRA balance and used for transaction fees. No separate faucet is needed for fee tokens — holding tMATRA automatically accrues the tMOTRA you need to transact.

How do I run an attestor?

Attestor registration is permissionless. Use the Materios Operator Kit for one-command installation and updates, or follow the operator guide in the documentation. There is no allowlist — any operator with sufficient stake can join the attestor committee.

What can I anchor to Materios?

Any hash-committable data: AI inference traces and audit trails, IoT sensor streams, supply-chain events, document checksums, off-chain database snapshots, witness uptime probes, ML model checkpoints, or business-process attestations. Materios stores only cryptographic hashes and pointers on-chain — raw payloads remain in your storage of choice.

How does Materios compare to Cardano L1 directly?

Cardano L1 offers ~20-second block time and ~0.2–0.3 ADA per anchor — excellent for low-frequency permanent settlement. Materios is a partner chain optimized for high-throughput certified receipts: thousands of anchors per second at sub-15-second certification finality, then hourly batched into Cardano L1 under metadata label 8746. Same Cardano settlement guarantees, much higher throughput and lower per-receipt cost.

What is the Materios committee?

The Materios committee is a decentralized set of 10 attestors that produce threshold signatures on data receipts. A 2-of-10 threshold is sufficient to certify a receipt, so the network tolerates attestor downtime and Byzantine behavior. The committee rotates based on stake-weighted selection and is permissionlessly joinable — no Flux Point Studios approval required.

How do I run a Materios attestor?

Install the Materios Operator Kit on a Linux server (one command), provision tMATRA stake, and register your attestor key on-chain. The Operator Kit handles validator + attestor node lifecycle, automated updates, and key rotation. Full hardware specs and the step-by-step guide are in the operator documentation linked from the Materios docs portal.

FLUX POINT STUDIOS Contact

Testnet live · 10-of-10 attestors

Receipts for
what your
system saw.

Most data claims live in a database the claimant controls. Materios is a Cardano partner chain that certifies receipts with a decentralized committee — 10 attestors, 2-of-10 threshold, ~12s latency — then anchors the Merkle root to Cardano L1. “This happened” becomes a proof anyone can replay.

Try the testnet Read the docs

MATERIOS

Block time

6 seconds

Validators

-- live

Attestors

-- committee

Cert latency

~12 seconds

First principles

Why receipts beat databases.

Three structural failures in trusting a single party with your most important data. Materios fixes each.

No single party decides "what happened."

Database rows are written by whoever runs the database. Materios certifies every receipt with a 2-of-10 threshold across an independent attestor committee — no operator can rewrite history alone.

Cryptographic provenance, not screenshots.

Status pages, exports, and "trust us" dashboards are unfalsifiable assertions. Every certified receipt carries committee signatures; the Merkle root anchors to Cardano mainnet under metadata label 8746 — replayable by anyone.

Open by default.

Attestor registration is permissionless. Operator kit, SDK, schemas, and chain code are open source. Inspect, audit, run a node — no API key, no approval process, no gatekeeper.

Receipt chain

How certification works.

Three steps from submission to L1. Every output is signed, verifiable, and recoverable without trusting us.

Submit

Sign a receipt with your sr25519 key and post it to a Materios validator. No API key, no approval — authentication is the signature. Per-target schemas reject malformed or implausible payloads before they hit the committee.

Certify

The 10-attestor committee reviews the receipt; once 2 (or more) attestors sign, the receipt is certified on-chain. Cert latency lands in ~12 seconds. Divergent attestations create disputes; honest attestors keep rewards, dishonest ones get slashed.

Anchor

Certified receipts batch into a Merkle tree; the root commits to Cardano mainnet under metadata label 8746 every hour. Anyone can replay the inclusion proof against a Cardano explorer to confirm the receipt is real.

What you can anchor

One receipt chain. Many surfaces.

The chain doesn't care what you certify. Game state, AI traces, uptime probes — all certified by the same committee, all anchored to the same L1.

Live

Game state

Player scores, achievements, item drops, leaderboard tops. Drop-rate disputes vanish when every drop is an on-chain receipt with a signature trail to L1.

Orynq

AI inference traces

Anchor model outputs, prompts, and tool-call traces to Materios via the Orynq SDK. Pay-per-call inference with a cryptographic audit log instead of vendor logs you have to trust.

Witness

Uptime probes

TEE-attested probes from real phones around the world, signed in hardware and certified by the committee. Powers the Materios Witness Network.

Q3 2026

Audit logs

Compliance trails for content moderation, takedown evidence, KYC flow events. A schema-validated, time-ordered, third-party-attested record nobody can quietly edit.

Q4 2026

Settlement receipts

Payment confirmations, royalty splits, in-game purchase receipts. Cardano L1 anchoring gives every settlement a cryptographic backstop without paying L1 per-tx costs.

Open schema

Anything schema-validated

Register your own on-chain schema. Submissions that pass validation get certified by the same committee that handles game state, AI traces, and uptime probes.

Interactive Onboarding

Try the Testnet

Get started in four steps. No wallet software needed — everything happens right here in your browser.

Create Wallet

Get tMATRA

Try It

Explore

Step 1: Create Wallet

Generate a keypair to interact with the Materios testnet. Keys are created locally in your browser — nothing is sent to any server.

Step 2: Get tMATRA

Request testnet tokens from the faucet. tMOTRA (fee tokens) are auto-generated from your tMATRA balance — no separate faucet needed.

Generate a keypair first

Step 3: Try It

Test real blockchain transactions with your funded wallet. Try both demos below!

Step 4: Explore

Your wallet is funded. Now explore the chain, run an attestor, or integrate your game.

Chain Explorer

Live chain stats, committee health, and receipt lookup

Run an Attestor

Join the certification committee

Integrate a Game

Submit certified data from your game

View on Cardano

See anchored batches on L1 (label 8746)

Architecture

Purpose-built for verifiable receipts.

Every design decision points at the same thing: Cardano-anchored, committee-certified, anyone-can-replay receipts.

Threshold certification

10-member attestor committee; 2-of-10 threshold; ~12-second cert latency. Cryptographic proof of committee agreement on every receipt.

Cardano L1 anchoring

Merkle roots of certified batches commit to Cardano mainnet metadata under label 8746 every hour. Permanent, replayable, no trust required.

Dual token economy

tMATRA stakes and governs. tMOTRA pays fees and auto-generates from your tMATRA balance — no separate faucet, no second token to acquire.

Permissionless attestors

No API keys, no approval process. Authenticate with an sr25519 signature; register an attestor with the stake requirement and the operator kit.

On-chain schema validation

Per-target schemas registered on-chain reject malformed or implausible payloads before they hit the committee. Content validation enforced at submission.