Quote from: AlexMc on January 26, 2015, 05:12:18 AM

Transaction too large error when sending

Hi

Anyone else had this error when trying to send DGB from the Digibyte Core v3.0.3.0-g354c0f3-MultiAlgo (64-bit) wallet. The transaction in question was for 1 million DGB.

I then managed to get it to send successfully for 879000 with a transaction fee of 0.04 DGB being added. When I tried again a few minutes later it seemed happy to send 1 million DGB, but this time it added a transaction fee of 2 DGB. Weird...

Any ideas.

I have seen doubling transaction fees on successive transactions quickly made one after another (e.g. .02, .04, .08, etc). I have also seen the fee immediately go back to zero if you wait 30 seconds or a minute after a string of successive transactions quickly made one after another (e.g. .02, .04, .08, wait a minute and send again). I have also seen the entire pattern repeat itself if sending many transactions quickly again after having gone back to zero fee after a wait period.

The fee, and its size, seems to be linked to the number of "sends" a user is trying to include in the same newly discovered block; however, that may be entirely wrong and it could be the number of users and their aggregate "sends" at the time that determine whether there is a fee or not and how much it will be. Since my experience is limited, I cannot give you further information or a better answer.

I am not aware if the Dev Team has published information clearly describing and informing on how this works. If they have, maybe someone could point us in the right direction to find that info, and if they haven't, I'm sure the Devs will make the effort to answer your question by making that information available to us as soon as they have the time to write down a few lines.

Very good question BTW. Thanks.