Difference between revisions of "Consensus Process (voting pools)"
Jump to navigation
Jump to search
(Initial page creation) |
(→Introduction: add inputstop parameter. Sorting at this level is unnecessary because the wallet will do it.) |
||
| Line 5: | Line 5: | ||
Each new consensus will result in a unanimous agreement on the following parameters: | Each new consensus will result in a unanimous agreement on the following parameters: | ||
| − | #The address identifier for the first input to be used for constructing withdrawal transaction(s). | + | # The address identifier for the first input to be used for constructing withdrawal transaction(s). |
| − | #The address identifier for the first change address to be used by the resulting withdrawal transaction(s). | + | # The address identifier for the first change address to be used by the resulting withdrawal transaction(s). |
| − | #A list of valid withdrawals to be processed | + | # The highest series number which at least <code>m</code> pool members have thawed. |
| + | # A list of valid withdrawals to be processed, which may be an empty list. | ||
==Procedure== | ==Procedure== | ||
Revision as of 12:43, 22 September 2014
Introduction
In order to process bitcoin withdrawals from the pool, the audit servers must agree on a set of parameters used to deterministically construct Bitcoin transactions. The servers arrive at a new consensus every five minutes, in a process which requires several rounds to achieve.
Each new consensus will result in a unanimous agreement on the following parameters:
- The address identifier for the first input to be used for constructing withdrawal transaction(s).
- The address identifier for the first change address to be used by the resulting withdrawal transaction(s).
- The highest series number which at least
mpool members have thawed. - A list of valid withdrawals to be processed, which may be an empty list.
