Talk:BIP 0021 - Revision history

Transisto: /* Feed partially signed transactions for wallet to sign */

2019-11-17T01:43:37Z

Feed partially signed transactions for wallet to sign

← Older revision		Revision as of 01:43, 17 November 2019
Line 169:		Line 169:

	== Feed partially signed transactions for wallet to sign ==		== Feed partially signed transactions for wallet to sign ==

	~~bitcoin:ANYaddress?presig=~~

	Example <nowiki>bitcoin:ANYaddress?presig=45505446ff0002000000000101beee3e40b018f740df8a88ddb411862abf5a634................1231e61c33b4d6992fb61871a2ec711e7b5793c69632b22ea342804110000050054aedf370900 </nowiki>		Example <nowiki>bitcoin:ANYaddress?presig=45505446ff0002000000000101beee3e40b018f740df8a88ddb411862abf5a634................1231e61c33b4d6992fb61871a2ec711e7b5793c69632b22ea342804110000050054aedf370900 </nowiki>

Transisto at 01:43, 17 November 2019

2019-11-17T01:43:03Z

← Older revision		Revision as of 01:43, 17 November 2019
Line 172:		Line 172:
	bitcoin:ANYaddress?presig=		bitcoin:ANYaddress?presig=

	Example `bitcoin:ANYaddress?presig=45505446ff0002000000000101beee3e40b018f740df8a88ddb411862abf5a634................1231e61c33b4d6992fb61871a2ec711e7b5793c69632b22ea342804110000050054aedf370900`		Example <nowiki>bitcoin:ANYaddress?presig=45505446ff0002000000000101beee3e40b018f740df8a88ddb411862abf5a634................1231e61c33b4d6992fb61871a2ec711e7b5793c69632b22ea342804110000050054aedf370900 </nowiki>

Transisto at 01:42, 17 November 2019

2019-11-17T01:42:36Z

← Older revision		Revision as of 01:42, 17 November 2019
Line 170:		Line 170:
	== Feed partially signed transactions for wallet to sign ==		== Feed partially signed transactions for wallet to sign ==

	`bitcoin:ANYaddress?presig=`		bitcoin:ANYaddress?presig=

	Example `bitcoin:ANYaddress?presig=45505446ff0002000000000101beee3e40b018f740df8a88ddb411862abf5a634................1231e61c33b4d6992fb61871a2ec711e7b5793c69632b22ea342804110000050054aedf370900`		Example `bitcoin:ANYaddress?presig=45505446ff0002000000000101beee3e40b018f740df8a88ddb411862abf5a634................1231e61c33b4d6992fb61871a2ec711e7b5793c69632b22ea342804110000050054aedf370900`

Transisto: pass pre-signed transaction to wallet.

2019-11-17T01:41:22Z

pass pre-signed transaction to wallet.

← Older revision		Revision as of 01:41, 17 November 2019
Line 165:		Line 165:
	Example:		Example:
	<nowiki>bitcoin:R-175tWpb8K1S7NmH4Zx6rewF9WQrcZv245W?amount=0.567&label=book&req-aal=1tZdShH7b38klseWrTZm5sE8PrtZPwqdK:0.123:game&message=Thank%20You</nowiki>		<nowiki>bitcoin:R-175tWpb8K1S7NmH4Zx6rewF9WQrcZv245W?amount=0.567&label=book&req-aal=1tZdShH7b38klseWrTZm5sE8PrtZPwqdK:0.123:game&message=Thank%20You</nowiki>



			== Feed partially signed transactions for wallet to sign ==

			`bitcoin:ANYaddress?presig=`

			Example `bitcoin:ANYaddress?presig=45505446ff0002000000000101beee3e40b018f740df8a88ddb411862abf5a634................1231e61c33b4d6992fb61871a2ec711e7b5793c69632b22ea342804110000050054aedf370900`

Michael S: /* Critical Improvement of BIP 0021 for "req-" param */

2013-09-12T01:41:14Z

Critical Improvement of BIP 0021 for "req-" param

← Older revision		Revision as of 01:41, 12 September 2013
Line 139:		Line 139:
	One aspect of current BIP 0021 is critical:		One aspect of current BIP 0021 is critical:

	It says that wallets that do not know ~~any of the~~ "req-" keys in the URI should reject (i.e. not process) the complete URI, to avoid doing anything in the wrong way.		It says that wallets that do not know one or several "req-" keys in the URI should reject (i.e. not process) the complete URI, to avoid doing anything in the wrong way.

	However, ~~even older~~ wallet apps may have not even implemented this rule and may still process the "known part" of the URI, thereby causing an unwanted result.		However, very old wallet apps may have not even implemented this rule and may still process the "known part" of the URI, thereby causing an unwanted result.

	The solution to the problem is to specify BIP 0021 in a way that, in case that at least one "req-" key is used, some other details of the URI must be modified too, such that it becomes "incompatible" and "undecodable" by older apps.		The solution to the problem is to specify BIP 0021 in a way that, in case that at least one "req-" key is used, some other details of the URI must be modified too, such that it becomes "incompatible" and "undecodable" by older apps.
