📅 Original date posted:2011-12-13
🗒️ Summary of this message: Green addresses protocol uses shorter Bitcoin addresses for multiple addresses in one QR code. DNS proposal allows for centralized or decentralized options.
📝 Original message:@Matt
I didn't thought about firstbits scalability, but the "registering
crap" and squatting arguments don't apply to green addresses because
no one wants fancy or easy to memorize names there. Is just a way to
make the bitcoin addresses shorter in the green addresses protocol to
be able to have various of them in the same QR-code.
@Amir
I see, the point is to be able to type the alias directly into the client.
I like the DNS proposal. This would allow for both well known working
centralized technology and namecoin (not proven, but decentralized)
options to be used.
2011/12/13, theymos <theymos at mm.st>:
> I like the user at server.com model. The protocol should be done entirely
> in DNS, though, not using HTTP connections to the server. Then the
> protocol can easily be used with Namecoin or other DNS
> replacements/enhancements later. Crypto to prevent MITM attacks can be
> an optional part of the protocol.
>
> Almost all users will be unable to set up *any* always-on Internet
> service to answer queries, so I'm not too concerned about how easy it is
> to set up the server software.
>
> I agree that FirstBits is bad for this. Unlike DNS, "registrations" last
> forever because private keys can't be transferred safely. All short
> names will be taken quickly. It will also be very expensive for clients
> to query this themselves.
>
> The CA model is broken and it should never be used by Bitcoin.
>
> ------------------------------------------------------------------------------
> Systems Optimization Self Assessment
> Improve efficiency and utilization of IT resources. Drive out cost and
> improve service delivery. Take 5 minutes to use this Systems Optimization
> Self Assessment. http://www.accelacomm.com/jaw/sdnl/114/51450054/
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
--
Jorge Timón
Jorge Timón [ARCHIVE] /
npub1fx…cl2d8
2023-06-07 02:43:12
in reply to nevent1q…6z36
Author Public Key
npub1fx98zxt3lzspjs5f4msr0fxysx5euucm29ghysryju7vpc9j0jzqtcl2d8Published at
2023-06-07 02:43:12Event JSON
{
"id": "b439d8d056fd14a22fe16320a7c0ad11e0ad4711c0efadc3ba0121695ecff836",
"pubkey": "498a711971f8a0194289aee037a4c481a99e731b5151724064973cc0e0b27c84",
"created_at": 1686105792,
"kind": 1,
"tags": [
[
"e",
"247922e9146ee6b54a634fc05ad7a489892c01debcd0510d008be95a47f6db80",
"",
"root"
],
[
"e",
"d49a0823599e4434ee6fb843a5b94a9b9d9477236f20cc270950e3a375ab0ae8",
"",
"reply"
],
[
"p",
"7b17a27b7a85e67ba7923c452fbb08ed536244f667a20168dfc3172a83c992df"
]
],
"content": "📅 Original date posted:2011-12-13\n🗒️ Summary of this message: Green addresses protocol uses shorter Bitcoin addresses for multiple addresses in one QR code. DNS proposal allows for centralized or decentralized options.\n📝 Original message:@Matt\nI didn't thought about firstbits scalability, but the \"registering\ncrap\" and squatting arguments don't apply to green addresses because\nno one wants fancy or easy to memorize names there. Is just a way to\nmake the bitcoin addresses shorter in the green addresses protocol to\nbe able to have various of them in the same QR-code.\n\n@Amir\nI see, the point is to be able to type the alias directly into the client.\n\nI like the DNS proposal. This would allow for both well known working\ncentralized technology and namecoin (not proven, but decentralized)\noptions to be used.\n\n\n2011/12/13, theymos \u003ctheymos at mm.st\u003e:\n\u003e I like the user at server.com model. The protocol should be done entirely\n\u003e in DNS, though, not using HTTP connections to the server. Then the\n\u003e protocol can easily be used with Namecoin or other DNS\n\u003e replacements/enhancements later. Crypto to prevent MITM attacks can be\n\u003e an optional part of the protocol.\n\u003e\n\u003e Almost all users will be unable to set up *any* always-on Internet\n\u003e service to answer queries, so I'm not too concerned about how easy it is\n\u003e to set up the server software.\n\u003e\n\u003e I agree that FirstBits is bad for this. Unlike DNS, \"registrations\" last\n\u003e forever because private keys can't be transferred safely. All short\n\u003e names will be taken quickly. It will also be very expensive for clients\n\u003e to query this themselves.\n\u003e\n\u003e The CA model is broken and it should never be used by Bitcoin.\n\u003e\n\u003e ------------------------------------------------------------------------------\n\u003e Systems Optimization Self Assessment\n\u003e Improve efficiency and utilization of IT resources. Drive out cost and\n\u003e improve service delivery. Take 5 minutes to use this Systems Optimization\n\u003e Self Assessment. http://www.accelacomm.com/jaw/sdnl/114/51450054/\n\u003e _______________________________________________\n\u003e Bitcoin-development mailing list\n\u003e Bitcoin-development at lists.sourceforge.net\n\u003e https://lists.sourceforge.net/lists/listinfo/bitcoin-development\n\u003e\n\n\n-- \nJorge Timón",
"sig": "91c8690a853da2245a08c752899fc7cafa69e67e2c6aae93145b6129d9e17b351bc3d99dcc4134949bea438e8461d32439ad7d8491ce2045a0d623ff92249ffe"
}