🔹 AbstractUltraDAG is a production-ready Layer 1 blockchain purpose-built for autonomous machine-to-machine micropayments. While legacy "IoT blockchains" struggle with unbounded storage, slow finality, or oversized binaries, UltraDAG delivers:
- Bounded storage: Automatic pruning keeps only the last 500 rounds — memory usage stays constant after sync
- Predictable finality: BFT consensus achieves finality in 3 rounds (~5-15 seconds), no coordinator required
- Minimal footprint: <2 MB release binary, ~2,800 LOC consensus core — runs on ESP32, Raspberry Pi Zero, industrial sensors
- Leaderless parallel throughput: All validators produce vertices in parallel; 3-4x throughput vs single-leader chains
- Bitcoin-style tokenomics: 21M max supply, halving every ~1.66 years, 100% emission-based distribution, zero pre-mine
Closed Mainnet is live today. Public open mainnet coming soon.
🔹 Closed Mainnet StatusUltraDAG mainnet is
live but closed — meaning the network is running with real consensus, real finality, and real token emission, but access is currently limited to:
- Council of 21 governance members
- Selected validator partners
- Early ecosystem contributors
Why closed? We are conducting final stress tests, security audits, and edge-case validation before opening to the public. If critical issues are discovered, we reserve the right to restart the network with fixes — ensuring a stable, secure launch for all users.
What this means for you:
- ✅ The protocol is real — not a testnet simulation
- ✅ Token emission and staking mechanics are active
- ⚠️ Public node operation and token transfers are not yet enabled
- ⚠️ Closed mainnet balances may not carry over to open mainnet if a restart occurs
Join the mailing list to be notified the moment open mainnet launches.
🔹 The Problem: Why Existing "IoT Chains" Fail on Real Devices| Chain | The Problem for Embedded Devices |
| IOTA | Delayed/unpredictable finality; coordinator still centralized; unbounded storage growth |
| Helium | LoRa-only network; cannot handle general-purpose micropayments between arbitrary devices |
| IoTeX | 15s+ block times; 100+ MB binary; higher fees make micro-transactions impractical |
| Ethereum L2s | Require bridges, smart contracts, gas estimation — too complex for embedded firmware |
| Byteball | Unbounded DAG growth; impossible for devices with limited flash/RAM |
UltraDAG's answer: A minimal, formally verified DAG-BFT protocol that runs
today on resource-constrained hardware.
🔹 Technical Specifications- Consensus: DAG-BFT with 3-round finality (~5-15 seconds)
- Binary size: <2 MB release build (x86_64, ARM64)
- Storage: Bounded to last 500 rounds (~100 MB after sync); automatic pruning
- Cryptography: Ed25519 signatures + blake3 hashing; on-chain verification: blake3(pubkey) == address
- Throughput: Leaderless parallel vertex production; scales linearly with validator count
- Sync: Fast-sync via BFT-signed checkpoints; new nodes sync in minutes, not hours
- Formal verification: Consensus safety proven via TLA+ and TLC model checker across 32.6M states; six invariants verified with zero violations
- Governance: On-chain Council of 21 seats; 10% quorum, 66% supermajority, execution delay for safety
// Example: Fetch closed mainnet status (authorized access only)
const res = await fetch("https://ultradag-node-1.fly.dev/status");
const status = await res.json();
console.log("Finalized round:", status.last_finalized_round);
console.log("Lag:", status.dag_round - status.last_finalized_round);
🔹 Tokenomics: Bitcoin-Style, Zero Pre-Mine- Max supply: 21,000,000 UDAG (fixed, no inflation beyond emission)
- Emission: 1 UDAG per round to validators & stakers (75%), DAO treasury (10%), Council (10%), founder (5%)
- Halving: Every 10.5M rounds (~1.66 years)
- Pre-mine: ZERO — no genesis allocation, no VC tokens, no presale
- Staking: Min 2,000 UDAG to validate; min 100 UDAG to delegate; ~2.8h unstake cooldown
- Slashing: Deflationary penalties for Byzantine behavior (equivocation, double-signing)
All emission shares are governable — the Council can adjust percentages via on-chain proposals.
🔹 Real-World Use Case: Sensor-to-Sensor MicropaymentsScenario: A weather sensor sells temperature data to an autonomous drone for navigation.
# Weather sensor (Node A) sells data to drone (Node B)
sensor-a $ ultradag-node send \
--to b7f3a1...drone-node-b \
--amount 0.001 \
--memo "temp:22.4C hum:61% pres:1013hPa"
tx: 9a2f08...c4e1 broadcast to 4 peers
included in vertex round 14,209 (0.8s)
finalized at round 14,211 (6.2s) ✓
Result: Payment confirmed in <10 seconds. Fee: 0.0001 UDAG. No human intervention required.
🔹 Run a Node (Closed Mainnet Access)Note: Node operation on closed mainnet requires authorization from the Council. Public node deployment will be enabled at open mainnet launch.
For authorized partners — Linux:
# Download and extract
curl -L https://github.com/UltraDAGcom/core/releases/download/latest/ultradag-node-linux-x86_64.tar.gz | tar xz
# Start validating (requires authorized key)
./ultradag-node-linux-x86_64 --port 9333 --validate --pkey YOUR_AUTHORIZED_KEY
# Check node status
curl http://localhost:10333/status
Public documentation: Full setup guides will be published at open mainnet:
ultradag.com/docs
🔹 Governance: Council of 21UltraDAG is governed by an on-chain
Council of 21 members — a decentralized, expertise-based governance body that replaces hard forks with automated protocol upgrades.
- Six expertise categories: Cryptography, distributed systems, economics, security, embedded systems, and protocol design
- One vote per seat: No stake requirement — seats are earned through demonstrated expertise and community trust
- Safety mechanisms: 10% quorum (3 members), 66% supermajority for passage, execution delay for emergency intervention
- On-chain execution: Approved proposals apply automatically — no coordination calls, no forced upgrades
- Transparent deliberation: All proposals, debates, and votes are recorded on-chain
The Council controls the DAO treasury (10% of emission) and can adjust emission percentages, protocol parameters, and upgrade schedules through governed proposals. This ensures UltraDAG evolves without centralization or contentious hard forks.
🔹 Join the Community
🔹 FAQQ: What is "Closed Mainnet"?- Closed mainnet means the network is live with real consensus and token emission, but access is limited to authorized participants. This allows final validation before public launch. If critical issues are found, we may restart the network — balances from closed mainnet may not carry over.
Q: When does open mainnet launch?- Timeline TBD. We will announce the exact date via our mailing list, Telegram, and Twitter once security audits and stress tests are complete. Join the mailing list at https://ultradag.com for instant notification.
Q: Is UDAG an ERC-20 token?- No — UDAG is the native token of the UltraDAG L1. An EVM bridge (UDAG ↔ ERC-20) is planned post-open-mainnet to enable DeFi composability.
Q: How is UltraDAG different from IOTA?- Three key differences: (1) Predictable 3-round BFT finality vs IOTA's coordinator-dependent model; (2) Bounded storage with automatic pruning vs IOTA's unbounded growth; (3) <2 MB binary vs IOTA's larger footprint.
Q: Can I run a validator on a Raspberry Pi?- Yes — the <2 MB binary and ~100 MB bounded storage are designed for devices like Raspberry Pi Zero, ESP32, and industrial sensors. Public validator access will be enabled at open mainnet.
Q: Will closed mainnet balances carry over to open mainnet?- Not guaranteed. If a network restart is required to fix critical issues, closed mainnet state may be reset. Only balances from open mainnet onward will be considered final. Join the mailing list for official updates.
⚠️ DisclaimerUltraDAG is a technology project. UDAG coins are utility tokens for network participation (staking, fees, governance). This announcement is for informational purposes only and does not constitute financial, legal, or investment advice. Cryptocurrency investments carry significant risk. Please conduct your own research and consult qualified professionals before participating. Token sales may be restricted in certain jurisdictions. Closed mainnet participation does not guarantee open mainnet allocation.Closed Mainnet Live • Open Mainnet: Coming Soon
👉 Join the Mailing List for Open Mainnet Launch Alert
Telegram • Twitter • GitHub