Search results

Jump to navigation Jump to search

Page title matches

  • ...will rely on this protocol to protect against most forms of attack in the deposit process.
    1 KB (211 words) - 11:31, 23 May 2014
  • ...the design criteria of [[:Category:Voting Pools|voting pools]], blockchain deposit addresses must be created in a deterministic manner such that any entity wi ...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
    3 KB (493 words) - 19:07, 7 October 2014

Page text matches

  • ...yset_(voting_pools)|deposit series]], and the service responsible for that address never generated a <code>[[PaymentRequest]]</code> for it. ...address receiving the unknown deposit is a [[Keyset_(voting_pools)|change address]].
    2 KB (302 words) - 11:45, 23 May 2014
  • ...malicious or compromised service must not be able to deliver an incorrect address to a customer (Type 1 event). ...hrough 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 reques
    2 KB (241 words) - 11:14, 23 May 2014
  • ...ent protocol]] mandatory and providing them with an API for requesting new deposit addresses on demand. ...antee that unsolicited funds will never be received to the previously-used address.
    2 KB (366 words) - 12:00, 23 May 2014
  • ...]. Addresses in the change series are differentiated from addresses in the deposit series by presenting the pubkeys in the output scripts in reverse standard ...series 20 being active. Change outputs created from withdrawals taken from deposit series 1 will be sent to change series 20. The standard order of the xpubs
    1 KB (205 words) - 22:06, 17 April 2014
  • ...e]] or [[unknown deposit|unknown deposits]] in the hot series to a deposit address in the active series.
    428 bytes (60 words) - 15:49, 19 September 2014
  • ...deposit script suitable for a BIP70 [[PaymentRequest]] based on a specific address. Deposit scripts may only be requested from active series, as indicated by the locat
    2 KB (277 words) - 13:38, 23 September 2014
  • ...a permanent record, because it's not possible to ensure users do not reuse deposit addresses. ...t to be credited for the bailment. All incoming blockchain deposits to the address defined in this record will be credited to this account.
    2 KB (294 words) - 14:59, 8 October 2014
  • ===Non-credited Deposit=== ...sible transaction server fails to credit the appropriate [[nym]] after the deposit is fully confirmed.
    1 KB (174 words) - 14:26, 23 May 2014
  • In order to avoid ambiguity, the terms "blockchain wallet" and "blockchain address" refers to the cryptocurrency for which is pool is tracking receipts. This ===Address Identification===
    4 KB (625 words) - 13:00, 12 November 2014
  • Customers will normally request a deposit address by interacting with the service front end web site or some other software a ...code>[[bailment]]</code> transaction request to the notary to initiate the deposit process.
    7 KB (1,135 words) - 13:54, 9 October 2014
  • ...send a fake deposit request that results in a customer sending funds to an address not controlled by the pool.
    1 KB (166 words) - 19:58, 17 April 2014
  • # The first [[Wallet_(blockchain)#Address_Identification|address identifier]] to be considered. ...es with eligible utxos to be used as inputs, the various parameters of the address identifier are incremented in the following order:
    5 KB (754 words) - 17:09, 7 October 2014
  • Voting pools do not require that every address issued to users ever receive a blockchain transaction, and it is allowable If a deposit is not received because a user never initiated it from their end, no correc
    945 bytes (156 words) - 11:31, 23 May 2014
  • ...the design criteria of [[:Category:Voting Pools|voting pools]], blockchain deposit addresses must be created in a deterministic manner such that any entity wi ...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
    3 KB (493 words) - 19:07, 7 October 2014
  • ...and find the hashed ID for any master credential that claims that Namecoin address as a source. In this way, Namecoin can replace CAs. A master credential mig ...two.) There might be a withdrawal item and a balance agreement item. Or a deposit item and a balance agreement item. Or a transfer item and a balance agreeme
    20 KB (3,232 words) - 23:41, 18 September 2013