Stellar: Soroban commit + first funded gated swap (ledger 65,338,112) — requesting $150K
×StellarCoreGuard is the intent-to-execution proof layer for Stellar. It gates wallet-signed swaps fail-closed and anchors a replayable receipt on Soroban — already live on Mainnet.
The new PSAR/1 film is an offline pre-sign authorization demonstration. The existing Mainnet film is the separate Stellar execution-truth and SCF story.
A technical evaluation film for the Freighter discussion: exact-XDR receipt binding, a clean-clone PASS, then BLOCK for changed bytes and an expired receipt. The terminal is a visual replay of captured clean-clone demo output, not a live screen recording. PSAR/1 does not judge amount policy or prove execution. Wallet integration is not built; external adoption is not yet.
The earlier ecosystem and SCF film: the live Soroban commitment anchor, the first signed funded swap, the execution-truth story and the $150K roadmap. This film is separate from the offline PSAR/1 pre-sign demonstration above.
Commit and swap screenshots captured from stellar.expert on 8 Nov 2026; success, ledgers, timestamps, fees and swap amounts cross-checked against Horizon. Contract and trustline images are earlier captures. Screenshots are not live balances.
A Stellar transaction now carries its own authorization proof before any signature exists. The receipt is bound to the exact XDR bytes; the wallet re-derives the decision itself — PASS or BLOCK, eleven frozen reject codes, executionProof: NOT_INCLUDED. Tamper one byte → XDR_BINDING_MISMATCH. Run: npm run stellar:presign. Freighter proposal written — no wallet embeds it yet.
Issuer-identity gap closed, v1 receipt verifier hardened, fresh-clone demo fail-closed, and a line-referenced threat-to-test map.
Create ledger 65,408,001 · contract CAZ3LQEMB37KICXEANKVMRNWMB5MD3O4FBC5GORB7QVUJE2WCPAHQPZB · balance arithmetic exact to the stroop (81,099,724) · fresh-vault readback SIMULATED_NONE · deploy verdict saved NOT_CONFIRMED.
Identity enforced inside the contract (owner.require_auth() host-gated). The live mainnet instance stays the deployed/1 binary — no deploy, no restatement.
The authorized intent is now bound field-by-field to the signed transaction bytes — what was approved is exactly what gets signed.
Commit read-back on-chain: {hash, seq} exact · anchor deployment untouched, no re-deploy · every row pinned to a digest-checked artifact in docs/evidence/.
AI agents can propose Stellar payments — CoreGuard decides. Never auto-pay; UNKNOWN stays HELD.
Every swap judged against real mainnet depth before signing — the same gate that cleared the first funded swap.
Six executed arms with committed artifacts — dApp calls are allowed, reviewed, denied or refused, fail-closed.
Know your Freighter signature matches exactly what you meant — before money moves.
Drop-in pre-sign guard: ALLOW / DENY / HOLD with a replayable receipt.
Cross-border disputes resolved by evidence packs, not by email threads.
Independent re-derivation of every claim — offline, byte-for-byte.
Let agents trade and pay on Stellar under a fail-closed policy gate.
Target users — not signed customers.
EXERCISED ON MAINNET · wrappers credential-gated
SHIPPED · 12 documents
A claim without a replayable artifact is a red flag.
Preflight gating of order-book swaps by real depth, wallet bounds and destMin.
commit / read of execution receipts on a live Soroban contract.
Wallet wrapper for intent checks before Freighter signs; no external wallet integration is claimed.
VERIFIED / REJECTED / HELD for AI-agent payment proposals; submission stays credential-gated.
Evidence bundles and explicit release decisions for anchors and PSPs; execution never implies delivery acceptance.
PASS / BLOCK receipt verification bound to the exact unsigned XDR. 37 tests; no v1 semantic XDR decode. External wallet integration NOT_BUILT.
DEX-GATE/1 + Soroban swap + DDE/1 + offline verifier with a 5/5 adversarial suite. Issue #26 completed; no named production DEX deployment.
Verify-before-release, digest-bound signature, single-spend and full refund in a 15-test JS mirror. No Soroban deploy, chain call or funds moved.
commit_authorized enforces owner.require_auth() and in-contract id derivation. A new mainnet instance still needs an owner decision; deployed/1 is unchanged.
Create ledger 65,408,001; exact stroop arithmetic; saved deploy verdict NOT_CONFIRMED. Open the digest-checked evidence artifact.
Replay receipts locally with authorize, verify and anchor workflows. Public npm publication remains double-gated.
Reserve-before-sign payment harness; live SaaS rails and credentials remain pending, not live.
Not claimed for Stellar: any owner-signed mainnet activity beyond the recorded first payment, anchor commit, funded swap and Phase 5 deploy evidence; public npm SDK publication (pending NPM_TOKEN + owner approval); external wallet adoption, production DEX integration, on-chain ESCROW/1, revenue, customers or partnerships — none.
VERIFIED ≠ SAFE: CoreGuard proves conformance to authorization; it does not certify a protocol as risk-free.
Every Stellar payment or swap is checked against the signed intent and policy, gated fail-closed, then anchored as a receipt on Soroban that anyone can replay byte-for-byte.
Horizon confirms path_payment_strict_send: 4.0598146 XLM → 0.6306239 USDC at ledger 65,338,112; minimum 0.6011661 USDC. Preflight gating is separate repository evidence, not a network-certified verdict.
When an anchor, wallet and recipient disagree, a DDE/1 evidence pack shows what was authorized vs. what executed — deterministic, offline, regulator-readable.
Contract CCKA…MXPSP is live and listed on stellar.expert. First commit(proofId, commitment) invoked at ledger 65,337,373 with a byte-exact on-chain read-back.
ALLOW / DENY / HOLD before Freighter signs. Wallet-bounded, depth-bounded, fee read-back to the stroop. UNKNOWN stays HELD — never silently passed.
JS SDK + CLI + Freighter wrapper: wallets, anchors and Soroban dApps add verification in a few lines. Goal: 5 integration pilots during the SCF award. (npm publish pending.)
The same verifier runs on Core DAO Mainnet (chainId 1116) and Stellar Mainnet, with 1576 machine-pinned tests (Foundry 43/43 CI-measured). Stellar inherits a proven core, not a prototype.
Teams that must prove to users and regulators exactly what moved and why. Target segment — no signed customers, revenue or partners are claimed.
Successful · 6 Nov 2026, 13:48:27 UTC · fee 351,299 stroops (0.0351299 XLM). Horizon confirms transaction success; stored-state read-back is separate repository evidence.
69044807410f65027c1227f4e525ad83f23a6cb1a2bb79790d82849c5dbc9fec
Successful · 6 Nov 2026, 14:50:02 UTC · fee 100 stroops (0.0000100 XLM) · minimum 0.6011661 USDC. Amounts confirmed by Horizon operation records. Preflight gates and offline replay are repository evidence, not network-certified results.
ac2a7990b3387aab96b197c0c921d57756bd25d65ad0e75b93561ded640b9097
The $150K request funds turning this proven pipeline into a public SDK, threat model and integrations for wallets, anchors and DEXs (tranches below).
Support the $150K requestIP · PLANNED — NOT FILED
The candidate invention is the coordinated CGEP/1 intent-to-execution evidence method, not blockchain technology, Stellar, Core DAO, a token or the CoreGuard brand. This is a proposed scope for patent-attorney review, not an issued claim or a conclusion of patentability.
Describe the signer or agent, assets, amount, recipient, expiry and policy version. A precise encoding and signature-validation procedure must be supplied in the application; the current preparation outline is not a complete specification.
The described method evaluates constraints such as wallet bounds, real order-book depth and minimum destination amount. ALLOW permits the next step; DENY or an unknown result prevents execution or holds it for review. Counsel must assess the potentially distinctive combination, rather than assume that an ordinary policy check is patentable.
The proposed pipeline canonicalizes and hashes the evidence and records a proof identifier and commitment on a public ledger. Stellar's Soroban commit(proofId, commitment) is implementation context. Exact hash inputs, encoding, sequencing and failure handling still need a complete enabling description.
The proposed receipt captures transaction identifiers, actual amounts and fees, then checks consistency against the intent and policy result. A public swap alone does not prove that all pre-execution checks occurred or that this comparison is implemented correctly.
The candidate verifier reconstructs the evidence chain and reports PASS, FAIL or an incomplete result conservatively. Exact verifier rules, test vectors, mismatch cases and alternatives must be documented. Verification is not a guarantee of safety: VERIFIED ≠ SAFE.
No novelty, non-obviousness, eligibility, inventorship, ownership or enforceable scope has been determined. Network records show transaction events, not a patent priority date. Core DAO-specific patent implementation evidence still needs review. Open-source publication may affect US and foreign rights; counsel must review the earliest disclosures, licenses and contributors.
Before an actual US filing: identify every inventor and any rights assignments, perform a prior-art review, complete the technical description and drawings, resolve disclosure deadlines and entity-fee eligibility, and authorize submission and payment through USPTO. A provisional is not examined and does not grant a patent; the appropriate follow-up normally must be arranged within 12 months to claim its benefit.
A US provisional application requires a detailed written description, any necessary drawings, inventor details, a cover sheet and the filing fee. The cover sheet alone is not an application. No patent has been filed or granted.
Discounts require eligibility; legal fees, drawings and additional-page fees are excluded.
Planning estimate, not a USPTO processing or approval promise. Attorney review may take longer.
File the appropriate follow-up to claim benefit. A provisional is not examined and never grants a patent by itself.
Existing public disclosures may affect US and foreign rights; obtain patent-attorney advice before filing. Patent costs are separate from the $150K SCF request. Fees checked 8 Nov 2026; confirm before payment.
STELLAR · MILESTONE-GATED REQUEST
| Phase | Requested budget | Deliverables | Approval / payment |
|---|---|---|---|
| T1 | $40,000 | Receipt registry, SDK & CLI Public receipt registry, SDK/CLI hardening, verifier specification and reference integration. | Not confirmed |
| T2 | $55,000 | Wallet & DEX protection Published threat model, Freighter pre-sign checks, DEX gating and anchor/PSP pilot integration. | Not confirmed |
| T3 | $55,000 | Explorer & adoption pilots Production release, public receipt explorer, dispute packs, target of five integration pilots and reported adoption metrics. | Not confirmed |
Submission dates were reported by the founder; confirmation receipts have not been independently verified. A CoreGuard inquiry is not an official SCF application. Existing Mainnet proofs are not tranche approvals. No award, payment or completion is claimed without evidence; each tranche requires reviewer acceptance.
Planned sustainability: per-receipt verification fees and B2B plans for anchors and payment providers. Requested budgets remain subject to SCF review.
COREGUARD × STELLAR · COLLABORATION
CoreGuard welcomes proposals from incubators, accelerators and ecosystem partners supporting execution integrity on Stellar. Proposed collaboration may include technical mentorship, product development, market access and introductions to wallet, DEX or infrastructure teams.
No account is required to submit. Partnership proposals are separate from funding inquiries. Submission does not establish a signed partnership, an incubation acceptance or an SCF award.
Submit an incubator partnership proposalTEAM ACCESS · REVIEWER INFORMATION
Reviewers can read the public Stellar evidence and funding terms without registering. Applicant details remain private; inquiry acceptance does not mean an SCF award or tranche payment.
