
Managing policy-governed spend in satoshis— escalation, audit, and Lightning-style cryptographic settlement proofs. Built for judges who expect depth, not buzzwords.
EclipseTreasury overview
Decentralized autonomous financial operations (demo)
Total balance
1.5M sats
+4.2% vs last week
Active agents
2 on mission
Nominal
Daily spend
650k 65% of limit
Critical alerts
Agent comparison
Agent Alpha
Liquidity provisioning
78% · 94.2%
Agent Beta
Arbitrage routing
32% · 88.5%
Recent activity
AWS Lambda
12,500 sats · compute
Policy threshold
System policy #42
Unknown oracle
Security protocol
Why Eclipse
Agents will spend autonomously—you need limits, human escalation, and a ledger that speaks Lightning’s language. Vendor names are simulated; policy, hashes, and UI are real.
Product depth
Per-tx limits, daily caps, categories, vendor rules, escalation—auto-approve safe spends, humans for the rest.
Gemini-backed missions with deterministic fallback; demo vendor catalog exercises every policy path.
Real SHA-256 preimage → payment hash on settle—the HTLC commitment pattern Lightning uses.
Internal trail vs competitor view: prove cryptography without leaking vendor strategy.
Queue, ledger, audit logs, CSV, printable treasury report—judge-ready operations.
Reset workspace, scripted mission, synthesis—then jump into the full dashboard.
01
Mission
Agent proposes spends in sats
02
Policy
Rules engine evaluates
03
Route
Approve · escalate · reject
04
Settle
Hash + preimage + treasury
Dashboard, agents, approvals, transactions, and cryptographically consistent settlement records—one click away.
● Secure session · SHA-256 preimage/hash settlement proofs