Payment Protocol (voting pools) - Revision history

Justusranvier: Add links

2014-05-23T11:14:16Z

Add links

Justusranvier at 22:00, 17 April 2014

2014-04-17T22:00:51Z

Justusranvier: Initial page creation

2014-04-17T22:00:09Z

Initial page creation

New page

==Format==

Services which are part of voting pools must be able to deliver a valid deposit address to their customers, and the security model of the voting pool requires that a malicious or compromised service must not be able to deliver an incorrect address to a customer (Type 1 event).

In order to meet this requirement, payment messages are embedded in OT messages and arrive at the customer’s device through the OT inbox. At this point the OT client can validate the deposit address and signatures against the voting pool contract prior to passing the request to a local Bitcoin wallet application.

The only message used out of the BIP70 protocol is the PaymentRequest/PaymentDetails message

The PaymentDetails section should contain a single P2SH output script to the appropriate deposit address.

The merchant_data field should contain the following data:

(pendingBailment Receipt hash, address identifier)

The PaymentRequest wrapper includes OT-specific values that enable the OT client to validate the deposit address as valid for the specified voting pool.

The pki_type field should be “open-transactions”
The pki_data field should contain the asset contract id for the voting pool.
The signature field, contains the signature of the transaction server which is processing the request.

@@ Line 5: / Line 5: @@
 In order to meet this requirement, payment messages are embedded in OT messages and arrive at the customer’s device through the OT inbox.  At this point the OT client can validate the deposit address and signatures against the voting pool contract prior to passing the request to a local Bitcoin wallet application.
-The only message used out of the BIP70 protocol is the PaymentRequest/PaymentDetails message
+The only message used out of the [https://github.com/bitcoin/bips/blob/master/bip-0070.mediawiki BIP70] protocol is the <code>PaymentRequest</code>/<code>PaymentDetails</code> message
-The PaymentDetails section should contain a single P2SH output script to the appropriate deposit address.
+The <code>PaymentDetails</code> section should contain a single [[P2SH]] output script to the appropriate deposit address.
-The merchant_data field should contain the following data:
+The <code>merchant_data</code> field should contain the following data:
-(pendingBailment Receipt hash, address identifier)
+<code>(pendingBailment Receipt hash, address identifier)</code>
-The PaymentRequest wrapper includes OT-specific values that enable the OT client to validate the deposit address as valid for the specified voting pool.
+The <code>PaymentRequest</code> wrapper includes OT-specific values that enable the OT client to validate the deposit address as valid for the specified voting pool.
-The pki_type field should be “open-transactions”
+The <code>pki_type</code> field should be “open-transactions”
-The pki_data field should contain the asset contract id for the voting pool.
+The <code>pki_data</code> field should contain the [[Asset_contract_(voting_pools)|asset contract id]] for the voting pool.
-The signature field, contains the signature of the transaction server which is processing the request.
+The <code>signature</code> field, contains the signature of the transaction server which is processing the request.
 [[Category: Voting Pool Technical Specifications]]

← Older revision		Revision as of 22:00, 17 April 2014
Line 18:		Line 18:
	The pki_data field should contain the asset contract id for the voting pool.		The pki_data field should contain the asset contract id for the voting pool.
	The signature field, contains the signature of the transaction server which is processing the request.		The signature field, contains the signature of the transaction server which is processing the request.
		+
		+	[[Category: Voting Pool Technical Specifications]]