đ
Original date posted:2015-09-11
đ Original message:What's some more information about the "memorizing and sharing" use
case? In most cases if you wanted someone to send you money you'd send
them a payment request via email (or just send them your address).
There's a bunch of solutions to your problem listed here:
https://github.com/bitcoin/bips/blob/master/bip-0015.mediawiki
But sending a payment request via BIP-70 is the "best practice":
https://github.com/bitcoin/bips/blob/master/bip-0070.mediawiki
On Thu, Sep 10, 2015 at 2:32 PM, Mark Friedenbach via bitcoin-dev
<bitcoin-dev at lists.linuxfoundation.org> wrote:
> Are you aware of the payment protocol?
>
> On Sep 10, 2015 2:12 PM, "essofluffy . via bitcoin-dev"
> <bitcoin-dev at lists.linuxfoundation.org> wrote:
>>
>> Hi Everyone,
>>
>> An issue I'm sure everyone here is familiar with is the problem concerning
>> the fact that Bitcoin addresses are too complex to memorize and share.
>> Current Bitcoin addresses can be very intimidating to new users. As Bitcoin
>> grows it's necessary to provide a much more user friendly experience to the
>> end user. I think that having the capability to assign a unique name to a
>> Bitcoin address is in the best interest of Bitcoin and it's users.
>> I've recently come up with a method for assigning a unique name to a
>> specific Bitcoin address. I'm looking to get some feedback/criticism on this
>> method that I have detailed below.
>>
>> Letâs run through Bob and Alice transacting with a Named Bitcoin Address.
>> Bob wants to collect a payment from Alice for a service/good he is
>> selling, but Alice wants to pay from her home computer where she securely
>> keeps all her Bitcoin. So now Bob needs to give Alice his Bitcoin address
>> and because Bob is using a Named Bitcoin Address and a supported wallet he
>> can give her an easy to memorize and hard to mess up address. Bobâs address
>> is simply âSendBitcoinsToBobâ which can easily be written down or memorized.
>> Now Alice can go home send the Bitcoin from her own supported wallet and be
>> positive that she sent it to Bob.
>>
>> Letâs look at how Bobâs supported wallet made that address.
>>
>> First Bob letâs his wallet know that he wants to create a new address. In
>> response, his wallet simply asks him what he wants that address to be named.
>> Bob then enters âSendBitcoinsToBobâ as his preferred address name. The
>> wallet then letâs Bob know if his preferred address name is available. If
>> itâs available the name is broadcasted to the network and ready to use.
>>
>> Now letâs get a little more technical.
>>
>> When Bob inputs his preferred address name the client has to make sure
>> this name hasnât been taken or else who knows where Alice will be sending
>> her Bitcoins. The client does this by referencing a downloaded âdirectoryâ
>> of names chosen by people using this system. This directory of names are
>> transactions sent to an address without a private key (but still viewable on
>> the blockchain) with the name appended to the transactions as an OP_RETURN
>> output. These transactions are downloaded or indexed, depending on whether
>> or not the wallet contains the full Blockchain or is an SPV wallet. Because
>> of such a large amount of possible address names a binary search method is
>> used to search through all this data efficiently. The names could be sorted
>> in two ways, the first being the first character and the second being the
>> total length of the name (I will being exploring additional methods to make
>> this process more efficient). So now that Bobâs client has verified that the
>> name has not been taken and is valid (valid meaning it's under 35 bytes long
>> and only using chars 0-9 and a-z) it sends a transaction of 1 satoshi and a
>> small fee to the address without a private key as talked about earlier. The
>> transaction's OP_RETURN output consists of two parts. The implementation
>> version of this method (up to 8 characters) and the name itself (up to 32
>> characters). Once the transaction is broadcasted to the network and
>> confirmed the name is ready to be used.
>>
>> Letâs look at how Aliceâs supported wallet sends her Bitcoin to Bobâs
>> Named Bitcoin Address.
>>
>> When Alice enters in Bobâs address, âSendBitcoinsToBobâ Aliceâs client
>> references the same âdirectoryâ as Bob only on her device and searches for
>> the OP_RETURN output of âSendBitcoinsToBobâ using a very similar binary
>> search method as used for the verification of the availability of an address
>> name. If a name isnât found the client would simply return an error. If the
>> name is found then the client will pull the information of that transaction
>> and use the address it was sent from as the address to send the Bitcoin to.
>>
>> Essentially what this idea describes is a method to assign a name to a
>> Bitcoin address in a way that is completely verifiable and independent of a
>> third party.
>>
>> Please ask your questions and provide feedback.
>>
>> - Devin
>>
>>
>> _______________________________________________
>> bitcoin-dev mailing list
>> bitcoin-dev at lists.linuxfoundation.org
>> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>>
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
Andy Chase [ARCHIVE] /
npub1hgâŚ2pv20
2023-06-07 17:39:57
in reply to nevent1qâŚksec
Author Public Key
npub1hgz0f5ghpavn49u2h2za7464v9w02fd534nx5w268plwr06zal3s32pv20Published at
2023-06-07 17:39:57Event JSON
{
"id": "32752c3b771fc8b2c245f74213a229687491d3cdfcc94f38bd6ae331bbe3cbe2",
"pubkey": "ba04f4d1170f593a978aba85df5755615cf525b48d666a395a387ee1bf42efe3",
"created_at": 1686159597,
"kind": 1,
"tags": [
[
"e",
"3a79f8bfa01f62843757ccd69db1de9234940fe2a7a004268205308b812ee156",
"",
"root"
],
[
"e",
"e925fd1c7b023deb3a89c6e80ea9dbe6e142e671ab79e38cb9946e1e70849934",
"",
"reply"
],
[
"p",
"1c61d995949cbfaf14f767784e166bde865c7b8783d7aa3bf0a1d014b70c0069"
]
],
"content": "đ
Original date posted:2015-09-11\nđ Original message:What's some more information about the \"memorizing and sharing\" use\ncase? In most cases if you wanted someone to send you money you'd send\nthem a payment request via email (or just send them your address).\n\nThere's a bunch of solutions to your problem listed here:\nhttps://github.com/bitcoin/bips/blob/master/bip-0015.mediawiki\nBut sending a payment request via BIP-70 is the \"best practice\":\nhttps://github.com/bitcoin/bips/blob/master/bip-0070.mediawiki\n\nOn Thu, Sep 10, 2015 at 2:32 PM, Mark Friedenbach via bitcoin-dev\n\u003cbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\u003e Are you aware of the payment protocol?\n\u003e\n\u003e On Sep 10, 2015 2:12 PM, \"essofluffy . via bitcoin-dev\"\n\u003e \u003cbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\u003e\u003e\n\u003e\u003e Hi Everyone,\n\u003e\u003e\n\u003e\u003e An issue I'm sure everyone here is familiar with is the problem concerning\n\u003e\u003e the fact that Bitcoin addresses are too complex to memorize and share.\n\u003e\u003e Current Bitcoin addresses can be very intimidating to new users. As Bitcoin\n\u003e\u003e grows it's necessary to provide a much more user friendly experience to the\n\u003e\u003e end user. I think that having the capability to assign a unique name to a\n\u003e\u003e Bitcoin address is in the best interest of Bitcoin and it's users.\n\u003e\u003e I've recently come up with a method for assigning a unique name to a\n\u003e\u003e specific Bitcoin address. I'm looking to get some feedback/criticism on this\n\u003e\u003e method that I have detailed below.\n\u003e\u003e\n\u003e\u003e Letâs run through Bob and Alice transacting with a Named Bitcoin Address.\n\u003e\u003e Bob wants to collect a payment from Alice for a service/good he is\n\u003e\u003e selling, but Alice wants to pay from her home computer where she securely\n\u003e\u003e keeps all her Bitcoin. So now Bob needs to give Alice his Bitcoin address\n\u003e\u003e and because Bob is using a Named Bitcoin Address and a supported wallet he\n\u003e\u003e can give her an easy to memorize and hard to mess up address. Bobâs address\n\u003e\u003e is simply âSendBitcoinsToBobâ which can easily be written down or memorized.\n\u003e\u003e Now Alice can go home send the Bitcoin from her own supported wallet and be\n\u003e\u003e positive that she sent it to Bob.\n\u003e\u003e\n\u003e\u003e Letâs look at how Bobâs supported wallet made that address.\n\u003e\u003e\n\u003e\u003e First Bob letâs his wallet know that he wants to create a new address. In\n\u003e\u003e response, his wallet simply asks him what he wants that address to be named.\n\u003e\u003e Bob then enters âSendBitcoinsToBobâ as his preferred address name. The\n\u003e\u003e wallet then letâs Bob know if his preferred address name is available. If\n\u003e\u003e itâs available the name is broadcasted to the network and ready to use.\n\u003e\u003e\n\u003e\u003e Now letâs get a little more technical.\n\u003e\u003e\n\u003e\u003e When Bob inputs his preferred address name the client has to make sure\n\u003e\u003e this name hasnât been taken or else who knows where Alice will be sending\n\u003e\u003e her Bitcoins. The client does this by referencing a downloaded âdirectoryâ\n\u003e\u003e of names chosen by people using this system. This directory of names are\n\u003e\u003e transactions sent to an address without a private key (but still viewable on\n\u003e\u003e the blockchain) with the name appended to the transactions as an OP_RETURN\n\u003e\u003e output. These transactions are downloaded or indexed, depending on whether\n\u003e\u003e or not the wallet contains the full Blockchain or is an SPV wallet. Because\n\u003e\u003e of such a large amount of possible address names a binary search method is\n\u003e\u003e used to search through all this data efficiently. The names could be sorted\n\u003e\u003e in two ways, the first being the first character and the second being the\n\u003e\u003e total length of the name (I will being exploring additional methods to make\n\u003e\u003e this process more efficient). So now that Bobâs client has verified that the\n\u003e\u003e name has not been taken and is valid (valid meaning it's under 35 bytes long\n\u003e\u003e and only using chars 0-9 and a-z) it sends a transaction of 1 satoshi and a\n\u003e\u003e small fee to the address without a private key as talked about earlier. The\n\u003e\u003e transaction's OP_RETURN output consists of two parts. The implementation\n\u003e\u003e version of this method (up to 8 characters) and the name itself (up to 32\n\u003e\u003e characters). Once the transaction is broadcasted to the network and\n\u003e\u003e confirmed the name is ready to be used.\n\u003e\u003e\n\u003e\u003e Letâs look at how Aliceâs supported wallet sends her Bitcoin to Bobâs\n\u003e\u003e Named Bitcoin Address.\n\u003e\u003e\n\u003e\u003e When Alice enters in Bobâs address, âSendBitcoinsToBobâ Aliceâs client\n\u003e\u003e references the same âdirectoryâ as Bob only on her device and searches for\n\u003e\u003e the OP_RETURN output of âSendBitcoinsToBobâ using a very similar binary\n\u003e\u003e search method as used for the verification of the availability of an address\n\u003e\u003e name. If a name isnât found the client would simply return an error. If the\n\u003e\u003e name is found then the client will pull the information of that transaction\n\u003e\u003e and use the address it was sent from as the address to send the Bitcoin to.\n\u003e\u003e\n\u003e\u003e Essentially what this idea describes is a method to assign a name to a\n\u003e\u003e Bitcoin address in a way that is completely verifiable and independent of a\n\u003e\u003e third party.\n\u003e\u003e\n\u003e\u003e Please ask your questions and provide feedback.\n\u003e\u003e\n\u003e\u003e - Devin\n\u003e\u003e\n\u003e\u003e\n\u003e\u003e _______________________________________________\n\u003e\u003e bitcoin-dev mailing list\n\u003e\u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e\u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev\n\u003e\u003e\n\u003e\n\u003e _______________________________________________\n\u003e bitcoin-dev mailing list\n\u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev\n\u003e",
"sig": "562080ed114b9c633c87a52b2928cb12f9e482dffeb578afb41f80af5e5eb21afc71fbd3ce6e92d5ee91d2152a74102bae3b3b559847da9b34f1908894b8a4dd"
}