Line 152:		Line 152:
	bitcoinurn = "bitcoin:" '''[ "R-" ]''' bitcoinaddress [ "?" bitcoinparams ]		bitcoinurn = "bitcoin:" '''[ "R-" ]''' bitcoinaddress [ "?" bitcoinparams ]
	where "R-" is mandatory as soon as at least one "reqparam" is used.		where "R-" is mandatory as soon as at least one "reqparam" is used.


	== Paying to Multiple Outputs ==		== Paying to Multiple Outputs ==

Michael S: /* Short parameter tags yielding shorter URIs for QR codes */

2013-09-12T01:38:27Z

Short parameter tags yielding shorter URIs for QR codes

← Older revision		Revision as of 01:38, 12 September 2013
Line 121:		Line 121:
	message= m=		message= m=
	tip= t=		tip= t=
	tipaddr= i=		tipaddr= ta=
	req- -		req- -
	req-tipaddr= -i=		req-tipaddr= -ta=
			req-aal= -aal=

	Hence, for example the following URIs are fully equivalent:		Hence, for example the following URIs are fully equivalent:
Line 130:		Line 131:
	<nowiki>bitcoin:175tWpb8K1S7NmH4Zx6rewF9WQrcZv245W?amount=0.567&tip=15%25&req-tipaddr=1waiter7b38klseWrTZm5sE8PrrupPB2Q2&message=Thank%20You&label=Charly%27s%20Bar</nowiki>		<nowiki>bitcoin:175tWpb8K1S7NmH4Zx6rewF9WQrcZv245W?amount=0.567&tip=15%25&req-tipaddr=1waiter7b38klseWrTZm5sE8PrrupPB2Q2&message=Thank%20You&label=Charly%27s%20Bar</nowiki>

	~~128~~ characters:		129 characters:
	<nowiki>bitcoin:175tWpb8K1S7NmH4Zx6rewF9WQrcZv245W?a=.567&t=15%25&-i=1waiter7b38klseWrTZm5sE8PrrupPB2Q2&m=Thank%20You&l=Charly%27s%20Bar</nowiki>		<nowiki>bitcoin:175tWpb8K1S7NmH4Zx6rewF9WQrcZv245W?a=.567&t=15%25&-ta=1waiter7b38klseWrTZm5sE8PrrupPB2Q2&m=Thank%20You&l=Charly%27s%20Bar</nowiki>

	== Critical Improvement of BIP 0021 for "req-" param ==		== Critical Improvement of BIP 0021 for "req-" param ==

Michael S: Enhancement: Multiple output addresses

2013-09-12T01:32:47Z

Enhancement: Multiple output addresses

← Older revision		Revision as of 01:32, 12 September 2013
Line 151:		Line 151:
	bitcoinurn = "bitcoin:" '''[ "R-" ]''' bitcoinaddress [ "?" bitcoinparams ]		bitcoinurn = "bitcoin:" '''[ "R-" ]''' bitcoinaddress [ "?" bitcoinparams ]
	where "R-" is mandatory as soon as at least one "reqparam" is used.		where "R-" is mandatory as soon as at least one "reqparam" is used.


			== Paying to Multiple Outputs ==
			([[User:Michael_S\|Michael_S]] ([[User talk:Michael_S\|talk]]) 12 Sept 2013)

			Another Enhancement relates to the "Humble Bundle" scenario: Paying one transaction with multiple outputs, specifying a dedicated amount for each output address.

			This scenario allows to specify additional pairs of addresses and amounts. Optionally, also further labels can be specified. We call the new parameter "'''req-aal'''" for '''a'''ddress-'''a'''mount-'''l'''abel, and we specify it as a '''req'''uired parameter because procesing an incomplete URI would result in sending only a partial amount.

			bitcoinparam = amountparam \| labelparam \| '''reqaalparam \|''' messageparam \| tipparam \| tipaddrparam \| otherparam \| reqparam
			reqaalparam = "req-aal=" bitcoinaddress ":" digit [ "." digit ] [ ":" *pchar]

			Example:
			<nowiki>bitcoin:R-175tWpb8K1S7NmH4Zx6rewF9WQrcZv245W?amount=0.567&label=book&req-aal=1tZdShH7b38klseWrTZm5sE8PrtZPwqdK:0.123:game&message=Thank%20You</nowiki>

