Seedless Wallet Infrastructure for Bitcoin Cash

Seedless Wallet Infrastructure for Bitcoin CashWhen Satoshi released Bitcoin Cash, it was miles ahead of what existed: a simple, open way to send money instantly to anyone, anywhere - without banks and gatekeepers. However, over the years, smartphones, internet banking, and apps like Venmo and Cash App have closed the convenience gap, despite being tangled in the same problems of modern finance. Moreover, people’s expectations have shifted: passwordless logins and Face ID taught the world that security can be both strong and effortless.Fortunately, BCH is now among only a handful of cryptocurrencies capable of bridging that gap due to the upcoming May 2026 Layla Upgrade. I have tested and developed a low-cost contract that supports modern device-backed signing keys (P-256), dramatically lowering the barrier to entry and improving the user experience and convenience. ide.bitauth.com/import-gist/16786d7eaf81d509ad907705f057f8faOnce deployed, a new generation of users, social apps, and non-crypto communities will be able to send, receive, and manage BCH, Cashtokens, and Identity on-chain without having to manage secrets.ProposalThis proposal funds the creation of seedless, device-bound wallets for Bitcoin Cash using P-256 (secp256r1) keys, backed by hardware security modules.The work includes:Production-ready P256 Smart Contract on the BCH VMBuilding a reference CLI vault wallet for macOSCreating a fork of Cashonize that requests WebAuthn P-256 signaturesPublishing a JavaScript library enabling developers to easily build seedless BCH wallet flowsThe result is a dramatically lower barrier to entry for users, with wallets that can be hardware-backed, seedless, cloud-recoverable, and familiar to non-crypto audiences.Funding request: 35 BCHDuration: ~4 months active development + cleanup/publishingGoal: Have working reference implementations before the May network upgrade.Progress: https://github.com/SeedlessBCH/signatures.cashMotivationToday, Bitcoin Cash wallets still rely primarily on seed phrases, which are confusing for new users, easy to lose or mishandle, and a major source of anxiety and technical burden.Nearly all modern devices already support secure, hardware-backed cryptography via:Apple Secure EnclaveAndroid StrongBox and KeystoreWindows TPMYubiKeysOS-level secure key storage as a fallbackBy enabling P-256 directly on the BCH VM, we unlock:Seedless wallets tied to a deviceOptional cloud backup on device restore (platform dependent)Familiar UX patterns similar to Apple Pay, passkeys, and modern passwordless login.This undertaking will be a crucial step toward making BCH usable for non-technical users, non-crypto communities, and real-world applications. The vision is to enable these users to onboard quickly and seamlessly, transacting either with BCH or CashTokens.As a BCH Developer with over 5 years of experience building BCH Applications and Smart Contracts, I will be able to achieve this by May 15 upgrade with your support.Scope of Work1. P-256 Smart Contract (Already Implemented)Finalize and document the existing P-256 Smart Contract implementationProvide example scripts and test vectorsThis is already complete but will need to be polished, documented, and made ready for developer use.2. macOS CLI Secure Vault (Reference Application)Command-line vault application for macOSUses OS-backed or hardware-backed P-256 keysNo seed phrase requiredThis serves as a reference and proof that BCH can function without mnemonic seeds.3. Cashonize Fork with WebAuthn P-256 SigningFork Cashonize to request WebAuthn signatures (assertions) using P-256Supports platform authenticators (Touch ID / Face ID / Windows Hello / TPM, etc.)The WebAuthn private key never leaves the authenticator (no key export)Extends the P-256 Smart Contract to parse and validate that a transaction is authorized by verifying:The returned P-256 signatureThe associated client data and authenticator dataThis demonstrates browser-based, seedless BCH wallets using the same primitives as passkeys and passwordless login.4. Publish JavaScript LibraryUnified JS library exposing:P-256 script templates for BCHWebAuthn signing / assertion handlingCLI and browser reference integrationsThis is designed for reuse across wallets, apps, and services.Stretch Goal: OAuth-Based Onboarding (Optional)In addition to a seedless wallet, it will also be possible to implement a novel onboarding method for new users by adding P-256 Smart Contracts, namely the ability to send funds to a specific Google or Apple ID that can be unlocked only by providing a valid OAuth response from the OpenID Provider. On spend, the coins are moved to a new device-bound secure signing (WebAuthn / platform keys).This enables flows like:“Send BCH to someone who only has a Google/Apple login — no wallet setup required.”TimelineMonth 1: Finalize P-256 Smart Contract, documentation, example vectorsMonth 2: macOS CLI vault wallet implementationMonth 3: Cashonize WebAuthn signing forkMonth 4: Cleanup, docs, and publishing JS library for all functionalityTarget: have working reference apps before the May upgrade.Funding Request35 BCH to complete Phase 1.This covers:Engineering timeReference implementationsDocumentation and test vectorsOpen-source publishing and maintainabilityOngoing support, upgrades, and consultation to integrate with popular BCH Wallets.ClosingBitcoin Cash can significantly reduce onboarding friction by embracing modern, hardware-backed cryptography and seedless flows, without turning the ecosystem into a custodial one.This proposal delivers immediate usability improvements, strong developer tooling, and a foundation for identity-linked and privacy-enhancing applications.Thank you for your support! Telegram: @sahidmiller