There is already a JSON standard that has been already used in the wild for
the last 7 years described in SLIP-0015 (mentioned by Clark in this
thread). No need to reinventing the wheel again.
On Wed 24. 8. 2022 at 21:44, Ryan Havar via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
Hi Craig,
This a really good proposal. I studied your BIP and I have some feedback on
some parts of it.
> The first line in the file is a header, and should be ignored on import.
>From past experience and lessons, most notably BIP39, it is important that a
>version byte is defined somewhere
I'd strongly suggest not using CSV. Especially for a standard. I've worked with
it as an interchange format many a times, and it's always been a clusterfuck.
Right off the bat, you have stuff like "The fields may be quoted, but this is
unnecessary as the first comma in the line will always be
On 2022-08-24 (Wed) at 11:18:43 +0200, Craig Raw via bitcoin-dev wrote:
> I would like to propose a BIP that specifies a format for the export and
> import of labels from a wallet. While transferring access to funds across
> wallet applications has been made simple through standards such as BIP39,
Craig,
Thanks for the proposal.
How does this proposal compare with SLIP-0015, which provides encryption by
default? Would it be worth exploring a merge of the two approaches?
https://github.com/satoshilabs/slips/blob/master/slip-0015.md
Clark
--- Original Message ---
On Wednesday,
Hi all,
I would like to propose a BIP that specifies a format for the export and
import of labels from a wallet. While transferring access to funds across
wallet applications has been made simple through standards such as BIP39,
wallet labels remain siloed and difficult to extract despite their
