Oath
Updated September 28, 2026 · public source 4.0.0 (73)
What is available in the public 4.0.0 release?
The published 4.0.0 source release (build 73) explicitly disables Silent Payments receiving and discovery pending a reviewed local scanner. Existing discovered outputs can be exported and spent. A fresh restore cannot discover unseen Silent Payments. These are release-specific statements from the public README, reviewed on September 28, 2026. Source publication does not establish a verified match to a separately distributed App Store binary.
Do not use an old screenshot as a support guarantee
Earlier versions of this article illustrated a remote scanning design and a Silent Payments receive selector in version 2.40.12. Those screenshots do not establish support in the public 4.0.0 release. The old instructions to enable receiving or rely on remote discovery have been removed. Check the release notes and actual capabilities of the version you use before sharing a payment instruction.
How Silent Payments differ from an ordinary Bitcoin address
BIP352 lets a receiver publish reusable payment information while compatible senders derive distinct Taproot output scripts. The reusable instruction is not an ordinary on-chain receive address. Receiving requires finding the relevant outputs through scanning; a conventional address lookup alone does not supply that discovery. Sending, receiving, scanning and restoring are separate capabilities and must be evaluated separately.
Before moving or restoring an existing wallet
Keep the source device available. The public release blocks direct device transfer when known Silent Payments outputs exist. Follow the supported output-key export path for already discovered outputs before changing devices, and keep any exported material private. A recovery phrase can reproduce base credentials without automatically reconstructing all undiscovered output information in a release whose scanner is unavailable. Do not erase the old device based only on a successful phrase import.
Which receiving method should you use instead?
Use a conventional Bitcoin receive format supported by both Oath and the sending service, such as Native SegWit or Taproot where supported. Choose the address from the intended account and verify the network. Read the Bitcoin address guide and fresh-address explanation for the difference between account recovery and normal address rotation.
Privacy has more than one boundary
Distinct output scripts do not make the entire wallet anonymous. A scanner design determines who can learn viewing information; network providers can observe public queries; payment descriptions and counterparties can reveal relationships. Never interpret the words self-custody or Silent Payments as a blanket anonymity guarantee. The security page documents the public source boundaries.
How to check a future release
Look for an explicit release statement covering sending, receiving, scanning, backup and recovery. Verify that the public source and documentation identify the version being described. If receiving or discovery is still unavailable, do not publish an sp1 instruction expecting the wallet to find new payments. A directory entry or an old product demonstration is not a substitute for those checks.
Sources and practical next steps
Read the pinned release README, audit scope and BIP352 specification. For other recovery methods, use the backup guide, new iPhone guide and import-method guide. Support will never need your recovery phrase, private key or passkey.
