Deposit Address (voting pools) - Revision history

Ttll at 19:07, 7 October 2014

2014-10-07T19:07:39Z

Justusranvier: /* Script= */

2014-04-17T20:44:38Z

‎Script=

Justusranvier: /* Procedure */

2014-04-17T20:44:22Z

‎Procedure

Justusranvier at 20:43, 17 April 2014

2014-04-17T20:43:21Z

Justusranvier: Initial page creation

2014-04-17T20:42:38Z

Initial page creation

New page

==Introduction==

In order to fufill the design criteria of [[Category:Voting Pools|voting pools]], blockchain deposit addresses must be created in a deterministic manner such that any entity with the [[Asset Contract (voting pools)|asset contract]] can predict the sequence of addresses and enumerate the holdings of the pool for auditing purposes.

==Procedure==

The asset contract contains an [[xpub]] for every member of the pool for every defined sequence in a [[keyset]]. The output scripts which defined the individual deposit addresses are composed from the set of public keys derived by applying the same index value to all xpubs.

For the rest of this discussion the following notation will be used.

<code>y3(5)</code>

The previous example should be interpreted as the specific public key derived by applying the index value of <code>5</code> to the [[xpub]] belonging to server <code>y</code> in series <code>3</code>.

Multisig output scripts are created in the general form:

<code>OP_m {pubkey}...{pubkey} OP_n OP_CHECKMULTISIG</code>

Voting pools will create P2SH versions of multisig output scripts to use as deposit addresses. This implies that the exact ordering of the pubkeys in the output script must be defined in order to predict the sequence of P2SH deposit addresses. The ordering is as follows:

Within a given series, the binary representations of the list of xpubs is sorted in ascending order.

The resulting ordering is the [[standard order]].

Public keys in a multisig output script are listed in standard order except the server which will issue an OT receipt for a given deposit moves its pubkey to the beginning of the list.

Because each server has its own unique list of deposit addresses, blockchain wallets must be capable of referencing addresses in a hierarchical fashion.

Each defined wallet produces n+1 independent lists of addresses: a list for each of the n servers in the pool, and a common change address list.

===Example===

Assume the standard order of the xpubs in series 1 doe a 2-of-3 voting pool is: <code>y1, z1, w1</code>. (this can and will change from series to series).

Server <code>y</code> will accept its very first three deposits to the P2SH addresses corresponding to the following output scripts:

<code>OP_2 y1(1) z1(1), w1(1) OP_3 OP_CHECKMULTISIG</code>

<code>OP_2 y1(2) z1(2), w1(2) OP_3 OP_CHECKMULTISIG</code>

<code>OP_2 y1(3) z1(3), w1(3) OP_3 OP_CHECKMULTISIG</code>

Server w, on the other hand, will use w-y-z ordering for deposits in this series:

<code>OP_2 w1(1) z1(1), y1(1) OP_3 OP_CHECKMULTISIG</code>

<code>OP_2 w1(2) z1(2), y1(2) OP_3 OP_CHECKMULTISIG</code>

<code>OP_2 w1(3) z1(3), y1(3) OP_3 OP_CHECKMULTISIG</code>

[[Category:Voting Pool Technical Specifications]]

@@ Line 34: / Line 34: @@
 ===Example===
-Assume the standard order of the xpubs in series 1 doe a 2-of-3 voting pool is: <code>y<sub>1</sub>, z<sub>1</sub>, w<sub>1</sub></code>. (this can and will change from series to series).
+Assume the standard order of the xpubs in series 1 does a 2-of-3 voting pool is: <code>y<sub>1</sub>, z<sub>1</sub>, w<sub>1</sub></code>. (this can and will change from series to series).
 Server <code>y</code> will accept its very first three deposits to the P2SH addresses corresponding to the following output scripts:

@@ Line 14: / Line 14: @@
 The previous example should be interpreted as the specific public key derived by applying the index value of <code>5</code> to the [[xpub]] belonging to server <code>y</code> in series <code>3</code>.
-==Script===
+===Script===
 Multisig output scripts are created in the general form:

@@ Line 7: / Line 7: @@
 The asset contract contains an [[xpub]] for every member of the pool for every defined sequence in a [[keyset]]. The output scripts which defined the individual deposit addresses are composed from the set of public keys derived by applying the same index value to all xpubs.
 For the rest of this discussion the following notation will be used.
@@ Line 12: / Line 13: @@
 The previous example should be interpreted as the specific public key derived by applying the index value of <code>5</code> to the [[xpub]] belonging to server <code>y</code> in series <code>3</code>.
 Multisig output scripts are created in the general form:

@@ Line 1: / Line 1: @@
 ==Introduction==
-In order to fufill the design criteria of [[Category:Voting Pools|voting pools]], blockchain deposit addresses must be created in a deterministic manner such that any entity with the [[Asset Contract (voting pools)|asset contract]] can predict the sequence of addresses and enumerate the holdings of the pool for auditing purposes.
+In order to fufill the design criteria of [[:Category:Voting Pools|voting pools]], blockchain deposit addresses must be created in a deterministic manner such that any entity with the [[Asset Contract (voting pools)|asset contract]] can predict the sequence of addresses and enumerate the holdings of the pool for auditing purposes.
 ==Procedure==