📅 Original date posted:2011-10-31
🗒️ Summary of this message: Gavin Andresen suggests moving away from Bitcoin addresses and creating an infrastructure where people or organizations are paid, but proposes a short-term solution using a new type of Bitcoin address.
📝 Original message:>
> How would I know that unless you told me?
At least you would have a hunch that something like that had happened as one of your addresses had been part of a transaction (at least in my setup it would pop up immediately...).
>
> 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.
I am not sure what you mean by this - just recall that the semi anonymously feature of bitcoin is one of its key features.
> 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.
Still, how do you solve the end less expansions of bitcoin addresses that each, depending of a leading 1, 2, 3... means a quite specific script inside the OP_EVAL ??? Its not esthetic...
Cheers,
M
>
> --
> --
> Gavin Andresen
Michael Grønager [ARCHIVE] /
npub15f…xlq6h
2023-06-07 02:35:58
in reply to nevent1q…2qec
Author Public Key
npub15fmnxm546tg2sv0l7elusrvqsgezdzdg3m0flpml5fr2qf3f5slskxlq6hPublished at
2023-06-07 02:35:58Event JSON
{
"id": "2832ab8d23ba7057ff8363c3dcb4341365fba56fed909c3ba9126c3507cccbd0",
"pubkey": "a277336e95d2d0a831fff67fc80d8082322689a88ede9f877fa246a02629a43f",
"created_at": 1686105358,
"kind": 1,
"tags": [
[
"e",
"38ab95ef62f6301977f9dec6ff3b1f25746d558345bec15abbd412157a28a77b",
"",
"root"
],
[
"e",
"2c600ca33755608c86fbe523a518594eaa4c982517d5e0c3644f4cf93f1c20b8",
"",
"reply"
],
[
"p",
"857f2f78dc1639e711f5ea703a9fc978e22ebd279abdea1861b7daa833512ee4"
]
],
"content": "📅 Original date posted:2011-10-31\n🗒️ Summary of this message: Gavin Andresen suggests moving away from Bitcoin addresses and creating an infrastructure where people or organizations are paid, but proposes a short-term solution using a new type of Bitcoin address.\n📝 Original message:\u003e \n\u003e How would I know that unless you told me?\n\nAt least you would have a hunch that something like that had happened as one of your addresses had been part of a transaction (at least in my setup it would pop up immediately...).\n\n\u003e \n\u003e I think the right long-term solution is moving away from bitcoin\n\u003e addresses as 'pay-to entity' and create an infrastructure where we're\n\u003e paying people or organizations.\n\nI am not sure what you mean by this - just recall that the semi anonymously feature of bitcoin is one of its key features.\n\n\u003e But in the short term, I think there\n\u003e are lots of benefits to creating a new type of bitcoin address built\n\u003e on top of OP_EVAL that will be very easy for all of our existing\n\u003e infrastructure to support.\n\nStill, how do you solve the end less expansions of bitcoin addresses that each, depending of a leading 1, 2, 3... means a quite specific script inside the OP_EVAL ??? Its not esthetic...\n\nCheers,\n\nM\n\n\u003e \n\u003e -- \n\u003e --\n\u003e Gavin Andresen",
"sig": "775f5b30be2f61e81a8d13cede4c70d8b0801f410308980ab0ee1487e5236aca4ec6e76a45a62a623b8cebd41ef7d76864c787b43e7dcc955cbe5620b6af27a8"
}