Eclipse Split runs on your own machine — the client starts it, so there is no endpoint to ping.
Pre-agreed revenue splits sealed at spawn, settled on completion records. LOCAL/fixture only.
Nothing serious here today
Today is the operative word: we check Eclipse Split every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Alternatives to Eclipse Split
same job, measured the same wayFailure-attribution recompute over hash-chained fixture records (local only): verdict + proof path.
Pre-flight FX verdicts over fixture FX records; spread sealed vs mandate cap; never settles.
Band-only age proofs over fixture attestations, sealed to one mandate; local only.
Sealed-policy cap bound proofs over fixture policies; recomputable certificate, local only.
Decision-evidence sealing + audit recompute over fixture decisions; local only.
Ballots sealed to vote-time mandate-eligibility proofs; fixture elections, local only.
Three-way settlement reconciliation (simulator, fixture records): ledger vs rail vs payout.
Per-action-class sponsor acceptance receipts over fixture sponsors/parties, local stdio only.
Eclipse Split — questions
Answers built from our own checks of this server.