📅 Original date posted:2011-10-29
🗒️ Summary of this message: Gavin Andresen suggests using a new type of bitcoin address built on top of OP_EVAL for easy support of existing infrastructure.
📝 Original message:RE: buying me and Gregory a shared beer:
> I would make a "both of two" btc-addresses script transaction using OP_EVAL. And post it.
> You would then not be able to know that you actually got a beer unless I told you so in a mail.
But that transaction won't show up in my bitcoin wallet as bitcoins I can spend.
And even if my wallet DID show me "transactions that involve your keys
but that you can't spend," all I would know is there are N bitcoins
that I can only spend if I can somehow figure out that Gregory has
public key XYZ.
How would I know that unless you told me?
I think the right long-term solution is moving away from bitcoin
addresses as 'pay-to entity' and create an infrastructure where we're
paying people or organizations. But in the short term, I think there
are lots of benefits to creating a new type of bitcoin address built
on top of OP_EVAL that will be very easy for all of our existing
infrastructure to support.
--
--
Gavin Andresen
Gavin Andresen [ARCHIVE] /
npub1s4…d44kw
2023-06-07 02:35:55
in reply to nevent1q…lzds
Author Public Key
npub1s4lj77xuzcu7wy04afcr487f0r3za0f8n2775xrpkld2sv639mjqsd44kwPublished at
2023-06-07 02:35:55Event JSON
{
"id": "2c600ca33755608c86fbe523a518594eaa4c982517d5e0c3644f4cf93f1c20b8",
"pubkey": "857f2f78dc1639e711f5ea703a9fc978e22ebd279abdea1861b7daa833512ee4",
"created_at": 1686105355,
"kind": 1,
"tags": [
[
"e",
"38ab95ef62f6301977f9dec6ff3b1f25746d558345bec15abbd412157a28a77b",
"",
"root"
],
[
"e",
"cf9d439cf0056ec77ad7f6721e05fce032bac19cc75c2e5f5dc135db6a30bcb7",
"",
"reply"
],
[
"p",
"a277336e95d2d0a831fff67fc80d8082322689a88ede9f877fa246a02629a43f"
]
],
"content": "📅 Original date posted:2011-10-29\n🗒️ Summary of this message: Gavin Andresen suggests using a new type of bitcoin address built on top of OP_EVAL for easy support of existing infrastructure.\n📝 Original message:RE: buying me and Gregory a shared beer:\n\n\u003e I would make a \"both of two\" btc-addresses script transaction using OP_EVAL. And post it.\n\u003e You would then not be able to know that you actually got a beer unless I told you so in a mail.\n\nBut that transaction won't show up in my bitcoin wallet as bitcoins I can spend.\n\nAnd even if my wallet DID show me \"transactions that involve your keys\nbut that you can't spend,\" all I would know is there are N bitcoins\nthat I can only spend if I can somehow figure out that Gregory has\npublic key XYZ.\n\nHow would I know that unless you told me?\n\nI think the right long-term solution is moving away from bitcoin\naddresses as 'pay-to entity' and create an infrastructure where we're\npaying people or organizations. But in the short term, I think there\nare lots of benefits to creating a new type of bitcoin address built\non top of OP_EVAL that will be very easy for all of our existing\ninfrastructure to support.\n\n-- \n--\nGavin Andresen",
"sig": "e2867dd48640302a5f2e00807ec44d9e09f062eae0c342cc287b7b55400c52c649358d1fecf6df8e965d9486599adcd325a4c6bced45eab8917a179447ecdb05"
}