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
Yes, reward me, please :-)
BTC 1JLKNFxKjkU3YsLs38y4e672iWiXBeFYP3
[ANC] ATAgJzuA7djZ8DijQPqtNieAughLPaFaa2
thx.
BTC 1JLKNFxKjkU3YsLs38y4e672iWiXBeFYP3
[ANC] ATAgJzuA7djZ8DijQPqtNieAughLPaFaa2
thx.
Yes the problem is we never get that message. We work those errors into our scripts if encountered but the daemon isnt presenting us with any warning. It happily sends the transaction and reports all is well
We do not send rawtransactions
All withdrawals are processed via "sendtoaddress"
Hi mullick,
I took a close look at the behavior of "sendtoaddress" in the most up to date version of our code and I have determined that it will always refuse to make a transaction greater than 100KB. I did not verify this for older versions (too busy with Zerocoin), but it looks like the best course of action for Cryptsy is to make sure you all are compiling anoncoind from the latest version in Github (either "master" or "newbase" branches). Either perform a "git checkout newbase && git pull" or download the zip file from Github.
Let me know if you are still having issues with this after the above has been deployed.