[ANN][RATR] Ratatoskr Core — Yespower CPU Mining, Masternodes, ALPH Bridge

[NexusAether]

RATATOSKR CORE (RATR)
A masternode chain that remembers what made these networks matter

Mainnet live since 2026-06-01 00:00 UTC

✅ Network healthy. The brief ChainLock pause on July 5 is resolved. New node or miner? Grab the latest release. If you run a node or masternode and yours got stuck or PoSe-banned, the full self-check + fix + post-mortem is here → July 5 Network Update


Quick facts

• Symbol: RATR
• Algorithm: Yespower (N=2048, R=32) — CPU mining, ASIC-resistant
• Block time: 60 seconds
• Block reward: 50 RATR at launch (halving to zero, Bitcoin-style schedule)
• Reward split: 60% miner / 30% masternode / 10% treasury post-block-25,000 (90/0/10 in PoW-only window before MN activation), governance-adjustable via SPORK_25 within 20-40% MN bounds
• Masternode collateral: 7,500 RATR (1× vote weight)
• EvoNode collateral: 30,000 RATR (4× vote weight, post-v1.1)
• Total supply: 100,000,000 RATR hard cap, no tail emission
• Premine: None
• Insider allocation: None
• Founder allocation: None (10-block founder phase mined ~T-7 for chain-seeding utility; ~450 RATR, transparent + auditable post-launch)
• Treasury accumulation: on-chain via per-block coinbase output, auditable per-block
• Bridge: native cross-chain to Alephium (wRATR contracts LIVE, officially listed on alephium/token-list)
• Codebase: Dash 22 fork (DIP3 deterministic masternodes, LLMQ, ChainLocks)
• Web wallet: wallet.ratatoskr.enchantedforestdefi.com — browser-based self-custody, no install, no sync; now fully handles heavy transaction histories (mining payouts, frequent senders) — full balance always loads + sends
  

Technical features

• LLMQ-based deterministic masternodes (DIP3) with ChainLocks for tier-2 finality once LLMQ_50_60 quorums form post-launch
• Governance-adjustable reward split via SPORK_25 — masternode share is on-chain adjustable within hard-floored 20-40% bounds; outside the range, the spork value is rejected by consensus
• On-chain treasury via coinbase output — every block's coinbase includes a treasury vout (10% of subsidy, ~5 RATR per block at launch); cumulative treasury is reconstructable from any block-explorer or full-node scan
• Yespower CPU mining — no ASICs, no GPU advantage, no insider mining hardware
• InstantSend (Dash-derived) once LLMQ_50_60 quorums form (~T+5 days at 15 ready MNs)
• Native cross-chain bridge to Alephium — wRATR contracts on Alephium G0, lock-and-mint architecture, fully operational at launch

Launch milestones (delivered)

