public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed

From: "'Keyser Söze' via Bitcoin Development Mailing List" <bitcoindev@googlegroups.com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: [bitcoindev] [BIP Proposal] Standard Encrypted Wallet Payload + Standard Encryption Envelope formats
Date: Sat, 13 Sep 2025 12:00:39 -0700 (PDT)	[thread overview]
Message-ID: <06b5d067-7293-4618-b3c5-510380a55efan@googlegroups.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1897 bytes --]

Hi community,

I’m sharing two early draft BIPs aimed at improving wallet interoperability 
and security in the Bitcoin ecosystem. Together, they address the absence 
of an interoperable, canonical, secure format for wallet backups and 
transfers.

*1. Standard Encrypted Wallet Payload*
A CBOR based format for serialising wallet data — including 
descriptor-based accounts, optional transactions/UTXOs, metadata, and root 
secrets. It cleanly separates the core data structure from its 
cryptographic protection, with encryption mandated via a companion 
standard. This builds on BIPs 329, 380, 388, and 389, emphasising 
extensibility and deterministic encoding to enable reliable restores across 
wallets.
The draft BIP can be found here:
https://gist.github.com/KeysSoze/7109a7f0455897b1930f851bde6337e3


*2. Standard Wallet Encryption Envelope*
A secure, versioned container for encrypting the payload using a password 
derived key with Argon2id, with scope for future extensions such as 
asymmetric encryption. It aims to provide robust protection while keeping 
the format modular and library-agnostic.
The draft BIP can be found here:
https://gist.github.com/KeysSoze/866d009ccd082edf6802df240154b20d


Both drafts are at a very early stage. I’m seeking feedback on the overall 
approach, technical details, potential gaps, and ways to improve them 
before formalising further or submitting PRs to the BIPs repository.

Thanks in advance for your review and input.

-- 
You received this message because you are subscribed to the Google Groups "Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bitcoindev+unsubscribe@googlegroups•com.
To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/06b5d067-7293-4618-b3c5-510380a55efan%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 2208 bytes --]

                 reply	other threads:[~2025-09-13 19:46 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=06b5d067-7293-4618-b3c5-510380a55efan@googlegroups.com \
    --to=bitcoindev@googlegroups.com \
    --cc=keys.soze@proton$(echo .)me \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox