Skip to content

OathConnect 0.3.0-alpha.3 — Solana network evidence

Pre-release
Pre-release

Choose a tag to compare

@OathWallet OathWallet released this 30 Oct 22:24
· 2 commits to main since this release
84def29

Development preview with public Solana network receipts and reproducible finality checks. This release does not enable production use or integrate Oath Wallet.

  • A free-funded 0.001 SOL transfer completed through the local relay on Solana devnet (slot 516914340). A separate transfer completed through the deployed Cloudflare relay on Solana testnet (slot 458656746). Each used one approval, one signature and one submission, with a 5,000-lamport fee and the expected recipient increase.
  • Read-only reconciliation verified signatures, fixed messages, receipt effects and agreement with provider-reported finalized status. It never resubmits; provider assertions do not independently prove consensus. Earlier stopped and unsuccessful attempts remain public.
  • The fixed Solana fixture pins cluster endpoints, genesis hashes and capabilities, uses unsigned simulation, retains the public signature before a single submission, and verifies the exact receipt. It is not a reusable general-purpose Solana adapter.
  • Includes the earlier deployed native Sepolia receipt and adversarial finality reconciliation tests. Fuji/BNB probes were read-only and do not establish transaction qualification.
  • Temporary validation access was disabled through GitHub deployment. An existing still-valid grant and a fresh grant were rejected; the private issuer file was removed.

Validation: 48 core TypeScript/Cloudflare tests, 21 Solana tests, 5 EVM finality tests, 16 Swift SDK host tests, 1 Swift fixture host test and 3 JavaScript fixture tests. CodeQL security-extended and dependency audits passed. All four exact CI package archives were installed together and checked in a fresh consumer project. Native sources remain unchanged from the earlier generic iOS build; no simulator or physical device checks were run.

Download the four package archives together; they are not published to the npm registry. SHA256SUMS covers the archives and RELEASE-EVIDENCE.json, which links the exact source, successful CI, deployment and scoped public receipts.

Remaining: other chain/method tests, THORChain swaps, operational qualification, independent security audit and remediation verification. No zero-bug or production-safety claim is made.