1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
|
Delivery-date: Sat, 13 Sep 2025 12:46:15 -0700
Received: from mail-oo1-f59.google.com ([209.85.161.59])
by mail.fairlystable.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
(Exim 4.94.2)
(envelope-from <bitcoindev+bncBDXYRAG544BRB64TS7DAMGQEYAIXBAI@googlegroups.com>)
id 1uxWCM-0005mk-Mo
for bitcoindev@gnusha.org; Sat, 13 Sep 2025 12:46:15 -0700
Received: by mail-oo1-f59.google.com with SMTP id 006d021491bc7-6218a3bbe5csf2495791eaf.1
for <bitcoindev@gnusha.org>; Sat, 13 Sep 2025 12:46:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=googlegroups.com; s=20230601; t=1757792768; x=1758397568; darn=gnusha.org;
h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post
:list-id:mailing-list:precedence:reply-to:x-original-sender
:mime-version:subject:message-id:to:from:date:from:to:cc:subject
:date:message-id:reply-to;
bh=FEQwnOeJKGC0hPb8oUWkwcx3FPj4lfIhVTF2f/Po2eQ=;
b=FGkYqumt2lFi0XjESzbkCG0U/Fm5LaMWEi6rlvXNoVamdQhL+5quSuzSdYzvj9xd1J
ssO6ZeYoeeEcWIkdUMthEmwdstDIwmFxN76RxsUqVHTf5xoKrpM8BQGLzb29Gk5nhcHv
XoSD84ISfoS0Ny70G3xbZulRuc6kSHgicuOfmlkw+SB/29SxF+h0ya/HAkiITq/FqpVH
WVjFnKgzs6Tz5l8i5Px+4FLw0GyS4+H6Sus+mcfkZimI0Syi/Q2RfFtA67AKtc6mvWW8
3+tAfcIkuxhATJBxOq1iXKNPylId6iTDVQ5fWLQylJmCAlB2kH1Rh7TOSptCmAQHi3S+
7O/A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20230601; t=1757792768; x=1758397568;
h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post
:list-id:mailing-list:precedence:reply-to:x-original-sender
:mime-version:subject:message-id:to:from:date:x-beenthere
:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to;
bh=FEQwnOeJKGC0hPb8oUWkwcx3FPj4lfIhVTF2f/Po2eQ=;
b=HEhJjk69blu43SR0BMReD5UVDMw2b7orj8lP60OpbXVv5M6Dl+PfjyNQPr7crZOLvf
CfWUwuffGuqbetRgZ8gHjU3DKUkUTSgAZVuXQ/R4KtHp/ZG/aT4fofpwYwGm4w07E+rK
8V+fSlH7zNfp1g/rb3+7HOrHi6v4kcxnFqYhcU4l/JZGehrQQukTpjp37w9AhMJUKj+q
135xTmvQihninxm72DC6IiCKskSelp7hA4sQLgGzHyjHdQi+V1xfVmqCiWLOVAFJSxlw
1rdACdRY1AcP8uw5kznNZodDJv0jxeodqjYJ8VCwE8dJcYtBg//Q8BWcFr/tlbE+qDSR
rKog==
X-Forwarded-Encrypted: i=1; AJvYcCXmuoi+v1S3f7uBAhCET4gPz+ohBsjLWh33f4RA6qR9wWc+4QwglmdgYciIYC+XfcQ3Qb8FVKYkwX0a@gnusha.org
X-Gm-Message-State: AOJu0YwPaNRgkXCpCIKNCt4WWu7WbhytyGdLKv727ZsOil88oCoZLg3F
aT/ti4ETIULOFVKW0ZxAckQ5CejqdN5cagmYR+iROMsMRd9tr+3wlHdN
X-Google-Smtp-Source: AGHT+IHbtz5XQurXxjDMPwLHV1zLRn9DNvJA/DEM0CIV6rBrhftWW9GDM08HsMsGGM6NuncipaM6LQ==
X-Received: by 2002:a05:6808:2124:b0:438:1ca3:11f0 with SMTP id 5614622812f47-43b7baf3fe4mr5259958b6e.10.1757792768143;
Sat, 13 Sep 2025 12:46:08 -0700 (PDT)
X-BeenThere: bitcoindev@googlegroups.com; h=ARHlJd4MVr0J4JcnSL9b+qB6KAcNU9EPXT/i3oF19RAljCn/kg==
Received: by 2002:a05:6870:b620:b0:31d:642d:3aab with SMTP id
586e51a60fabf-32d03028ae5ls1799975fac.0.-pod-prod-08-us; Sat, 13 Sep 2025
12:46:02 -0700 (PDT)
X-Received: by 2002:a05:6808:19a9:b0:438:40c3:8759 with SMTP id 5614622812f47-43b8d9fad7emr3549545b6e.30.1757792762891;
Sat, 13 Sep 2025 12:46:02 -0700 (PDT)
Received: by 2002:a05:690c:6006:b0:723:969e:b18b with SMTP id 00721157ae682-7308ce16617ms7b3;
Sat, 13 Sep 2025 12:00:40 -0700 (PDT)
X-Received: by 2002:a05:690c:6b0e:b0:71e:759c:f7bc with SMTP id 00721157ae682-73064b0a307mr73439867b3.36.1757790039773;
Sat, 13 Sep 2025 12:00:39 -0700 (PDT)
Date: Sat, 13 Sep 2025 12:00:39 -0700 (PDT)
From: =?UTF-8?Q?=27Keyser_S=C3=B6ze=27_via_Bitcoin_Development_Mailing_List?= <bitcoindev@googlegroups.com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Message-Id: <06b5d067-7293-4618-b3c5-510380a55efan@googlegroups.com>
Subject: [bitcoindev] [BIP Proposal] Standard Encrypted Wallet Payload +
Standard Encryption Envelope formats
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="----=_Part_8688_1233915288.1757790039510"
X-Original-Sender: keys.soze@proton.me
X-Original-From: =?UTF-8?Q?Keyser_S=C3=B6ze?= <keys.soze@proton.me>
Reply-To: =?UTF-8?Q?Keyser_S=C3=B6ze?= <keys.soze@proton.me>
Precedence: list
Mailing-list: list bitcoindev@googlegroups.com; contact bitcoindev+owners@googlegroups.com
List-ID: <bitcoindev.googlegroups.com>
X-Google-Group-Id: 786775582512
List-Post: <https://groups.google.com/group/bitcoindev/post>, <mailto:bitcoindev@googlegroups.com>
List-Help: <https://groups.google.com/support/>, <mailto:bitcoindev+help@googlegroups.com>
List-Archive: <https://groups.google.com/group/bitcoindev
List-Subscribe: <https://groups.google.com/group/bitcoindev/subscribe>, <mailto:bitcoindev+subscribe@googlegroups.com>
List-Unsubscribe: <mailto:googlegroups-manage+786775582512+unsubscribe@googlegroups.com>,
<https://groups.google.com/group/bitcoindev/subscribe>
X-Spam-Score: -1.0 (-)
------=_Part_8688_1233915288.1757790039510
Content-Type: multipart/alternative;
boundary="----=_Part_8689_634330491.1757790039510"
------=_Part_8689_634330491.1757790039510
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Hi community,
I=E2=80=99m sharing two early draft BIPs aimed at improving wallet interope=
rability=20
and security in the Bitcoin ecosystem. Together, they address the absence=
=20
of an interoperable, canonical, secure format for wallet backups and=20
transfers.
*1. Standard Encrypted Wallet Payload*
A CBOR based format for serialising wallet data =E2=80=94 including=20
descriptor-based accounts, optional transactions/UTXOs, metadata, and root=
=20
secrets. It cleanly separates the core data structure from its=20
cryptographic protection, with encryption mandated via a companion=20
standard. This builds on BIPs 329, 380, 388, and 389, emphasising=20
extensibility and deterministic encoding to enable reliable restores across=
=20
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=
=20
derived key with Argon2id, with scope for future extensions such as=20
asymmetric encryption. It aims to provide robust protection while keeping=
=20
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=E2=80=99m seeking feedback on the =
overall=20
approach, technical details, potential gaps, and ways to improve them=20
before formalising further or submitting PRs to the BIPs repository.
Thanks in advance for your review and input.
--=20
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 e=
mail to bitcoindev+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/=
06b5d067-7293-4618-b3c5-510380a55efan%40googlegroups.com.
------=_Part_8689_634330491.1757790039510
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Hi community,<br /><br />I=E2=80=99m sharing two early draft BIPs aimed at =
improving wallet interoperability and security in the Bitcoin ecosystem. To=
gether, they address the absence of an interoperable, canonical, secure for=
mat for wallet backups and transfers.<br /><br /><b>1. Standard Encrypted W=
allet Payload</b><br />A CBOR based format for serialising wallet data =E2=
=80=94 including descriptor-based accounts, optional transactions/UTXOs, me=
tadata, and root secrets. It cleanly separates the core data structure from=
its cryptographic protection, with encryption mandated via a companion sta=
ndard. This builds on BIPs 329, 380, 388, and 389, emphasising extensibilit=
y and deterministic encoding to enable reliable restores across wallets.<br=
/>The draft BIP can be found here:<br />https://gist.github.com/KeysSoze/7=
109a7f0455897b1930f851bde6337e3<br /><br /><br /><b>2. Standard Wallet Encr=
yption Envelope</b><br />A secure, versioned container for encrypting the p=
ayload using a password derived key with Argon2id, with scope for future ex=
tensions such as asymmetric encryption. It aims to provide robust protectio=
n while keeping the format modular and library-agnostic.<br />The draft BIP=
can be found here:<br />https://gist.github.com/KeysSoze/866d009ccd082edf6=
802df240154b20d<br /><br /><br />Both drafts are at a very early stage. I=
=E2=80=99m seeking feedback on the overall approach, technical details, pot=
ential gaps, and ways to improve them before formalising further or submitt=
ing PRs to the BIPs repository.<br /><br />Thanks in advance for your revie=
w and input.
<p></p>
-- <br />
You received this message because you are subscribed to the Google Groups &=
quot;Bitcoin Development Mailing List" group.<br />
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to <a href=3D"mailto:bitcoindev+unsubscribe@googlegroups.com">bitcoind=
ev+unsubscribe@googlegroups.com</a>.<br />
To view this discussion visit <a href=3D"https://groups.google.com/d/msgid/=
bitcoindev/06b5d067-7293-4618-b3c5-510380a55efan%40googlegroups.com?utm_med=
ium=3Demail&utm_source=3Dfooter">https://groups.google.com/d/msgid/bitcoind=
ev/06b5d067-7293-4618-b3c5-510380a55efan%40googlegroups.com</a>.<br />
------=_Part_8689_634330491.1757790039510--
------=_Part_8688_1233915288.1757790039510--
|
