Quote from: K1773R on October 12, 2014, 09:07:09 AM

Quote from: Gnosis- on October 12, 2014, 05:00:22 AM

Quote from: K1773R on October 11, 2014, 05:56:14 PM

Quote from: Simcom on October 11, 2014, 02:39:46 PM

This was a good review of the problem - thanks for compiling this. Looks like if the transaction size is too big it will fail to confirm regardless of the the fee included. Can we get a dev response? Are you guys trying to identify this bug? The doesn't seem like it should be a very difficult thing to fix, probably just a couple lines of code.

I posted that they shouldnt change fee settings and/or also shouldnt patch the client o allow such huge txs (txs are limited to 100KB normaly).
Nothing from our side to be done as there is nothing to fix. If someone dosnt want to play according to the rules, they shouldnt wonder why things break. Thats the beauty of a decentralized system.

mullick says they don't patch anoncoind. Maybe they are doing some exotic combination of RPC commands (sendrawtransaction...)? I still think there's a way to create txs bigger than 100KB with an un-patched anoncoind, just not an easy way.
I will PM mullick now to ask what RPC commands are being performed.

Yes, with sendrawtransaction you obviously can create larger txs as you create the tx yourself.

Oh that is interesting. Is there another size limit, of what maximum tx-size is allowed get into the blockchain?

EDIT: Found it myself. https://github.com/Anoncoin/anoncoin/blob/master/src/main.h#L31 :-)

Quote from: K1773R on October 12, 2014, 12:00:12 AM

Quote from: Simcom on October 11, 2014, 10:52:59 PM

[...] but shouldn't the wallet be able to handle this by adding a larger mining fee so that the txn gets confirmed?

The default wallet dosnt create transaction bigger than 100KB, https://github.com/Anoncoin/anoncoin/blob/master/src/main.h#L33
Everything above is non-standard and not mined with default settings/codebase.

You seem to have solved it, now he knows what to do?

Still, perhaps the following might help? Cryptsy, are you ever looking at the error reports of your (failed) RPC commands? If the error is "{"code":-4,"message":"Transaction too large"}", then I might once have encountered a not un-comparable problem, when I tried to send coins aggregated from thousands of p2pool mining micropayments. Have a look at my error description, and how (unelegantly) I solved it back then: https://bitcointalk.org/index.php?topic=488167.msg5399167#msg5399167 "sendmany.sh" -Sometimes analogous cases help to find your way out Wink

Yes, reward me, please :-)
BTC 1JLKNFxKjkU3YsLs38y4e672iWiXBeFYP3
[ANC] ATAgJzuA7djZ8DijQPqtNieAughLPaFaa2
thx.