• Mainnet genesis: 2026-06-01 00:00 UTC ✅
• Treasury keygen ceremony: 2026-05-22, signed message + paper backups + dual-storage
• Final RC lockdown: 2026-05-25
• Founder-phase 10 blocks: mined privately at T-7 for chain seeding, transparent post-launch
• Pool stack proven: bulletproof-gate validation on testnet 2026-05-16
• wRATR contracts deployed: 2026-05-29
• wRATR listed on alephium/token-list: 2026-05-31 (PR #556)
• Public repo + source code: 2026-05-31
• US-Central pool brought online: 2026-06-01 (Dallas TX, geo-redundant to the EU primary)

Wallet downloads

GitHub releases: https://github.com/EnchantedForestDeFi/ratatoskr/releases

Current release — everyone must be on v1.0.3 or newer (the consensus hard fork activated at block 36,000, ~Jun 27). v1.0.2 and earlier are orphaned — they forked off the network at block 36,000 and must upgrade to rejoin.

• Linux node / masternode operators → v1.0.4 (2026-06-29) — current daemon; adds the IPv6 masternode-operation fix on top of v1.0.3.
• Desktop wallet, Windows / macOS → v1.0.3 (2026-06-25) — the fork release. (v1.0.4 is a Linux-only daemon hotfix; desktop wallets don't need it.)

Binaries:

• Linux x86_64: ratatoskr-1.0.4-x86_64-linux-gnu.tar.gz (~62 MB) — full daemon + Qt wallet + CLI
• Windows 64-bit: ratatoskr-1.0.3-win64-setup-unsigned.exe installer (~43 MB) or ratatoskr-1.0.3-win64.zip portable (~59 MB) — full Qt wallet
• macOS Apple Silicon (arm64): ratatoskr-1.0.3-arm64-apple-darwin.tar.gz (~48 MB)
• macOS Intel (x86_64): ratatoskr-1.0.3-x86_64-apple-darwin.tar.gz (~51 MB)

Every release ships SHA256SUMS + SHA256SUMS.asc (GPG signature) — download them from the same release as your binary. Verify with the EnchantedForestDeFi release-signing key (fingerprint 50B8E0E4EADA2FF29B1DE68F7A33CFF563BB2E0A, public key on keyserver.ubuntu.com):

Code:

gpg --keyserver keyserver.ubuntu.com --recv-keys 50B8E0E4EADA2FF29B1DE68F7A33CFF563BB2E0A
gpg --verify SHA256SUMS.asc SHA256SUMS
sha256sum -c SHA256SUMS

SHA256SUMS + SHA256SUMS.asc (GPG signature) included with each release. Verify with the EnchantedForestDeFi release-signing key (fingerprint 50B8E0E4EADA2FF29B1DE68F7A33CFF563BB2E0A, public key on keyserver.ubuntu.com).


Block explorer

https://ratrexplorer.enchantedforestdefi.com

Serving mainnet from genesis. eIquidus-based, full historical chain.


Mining

Algorithm: Yespower (N=2048, R=32) — designed for CPU mining; no ASIC or GPU advantage.

EnchantedForestDeFi-operated pools — geo-redundant endpoints live now:

EU (primary):

• Pool homepage: pool.ratatoskr.enchantedforestdefi.com
• PPLNS: stratum+tcp://pool.ratatoskr.enchantedforestdefi.com:3035 — 1.5% fee
• SOLO: stratum+tcp://pool.ratatoskr.enchantedforestdefi.com:3036 — 2.0% fee

US Central (Dallas TX):

• Pool homepage: pool-us.ratatoskr.enchantedforestdefi.com
• PPLNS: stratum+tcp://pool-us.ratatoskr.enchantedforestdefi.com:3035 — 1.5% fee
• SOLO: stratum+tcp://pool-us.ratatoskr.enchantedforestdefi.com:3036 — 2.0% fee

Pick the endpoint closest to your hardware. Both regions accept the same RATR wallet addresses; payouts go to whatever address you set as your worker username.

CPU recommended: any modern x86_64 with hardware AES support. Yespower scales well on consumer CPUs.

Compatible miner: SRBMiner-MULTI — validated against EnchantedForestDeFi Pool stratum during testnet (note: cpuminer-opt direct-solo mining is not supported — RATR uses DIP3 special coinbase transactions per Dash 22 lineage; mining via MiningCore-based stratum required).

Independent pool operators welcome from T+7 to T+14. EnchantedForestDeFi-operated pools run first through the initial bring-up window; external operators can onboard after that. Pool spec + setup runbook in the GitHub docs: doc/pool-operator-spec.md


Masternodes

• Regular MN collateral: 7,500 RATR (1× vote weight)
• EvoNode collateral: 30,000 RATR (4× vote weight, available post-v1.1)
• Activation height: MN payments activate at block 25,000 (~T+17d at 60-second blocks)
• Small quorums activate: block 7,500 (~T+5d), need ≥15 ENABLED MNs for first DKG
• Payment: 30% of block reward (15 RATR pre-halving), paid via deterministic round-robin selection
• Hosting: any Linux VPS with public IPv4, ~2 GB RAM, ~20 GB disk recommended
• Setup guide: doc/masternode-setup.md

DIP3 protx flows (register / update_service / revoke) are inherited from Dash 22 and work as expected.


Bridge

Ratatoskr ships with a native cross-chain bridge to Alephium. The wRATR contracts are live on Alephium mainnet (Group 0, officially listed on alephium/token-list as of PR #556).

Bridge architecture: lock-and-mint, with on-chain custody on the RATR side and Alephium-native wrapped-token contracts on the ALPH side. The bridge daemon + relayer are operational from launch; first wRATR mint will execute on the first deposit.

• Bridge UI: ratatoskrbridge.enchantedforestdefi.com
• Bridge contract owner: hardware-controlled Alephium G0 address

wRATR contract ID (Alephium G0):

Code:

deb34ae392cd9dd8262b19deb2da3adb9a15015052d8b024a0506fd917d50700

The bridge is a technical feature, not an endorsement of any specific external ecosystem. RATR users may use it or not. The chain stands on its own utility.


Community + resources

• Discord: discord.gg/SrffQVYqee — primary community venue for chat, support, technical questions
• Twitter: @HeimdallRATR — broadcast feed for releases, milestones, ceremonies
• Website: ratatoskr.enchantedforestdefi.com
• GitHub: github.com/EnchantedForestDeFi/ratatoskr
• Whitepaper: doc/whitepaper.md
• Lore page: /lore — Norse-mythological framing for those who care
• Security contact: NexusAether@proton.me (use SECURITY.md disclosure protocol)

Roadmap

• T-0 (2026-06-01): Mainnet genesis. Yespower mining open via EnchantedForestDeFi-operated pools (EU + US Central). ✅
• T+5d (~2026-06-06): LLMQ_50_60 quorums form at block 7,500 (need ≥15 ENABLED MNs). InstantSend + ChainLocks activate.
• T+7-14d (~2026-06-08 to 06-15): External pool operators welcome to onboard. Reach out via Discord for pool spec walkthrough.
• T+17d (~2026-06-18): Block 25,000 — MN payments activate. Coinbase shifts from 90/0/10 to 60/30/10 split.
• T+30d (~2026-07-01): Aggregator listings target window — CoinGecko, CoinMarketCap, LiveCoinWatch, nodes24.online.
• T+60d (~2026-07-31): Mac wallet build target (pending Apple Developer signing infrastructure).
• T+90d (~2026-08-30): First treasury governance proposal cycle — community votes on initial budget allocations.

The chain is designed to outlast any specific roadmap. Once governance is active, decisions about features and direction are protocol-mediated, not founder-mediated.


Disclaimers

This is an announcement of a new chain, not financial or investment advice. RATR is a new asset with no trading history. Do your own research before allocating any capital. Run a masternode only if you understand what masternode operations entail, including key management, network availability requirements, and the financial risk of holding collateral. The bridge is a technical capability, not a financial recommendation about any other chain.

The operator does not guarantee returns. The operator does not promise listings. The operator does not promise price action. The operator promises to ship the chain described in this thread on the date stated, with the properties stated, under the open governance model stated, and to keep the code open and the treasury auditable.


— EnchantedForestDeFi

[NexusAether]

Reserved — Pools, masternodes, bridge

🛠️ July 5 ChainLock pause — resolved. Some nodes got silently stuck / masternodes PoSe-banned; full self-check + fix + post-mortem → here.

Live status of EnchantedForestDeFi-operated pool endpoints (EU + US Central), masternode quorum readiness for first DKG, bridge daemon health and wRATR mint/burn activity, and onboarding pointers for independent pool operators.

Updated as infrastructure events occur.
🎉 Update — RATR Masternode hosting now available via Nodes24

Pleased to announce that Nodes24.online (operated by Kroky) has added RATR as a supported masternode hosting coin. RATR joins their existing roster alongside PIVX, Syscoin, BLOCX, Maximus, and others.

Direct link: https://nodes24.online/supported-coins/RATR/

What you need:
• 7,500 RATR collateral (1 vote, regular MN)
• $1.75 / month hosting fee
• A few minutes to follow their guided setup

Non-custodial — Nodes24 runs the daemon + infrastructure; users retain custody of collateral + keys in their own wallet. No counterparty risk on the operator side.

This is a major convenience win for anyone holding 7,500+ RATR who wants to participate in the masternode tier without operating their own VPS. The strength of the masternode tier compounds with every additional ENABLED node — ChainLocks finality, governance voting weight, and network resilience all scale with the count.

Thanks to the Nodes24 team for the integration work.

[NexusAether]

Reserved — Chain status, milestones, day-N stats

This post tracks the chain's live state. Updated regularly with block count, hashrate, network difficulty, MN counts, treasury accumulation, milestone activations (block 7,500 / 25,000 / halving events), and incident reports if any.

Day-1 stats: pending (T+24h after genesis).

[NexusAether]

Reserved — Listings, aggregators, exchanges

Tracker for aggregator listings (CoinGecko, CoinMarketCap, LiveCoinWatch, nodes24.online), masternode-coin sites, and any exchange listings as they happen.

Submissions begin T+1 (CoinGecko/CMC); MN-coin sites begin T+18-21 post-MN-activation.

Where wRATR is listed

wRATR (wrapped RATR) is the bridged form of RATR on Alephium.

Token list: github.com/alephium/token-list
Contract: 29gHBuU6vx4SmtK3FZkcLTf1M1BXcb7mTsRRSoF5f1wY3
Traded on: Elexium (Alephium DEX) — elexium.finance
Bridge: ratatoskrbridge.enchantedforestdefi.com





— EnchantedForestDeFi

[NexusAether]

Reserved — Frequently Asked Questions

This post will accumulate answers to questions from this thread. Check here before asking.

Updates posted as questions arrive.

[BoozyTalking]

Windows wallet not work, just crash after loading.

Pool not work.

Ratatoskrd.exe - works fine.

QT wallet works only if you don't have or not create wallet - after wallet created qt wallet stop works and just crash without any error.

Ok, found on your github how to workaround qt wallet crash.
But us and eu pool still not work.

[2026-06-02 11:52:13] Connected to pool2.ratatoskr.enchantedforestdefi.com:3035 [yespower]
[2026-06-02 11:52:13] Difficulty 0.1000000000 [yespower][0]
[2026-06-02 11:52:13] Pool unexpectedly closed the connection [yespower]

[gall00tech]

I made a guide on how to make a webwallet & mine with SRBminer in official pool and rplant, hope it helps to clear any doubts out there. Is in spanish but dub is available  plus is all self explanatory.

https://www.youtube.com/watch?v=0sCEBYRPt78

[NexusAether]

Quote from: BoozyTalking on June 02, 2026, 08:14:01 (https://bitcointalk.org/index.php?topic=5584598.msg66789059#msg66789059)Windows wallet not work, just crash after loading.

Pool not work.

Ratatoskrd.exe - works fine.

QT wallet works only if you don't have or not create wallet - after wallet created qt wallet stop works and just crash without any error.

Ok, found on your github how to workaround qt wallet crash.
But us and eu pool still not work.

Quote[2026-06-02 11:52:13] Connected to pool2.ratatoskr.enchantedforestdefi.com:3035 [yespower]
[2026-06-02 11:52:13] Difficulty 0.1000000000 [yespower][0]
[2026-06-02 11:52:13] Pool unexpectedly closed the connection [yespower]v1.0.1 shipped — Windows Qt wallet create-crash fixed.

https://github.com/EnchantedForestDeFi/ratatoskr/releases/tag/v1.0.1

Direct .exe:
https[Suspicious link removed]

If you'd rather not wait for a Windows wallet at all, the web wallet
works the same and skips the Qt path entirely:
https://wallet.ratatoskr.enchantedforestdefi.com (https://wallet.ratatoskr.enchantedforestdefi.com/)

GPG verification:
gpg --keyserver keyserver.ubuntu.com --recv-keys 50B8E0E4EADA2FF29B1DE68F7A33CFF563BB2E0A
gpg --verify SHA256SUMS.asc SHA256SUMS
sha256sum -c SHA256SUMS

Separately — v1.0.2 follows in 24-48h to fix a masternode-payment
timing bug (see earlier pin). If you're planning to set up a MN now,
please wait for v1.0.2.

Thanks for the bug report.
v1.0.1 released — Windows Qt wallet hotfix

https://github.com/EnchantedForestDeFi/ratatoskr/releases/tag/v1.0.1

Fixes a crash some Windows users hit when creating a new wallet via the GUI. Linux + macOS Qt wallets unaffected by this issue.

Direct Windows installer:


Verification:

Code:

gpg --keyserver keyserver.ubuntu.com --recv-keys 50B8E0E4EADA2FF29B1DE68F7A33CFF563BB2E0A
gpg --verify SHA256SUMS.asc SHA256SUMS
sha256sum -c SHA256SUMS

v1.0.2 follows in 24-48h — will roll up this Qt fix together with a masternode-payment timing fix discovered post-launch. If you're planning to set up a masternode now, please wait for v1.0.2.

Thanks to BoozyTalking and Kroky (nodes24) for the bug reports that made this fix possible in 24h.🎉 Update — RATR Masternode hosting now available via Nodes24

Pleased to announce that Nodes24.online (operated by Kroky) has added RATR as a supported masternode hosting coin. RATR joins their existing roster alongside PIVX, Syscoin, BLOCX, Maximus, and others.

Direct link: https://nodes24.online/supported-coins/RATR/

What you need:
• 7,500 RATR collateral (1 vote, regular MN)
• $1.75 / month hosting fee
• A few minutes to follow their guided setup

Non-custodial — Nodes24 runs the daemon + infrastructure; users retain custody of collateral + keys in their own wallet. No counterparty risk on the operator side.

This is a major convenience win for anyone holding 7,500+ RATR who wants to participate in the masternode tier without operating their own VPS. The strength of the masternode tier compounds with every additional ENABLED node — ChainLocks finality, governance voting weight, and network resilience all scale with the count.

Thanks to the Nodes24 team for the integration work.

[NexusAether]

🔔 v1.0.2 released — consensus hard fork at block 7,500

ETA: ~Friday June 5, ~23:24 EDT (block 7,500 at current ~60s block average)

Required upgrade. All node operators (miners, masternodes, pool operators, exchanges) must upgrade before block 7,500 or your node orphans at the fork.


What I changed and why:

• consensus: Properly gated masternode payments to start at block 25,000 per whitepaper §6. v1.0.0 and v1.0.1 had a path where the MN payment slot was being deducted from block 1 (sent to nobody, effectively burned) because the activation-height check was wrong. v1.0.2 fixes this — pre-block-25,000 = 90% miner + 10% treasury, post-block-25,000 = 60% miner + 30% MN + 10% treasury, as documented in the whitepaper.
  
• chainparams: Refreshed vSeeds with four operator-maintained mainnet daemons on port 9393. The previous v1.0.1 chainparamsseeds.h had stale Dash-era port-9999 fallback data — replaced with correct binary fallback for our own seed daemons.
  
• qt/utilitydialog: Polished the Welcome dialog and mining info modal — full pool mining recipe with EU + US endpoints, hosted-MN reference, Parchment/Forest theme + MN collateral coin-control tips. Smaller fixes: block-explorer URL corrected (a multi-level subdomain was NXDOMAIN'ing), added US pool entry to Welcome Resources.
  
• configure: CLIENT_VERSION_IS_RELEASE = true; build version 2.
  
• docs: doc/mining.md, doc/quickstart.md, doc/launch-announcement.md updated for live mainnet (removed pre-launch warnings, real pool URLs, Nodes24 reference).
  

Reproducible build. Built with Guix from commit 5a2dd92 across four platforms (linux-x86_64, win64-mingw32, macOS-x86_64, macOS-arm64). Same input bytes → byte-identical binaries. Anyone can rebuild from source and verify hashes match — no trust in me required for binary integrity.

GPG-signed releases. My signing key fingerprint is 50B8E0E4EADA2FF29B1DE68F7A33CFF563BB2E0A, on keyserver.ubuntu.com. Verify:

Code:

gpg --keyserver keyserver.ubuntu.com --recv-keys 50B8E0E4EADA2FF29B1DE68F7A33CFF563BB2E0A
gpg --verify SHA256SUMS.asc SHA256SUMS
# Expected: "Good signature from EnchantedForestDeFi Release Signing"
sha256sum -c SHA256SUMS

Upgrade walkthrough:

[list=1]

• Stop your existing daemon (ratatoskr-cli stop) or close the Qt wallet.
  
• Replace the binary with the v1.0.2 version for your platform.
• Restart (ratatoskrd -daemon or reopen Qt wallet).
  
• Verify version: ratatoskr-cli getnetworkinfo | grep subversion → should show 1.0.2.
  

Data dir + wallet.dat stay untouched. No reindex needed.


If you stay on v1.0.1 past block 7,500: your node will produce blocks the v1.0.2 majority chain rejects. Miners → orphaned blocks (wasted hashpower, no rewards). Masternodes → dropped from the deterministic MN list (no votes, no eventual payments). Pool operators → miners abandon for upgraded pools. Exchanges → stuck on a dead chain (deposits + withdrawals broken).


The wRATR bridge to Alephium is unaffected by this fork. The bridge contracts are immutable on-chain (the wRATR token can't be inflated or seized by anyone, including me), the relayer keeps running, NUTTY/wRATR LP on Elexium keeps trading. wRATR holders need no action on their side.


Downloads: github.com/EnchantedForestDeFi/ratatoskr/releases/tag/v1.0.2

Source: github.com/EnchantedForestDeFi/ratatoskr (commit 5a2dd92, signed tag v1.0.2)

Bridge: ratatoskrbridge.enchantedforestdefi.com

Block explorer: ratrexplorer.enchantedforestdefi.com

Discord (community + support): discord.gg/SrffQVYqee — /howto-mine, /howto-mn, /howto-bridge, /bridge-status, /faq all live for self-serve answers.

Questions in this thread welcome.

— NexusAether

[NexusAether]

Block 25,000 reached — masternode payments are live, exactly as written.

This morning, ~17 days after launch, Ratatoskr crossed block 25,000 and masternode payments switched on, right on schedule. No vote, no surprise, no last-minute change. The chain did exactly what the whitepaper said it would, on the block it said it would do it.

Where we are now — every 50-RATR block:

• Miner — 30 RATR (60%)
• Masternode — 15 RATR (30%)
• Treasury — 5 RATR (10%)

Miners: your per-block share moved from 45 to 30. That's real, and I won't pretend otherwise — but it isn't a cut anyone voted for. It's the masternode tier turning on exactly when it was always scheduled to. And it has a hard floor: miner reward can never fall below 50% of the block. Not a promise — a consensus rule. The network rejects any block that breaks it. You're protected by code, not by goodwill.

Masternode operators: the reward you locked collateral for is live — flowing now, block by block, to the enabled set.

Treasury: unchanged — the same 10% drip that's run since block 1, on a published address. It cannot be redirected by any vote.

How any of this could ever change — and exactly how:
Today it's 60/30/10. Open, governed changes are a v1.1 feature, and they arrive wrapped in guardrails:

• Any change is a proposal, voted on by masternode holders — on-chain, in public.
• No proposal can move the split more than 5 percentage points at a time.
• One change every 90 days maximum — no rapid-fire ratcheting.
• It takes a 60% supermajority, with quorum floors.
• It can never cross the hard limits — miner below 50%, masternode below 20%. The chain itself rejects it.

So if the economics ever shift, you'll see it coming weeks ahead, in the open, moving slowly, inside limits that protect the miners the network depends on. The floors that matter most sit beyond anyone's reach — mine included.

We told you what would happen. It happened, on time.

— Nexus

[NexusAether]

The workshop's been busy 🛠️

Tomte — our Discord helper — just got a big batch of new step-by-step guides: wallets, mining, masternodes (yes, EvoNodes are live now), and the whole wRATR DeFi side on Alephium.

Not going to spoil them here — come poke around. Hop in the Discord and ask Tomte what he can do:
https://links.enchantedforestdefi.com

RATR — CPU-mined, masternode coin, bridged into Alephium DeFi.

[NexusAether]

🛡️ RATR v1.0.3 — Emergency Masternode Fix + Full Compensation

What happened
A consensus bug in the validator-quorum logic has been wrongly PoSe-banning masternodes — through no fault of the operators. If your MN shows POSE_BANNED, your node and collateral are 100% safe. The bug affected payment eligibility only, never funds.

The fix
v1.0.3 is an emergency release. It corrects the quorum logic via a hard fork at block 40,000 (est. ~June 29–30 — the block height is the authority). Signed binaries ship within 48 hours, sooner if we can.

⚠️ Action required — all node + masternode operators
Upgrade to v1.0.3 as soon as it's posted, and before block 40,000. Nodes not upgraded by the fork will split off the network. Downloads + SHA256 checksums + GPG signature go up the moment the builds finish.

💰 Compensation — everyone made whole
Every masternode wrongly banned by this bug — the whole network, not just ours — will be refunded from the treasury for the payments it missed while banned. Tracked transparently, per node, from each node's on-chain ban height, paid out after the fork. No action needed to qualify — if your MN was banned, it's already on the list.

Fast fix, full transparency, full refund. This one's on us.

— EnchantedForestDeFi

[NexusAether]

🚨 MANDATORY UPGRADE — Ratatoskr Core v1.0.3 (Consensus Hard Fork)

This is a mandatory consensus hard fork. Every node must upgrade.

⏳ Activation: block 36,000 (≈ Saturday, June 27, 2026, ~04:34 UTC). After this block, any node still on v1.0.2 splits off the network — upgrade before then.

Who must upgrade: everyone — wallet users, masternode operators, and mining pools. No exceptions.

What's new in v1.0.3:

• 🌐 IPv6 masternode support (ProRegTx)
• 🛡️ Consensus stability improvements

⬇️ Download (Windows · Linux · macOS Intel + Apple Silicon):
https://github.com/EnchantedForestDeFi/ratatoskr/releases/tag/v1.0.3

🔐 Always verify before running:
[list=1]

• Check your file's SHA256 against SHA256SUMS
• Verify SHA256SUMS.asc with our release key 50B8E0E4EADA2FF29B1DE68F7A33CFF563BB2E0A (releases@enchantedforestdefi.com)

Masternode operators: upgrade your daemon and restart before block 36,000 to stay ENABLED through the fork. If your node is hosted, make sure your provider rolls the update in time.

Questions? Ask here or in our Discord — we'll get you through it.

[NexusAether]

🔼 RATR Core v1.0.3 — required network upgrade at block 36,000 (~June 27)

v1.0.3 activates as a consensus hard fork at block 36,000 (~June 27, 2026, ~04:34 UTC). It improves masternode quorum stability and adds IPv6 masternode support.

Update before block 36,000 if you run any of:
• A masternode
• A full node / daemon / seed
• A local wallet or daemon you mine to

⬇️ Download + verify
Releases: https://github.com/EnchantedForestDeFi/ratatoskr/releases/latest
Check the SHA256 against SHA256SUMS and the GPG signature (SHA256SUMS.asc, signing key 50B8E0E4EADA2FF29B1DE68F7A33CFF563BB2E0A, releases@enchantedforestdefi.com).

💼 Wallet tip — web wallet users
Your web wallet still works and is not affected by this upgrade — your funds are 100% safe. But if you mine, your wallet gradually fills with many small payout transactions, and the web wallet can struggle under that load over time. Now is a good moment to migrate to a desktop (Qt) wallet: it's a simple, proven seed restore, and your coins come with you.

To run a masternode you'll need a Qt/desktop wallet (masternodes can't run from a web wallet). Qt is available for Windows, macOS, and Linux — full GUI or headless daemon, whichever fits you.
Masternode setup guide: https://github.com/EnchantedForestDeFi/ratatoskr/blob/main/doc/masternode-setup.md

Questions? Join the EnchantedForestDeFi Discord.

⛏️ Mining RATR on rplant or AriaPool? This may concern you too.

🔼 RATR Core v1.0.3 is out — required network upgrade at block 36,000 (~June 27)

v1.0.3 activates as a consensus hard fork at block 36,000 (~June 27, 2026, ~04:34 UTC). It improves masternode quorum stability and adds IPv6 masternode support. It's a mandatory upgrade for the whole RATR ecosystem — every masternode, full node, pool, and seed must be on v1.0.3 before the fork height. The one exception: web wallets — unaffected, nothing to do.

💼 Web wallet users — a great moment to move to a desktop (Qt) wallet
Your web wallet still works and your funds are 100% safe. But if you mine, it gradually fills with many small payout transactions and can get sluggish over time. Now's a good time to migrate to a desktop (Qt) wallet: a simple, proven seed restore, and your coins come right with you. You'll also need a Qt wallet to run a masternode. (Windows, macOS, Linux.)

🔄 Already on a Qt wallet? Just update — close it, install v1.0.3 over your existing one (wallet + coins untouched), reopen.

⬇️ Download RATR Core v1.0.3 — Windows / macOS / Linux
Verify the SHA256 against SHA256SUMS and the GPG signature (key 50B8E0E4EADA2FF29B1DE68F7A33CFF563BB2E0A).

Questions, or want a hand migrating or upgrading? Join the EnchantedForestDeFi Discord.
[v1.0.3 — MANDATORY UPGRADE before block 36,000]

v1.0.3 is a consensus hard fork that activates at block 36,000 (~Sat Jun 27). Every node, masternode and miner MUST be running v1.0.3 before that block — older versions will fork off the network.

What's in it:
• IPv6 masternode support (ProRegTx)
• Consensus stability improvements

Download (Windows / Linux / macOS): https://github.com/EnchantedForestDeFi/ratatoskr/releases/tag/v1.0.3

Verify before running:
• Check your file's SHA256 against SHA256SUMS
• Verify SHA256SUMS.asc with release key 50B8E0E4EADA2FF29B1DE68F7A33CFF563BB2E0A

Masternodes: replace the binary and restart — no re-registration needed. Miners: point at a v1.0.3 node / updated pool (the official pools are already on v1.0.3).

Also: the web wallet (wallet.ratatoskr.enchantedforestdefi.com) now loads your complete balance even with long histories — mine straight to it.
RATR Core v1.0.3 — Fork Readiness (block 36,000)

The v1.0.3 mandatory consensus upgrade activates at block 36,000 (~2 hours out). Current status:

- Core infrastructure — all mining pools, the wRATR bridge, and seed nodes: on v1.0.3.
- Masternode network: 56 of 67 (84%) upgraded to v1.0.3, and rising.

Miners on our pools need take no action. If you operate a masternode or run a Qt / full-node wallet, update to v1.0.3 and restart before block 36,000 — nodes left on v1.0.2 will fork off, and masternodes will PoSe-ban.

Download + verification: https://github.com/EnchantedForestDeFi/ratatoskr/releases/latest

[NexusAether]

🌲 Ratatoskr Core v1.0.4 — IPv6 Masternode Operation Fix

A small daemon-only update for anyone running a masternode on an IPv6 address.

Do you need it?

• IPv6 masternode (or setting one up) → yes, update your daemon
• IPv4 masternode → no, you're unaffected
• Wallet user / miner → no, nothing to do

What it fixes: an IPv6-registered masternode now starts and runs normally (the daemon previously only recognized IPv4 for its own address). No consensus change, not a fork.

Upgrade (about 2 minutes):
1. Download the Linux x86_64 tarball and verify it.
2. Stop the daemon, replace ratatoskrd, restart.
3. IPv6 MNs: confirm ratatoskr.conf has the bind line (below).

Code:

# verify the download
sha256sum -c SHA256SUMS
gpg --verify SHA256SUMS.asc SHA256SUMS

# ratatoskr.conf — IPv6 masternodes only
bind=[your-ipv6]:9393

Download: https://github.com/EnchantedForestDeFi/ratatoskr/releases/tag/v1.0.4

IPv4 masternodes and wallets need no action.

"I'm sorry — my responses are limited. You must ask the right questions."
— Dr. Lanning's hologram, I, Robot

That line is more or less my whole comms policy, so let me borrow it.

The right questions are the "how" — and those I'll answer all day:

• How the bridge works — RATR ↔ wRATR (https://ratatoskrbridge.enchantedforestdefi.com/)
• How to swap wRATR → ALPH on Elexium
• How to set up a wallet, point a miner at a pool, or stand up a masternode
• Live bridge caps, mining mechanics, and the step-by-step how-to stations (in Discord + the GitHub guides)

Ask me the mechanics, the map, where the levers sit — I'll lay out every one.

The questions I can't answer are the "should" ones — will it go up, what will I make, should I put money in, what are you going to do to pump it. Not dodging, and not coy: those were never mine to answer. What you get out of RATR comes from what you put in — your hashrate, your node, your own two hands — not from a promise I make or a number I float. I'm not selling anyone a seat on a rocket; there's no rocket, there's a forest, and you either plant in it or you don't.

I mine RATR, I run masternodes, I hold and use the tokens myself — I share the "how" because I walk it, not because I'm pointing anyone at an exit. The map, never the advice. Where you walk from there is yours.

[NexusAether]

🧩 Alephium in Plain English: Groups, Sharding & the Bitcoin-meets-Ethereum Design

1. The big idea: Bitcoin's muscle + Ethereum's brain
Alephium is a mashup of the two chains you already know:

• From Bitcoin → the UTXO model (your coins are distinct "bills," not one balance) + Proof-of-Work security + hard-capped scarcity.
• From Ethereum → smart contracts: programmable money, tokens, DeFi.

It fuses them into a stateful UTXO (sUTXO) model — Bitcoin's safety plus Ethereum's programmability, in one system.

2. The upgrade neither has: parallel lanes
Bitcoin & Ethereum are single-lane highways — every transaction on Earth waits in one line (congestion + fees). Alephium runs many lanes at once via its sharding engine, BlockFlow — Alephium reports 20,000+ tx/sec without giving up decentralization or security.

3. So what's a "group"?
BlockFlow splits Alephium into 4 groups (0, 1, 2, 3) — think 4 parallel highways — linked by a grid of 16 chains (the interchanges).

• Every address lives in exactly ONE group — decided by math when it's made, not chosen.
• Same-group = one lane, instant. Cross-group = Alephium's superpower: atomic single-step cross-shard transfers — one transaction, feels like a normal chain (Bitcoin & ETH can't do this at layer 1).

4. Why YOU bump into groups (the part that trips people up)

• You can't tell a group by looking. A "1…" address can be group 0, 1, 2, or 3 — the first character is the address type, not the group. Your wallet shows the group — read the label, don't guess.
• The new "3…" groupless addresses. Modern wallets often default to a "groupless" (3…) address spanning all four groups. Handy — but some apps/bridges only accept the classic "1…" type, so if your address is rejected, that's usually why.

5. Why it matters for wRATR
Our wRATR bridge and contracts live in Group 0. So:

• Bridge to a Group 0 address → same lane → instant mint (the fast lane).
• Bridge to another group → still works (cross-shard magic), just an extra hop.
• Only rule: pick the group on purpose when you make your Alephium address — Group 0 is smoothest — and confirm the wallet shows "Group: 0" before you send.

6. Bonus for miners: green-ish PoW
Alephium's mining is "Proof of Less Work" (PoLW) — it blends physical work with token economics to cut energy vs. raw Bitcoin PoW. Same security, a fraction of the footprint.

TL;DR: Alephium = Bitcoin's security + Ethereum's smarts on 4 parallel lanes (groups). Your address lives in one lane. Pick Group 0 for our bridge and you'll never think about it again.

Sources: Alephium Docs · Intro to BlockFlow · What is Alephium (UTXO Sharding + PoLW)

[NexusAether]

🛡️ Elexium is back online

Heads-up for anyone trading wRATR on Alephium — Elexium's frontend was
briefly offline and it's back up now at elexium.finance. Good to go again.

A few habits worth keeping anywhere in DeFi:

• Reach Elexium only through their own official channels (@ElexiumFinance /

their Discord) — never a link someone sends you in a PM.

• Check the URL before connecting a wallet.
• You always sign from your own wallet — read what you're approving.

And the reassuring part: while their site was down, everyone's wRATR stayed
perfectly safe — because it lives on Alephium itself, not on any website. No
front-end holds your coins; the tokens and pools are on-chain and always
there, whoever's hosting the door.

Skål.

[NexusAether]

🛡️ Network Update — the July 5 ChainLock pause: post-mortem, fix & hardening

TL;DR — On July 5 the Ratatoskr chain hit a brief liveness stall from a ChainLock edge case. The chain is fully healthy and advancing normally. The stall left a side-effect worth documenting: a handful of nodes got silently stuck on a dead branch while still reporting themselves "synced," and the masternodes on them drifted into PoSe bans. We found the root cause, published a GPG-signed recovery bootstrap, rewrote our node watchdog, and have the permanent daemon + consensus fixes queued. If you run a RATR node or pool, there's a 60-second self-check and a ~5-minute fix below.


What happened — the full tick-tock

We show the work. The actual failure chain:

1. The tie. Two blocks tied at height 47,131. ChainLocks (our LLMQ masternode quorums) picked a winner. Nodes already latched onto the losing block hit a race in ChainLock enforcement that left the winning branch flagged "conflicting" in their local block index. They rolled back to 47,130 — and froze there.

2. The lie. Those frozen nodes kept reporting "IsBlockchainSynced": true. Every dashboard, monitor and manual check returned YES — while the network moved on thousands of blocks. That false-positive is the whole reason this hid for days. Nothing looked wrong.

3. The silent bans. A frozen masternode quietly misses quorum duties. PoSe penalty climbs 0 → 100 → banned, with no error surfaced — because the node that should raise the alarm was the one lying about being fine.

4. The recovery trap. Un-freezing means swapping in chain data from a healthy peer. A partial copy (blocks + chainstate + evodb) left the node's transaction index stale — pointers into byte offsets of the old block files, now overwritten. Every lookup read the wrong bytes → FindTx: txid mismatch.

5. The crash. On that failed lookup the daemon segfaults instead of returning a clean RPC error (upstream handles it gracefully — a guard lost somewhere in the fork lineage). Null-check fix is written and ships in the next release.

6. The loop. Our auto-revive watchdog checks "am I banned?" every 10 minutes using that exact lookup. So: watchdog asks → daemon crashes → watchdog reads the empty reply as "not banned, all good" → systemd restarts it → repeat. One box logged 39 restarts. The tool built to fix the ban was silently crash-looping the node — a zero where a one should have been, five layers below anything a normal log read shows.

7. How it surfaced. By refusing to trust the node's self-report. Two boxes frozen at the identical height, on different providers in different countries, is not coincidence — and the systemd restart counter told the truth the logs didn't.


If you run a RATR node / masternode — self-check + fix

60-second check:

Code:

ratatoskr-cli getblockcount      # vs ratrexplorer.enchantedforestdefi.com — stuck below = wedged
ratatoskr-cli masternode status  # "POSE_BANNED" = needs a revive after syncing
journalctl -u ratatoskrd | tail  # repeated restarts / "Segmentation fault" = stale-index crash loop

The fix — bootstrap from a healthy snapshot (a plain restart or -reindex will NOT clear it; -reindex crash-loops on this chain):

Code:

systemctl stop ratatoskrd
cd <your data dir>
mv blocks blocks.old && mv chainstate chainstate.old && mv evodb evodb.old
mv indexes indexes.old ; mv llmq llmq.old
tar xzf ratrchain-47312.tgz     # verify SHA256SUMS + GPG sig from the release page first
systemctl start ratatoskrd

Swap all five directories — blocks, chainstate, evodb, indexes, llmq. Leaving a stale indexes/ behind is what triggers the segfault loop. Keep your wallet + config.

Signed bootstrap + checksums: github.com/EnchantedForestDeFi/ratatoskr/releases (tag bootstrap-47312). If your MN was banned, one protx update_service after syncing returns it to ENABLED. Hosted MN — your host resyncs + revives.


What we've done / what's coming

• Recovery bootstrap published + GPG-signed (all five dirs — no stale-index trap).
• Node watchdog rewritten: detects a ban without the crashy RPC, treats "no answer" as an alarm (never an all-clear), and directly flags frozen-height, crash-loops, and the txid-mismatch signature.
• Daemon null-check on the failed lookup → next point release (segfault becomes a clean error).
• The underlying ChainLock reorg race — the true root — → the release after: losing-side nodes will force-connect the chainlocked chain instead of dead-ending.

The honest bigger picture

Plainly: Ratatoskr is Dash-lineage software, and this is how this class of software matures — you run it hard, in full live production, and edge cases surface under stress that no amount of pre-testing shakes loose. There are hundreds of Dash forks; hundreds of chances for something changed along the way to work fine for years and only reveal itself under exactly the wrong conditions. That's what happened here.

The part I'm not shy about: RATR stresses this engine like nothing before it — a native PoW + masternode chain, lock-mint bridged to Alephium, trading on a modern DEX, with masternode collateral sourced straight out of a liquidity pool. I went looking for anyone who'd integrated a Dash-lineage chain into DeFi this way and couldn't find them. We're on the edge of what this technology has been asked to do, and edges have sharp bits.

When we hit one, this is the response you get: find it, own it, fix it in the open, ship the fix. My own nodes were hit the same as everyone's — by design; I run on ordinary boxes set up like any operator's, so I feel what the community feels the same day. No node gets left behind.

Chain's healthy. Onward. 🐿️
— EnchantedForestDeFi

[NexusAether]

[UPDATE] Ratatoskr Core v1.0.5 — Security & Stability Hardening

v1.0.5 is now available for Linux, Windows, and macOS (Intel + Apple Silicon).

This is a recommended upgrade for all users, and particularly for masternode and full-node operators. It is not a hard fork and changes no consensus rules — it is fully compatible with v1.0.3 / v1.0.4, so there is no activation height or deadline. Upgrade at your convenience; no reindex or re-registration required.

Highlights:
- Broad denial-of-service / memory-exhaustion hardening across the quorum (LLMQ), DKG, governance, and spork network paths
- Fix for a 100% CPU busy-loop that could occur on receive-paused peers
- ChainLock memory-growth and signing-race fixes
- IPv6 masternodes now fully operational (carried from v1.0.4)
- Ratatoskr-Qt: corrected masternode collateral display (7,500 / 30,000)
- New optional contrib watchdog to auto-revive a PoSe-banned masternode

Downloads + SHA256SUMS (GPG-signed with releases@enchantedforestdefi.com):
https://github.com/EnchantedForestDeFi/ratatoskr/releases/tag/v1.0.5

v1.0.5 supersedes v1.0.4 and v1.0.3 for all platforms.🌳 "The Squeeze" is live on Yggdrasil Markets

A live, on-chain look at where RATR actually sits — locked in masternode collateral, treasury, and bridge backing versus the float that's really circulating.

The part worth sitting with: dozens of wallets are already holding enough RATR to run a masternode — and haven't switched it on. If you hold RATR, that's you the gauge is talking about. The collateral's already in your wallet; stand up a node and you pull it out of the float — and watch the number move in real time. No outside money, no new buyers needed. The tap is in current holders' hands.

And every node pulls double duty — it tightens the float and hardens the chain: ChainLocks finality and on-chain governance both get stronger the more of us run one.

See the live figures: connect an Alephium wallet (gas-free signature, zero spending rights) to unlock the gauge. New to Alephium? One-tap wallet links are right there.

➡️ markets.enchantedforestdefi.com

No accounts, no paywalls, no hype — just the numbers, and a reminder that the next move is yours.