🏷️ Categories: bitcoin-dev
quoting naddr1qq…4pzs📝 Summary: Silent payment addresses should have an expiration date to prevent funds from being lost. Peter Todd suggests adding a 3-byte field to encode the expiration date. Brandon Black proposes encoding expiration dates in terms of days after an epoch using custom compact encoding. Samson Mow questions the 180-year limit and suggests a longer timeframe, providing historical examples.
👥 Authors: • Peter Todd ( Peter Todd [ARCHIVE] (npub1m23…2np2) ) • Brandon Black ( Brandon Black [ARCHIVE] (npub1txg…rmss) )
📅 Messages Date Range: 2023-08-04 to 2023-08-05
✉️ Message Count: 4
📚 Total Characters in Messages: 6758
Messages Summaries
✉️ Message by Peter Todd on 04/08/2023: Silent Payment addresses, which allow for multiple payments without privacy concerns, should have an expiration date to prevent funds from being lost forever. Adding a 3-byte field to encode the expiration date is a simple solution. Wallets should have a default expiration date and attempts to pay an expired address should fail.
✉️ Message by Brandon Black on 04/08/2023: Adding a field to silent payment addresses to encode expiration dates in terms of days after an epoch can fix the risk of non-expiring addresses in Bitcoin. Custom compact encoding can be used for different levels of granularity.
✉️ Message by Peter Todd on 05/08/2023: Adding a field to silent payment addresses to encode expiration dates is suggested, with different byte lengths for different granularities.
✉️ Message by Peter Todd on 05/08/2023: Samson Mow questions the 180-year limit for planning, suggesting a longer timeframe, and provides examples of historical inventions.
Follow Bitcoin Mailing List (npub15g7…08lk) for full threads
⚠️ Heads up! We've now started linking to replaceable long-form events (NIP-23), which allow for dynamic display of thread details like summaries, authors, and more. If you're unable to see this, your client may not support this feature yet.