Eclipse Crosspay runs on your own machine — the client starts it, so there is no endpoint to ping.
Pre-flight FX verdicts over fixture FX records; spread sealed vs mandate cap; never settles.
The linked repository no longer exists on GitHub — it was deleted or made private.
This one has been quiet for a while
Quiet is not dead — but it is worth knowing when it wakes up, or when someone else takes it over. We watch the repository and tell you either way.
Alternatives to Eclipse Crosspay
same job, measured the same wayBurn-trajectory forecast over sealed fixture mandates: receipted pre-breach verdicts.
Pre-payment verdict over fixture PO/mandate/delivery triples; verdict only, never executes payment.
Pre-agreed revenue splits sealed at spawn, settled on completion records. LOCAL/fixture only.
Three-way settlement reconciliation (simulator, fixture records): ledger vs rail vs payout.
Sealed-policy cap bound proofs over fixture policies; recomputable certificate, local only.
Band-only age proofs over fixture attestations, sealed to one mandate; local only.
Failure-attribution recompute over hash-chained fixture records (local only): verdict + proof path.
Agent birth-certificate sealing + out-of-purpose detection, fixture records; detects, never blocks.
Eclipse Crosspay — questions
Answers built from our own checks of this server.