Post
Topic
Board Announcements (Altcoins)
Re: Official Anoncoin chat thread (including history)
by
Clyze
on 13/10/2014, 22:32:29 UTC
So due to volume I wanted to transfer my Anoncoins from Bittrex back to Cryptsy. Now it seems Bittrex has "confirmed" my withdrawal, but nothing is showing up on the blockchain. It has been 2 hours since I requested my withdrawal.

As I read above (stupidly I read more of this thread after my withdrawal) it seems that bigger transactions are struggling to get through
I lack knowledge when it comes to techs & specifications. Is this problem solved/being solved?

Sorry for bothering ;-)


Thanks in advance,

Clyze



Hi guys, referring back to this post;

It has been quite a while since I requested my withdrawal from Bittrex to Cryptsy. Here is some more information regarding my withdrawal.

Withdrawal History    Hide cancelled withdrawals
Search:
DATE   CURRENCY   UNITS   STATUS
   10/13/2014 12:37:03 PM   ANC   969.26520089   Completed
Address: AYUpQqCftJbQEqpuvw4RrQKz19gFtC2VFC
TxId: 838e3b333ac6a64e5eed95c320bdee2ff2121dac170a634fbe498f739d2257c9

It does not show up on the blockchain and I am quite sure we're at a new block at the moment. Time passes by and I am getting more concerned. As I am incredibly clueless on this whole situation.

The last information I could provide is the address of my Bittrex account; AWQNFCwMBomJWxNLT2RrXnvtVbt1tL4yQU
If you search that addy on the blockchain it still shows the funds before my withdrawal.

I hope someone can clarify things for me. Is there a reason to be concerned?

Thanks in advance,

Clyze


No you should not be concerned - the fact that the transaction has not hit the blockchain yet suggests this is a problem on bittrex's end.  Open a support ticket with bittrex and they will take care of it for you.

EDIT: I just confirmed with bittrex they seem to be having the same issue. But on a smaller scale as they have far less unspent inputs



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.



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.

I have compiled from the master branch about 8 times to make sure we were up to date and even did a dif of the source to verify

We are running from the master branch last compiled on

Aug 19 22:07 anoncoin


Thanks about the update.
I have indeed contacted both Cryptsy and Bittrex and both of them forward me to this thread. What does this situation mean for me? How long would it approximately take to solve this problem? Are my coins in danger?

Once again, sorry for bothering; just a tidy bit concerned.

Cheers,
Clyze