Escrow transactions

Escrow transactions should now be enabled.

Usage:

In the sidebar, after clicking Transactions, there is an entry for escrow. Click it to go to the escrow screen.
In the escrow screen, there is a button in the upper right labelled "Create Escrow" which will open the escrow create dialogue.
Fill it out like this:
Recipient: The recipient of the escrow in either BURST- or numeric id(you can hit backspace to remove the existing BURST-___ entry to type numbers)
Amount: The amount you want to transfer
Escrow deadline: A time limit in seconds that if runs out, the escrow will be automatically completed with the deadline action selected in the next step. This deadline must be 1 - 7776000(up to 3 months) seconds.
Deadline Action: The action that will occur automatically if the deadline runs out without the escrow being completed. This can be release, refund, or split.
Required signers: A number from 1 - 10, saying how many people need to sign off on a decision to cause that action to be taken. Regardless of what this number is set to, a sender can always release, and a recipient can always refund.
Signers: A list of accounts allowed to sign off on a decision. BURST- addresses and numeric ids can be used. They are separated by semicolons ( ; ). 1 - 10 must be specified. (ex: BURST-AAAA-AAAA-AAAA-AAAAA;1234556;987654321;BURST-BBBB-BBBB-BBBB-BBBBB;1357913579 )
Message: A message can optionally be attached. If you want signers to be able to see the message, it must not be encrypted.

Fees: There is a network fee that is 1 burst by default, and an additional fee equal to the number of signers specified. The additional fee is given to the signers, so they have a coin to make their decision transaction with if necessary. This also makes it easy for people to participate in escrows as signers without having an existing funded burst account.

Once the escrow transaction has been included in a block, it will be listed on the escrow screen if you are involved in it(sender, recipient, or listed as a signer is considered involved)
Clicking on the transaction id in the screen brings up the decision making screen. Various information is shown on it(signers' ids and decisions, deadline time and action, etc)
A decision can be selected from the dropdown and submitted to sign off on that decision.
Senders can select release which will release the funds when it gets included in a block.
Recipients can select refund which will refund the funds when it gets included in a block.
Signers can select release, refund, split, or undecided. When their decision gets included in a block, the escrow details will be updated to show their decision. If their decision makes the number of signers with that decision at least the number of required signers, that decision is executed.

Can anyone explain me this?
If the plot size is 5000 nonces, why result 10000 nonces??

I think the rest don't have 10000 nonces.
If you used the plot generator to create from 5000 nonces another 5000 it should have 5000 nonces. from 5000 to 10000.

Hi all,

I've setup a BURST pool at http://tompool.org:82, it appears to be working however I'm not seeing the share tally change. I only have about 800GB plotted so far but the other miner has around 6TB. Is this simply a case of low plotting power meaning the shares are too insignificant to be counted in 2 decimal places or am I missing a setting?

The best share I've seen on the pool so far is 41 years :/

Greatly appreciate any help!

Uray do you planing fix memory leaks in your minner?..
not cleans up memory after itself.. not in windows not in linux

No pos

Fixed:
* Memory leaks
* Exceeding the boundaries of data
* 100% usage CPU at idle, now 1%

Fixed:
* Memory leaks
* Exceeding the boundaries of data
* 100% usage CPU at idle, now 1%

Are you sure it works? My miner stopped after 30 minutes: Error allocating memory.

I would like to try your miner, however I get multiple dll errors on Windows Server 2008 R2, any advice?

tested 3 PC, 2 days...

did you set EnablePrefetch & EnableSuperPrefetch to 0 in registry?