Roadmap

Now · Make the core easier to use and maintain

Remove redundant code and tests, shorten the guides, and make recovery limits explicit. Keep focused checks for cryptography, hostile inputs, and recovery failures.

One recorded iPhone journey covers an ordinary send, MuSig2 receive/send, and script-path 2-of-3 receive/send with Bitcoin Core cosigners. The private signet fixture mines automatically for prompt confirmation. That successful flow complements lower-level tests; it does not establish every failure case. Inspect the current recording and source →

Earlier proposals · Not scheduled

Recover through interruptions

Outcome: understandable recovery after an interrupted sync or payment. Ready when: restart, disconnect, fee replacement, stale backup, network switching, and chain-reorganization cases leave the screen, stored wallet, and peer-observed payment in agreement. Measure bandwidth, memory, and battery use on supported iPhones.

Broader beta

Outcome: a defined feature set with usable instructions. Ready when: new users complete everyday payments and recovery from those instructions, supported devices are defined, and reproducible critical findings have regression coverage. Pre-release builds use TestFlight.

Independent security review

Outcome: an inspectable review of a specific release. Ready when: blocking findings are fixed and verified, with the reviewed revision, exercised flows, and remaining limits published. A version number is not a security conclusion.

Research · Not planned

These are not supported features or automatic upgrades. Each needs its own implementation, review, and recovery evidence.

An optional P2WSH Safe

A separate, opt-in storage choice. It must demonstrate creation, receiving, backup, restoration on another installation, and withdrawal, including fresh change, exposure tracking, and refusal of damaged or incomplete backups. Limitations must be clear before funding. This proposal does not provide full post-quantum signing.

Signing devices and independent cosigners

Prove compatibility with the exact script, derivation, receiving address, signing exchange, and recovery process. Hardware evidence must identify the model, firmware, coordinator, and tested revision. Define who controls keys and backups, who can spend without the owner, and what happens when approval is refused or unavailable.

Winnow has no verified professional-cosigner or lending integration. Trusts, inheritance, and collateral arrangements need legal authority and key access to agree; Bitcoin only checks signatures. In a borrower–lender–key-agent 2-of-3, the lender and key agent could spend without the borrower. A label or signed statement cannot enforce repayment, succession, delay, or protection from coercion.

Tor and I2P

The app bundles no Tor or I2P client. It can route peer connections through Tor and I2P gateways the user runs on their own Tailscale network (gateway setup); without them it connects directly. Embedded Tor was removed in 0.7.1; its code and license inventory remain on the archive branch. Returning it requires review of the integration and dependencies, no silent direct fallback, and physical-iPhone checks across foreground, background, failure, and explicit off states.

The earlier I2P proposal called for a feasibility study: measure reliable tunnel startup, cold and warm starts, battery, bandwidth, and app-size cost for a foreground-only wallet. Tailscale gateway routing now covers the user-controlled external router; an embedded router remains unscheduled. The archived decision record supplies background; #164 records the decision not to pursue it.

Future network rules

P2MR research needs actual network enforcement, interoperability, recovery behavior, and a complete opt-in migration path before it becomes a release plan. A patched test network or prototype is not evidence of deployment on Bitcoin. No activation date is implied.