Keyset (voting pools) - Revision history

Larshesel: Make it explicit that it is the private keys that are online

2014-09-22T13:03:12Z

Make it explicit that it is the private keys that are online

Larshesel: Move definition of x to keyset definition

2014-09-22T10:00:34Z

Move definition of x to keyset definition

Justusranvier: /* Series */

2014-09-04T12:46:19Z

‎Series

Justusranvier: /* Keysets */ formatting

2014-05-26T09:11:13Z

‎Keysets: formatting

Justusranvier: /* Series */ Add image

2014-05-23T07:07:20Z

‎Series: Add image

Justusranvier at 20:47, 17 April 2014

2014-04-17T20:47:52Z

Justusranvier at 20:47, 17 April 2014

2014-04-17T20:47:35Z

Justusranvier at 20:08, 17 April 2014

2014-04-17T20:08:53Z

Justusranvier: Clean up and wikification

2014-04-17T17:30:41Z

Clean up and wikification

Justusranvier at 17:27, 17 April 2014

2014-04-17T17:27:00Z

@@ Line 50: / Line 50: @@
 At any given time, one series is “active”. This is the series containing the keys which will be used to create deposit and change addresses. Pool members will “fill up” this series with deposits until the next series rotation, then will begin filling up the next series.
-At any given time, one series is “hot”. The hot series is the one whose keys are online and is currently being used to process withdrawals. All series between the hot series and the active series are inactive. Slightly before the hot series is depleted of unspent outputs (to avoid withdrawal delays) the private keys for the next inactive series are brought online and that series becomes the new hot series.
+At any given time, one series is “hot”. The hot series is the one whose private keys are online and is currently being used to process withdrawals. All series between the hot series and the active series are inactive. Slightly before the hot series is depleted of unspent outputs (to avoid withdrawal delays) the private keys for the next inactive series are brought online and that series becomes the new hot series.
 Each series can be subdivided into two sub-series. The deposit series consists of n lists of deposit addresses, one for each member of the pool. The change series is a list of change outputs from previous withdrawal transactions.

@@ Line 33: / Line 33: @@
 Pool definitions are versioned for future extendibility.
 ===Series===
@@ Line 42: / Line 44: @@
 Series numbers are always monotonic (strictly increasing).
-Series numbers are incremented on a schedule, shown above as “x”. x is time interval expressed in [http://www.nncron.ru/help/EN/working/cron-format.htm Cron] format, either a semicolon-separated list of column values, or one of the [http://en.wikipedia.org/wiki/Cron#Predefined_scheduling_definitions predefined patterns]. The default and recommended schedule is “@weekly”.
+Series numbers are incremented on a schedule, shown above as “x”.
 All series rotations are calculated based on UTC time.

@@ Line 38: / Line 38: @@
 [[File:Voting_Pools_Series_Progression.png|800px]]
-The keyset contains a list of series numbers, each one of which contains an xpub for every member of the pool.
+The keyset contains a list of series numbers, each one of which contains an [[xpub]] for every member of the pool.
 Series numbers are always monotonic (strictly increasing).

@@ Line 12: / Line 12: @@
 		<server id=”server_id_w” />
 	</members>
-<keyset schedule=”x”  m=”u” n=”v”>
+	<keyset schedule=”x”  m=”u” n=”v”>
 		<series number=”1”>
 			<key server=”server_id_y”>xpub_y1</key>
-<key server=”server_id_z”>xpub_z1</key>
+			<key server=”server_id_z”>xpub_z1</key>
 			<key server=”server_id_w”>xpub_w1</key>
-</series>
+		</series>
-	<series number=”2”>
+		<series number=”2”>
 			<key server=”server_id_y”>xpub_y2</key>
-	<key server=”server_id_z”>xpub_z2</key>
+			<key server=”server_id_z”>xpub_z2</key>
-<key server=”server_id_w”>xpub_w2</key>
+			<key server=”server_id_w”>xpub_w2</key>
-	</series>
+		</series>
-</keyset>
+	</keyset>
 </pool></pre>

← Older revision		Revision as of 07:07, 23 May 2014
Line 35:		Line 35:

	===Series===		===Series===
		+
		+	[[File:Voting_Pools_Series_Progression.png\|800px]]

	The keyset contains a list of series numbers, each one of which contains an xpub for every member of the pool.		The keyset contains a list of series numbers, each one of which contains an xpub for every member of the pool.

← Older revision		Revision as of 20:47, 17 April 2014
Line 51:		Line 51:


−	[[Category:Voting Pool Technical ~~Specification~~]]	+	[[Category:Voting Pool Technical Specifications]]

← Older revision		Revision as of 20:08, 17 April 2014
Line 51:		Line 51:


−	[[Category:Voting ~~Pools~~]]	+	[[Category:Voting Pool Terms]]

@@ Line 4: / Line 4: @@
 <pre>
 <pool id=”uuid” version=”1”>
 	<blockchain>bitcoin</blockchain>
@@ Line 25: / Line 24: @@
 	</series>
 </keyset>
-</pool></code></pre>
+</pool></pre>
 In the above example there are three servers, y, z, and w. All decisions made by the pool must be signed by u of v members of the pool. Every server contributes a different xpub for each series defined in the keyset.
@@ Line 31: / Line 30: @@
 Each pool must explicitly define the crypto-currency being managed by the pool, and whether to treat the deposits as regular units or as colored units.
-Regular pools have a <color> value of 0. Colored coin pools are designated by including a color definition in the <color> section.
+Regular pools have a <color> value of 0. Colored coin pools are designated by including a [[color definition]] in the <color> section.
 Pool definitions are versioned for future extendibility.
@@ Line 41: / Line 40: @@
 Series numbers are always monotonic (strictly increasing).
-Series numbers are incremented on a schedule, shown above as “x”. x is time interval expressed in Cron format, either a semicolon-separated list of column values, or one of the predefined patterns. The default and recommended schedule is “@weekly”.
+Series numbers are incremented on a schedule, shown above as “x”. x is time interval expressed in [http://www.nncron.ru/help/EN/working/cron-format.htm Cron] format, either a semicolon-separated list of column values, or one of the [http://en.wikipedia.org/wiki/Cron#Predefined_scheduling_definitions predefined patterns]. The default and recommended schedule is “@weekly”.
 All series rotations are calculated based on UTC time.