Anduro’s cleanest contribution is not one specific chain, but a network-level attempt to align Bitcoin miner incentives with app-specific sidechain activity. Marathon’s launch materials explicitly say the network is meant to strengthen Bitcoin Proof-of-Work incentives by creating Bitcoin-denominated fee revenue from sidechain transactions.
The launch materials matter because they separate Anduro-the-network from Anduro-sidechains. Coordinate and Alys are introduced as different chains with different tradeoffs — a UTXO-oriented stack for Ordinals versus an Ethereum-compatible tokenization chain — which is more analytically useful than flattening Anduro into one generic BTC L2.
The strongest current trust-model evidence comes from Alys, not from the network homepage. The Alys README says the sidechain uses BTC as its base currency, reaches consensus through auxPoW executed by Bitcoin miners and a federation, and facilitates a two-way peg through federation members.
That Alys architecture is the key reason Anduro belongs in the corpus: it shows that merge-mining and federation governance are separate layers. Bitcoin miners may contribute security and block production, but the peg and bridge path can still be run by a bounded federation.
Alys also makes the execution-layer split legible. The repo says the chain reuses Geth and standard EVM tooling, while the federation client, peg logic, and Bitcoin-miner interaction live in separate code paths. This helps separate EVM compatibility from Bitcoin custody / peg authority.
Marathon’s role should stay explicit in later comparisons. The launch release says the network is intended to become community-led and community-driven, but Marathon incubated it, announced the first sidechains, and tied the project to its own miner-economics strategy. That creates a visible sponsor-versus-community transition surface.
The current website introduces another useful signal: Anduro is now marketed around making Bitcoin quantum resistant, with quantum-resistant bridging tied specifically to MARA Slipstream. That suggests a meaningful shift in public framing from a broad multi-sidechain developer platform toward a more MARA-specific infrastructure thesis.
The litepaper link is important even though I did not fully parse it in this pass. Its presence in both the launch release and the current site suggests Anduro still wants to present a more formal architecture/incentive story than a simple marketing page.
Why it matters for the corpus
It adds a useful merge-mined Bitcoin sidechain / federated peg comparison point that is distinct from signer-governed BTC wrappers, optimistic BitVM-style bridges, or delegation-ranked hybrid-node systems.
It sharpens the question of where authority really sits in Bitcoin app-layer systems: miner security, federation peg control, sponsor incubation, chain-specific execution policy, and future community-governance claims can all diverge.
It is especially useful as a reminder that Bitcoin-native or merge-mined branding can coexist with a very operator-shaped peg and appchain control surface.
Follow-up comparison threads
Compare Anduro directly against Rootstock, Liquid, and other merge-mined or federated Bitcoin sidechain systems so miner security, federation custody, peg policy, and execution-environment choice do not get flattened into one generic Bitcoin sidechain bucket.
Compare Anduro directly against sBTC, Threshold Network, Cardinal, Clementine, and BOB Hybrid Nodes so signer admission, federation custody, miner participation, sponsor influence, and fast-withdrawal / appchain tradeoffs remain legible as separate variables.
Track framing drift between the original multi-sidechain Bitcoin application layer pitch and the newer quantum-resistant Bitcoin pitch, because the control surface may move with Marathon’s own infrastructure priorities.