Deposit Never Received - Revision history

Justusranvier: correct category

2014-05-23T11:31:42Z

correct category

Justusranvier at 11:29, 23 May 2014

2014-05-23T11:29:58Z

Justusranvier: Initial page creation

2014-05-23T11:27:27Z

Initial page creation

New page

Voting pools do not require that every address issued to users ever receive a blockchain transaction, and it is allowable for multiple [[Voting_Pool_Deposit_Process|bailments]] to be in progress at the same time.

The transaction server may limit the number of <code>[[pendingBailment]]</code> notices a user may have open at a given time. If a user has too many <code>pendingBailments</code> open it may refuse to create new ones until the old ones have been either canceled or completed.

Services may also implement rate limiting to prevent a malicious user from performing a DoS attack on the pool’s bitcoin wallet or the user's [[OT inbox]].

[[Category:Type 1 events (voting pools)]]

← Older revision		Revision as of 11:31, 23 May 2014
Line 5:		Line 5:
	If the user does initiate a blockchain transaction, the voting pool relies on the blockchain network to successfully complete the transfer.		If the user does initiate a blockchain transaction, the voting pool relies on the blockchain network to successfully complete the transfer.

−	[[Category:Type 1 events (voting pools)]]	+	[[Category:Type 0 events (voting pools)]]

@@ Line 1: / Line 1: @@
 Voting pools do not require that every address issued to users ever receive a blockchain transaction, and it is allowable for multiple [[Voting_Pool_Deposit_Process|bailments]] to be in progress at the same time.
-The transaction server may limit the number of <code>[[pendingBailment]]</code> notices a user may have open at a given time. If a user has too many <code>pendingBailments</code> open it may refuse to create new ones until the old ones have been either canceled or completed.
+If a deposit is not received because a user never initiated it from their end, no corrective action is necessary. The transaction server may limit the number of <code>[[pendingBailment]]</code> notices a user may have open at a given time. If a user has too many <code>pendingBailments</code> open it may refuse to create new ones until the old ones have been either canceled or completed. Services may also implement rate limiting to prevent a malicious user from performing a DoS attack on the pool’s bitcoin wallet or the user's [[OT inbox]].
-Services may also implement rate limiting to prevent a malicious user from performing a DoS attack on the pool’s bitcoin wallet or the user's [[OT inbox]].
+If the user does initiate a blockchain transaction, the voting pool relies on the blockchain network to successfully complete the transfer.
 [[Category:Type 1 events (voting pools)]]