Search results

Create the page "Voting Pool Technical Specifications" on this wiki! See also the search results found.

• Outputs (Voting Pool Wallet API)
  ...[[startwithdrawal]] API call accepts a list of outputs to be created since voting pools process withdrawals in batches. [[Category:Voting Pool Technical Specifications]]
  461 bytes (60 words) - 15:24, 26 September 2014
• Payment Protocol (voting pools)
  ...d 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 delive ...client can validate the deposit address and signatures against the voting pool contract prior to passing the request to a local Bitcoin wallet application
  2 KB (241 words) - 11:14, 23 May 2014
• Signature status
  ...a list of signatures which can be shared with other members of the voting pool to create an valid withdrawal transaction. [[Category:Voting Pool Technical Specifications]]
  689 bytes (97 words) - 22:23, 30 November 2015
• Consensus Process (voting pools)
  In order to process blockchain withdrawals from the pool, the audit servers must agree on a set of parameters used to deterministica # The address identifier for the first [[Change Address (voting pools)|Change Address]] to be used by the resulting withdrawal transaction(
  964 bytes (144 words) - 14:48, 12 November 2014
• Asset contract (voting pools)
  Asset contract for voting pools differ from standard OT asset contracts in two ways: they contain a c ...s the asset contracts can not be identified by their hash. Instead, voting pool contracts are linked to a [[Colored_coins#Smart_Property|smart property]],
  2 KB (351 words) - 14:36, 12 November 2014
• Change Address (voting pools)
  In order to fufill the design criteria of voting pools, change outputs generated from withdrawal transactions must be sent t ...nerated by a withdrawal transaction is sent to an address in the [[Keyset (voting pools)#Series|active change series]]. Addresses in the change series are di
  1 KB (205 words) - 22:06, 17 April 2014
• Bailment Database
  Voting pools must be able to maintain accurate accounting between the OT balances ...ditor in the voting pool maintains a full bailment database for the entire pool. Auditors need a full database to ensure that notaries credit the correct n
  2 KB (294 words) - 14:59, 8 October 2014
• Siglist
  ...a list of signatures which can be shared with other members of the voting pool to create an valid withdrawal transaction. In order for members of the voting pool to coordinate transaction signing, all transactions '''MUST''' be binary-id
  2 KB (331 words) - 15:52, 26 September 2014
• Deposit Address (voting pools)
  ...]] can predict the sequence of addresses and enumerate the holdings of the pool for auditing purposes. The asset contract contains an [[xpub]] for every member of the pool for every defined sequence in a [[keyset]]. The output scripts which define
  3 KB (493 words) - 19:07, 7 October 2014
• Keyset (voting pools)
  The multisig structure of a pool is called the keyset definition and is expressed in XML and stored in the O <pool id=”uuid” version=”1”>
  3 KB (474 words) - 13:03, 22 September 2014
• Withdrawal status
  [[Category:Voting Pool Technical Specifications]]
  1 KB (168 words) - 14:46, 21 October 2014
• Input Selection Algorithm (voting pools)
  ...that the number of branches may vary from series to series because voting pool members may be added or removed when moving between series. By rejecting all inputs with less than 100 confirmations, the pool effectively has a 16 hour window in which to detect duplicate deposits and
  5 KB (754 words) - 17:09, 7 October 2014