CoreGuardCoreGuard
$150K · SCF #46★ Stellar Mainnet LIVE

Stellar: Soroban commit + first funded gated swap (ledger 65,338,112) — requesting $150K

Open the Stellar page Apply / back the $150K request
← Launch kit

CoreGuard — US provisional preparation template

DRAFT — NOT FILED. Not an official USPTO form, legal opinion, or filing-ready specification.

This worksheet accompanies the official PTO/SB/16 cover sheet. A cover sheet alone is insufficient. Complete the missing facts and obtain a patent professional's review before submission through USPTO Patent Center. Do not send personal inventor information through CoreGuard's public funding form.

1. Cover-sheet details to supply privately

  • Proposed invention title: Fail-closed intent-to-execution verification using ledger-anchored commitments and replayable receipts.
  • Inventor legal name(s): [TO BE PROVIDED — name every actual inventor].
  • Each inventor's city and state/country of residence: [TO BE PROVIDED].
  • Correspondence name, postal address, telephone and email: [TO BE PROVIDED].
  • Applicant/ownership and assignments: [VERIFY WITH COUNSEL — CoreGuard is a brand, not evidence of inventorship or legal ownership].
  • Entity status: [LARGE / SMALL / MICRO — determine eligibility; attach certification where required].
  • US government funding/support: [TO BE CONFIRMED].
  • Enclosures: written specification [page count]; necessary drawings [sheet count]; cover sheet; fee/payment details.
  • Authorized signature and date: [SIGN ONLY AFTER REVIEW]. Never place payment-card data in the specification.

2. Technical disclosure to expand

Field and problem

Describe how systems compare an authorized transaction intent with actual execution. Explain concrete deficiencies in existing systems, with citations and no unsupported novelty claims.

Proposed method — discussion outline only

  1. Represent intent, signer, permitted assets, amounts, recipient, expiry and policy version.
  2. Evaluate policy before signing/broadcast; specify ALLOW, DENY, HOLD and failure handling.
  3. Canonicalize and hash the intent and policy result; specify fields, encoding, algorithms and domain separation.
  4. Bind the commitment to a ledger anchor and identifier; explain ordering, authentication and replay protection.
  5. Recover actual execution amounts, fees and transaction identifiers; compare them with the authorization.
  6. Produce a receipt and an independent verifier; specify PASS/FAIL conditions and incomplete-data handling.

Required drafting work: supply sufficient implementation detail for a skilled person to make and use the invention; explain every contemplated feature and alternative you may later claim. Generic headings, a repository link and screenshots are not a substitute for an enabling written description. Later new matter cannot simply be added while retaining the original date.

Embodiments and drawings

  • Figure 1: intent → policy evaluation → signing/broadcast or refusal.
  • Figure 2: commitment anchoring and receipt verification sequence.
  • Figure 3: Stellar/Soroban implementation with full interfaces and error paths.
  • Figure 4: Core DAO implementation with ledger-specific differences.
  • Figure 5: replay, stale data, reorg/finality, duplicate requests and compromised-signer handling.

Provide numbered drawings, explanatory text, example structures, pseudocode and alternatives. Validate the actual execution order rather than assuming all transactions occur in one atomic operation.

3. Evidence and disclosure history

  • Stellar commit transaction: 69044807410f65027c1227f4e525ad83f23a6cb1a2bb79790d82849c5dbc9fec, ledger 65,337,373, 6 Nov 2026 13:48:27 UTC.
  • Stellar swap transaction: ac2a7990b3387aab96b197c0c921d57756bd25d65ad0e75b93561ded640b9097, ledger 65,338,112, 6 Nov 2026 14:50:02 UTC.
  • Horizon confirms transaction success and swap amounts; policy checks and offline replay are separate repository evidence, not network-certified patent claims.
  • Core DAO implementation evidence: [LIST EXACT FILES, TRANSACTIONS AND DATES AFTER REVIEW].
  • First GitHub/public disclosure, demo, website publication, sale/offer and all third-party contributions: [LIST ALL DATES AND AUTHORS].

Public disclosures may destroy foreign rights and trigger US deadlines. The US inventor-disclosure grace period is limited and fact-dependent; do not assume it protects this invention or permits delay. Seek counsel promptly. Blockchain timestamps establish transaction events, not patent priority, novelty or inventorship.

4. Costs and timing

USPTO provisional filing fees checked 8 Nov 2026: $325 large / $130 small / $65 micro entity, subject to eligibility. If specification and drawings exceed 100 sheets, the current additional-size fee is $450 / $180 / $90 per additional 50 sheets or fraction. Legal drafting, searching, drawings, translation, later nonprovisional/PCT work and other charges are separate; request written quotes. No professional-fee total has been verified.

Preparation planning estimate: 2–4 weeks after inventor information and technical materials are complete, potentially longer after review. This is not an official processing estimate. A qualifying provisional receives a filing date under USPTO rules, is not examined for patentability and does not grant a patent. File an appropriate follow-up within 12 months to claim benefit; docket the deadline with counsel. Do not describe the invention as patented; do not use patent pending before a qualifying application is actually filed.

Patent costs are not included in CoreGuard's $150,000 SCF budget. No filing, payment or application number is claimed.

Official sources