Kalle Rosenbaum [ARCHIVE] on Nostr: 📅 Original date posted:2015-06-06 📝 Original message:>> The idea is to simplify ...
📅 Original date posted:2015-06-06
📝 Original message:>> The idea is to simplify implementation. Existing software can be used
>> as is to sign and validate PoPs. But I do agree that it would be a
>> cleaner specification if we would make the PoP invalid as a
>> transaction. I'm open to changes here. I do like the idea to prepend a
>> constant string. But that would require changes in transaction signing
>> and validation code, wouldn't it?
>
>
> Yes, of course. An alternative is adding a 21M BTC output at the end, or
> bitflipping the txin prevout hashes, or another reversible transformation on
> the transaction data that is guaranteed to invalidate it.
If we do decide to make Pops invalid as transactions, there are a lot
of ways to do that. I guess the main question is if we should make
Pops invalid as transactions or not. So far I prefer to keep them
valid for the above reason.
>
> I think that the risk of asking people to sign something that is not an
> actual transaction, but could be used as one, is very scary.
>
I would feel comfortable doing it. It's just a matter of trusting your
wallet, which you already do with your ordinary transactions.
>>
>> > Also, I would call it "proof of transaction intent", as it's a
>> > commitment to
>> > a transaction and proof of its validity, but not a proof that an actual
>> > transaction took place, nor a means to prevent it from being double
>> > spent.
>>
>>
>> Naming is hard. I think a simpler name that explains what its main
>> purpose is (prove that you paid for something) is better than a name
>> that exactly tries to explain what it is.
>
>
> "Proof of Payment" indeed does make me think it's something that proves you
> paid. But as described, that is not what a PoP does. It proves the ability
> to create a particular transaction, and committing to it. There is no actual
> payment involved (plus, payment makes me think you're talking about BIP70
> payments, not simple Bitcoin transactions).
>
>>
>> "Proof of transaction
>> intent" does not help me understand what this is about. But I would
>> like to see more name suggestions. The name does not prevent people
>> from using it for other purposes, ie internet over telephone network.
>
>
> I don't understand why something like "Proof of Transaction Intent" would be
> incompatible with internet over telephone network either...
>
No, I meant that it's ok to call it Proof of Payment even though
people may use it for other stuff.
> --
> Pieter
>
Published at
2023-06-07 15:36:49Event JSON
{
"id": "247b30ad51ccea9aae50d0c837cc4a5a8781e21df1fe60ce296c2b6cb0f80838",
"pubkey": "e39d9ce3b0ed9cbb17528b25bb4b33bcee465476e44ea5980fb6f2693b97ab95",
"created_at": 1686152209,
"kind": 1,
"tags": [
[
"e",
"e1766602ba0f6768319a1583d11fb84dd1782fa79b735d969ef1342e648fd1da",
"",
"root"
],
[
"e",
"bfcd6f4841ab9a7c4b211fba913e1167bf2d1e0a7410d91a2942a36fb2f302fc",
"",
"reply"
],
[
"p",
"5cb21bf5d7f25a9d46879713cbd32433bbc10e40ef813a3c28fe7355f49854d6"
]
],
"content": "📅 Original date posted:2015-06-06\n📝 Original message:\u003e\u003e The idea is to simplify implementation. Existing software can be used\n\u003e\u003e as is to sign and validate PoPs. But I do agree that it would be a\n\u003e\u003e cleaner specification if we would make the PoP invalid as a\n\u003e\u003e transaction. I'm open to changes here. I do like the idea to prepend a\n\u003e\u003e constant string. But that would require changes in transaction signing\n\u003e\u003e and validation code, wouldn't it?\n\u003e\n\u003e\n\u003e Yes, of course. An alternative is adding a 21M BTC output at the end, or\n\u003e bitflipping the txin prevout hashes, or another reversible transformation on\n\u003e the transaction data that is guaranteed to invalidate it.\n\nIf we do decide to make Pops invalid as transactions, there are a lot\nof ways to do that. I guess the main question is if we should make\nPops invalid as transactions or not. So far I prefer to keep them\nvalid for the above reason.\n\n\u003e\n\u003e I think that the risk of asking people to sign something that is not an\n\u003e actual transaction, but could be used as one, is very scary.\n\u003e\n\nI would feel comfortable doing it. It's just a matter of trusting your\nwallet, which you already do with your ordinary transactions.\n\n\u003e\u003e\n\u003e\u003e \u003e Also, I would call it \"proof of transaction intent\", as it's a\n\u003e\u003e \u003e commitment to\n\u003e\u003e \u003e a transaction and proof of its validity, but not a proof that an actual\n\u003e\u003e \u003e transaction took place, nor a means to prevent it from being double\n\u003e\u003e \u003e spent.\n\u003e\u003e\n\u003e\u003e\n\u003e\u003e Naming is hard. I think a simpler name that explains what its main\n\u003e\u003e purpose is (prove that you paid for something) is better than a name\n\u003e\u003e that exactly tries to explain what it is.\n\u003e\n\u003e\n\u003e \"Proof of Payment\" indeed does make me think it's something that proves you\n\u003e paid. But as described, that is not what a PoP does. It proves the ability\n\u003e to create a particular transaction, and committing to it. There is no actual\n\u003e payment involved (plus, payment makes me think you're talking about BIP70\n\u003e payments, not simple Bitcoin transactions).\n\u003e\n\u003e\u003e\n\u003e\u003e \"Proof of transaction\n\u003e\u003e intent\" does not help me understand what this is about. But I would\n\u003e\u003e like to see more name suggestions. The name does not prevent people\n\u003e\u003e from using it for other purposes, ie internet over telephone network.\n\u003e\n\u003e\n\u003e I don't understand why something like \"Proof of Transaction Intent\" would be\n\u003e incompatible with internet over telephone network either...\n\u003e\n\nNo, I meant that it's ok to call it Proof of Payment even though\npeople may use it for other stuff.\n\n\u003e --\n\u003e Pieter\n\u003e",
"sig": "48161c03279fbb72825345d9a07a4f79ac622e478cdd94c535176aa558b4add8fa706fe65cea26c4edbe2e4186f478159e340db9ede932405f438add303e3bc6"
}