From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.osuosl.org (smtp1.osuosl.org [IPv6:2605:bc80:3010::138]) by lists.linuxfoundation.org (Postfix) with ESMTP id BA2D0C0039 for ; Thu, 23 Nov 2023 22:26:12 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp1.osuosl.org (Postfix) with ESMTP id A83B282077 for ; Thu, 23 Nov 2023 22:26:11 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp1.osuosl.org A83B282077 Authentication-Results: smtp1.osuosl.org; dkim=pass (2048-bit key, unprotected) header.d=seedhammer.com header.i=@seedhammer.com header.a=rsa-sha256 header.s=protonmail2 header.b=It65La6k X-Virus-Scanned: amavisd-new at osuosl.org X-Spam-Flag: NO X-Spam-Score: -2.1 X-Spam-Level: X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Received: from smtp1.osuosl.org ([127.0.0.1]) by localhost (smtp1.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qgSqNCvC4vUQ for ; Thu, 23 Nov 2023 22:26:10 +0000 (UTC) X-Greylist: delayed 2247 seconds by postgrey-1.37 at util1.osuosl.org; Thu, 23 Nov 2023 22:26:09 UTC DKIM-Filter: OpenDKIM Filter v2.11.0 smtp1.osuosl.org 460418204D Received: from mail-4018.proton.ch (mail-4018.proton.ch [185.70.40.18]) by smtp1.osuosl.org (Postfix) with ESMTPS id 460418204D for ; Thu, 23 Nov 2023 22:26:09 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=seedhammer.com; s=protonmail2; t=1700778366; x=1701037566; bh=hwCHTCMLA4HfWWehRTjloD9OrO3e/fqazpbqUdZBLvc=; h=Date:To:From:Subject:Message-ID:Feedback-ID:From:To:Cc:Date: Subject:Reply-To:Feedback-ID:Message-ID:BIMI-Selector; b=It65La6kiJdBJREybkBv+RcDArW1I578b9IFEWS83JkgyKIWj9afI8IIPoffufX2S L8E/YG7V/HJoJcIUrib3gQeS3UOkU9LAxbQLKeMA1XtSLRyOiL/8zMgX8bcs2xFUj9 C2JENTLrVxp0ZDjhvZqlRXykl0ZWHZMycqeODOksSieAVgq81LXN0qklVf4pTC9oIO Ps0+B1Ym7LJyJydEW4HJH+TTXBHPYdpRUhLYixRqcZuSvObc1qkwdd5IZCk/+GOJ7g iXabIDOGGbMTAKla8MU86uY2+lVDcVs23ix6bOKb9/j9Tb/Uq7FHBxqITI/ygJ7R6L nGPrKM7ZSeUdQ== Date: Thu, 23 Nov 2023 22:25:43 +0000 To: "bitcoin-dev@lists.linuxfoundation.org" From: SeedHammer Team Message-ID: <_pNFQS1xsa8HZF-9x3hk8EBZRfYAbzCAha1rKaFbwpfqMqjK51rGQspALrdYvB0R0r90iReLLsktJOfFowJG-wkX3E1NvPwtEQyMT95uo_4=@seedhammer.com> Feedback-ID: 63600324:user:proton MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Mailman-Approved-At: Fri, 24 Nov 2023 14:30:21 +0000 Subject: [bitcoin-dev] A proposal for a "PSBT for descriptors" format X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Bitcoin Protocol Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Nov 2023 22:26:12 -0000 Hi, At SeedHammer we're interested in standard, compact output descriptors to m= ake self-contained metal engraved backups feasible. To that end, we're proposin= g a descriptor format based on the PSBT binary encoding. The format has not rea= ched widespread consensus, never mind adoption, so at this point we're solicitin= g comments before formally proposing it as a BIP. See [proposal], [implementation] and [playground] for details and examples. The format is a binary and compact serialization specification for the [wallet-policies] BIP. Features: - Based on the binary [BIP174] PSBT format, including re-using the compact PSBT_GLOBAL_XPUB encoding for extended keys. - The descriptor itself is encoded in the same textual format as described in BIPs 380-386 (+389). - Key references (always) use the wallet-policies format @. - Miniscript is trivially supported, except inline keys are not allowed, an= d pk(NAME) expressions are replaced with indexed (@) key references. - Metadata such as labels and birthdate blocks are encoded as PSBT map entries. Known issues: - CBOR vs PSBT. Blockchain Commons believes[0] that a CBOR based format is = better because it is a widely used binary encoding standard, whereas we believe = the complexity of CBOR doesn't justify its cost compared to the PSBT encoding already widely supported by wallet software. - The proposal specifies a separate header and magic; should the format ins= tead be an extension to the PSBT format? Thanks, E [proposal] https://github.com/BlockchainCommons/Research/issues/135 [implementation] https://github.com/seedhammer/bip-serialized-descriptors [playground] https://go.dev/play/p/nouZlbbcEWt [wallet-policies] https://github.com/bitcoin/bips/blob/bb98f8017a883262e031= 27ab718514abf4a5e5f9/bip-wallet-policies.mediawiki [BIP174] https://github.com/bitcoin/bips/blob/master/bip-0174.mediawiki [0] https://github.com/BlockchainCommons/Research/issues/135#issuecomment-1= 789644032