Michael S: Critical improvement proposal of BIP 0021 for "req-" parameter

2013-09-12T01:07:53Z

Critical improvement proposal of BIP 0021 for "req-" parameter

← Older revision		Revision as of 01:07, 12 September 2013
Line 132:		Line 132:
	128 characters:		128 characters:
	<nowiki>bitcoin:175tWpb8K1S7NmH4Zx6rewF9WQrcZv245W?a=.567&t=15%25&-i=1waiter7b38klseWrTZm5sE8PrrupPB2Q2&m=Thank%20You&l=Charly%27s%20Bar</nowiki>		<nowiki>bitcoin:175tWpb8K1S7NmH4Zx6rewF9WQrcZv245W?a=.567&t=15%25&-i=1waiter7b38klseWrTZm5sE8PrrupPB2Q2&m=Thank%20You&l=Charly%27s%20Bar</nowiki>

			== Critical Improvement of BIP 0021 for "req-" param ==
			([[User:Michael_S\|Michael_S]] ([[User talk:Michael_S\|talk]]) 12 Sept 2013)

			One aspect of current BIP 0021 is critical:

			It says that wallets that do not know any of the "req-" keys in the URI should reject (i.e. not process) the complete URI, to avoid doing anything in the wrong way.

			However, even older wallet apps may have not even implemented this rule and may still process the "known part" of the URI, thereby causing an unwanted result.

			The solution to the problem is to specify BIP 0021 in a way that, in case that at least one "req-" key is used, some other details of the URI must be modified too, such that it becomes "incompatible" and "undecodable" by older apps.

			The concrete proposal here is to append "R-" directly after "bitcoin:". Then a string with a "req-" parameter would look like this:
			<nowiki>bitcoin:</nowiki>'''R-'''<nowiki>175tWpb8K1S7NmH4Zx6rewF9WQrcZv245W?amount=0.567&tip=15%25&</nowiki>'''req-'''<nowiki>tipaddr=1waiter7b38klseWrTZm5sE8PrrupPB2Q2&message=Thank%20You&label=Charly%27s%20Bar</nowiki>


			The BFN Syntax then looks as follows:
			bitcoinurn = "bitcoin:" '''[ "R-" ]''' bitcoinaddress [ "?" bitcoinparams ]
			where "R-" is mandatory as soon as at least one "reqparam" is used.

Michael S: Added short figure descriptions

2013-09-09T20:00:04Z

Added short figure descriptions

← Older revision		Revision as of 20:00, 9 September 2013
Line 60:		Line 60:

	The details are of course dependent on the client app implementation, a best practice-example is demonstrated in the following images.		The details are of course dependent on the client app implementation, a best practice-example is demonstrated in the following images.

			Standard send dialog (no tips):

	[[File:bitcoin-app-tipOFF_BIP_0021.png\|border]]		[[File:bitcoin-app-tipOFF_BIP_0021.png\|border]]


			Advanced send dialog for giving tips:

	[[File:bitcoin-app-tipON_BIP_0021.png\|border]]		[[File:bitcoin-app-tipON_BIP_0021.png\|border]]

Michael S: Give reason why BIP 0021 protocol change complements sole wallet app improvement

2013-09-09T19:55:46Z

Give reason why BIP 0021 protocol change complements sole wallet app improvement

← Older revision		Revision as of 19:55, 9 September 2013
Line 66:		Line 66:
	[[File:bitcoin-app-tipON_BIP_0021.png\|border]]		[[File:bitcoin-app-tipON_BIP_0021.png\|border]]

			Discussion: It has been argued that the described improvement of the user experience for the scenario "make payment with a tip" can be achieved by sole improvement of the wallet app, without any protocol change.

			But this is only partly true. Certainly enhancement of the wallet app to provide an advanced "send" dialog for easy tipping is crucial. However, with the legacy BIP 0021 the wallet app cannot know whether it shall display the standard send dialog (no tip) or the advanced send dialog (with tip option) to the user. So the user has to select this manually. With the optional "tip" parameter in the URI, the wallet app can readily display the appropriate send dialog without extra user interaction, thereby providing ultimate user experience.

	== Further enhancement for paying tips in restaurant/bar: "tip address" ==		== Further enhancement for paying tips in restaurant/bar: "tip address" ==