WDL
Newbie
Offline
Activity: 54
Merit: 0
|
|
October 25, 2014, 03:20:36 PM |
|
THANKS.But it doesn't work for me.
|
|
|
|
|
TheKoziTwo
Legendary
Offline
Activity: 1552
Merit: 1047
|
|
October 25, 2014, 04:54:27 PM |
|
This is what I got from the crypsy chatroom:
"Mullick told me that he will put online ANC blockchain explorer today and use it as a node for all ANC transactions including stucked ones"
So apparently, from that garbled mess, that means Mullick is on the job? Because I messaged him two days ago on the bitcointalk account -- asking if he could get the raw transactions -- and I haven't heard anything back from him since.
The cryptsy saga continues.
Meanwhile they have stopped replying to my open ticket thread.
I successfully broadcast 276 transactions with altexplorer last night that cryptsys wallet refused to. i cant keep doing this for every withdrawal. So the wallet will remain in maintenance until the developers fix the issue. If anyone has a transactions that did not get confirmed last night please pm me with the details Can you enable the wallet so that current pending deposits will confirm? I am stuck (sent deposit before you disabled the wallet).
|
|
|
|
JMcGrath
Member
Offline
Activity: 72
Merit: 10
|
|
October 25, 2014, 05:35:32 PM |
|
Just a quick update on my Cryptsy ANC withdrawal issue for what it's worth... I posted a few days ago about my transactions being "stuck" and got zero support from Cryptsy other than pointing me to various forum threads including this one. I had a total of 4 transactions ranging from 140 ANC up to 1,200 ANC... 3 of which were going to CEX and 1 going to my personal wallet. Finally today, after 4 days (or was it 5...?) I finally got all 4 transactions to both CEX and my wallet! I don't know if this helps anyone or not, it doesn't look like Cryptsy has the problem solved and even if they did I don't think I would trust using them again. Looking at the txID's it was definitely a Cryptsy issue from what I can see so no need to panic about ANC having issues. If you're still waiting on Cryptsy it looks like their transactions will *Eventually* go through, but it will probably take some time because of the massive tx sizes they are sending. Hopefully no one has lost too much money over this issue, I could have more than doubled my BTC if the tx had gone through right away... but at this point I'm just happy to report I finally got them and made just a few percent!! Sorry Cryptsy, I'll have to use someone else now but thanks for nothing! Good luck to anyone else that had issues! Hope you get your coins back from Craptsy soon...
|
|
|
|
entertheabyss
|
|
October 25, 2014, 08:01:21 PM |
|
just did an over-the-counter trade with skaia
anybody want to buy ANC outside of an exchange PM me
|
|
|
|
mullick
Legendary
Offline
Activity: 1064
Merit: 1002
|
|
October 25, 2014, 10:00:40 PM |
|
Just a quick update on my Cryptsy ANC withdrawal issue for what it's worth... I posted a few days ago about my transactions being "stuck" and got zero support from Cryptsy other than pointing me to various forum threads including this one. I had a total of 4 transactions ranging from 140 ANC up to 1,200 ANC... 3 of which were going to CEX and 1 going to my personal wallet. Finally today, after 4 days (or was it 5...?) I finally got all 4 transactions to both CEX and my wallet! I don't know if this helps anyone or not, it doesn't look like Cryptsy has the problem solved and even if they did I don't think I would trust using them again. Looking at the txID's it was definitely a Cryptsy issue from what I can see so no need to panic about ANC having issues. If you're still waiting on Cryptsy it looks like their transactions will *Eventually* go through, but it will probably take some time because of the massive tx sizes they are sending. Hopefully no one has lost too much money over this issue, I could have more than doubled my BTC if the tx had gone through right away... but at this point I'm just happy to report I finally got them and made just a few percent!! Sorry Cryptsy, I'll have to use someone else now but thanks for nothing! Good luck to anyone else that had issues! Hope you get your coins back from Craptsy soon... You should read the thread. This isnt a cryptsy issue. Its an anc issue. I spent 3 hours relaying transactions last night and setting up the node to get everyones transactions confirmed. Bittrex has their wallet disabled due to the same issue
|
|
|
|
mullick
Legendary
Offline
Activity: 1064
Merit: 1002
|
|
October 25, 2014, 10:15:34 PM Last edit: October 25, 2014, 10:55:47 PM by mullick |
|
Ok lets set this straight since the developers have stopped communicating with us and trying to fix the issue. I have gone above and beyond to make anoncoin work on our exchange. I kept the ANC wallet open when bittrex shut it down to not lock customers from their funds This was made impossible by the false accusations and general slander from the community and developers themselves I will say it again. I manage 236 wallets. ANC is the only one to have this issue. And it is NOT a cryptsy issue. Pay special attention to the bold textHi Mullick,
I am one of the Anoncoin developers, and I want to work with you to see if we can get to the bottom of this. So the issue appears to happen when you create a transaction and it is greater than 100KB. By design, such a transaction will not be relayed in the network.
What RPC commands are you using to create and send these transactions?
Thanks, Gnosis
Hello, Thanks for the reply The onlycommand issued to our daemons for withdrawal is a "sendtoaddress" The problem seems to be anoncoind is allowing the transactions instead of reporting "Transaction creation failed" out "Transaction too large" It just happily creates the transactions pretends all is well Our wallet does have a few thousand unspent inputs which we have been merging on and off to reduce tx sizes If there is anything else that would help please let me know -Mullick mullick@cryptsy.comI have tried both the master and the previous official release. Currently we are running the master branch
What does "git rev-parse HEAD" say?
Thanks for the reply. Here ya go git rev-parse HEAD fffef88265b965c6d9b6d5ee64e0a9406699018d Almost done merging inputs as well Started with over 100k Remaining are 11672 unspent inputs. 85b72e5119946d6589569cb3f36e796aebdc13e1bc38f0959e7186df5591fd39 I just confirmed with bittrex they seem to be having the same issue Mullick https://bitcointalk.org/index.php?topic=227287.msg8354734#msg8354734 Thats what our unconfirmed transactions looked like @bittrex-richie "amount" : -969.26520089, "fee" : -0.60000000, "confirmations" : 0, "txid" : "838e3b333ac6a64e5eed95c320bdee2ff2121dac170a634fbe498f739d2257c9", yeah.. looks to be similar do they never clear? Mullick One of the devs had to solomine with a modified daemon to allow larger transaction sizes They got most of ours confirmed nm daemon wasnt modified he just decalred max tx sizes in the anoncoin.conf Mullick You could remove it from your wallet and resend after 48 hours as well after 48 hours it should be cleared from everyone mempool @bittrex-richie those both seem like ridicoulous answers Mullick lol yep If they dont have the fix in by the time mintsy goes live ill modify the mintsy daemon to confirm those transactions So I think this is easier with all 4 of us on one PM thread. Let's try to keep it that way Mullick, I have confirmed with you that you're building from source. richie, if you aren't, please check out the master branch from our repo ( https://github.com/Anoncoin/anoncoin). At any rate, I would like you both to patch this into your src/wallet.cpp around line 1295. Where it says this: // Limit size unsigned int nBytes = ::GetSerializeSize(*(CTransaction*)&wtxNew, SER_NETWORK, PROTOCOL_VERSION); if (nBytes >= MAX_STANDARD_TX_SIZE) { strFailReason = _("Transaction too large"); return false; } dPriority /= nBytes; Replace it with this: // Limit size unsigned int nBytes = ::GetSerializeSize(*(CTransaction*)&wtxNew, SER_NETWORK, PROTOCOL_VERSION); if (nBytes >= MAX_STANDARD_TX_SIZE) { strFailReason = _("Transaction too large"); printf("DEBUGTXN: disallowing txn %s because size (%d bytes) not less than max (%d bytes)\n", wtxNew.GetHash().ToString().c_str(), nBytes, MAX_STANDARD_TX_SIZE); return false; } else printf("DEBUGTXN: allowing txn %s because size (%d bytes) less than max (%d bytes)\n", wtxNew.GetHash().ToString().c_str(), nBytes, MAX_STANDARD_TX_SIZE); dPriority /= nBytes; ...and then recompile and re-deploy. You can then submit large transactions and search debug.log for "DEBUGTXN". Let me know what you find when this problem happens again. Thanks, Gnosis I've done this, but considering i've turned off the wallet, this code is never going to get hit... Is there an easy way to clear this first? The wallet is disconnected from your exchange software, but it still has many unspent outputs, right? I would create an address in a second Anoncoin wallet, and send a very large amount to it (hence causing a large transaction to be generated) from the wallet with customer accounts. Later, after fixing this problem and before reconnecting the first wallet to the exchange, send that ANC back to it. I don't know the internals of your exchange software, but this would not cause problems for exchanges I have worked with. I should also mention that this code will only get hit with the "sendtoaddress" RPC command. Inputs are pretty well merged in our wallet so i had some trouble creating transaction of that size. I moved some around in bunches of 25k anoncoind sendtoaddress Ab8Esj3NSpSdi8DqPLJ1EvzHHyJuZbi3kS 25000 6f5b88f4f7b679f46f3f6c51d226180e886402cea45e7125df64b5332af15e08
anoncoind sendtoaddress Ab8Esj3NSpSdi8DqPLJ1EvzHHyJuZbi3kS 25000 61582db98cd0618ae467e5ab306ec04d31456a8fdd3e1bebefa7b3ed6c60883d
anoncoind sendtoaddress Ab8Esj3NSpSdi8DqPLJ1EvzHHyJuZbi3kS 25000 error: {"code":-4,"message":"Transaction too large"}
anoncoind sendtoaddress Ab8Esj3NSpSdi8DqPLJ1EvzHHyJuZbi3kS 20000 cedd565e12483ada162b8f00501969f8b9041d19b19ebc9d15d0308bbdab32ab
anoncoind sendtoaddress Ab8Esj3NSpSdi8DqPLJ1EvzHHyJuZbi3kS 20000 0d02541a95f87d3f09ab9c9cbbec7dc1c4563b0908d9e7a8b35f9089fe5cd3d5
cat debug.log | grep "DEBUGTXN" 2014-10-15 05:28:06 DEBUGTXN: allowing txn aac9d87e2de8753651732af4a5d3ace4443ee868742bbc4bb9e310e463950694 because size (2024 bytes) less than max (100000 bytes) 2014-10-15 05:28:06 DEBUGTXN: allowing txn 6f5b88f4f7b679f46f3f6c51d226180e886402cea45e7125df64b5332af15e08 because size (1337 bytes) less than max (100000 bytes) 2014-10-15 05:28:12 DEBUGTXN: allowing txn 78cecf1250d0ae7b8e5bd3cc737d7549403e9c7b47414a9de193662738bfcc53 because size (4544 bytes) less than max (100000 bytes) 2014-10-15 05:28:12 DEBUGTXN: allowing txn 61582db98cd0618ae467e5ab306ec04d31456a8fdd3e1bebefa7b3ed6c60883d because size (3497 bytes) less than max (100000 bytes) 2014-10-15 05:28:22 DEBUGTXN: disallowing txn 08521fd96fda8cfd9504c5d0f1d1e3cb422ae70fabb21a5752919695ff1f15f0 because size (207955 bytes) not less than max (100000 bytes) 2014-10-15 05:29:31 DEBUGTXN: allowing txn be881799bd459bbab5652fa557ceb3f91658ba2a0c324a539ee1d8a49371fae8 because size (2777 bytes) less than max (100000 bytes) 2014-10-15 05:29:32 DEBUGTXN: allowing txn cedd565e12483ada162b8f00501969f8b9041d19b19ebc9d15d0308bbdab32ab because size (2594 bytes) less than max (100000 bytes) 2014-10-15 05:37:04 DEBUGTXN: allowing txn 1f5f8f0c2255a115679a94412898ee77788c354eea0a894555e114c71c38ec22 because size (19028 bytes) less than max (100000 bytes) 2014-10-15 05:37:04 DEBUGTXN: allowing txn 0d02541a95f87d3f09ab9c9cbbec7dc1c4563b0908d9e7a8b35f9089fe5cd3d5 because size (12610 bytes) less than max (100000 bytes)
Doesn't appear to be anything useful. Its down to the smallest inputs in that wallet now so ill send the results again after 24 hours After roughly 20 blocks none of the transactions have been picked up. This caused our security to go a little nuts and paused the ANC market for a few minutes Cool, thanks for your help. It looks like the check where we added the print statements is always being executed. It's interesting that none of the transactions were picked up. I'm not sure why that's the case... Anyway, the next step is to see whether nodes are refusing to relay these transactions, and if so, why. On line 670 of main.cpp, where it says: if (!fTestNet && !tx.IsStandard(strNonStd)) return error("CTxMemPool::accept() : nonstandard transaction (%s)", strNonStd.c_str()); Please change it to: if (!fTestNet && !tx.IsStandard(strNonStd)) { printf("DEBUGTXN: not accepting tx %s into mempool because '%s'\n", tx.GetHash().ToString().c_str(), strNonStd.c_str()); return error("CTxMemPool::accept() : nonstandard transaction (%s)", strNonStd.c_str()); } Compile this and start it with a separate like this "mkdir /tmp/relay_anc_datadir && ./anoncoind -datadir=/tmp/relay_anc_datadir". You'll need to setup anoncoin.conf as usual. This will be your relay node; you'll need to know the IP for the next step. You can grep its debug.log for "DEBUGTXN" to see refusals to relay, though it's possible some of them will be from other nodes. Going back to the regular wallet you were using before, add the argument "-connect=<RELAY_IP>:9377" where RELAY_IP is the IP above. Now it will only connect to that node. Please start it and create another large transaction (if possible). richiela, if you read this far, please also do the above
|
|
|
|
An0nj0k3
Newbie
Offline
Activity: 41
Merit: 0
|
|
October 25, 2014, 11:20:25 PM |
|
|
|
|
|
mullick
Legendary
Offline
Activity: 1064
Merit: 1002
|
|
October 25, 2014, 11:41:00 PM |
|
|
|
|
|
blahcoin
Newbie
Offline
Activity: 8
Merit: 0
|
|
October 26, 2014, 12:39:25 AM |
|
|
|
|
|
blahcoin
Newbie
Offline
Activity: 8
Merit: 0
|
|
October 26, 2014, 02:20:57 AM |
|
On a serious note, a question about anonymity. I can't figure out how considering I have an impossible to guess password and have setup yubikey for withdrawels but someone emptied out my account for about 80 BTC today!
Luckily I keep most of my BTC in my own wallet but wtf can I do now? Anything? I've been trying to contact Mt Gox all day but it just keeps saying "getting an agent..."
BTW, the person that hacked my account's address is:
1JgqPGJCJWzgeMiTFbmeLi3cpKC9jahPS4
I'll give a reward if I can find out who this person is so I can beat the **** out of them!
It is easy for a novice like myself to follow the trail to a wallet that was active just a few hours ago. Is there no way to connect those stolen funds to an id on an exchange or other service?
|
|
|
|
flound1129
|
|
October 26, 2014, 05:37:24 AM |
|
The network is segmented. Multipool has to mine our own transactions or they don't get relayed. IMO there are not enough clearnet nodes to sustain the network between pools and exchanges. Haven't seen any major forks yet but those could be around the corner. I posted on Reddit about this over 2 months ago: http://www.reddit.com/r/Anoncoin/comments/2dilks/clearnet_nodes_are_getting_sparse/Devs need to set up 2 or 3 open seed nodes on clearnet. It'd also be nice if we could also get an officially tagged release in Git with proper versioning. All of my wallets (built from tag v0.8.5.6) still report version v0.8.5.1-82-gc0b7034-beta and "This is a pre-release test build - use at your own risk - do not use for mining or merchant applications".
|
Multipool - Always mine the most profitable coin - Scrypt, X11 or SHA-256!
|
|
|
overthetop2011
|
|
October 26, 2014, 06:13:01 AM |
|
Where is meen? What is the plan of ANC next?
|
|
|
|
gostrol
Newbie
Offline
Activity: 57
Merit: 0
|
|
October 26, 2014, 09:45:21 AM |
|
New nodes from 26 October: 37.187.144.36 67.209.191.40 193.150.121.37 193.150.121.66 211.149.175.37 37.187.134.204 54.201.183.106 96.126.102.159 104.131.230.129 162.243.149.125 162.243.227.221 162.252.242.123 162.255.116.196 81.247.69.65 80.74.157.31 72.78.100.3 71.175.81.45 69.64.50.226 23.92.28.212 209.188.7.222 198.58.126.7 198.50.242.33 198.50.242.32 192.99.241.164 192.99.13.126 182.92.184.107 182.92.183.58 173.76.224.153 162.243.63.239 162.243.57.246 148.251.70.194 144.76.91.109 108.61.10.90 THANKS.But it doesn't work for me.
|
|
|
|
defaced
Legendary
Offline
Activity: 2198
Merit: 1014
Franko is Freedom
|
|
October 26, 2014, 12:40:58 PM |
|
looks just like you mullick
|
|
|
|
WDL
Newbie
Offline
Activity: 54
Merit: 0
|
|
October 26, 2014, 06:02:49 PM |
|
New nodes from 26 October: 37.187.144.36 67.209.191.40 193.150.121.37 193.150.121.66 211.149.175.37 37.187.134.204 54.201.183.106 96.126.102.159 104.131.230.129 162.243.149.125 162.243.227.221 162.252.242.123 162.255.116.196 81.247.69.65 80.74.157.31 72.78.100.3 71.175.81.45 69.64.50.226 23.92.28.212 209.188.7.222 198.58.126.7 198.50.242.33 198.50.242.32 192.99.241.164 192.99.13.126 182.92.184.107 182.92.183.58 173.76.224.153 162.243.63.239 162.243.57.246 148.251.70.194 144.76.91.109 108.61.10.90 THANKS.But it doesn't work for me. Thanks for your kind. And it just doesn't work for me. Wierd. Need help.
|
|
|
|
gunzeon
Member
Offline
Activity: 73
Merit: 10
There's a new king in the streets
|
|
October 26, 2014, 06:50:50 PM |
|
Just to be sure, you must put lines in your anoncoin.conf thus: addnode=37.187.144.36 addnode=67.209.191.40 ... and so on for all the IPs that are on the list Apologies if you'd already done it this way but never know
|
BTC: 1gunzeo8X7iYznsnmgveUQDuRj6vhzyK6 ~~~
|
|
|
WDL
Newbie
Offline
Activity: 54
Merit: 0
|
|
October 26, 2014, 07:02:09 PM |
|
Just to be sure, you must put lines in your anoncoin.conf thus: addnode=37.187.144.36 addnode=67.209.191.40 ... and so on for all the IPs that are on the list Apologies if you'd already done it this way but never know Of course I do.But no snyc.So wierd.
|
|
|
|
robinson5
|
|
October 27, 2014, 03:43:41 AM |
|
I'm starting to get concerned. First there were the zerocoin delays and the exchange problems. But now meeh, who was supposed to give an update on the auxPoW and difficulty problems, is asking people what they think of myriad? Didn't the community decide we wanted to switch about a month ago and according to this post ( http://www.reddit.com/r/Anoncoin/comments/2ix6ny/a_hard_fork_is_imminent_pay_attention_to_forum/) a hardfork was supposed to happen? How is meeh now asking what we think of myriad and auxPoW? Wasn't he supposedly coding for a hardfork the past month? Is anyone able to read code and verify that there has been actual progress on this coin? Exchanges still aren't working and my coins are still stuck in crypsty! I don't think this is a cryptsy problem. The devs need to fix this and work with the exchanges rather than trying to blame it on them. Edit: Are there any exchanges that are currently allowing anoncoin trading? I couldn't buy/sell any if I decided I wanted to
|
|
|
|
thunderjet
|
|
October 27, 2014, 04:08:58 AM |
|
Anoncoin rpcwallet.cpp is broken.That is a probable cause of wallet erratic behaviour.Error in code for wallet tx - JSON connection :
Line 41 - if (confirms) should be if (confirms > 0)
|
|
|
|
|