Pieter, thanks for your comments. Here my thoughts:
Pieter Wuille wrote on 8/29/21 9:24 AM:
On Saturday, August 28th, 2021 at 5:17 PM, ts via bitcoin-dev
wrote:
Following up on my original proposal, I would like to get some more feedback of
the community
to see if this could be realized at
Pieter Wuille wrote on 8/29/21 9:42 AM:
On Thursday, August 19th, 2021 at 1:02 PM, ts via bitcoin-dev
wrote:
In any case --- the last 5 characters of a bech32 string are already a
human-readable 5-digit code, with fairly good properties, why is it not usable
for this case?
Side note: it's
I fully agree with sipa and his reasoning that this proposal is not solving
any particular problem, but making it actually a bit worse.
Also, do you know what I hate more than copy&pasting bitcoin addresses?
Copy pasting zillion random fields for SEPA/wire transfers. And I believe
that a single co
Good morning Zac,
> Perhaps you could help me understand what would be required to implement the
> *unmodified* proposal. That way, the community will be able to better assess
> the cost (in terms of effort and risk) and weigh it against the perceived
> benefits. Perhaps *then* we find that th
Hi ZmnSCPxj,
Thank you for your helpful response. We're on the same page concerning
privacy so I'll focus on that. I understand from your mail that privacy
would be reduced by this proposal because:
* It requires the introduction of a new type of transaction that is
different from a "standard" tr
Good morning Zac,
> Hi ZmnSCPxj,
>
> Thank you for your helpful response. We're on the same page concerning
> privacy so I'll focus on that. I understand from your mail that privacy would
> be reduced by this proposal because:
>
> * It requires the introduction of a new type of transaction that
Hi list!
I am proposing to register the following MIME (RFC 2046) media types with the
IANA:
bitcoin/psbt
- aka. a BIP-174 file, in binary
- does not make any claims about signed/unsigned status; lets leave that to
the file
bitcoin/txn
- aka. wire-ready fully-signed transaction
Hi Peter,
It would be nice to have mime types registered for Bitcoin things, but
I'm not sure that it will be possible, at least not in the way that we
would like. I tried doing this with "application/bitcoin-psbt" back in
2019 but it was not accepted. From that attempt, here is what I have
learne
Note that a number of wallet companies are now supporting the UR encoded
version of PSBTs, allowing for better QR & Airgap solutions, and also
leverage CBOR which is an IETF standard.
We have a community of Airgap wallet developers at
https://github.com/BlockchainCommons/Airgapped-Wallet-Community
QR Codes do not use IANA mime-types.
If anyone wanted to use UR encoding for PSBT data in a web context (http),
NFC, or email, it would probably be best to discourage them.
While I can understand the need for UR encoding in animated QR
codes, I don't think any other use-case could justify introdu
On Tue, Aug 31, 2021 at 12:18 PM Peter D. Gray wrote:
> QR Codes do not use IANA mime-types.
>
> If anyone wanted to use UR encoding for PSBT data in a web context (http),
> NFC, or email, it would probably be best to discourage them.
>
> While I can understand the need for UR encoding in animate
11 matches
Mail list logo
