Research blog
Stellar & Core DAO security research — proof, not logs.
Deep dives, Mainnet case studies and network FAQs. Every post links to the code or transaction behind it.
Intent-to-Execution Proof: verifying what was authorized against what actually ran
The core CoreGuard thesis: logs describe, receipts prove. A summary of the repository's intent-to-execution design and its fail-closed verdicts.
Read post →PSAR/1: pre-sign authorization receipts for Stellar wallets
A receipt bound to the exact unsigned transaction bytes, re-checked before signing: PASS, BLOCK on tampering, BLOCK on expiry.
Read post →Toward shared receipt semantics on Stellar (internal SEP draft)
An internal draft exploring a common vocabulary for execution receipts across Stellar wallets, anchors and apps.
Read post →Why logs are not proof — and what Web3 should use instead
The problem in plain English: disputes, AI agents and cross-border payments need evidence that a third party can re-check without trusting the operator.
Read post →Fail-closed by default: guardrails for AI agents that move money
Why agent payments need a policy gate that denies on doubt, plus budget limits and offline receipt verification.
Read post →Case study: a Soroban commitment and a funded swap on Stellar Mainnet
Public, re-checkable transactions: a commit on ledger 65,337,373 and a path-payment swap on ledger 65,338,112.
Read post →Case study: EvidenceRegistry live on Core DAO (chain 1116)
The evidence registry contract on Core Mainnet, backed by an invariant suite that passes 43/43 in CI.
Read post →Stellar FAQ
Short answers about CoreGuard on Stellar.
Read post →Core DAO FAQ
Short answers about CoreGuard on Core.
Read post →Pi Network FAQ
Short answers about CoreGuard on Pi Network.
Read post →