Reviews

Security & code reviews — the findings, unsoftened.

We publish what reviewers praised and what they challenged. That honesty is the product.

Back the next milestone

The $150K plan funds the gaps these reviews name: integrations and an independent audit.

Support the $150K request
External assessment2026-11-10

Executive review by an external reader

An external reviewer read the full repository. The assessment is recorded as received, with the actions it produced.

  • Problem strength: high · Architecture: promising · Security idea: important
  • Stellar: components and Mainnet experiments exist; general integration incomplete
  • No completed independent security audit and not enough evidence of external adoption yet
Read the full document on GitHub →
Self-review2026-11-12

PSAR/1 critical security self-review

Line-referenced review of the pre-sign receipt module and its tests, answering whether an untrusted party can forge a PASS.

  • A PASS cannot be forged without the issuer's Ed25519 private key
  • Verification re-derives the digest and signature instead of trusting the receipt
  • Explicitly a self-review — not an external audit
Read the full document on GitHub →
Readiness audit2026-11-11

Stellar institutional & SCF readiness audit

Measures code, execution and adoption directly from committed artifacts. Not a funding claim.

  • Code: yes · Execution: yes, with Mainnet artifacts
  • Fail-closed by construction: UNKNOWN never becomes ALLOW
  • Adoption: zero external integrators today — the gap the $150K plan targets
Read the full document on GitHub →
Threat model2026

Signed-envelope threat model — authorized ≠ signed ≠ submitted

Asks one question: is the transaction about to be signed exactly the one that was authorized, provable offline?

  • Code BUILT, field-by-field tamper matrix TEST_EXECUTED
  • Integration NOT_BUILT — no wallet has embedded it yet
  • Keys, custody and price correctness explicitly out of scope
Read the full document on GitHub →
State audit2026-09-25

Current-state audit of main

Machine-measured snapshot of the repository, enforced in CI so published numbers cannot drift.

  • Boundary audit PASS — 0 violations at the time
  • Test totals pinned to state-snapshot.json (now 1576)
  • External signals are never presented as endorsements
Read the full document on GitHub →

No completed independent security audit is claimed. VERIFIED means the evidence matches — never that a transaction was safe.