newb4now



Offline



Activity: 686

Merit: 500







Hero MemberActivity: 686Merit: 500 Re: Official Anoncoin chat thread (including history) October 02, 2014, 07:52:09 AM #3061



The issue seems to be continually ignored and is of extreme importance for Anoncoin. Before Zerocoin is launced can we please try to fix whatever bug in the Anoncoin code that is causing transactions to get stuck?



Cryptocurrencies are worthless if they cannot be used in transactions (without getting stuck). Merged inputs occur and are not an excuse to ignore the issue.



Quote from: mullick on September 18, 2014, 03:45:34 AM



I have NOT modified our daemon in anyway. We have built directly from source with no changes. Anoncoind is creating these transaction and paying the large fee required. yet they are not being accepted into the chain. As you can see by my previous post.



Quote from: mullick on August 14, 2014, 07:45:14 PM



Im currently investigating an issue with our ANC wallet where the blockchain isnt picking up the majority of our send transactions. We apologize it took us so long to spot the issue. But we are working hard on correcting it and getting the unconfirmed transactions pushed to the blockchain



Some of them get confirmed after a simple restart of the daemon but others do not/ Ill keep everyone informed when I find the solution



Thank you for your patience



UPDATE:



I think it comes down to transaction sizes. Our daemon is sending transactions that are too large to be accpeted into the chain. Im basing this on the fact that all unconfirmed send transactions have unusually high fees paid. Our default Txfee is .01 ANC and the mean over the last 1000 transactions is 0.10169169169169 which is why our withdrawal fee is set to .1 ANC



Code: anoncoind listtransactions "" 1000 | grep -A 1 -B 4 '"confirmations" : 0,' | grep fee

"fee" : -0.82000000,

"fee" : -0.90000000,

"fee" : -0.98000000,

"fee" : -0.65000000,

"fee" : -0.69000000,

"fee" : -0.72000000,

"fee" : -0.74000000,

"fee" : -0.76000000,

"fee" : -0.77000000,

"fee" : -0.81000000,

"fee" : -1.00000000,

"fee" : -0.68000000,

"fee" : -0.72000000,

"fee" : -0.73000000,

"fee" : -0.74000000,

"fee" : -0.74000000,

"fee" : -0.74000000,

"fee" : -0.75000000,

"fee" : -0.75000000,

"fee" : -0.75000000,

"fee" : -0.75000000,

"fee" : -0.75000000,

"fee" : -0.75000000,

"fee" : -0.75000000,

"fee" : -0.75000000,

"fee" : -0.76000000,

"fee" : -0.76000000,

"fee" : -0.77000000,

"fee" : -0.77000000,

"fee" : -0.77000000,

"fee" : -0.78000000,

"fee" : -0.79000000,

"fee" : -0.85000000,

"fee" : -0.96000000,

"fee" : -0.64000000,

"fee" : -0.66000000,

"fee" : -0.67000000,

"fee" : -0.69000000,

"fee" : -0.71000000,

"fee" : -0.72000000,

"fee" : -0.73000000,

"fee" : -0.74000000,

"fee" : -0.75000000,

"fee" : -0.77000000,

"fee" : -0.79000000,

"fee" : -0.84000000,

"fee" : -0.87000000,

"fee" : -0.92000000,

"fee" : -0.95000000,

"fee" : -0.98000000,

"fee" : -0.63000000,

"fee" : -0.64000000,

"fee" : -0.65000000,

"fee" : -0.66000000,

"fee" : -0.68000000,

"fee" : -0.68000000,

"fee" : -0.69000000,

"fee" : -0.70000000,

"fee" : -0.71000000,

"fee" : -0.71000000,

"fee" : -0.72000000,

"fee" : -0.73000000,

"fee" : -0.74000000,

"fee" : -0.74000000,

"fee" : -0.74000000,

"fee" : -0.74000000,

"fee" : -0.74000000,

"fee" : -0.75000000,

"fee" : -0.75000000,

"fee" : -0.75000000,

"fee" : -0.75000000,

"fee" : -0.76000000,

"fee" : -0.78000000,

"fee" : -0.80000000,

"fee" : -0.83000000,

"fee" : -0.88000000,

"fee" : -0.92000000,

"fee" : -0.99000000,

"fee" : -0.98000000,

"fee" : -0.97000000,

"fee" : -0.87000000,

"fee" : -0.81000000,

"fee" : -0.86000000,

Our daemon is up to date so ill be going over the source to see if I can find anything that would cause this

Hello everyone,Im currently investigating an issue with our ANC wallet where the blockchain isnt picking up the majority of our send transactions. We apologize it took us so long to spot the issue. But we are working hard on correcting it and getting the unconfirmed transactions pushed to the blockchainSome of them get confirmed after a simple restart of the daemon but others do not/ Ill keep everyone informed when I find the solutionThank you for your patienceUPDATE:I think it comes down to transaction sizes. Our daemon is sending transactions that are too large to be accpeted into the chain. Im basing this on the fact that all unconfirmed send transactions have unusually high fees paid. Our default Txfee is .01 ANC and the mean over the last 1000 transactions is 0.10169169169169 which is why our withdrawal fee is set to .1 ANCOur daemon is up to date so ill be going over the source to see if I can find anything that would cause this

As you can see from my request to the daemon:



Code: anoncoind listtransactions "" 1000 | grep -A 1 -B 4 '"confirmations" : 0,' | grep fee

I grabbed the last 1000 transactions and searched for any with "confirmations" : 0, and grabbed the fee for the transaction.



All of the unconfirmed transactions in our wallet paid a high fee suggesting its due to block size.



To counteract this until the issue is resolved by the developers i have merged any input in our wallet less than .1 anc ( about 50k of them ) into inputs over 1 ANC. These may have broken down to some smaller ones now so ill likely have to run it again



Here are some others with the same problem



Quote from: shtako on August 23, 2014, 07:57:45 AM Quote from: SmokingSkull on August 21, 2014, 07:50:06 PM



It makes me mad all the time



And It's not good at all for beginners who want to buy into ANC when there are problems with Buying and Withdrawing.

Same Problem.It makes me mad all the timeAnd It's not good at all for beginners who want to buy into ANC when there are problems with Buying and Withdrawing.

Same problem. Tried to withdraw from bleutrade 2 days ago and the transaction still havent gone trough. To fix this should be highest priority.

Same problem. Tried to withdraw from bleutrade 2 days ago and the transaction still havent gone trough. To fix this should be highest priority.

Quote from: niteglider on August 22, 2014, 11:31:12 PM Quote from: TCB4728 on August 21, 2014, 06:32:52 PM Anyone else with the following problems with ANC? My multipool operator sent earned ANC to me on August 18 at 2:01AM CDT, was not received and posted to my wallet until August 21 at 13:58 CDT. The multipool operator states: "The transaction hasn't been included in a block yet. It should make it into a block eventually and be confirmed. I have no control over this. It's been an ongoing issue with the ANC network for a few weeks now." That would seem to be a very strong negative against this coin.









Yes, I am on the anonmining.com pool and it took a couple of days for an autotransfer to actually post to my wallet.



It was only 5 ANCs.



What gives?

Yes, I am on the anonmining.com pool and it took a couple of days for an autotransfer to actually post to my wallet.It was only 5 ANCs.What gives?

In conclusion this is not a problem with cryptsy or "craptsy" as it is being called. It seems meeh and k1773R are aware and getting these transactions to confirm eventually so i see no reason to suspend the wallet as suggested above

Ok lets clear this up once and for all.I have NOT modified our daemon in anyway. We have built directly from source with no changes. Anoncoind is creating these transaction and paying the large fee required. yet they are not being accepted into the chain. As you can see by my previous post.As you can see from my request to the daemon:I grabbed the last 1000 transactions and searched for any with "confirmations" : 0, and grabbed the fee for the transaction.All of the unconfirmed transactions in our wallet paid a high fee suggesting its due to block size.To counteract this until the issue is resolved by the developers i have merged any input in our wallet less than .1 anc ( about 50k of them ) into inputs over 1 ANC. These may have broken down to some smaller ones now so ill likely have to run it againHere are some others with the same problemIn conclusion this is not a problem with cryptsy or "craptsy" as it is being called. It seems meeh and k1773R are aware and getting these transactions to confirm eventually so i see no reason to suspend the wallet as suggested above SOMEONE PLEASE RESPOND TO THIS.The issue seems to be continually ignored and is of extreme importance for Anoncoin. Before Zerocoin is launced can we please try to fix whatever bug in the Anoncoin code that is causing transactions to get stuck?Cryptocurrencies are worthless if they cannot be used in transactions (without getting stuck). Merged inputs occur and are not an excuse to ignore the issue.

BlindMayorBitcorn



Offline



Activity: 1260

Merit: 1107









LegendaryActivity: 1260Merit: 1107 Re: Official Anoncoin chat thread (including history) October 02, 2014, 07:59:38 AM #3062 How crypto This is why the insane pump the second after I divest...Big sticky transactions in teh blockchainHow crypto Forgive my petulance and oft-times, I fear, ill-founded criticisms, and forgive me that I have, by this time, made your eyes and head ache with my long letter. But I cannot forgo hastily the pleasure and pride of thus conversing with you.

lunokhod2



Offline



Activity: 249

Merit: 250







Sr. MemberActivity: 249Merit: 250 Re: Official Anoncoin chat thread (including history) October 02, 2014, 09:03:25 AM #3065 Quote from: newb4now on October 02, 2014, 07:52:09 AM



The issue seems to be continually ignored and is of extreme importance for Anoncoin. Before Zerocoin is launced can we please try to fix whatever bug in the Anoncoin code that is causing transactions to get stuck?



Cryptocurrencies are worthless if they cannot be used in transactions (without getting stuck). Merged inputs occur and are not an excuse to ignore the issue.



Quote from: mullick on September 18, 2014, 03:45:34 AM



I have NOT modified our daemon in anyway. We have built directly from source with no changes. Anoncoind is creating these transaction and paying the large fee required. yet they are not being accepted into the chain. As you can see by my previous post.



Quote from: mullick on August 14, 2014, 07:45:14 PM



Im currently investigating an issue with our ANC wallet where the blockchain isnt picking up the majority of our send transactions. We apologize it took us so long to spot the issue. But we are working hard on correcting it and getting the unconfirmed transactions pushed to the blockchain



Some of them get confirmed after a simple restart of the daemon but others do not/ Ill keep everyone informed when I find the solution



Thank you for your patience



UPDATE:



I think it comes down to transaction sizes. Our daemon is sending transactions that are too large to be accpeted into the chain. Im basing this on the fact that all unconfirmed send transactions have unusually high fees paid. Our default Txfee is .01 ANC and the mean over the last 1000 transactions is 0.10169169169169 which is why our withdrawal fee is set to .1 ANC



Code: anoncoind listtransactions "" 1000 | grep -A 1 -B 4 '"confirmations" : 0,' | grep fee

"fee" : -0.82000000,

"fee" : -0.90000000,

"fee" : -0.98000000,

"fee" : -0.65000000,

"fee" : -0.69000000,

"fee" : -0.72000000,

"fee" : -0.74000000,

"fee" : -0.76000000,

"fee" : -0.77000000,

"fee" : -0.81000000,

"fee" : -1.00000000,

"fee" : -0.68000000,

"fee" : -0.72000000,

"fee" : -0.73000000,

"fee" : -0.74000000,

"fee" : -0.74000000,

"fee" : -0.74000000,

"fee" : -0.75000000,

"fee" : -0.75000000,

"fee" : -0.75000000,

"fee" : -0.75000000,

"fee" : -0.75000000,

"fee" : -0.75000000,

"fee" : -0.75000000,

"fee" : -0.75000000,

"fee" : -0.76000000,

"fee" : -0.76000000,

"fee" : -0.77000000,

"fee" : -0.77000000,

"fee" : -0.77000000,

"fee" : -0.78000000,

"fee" : -0.79000000,

"fee" : -0.85000000,

"fee" : -0.96000000,

"fee" : -0.64000000,

"fee" : -0.66000000,

"fee" : -0.67000000,

"fee" : -0.69000000,

"fee" : -0.71000000,

"fee" : -0.72000000,

"fee" : -0.73000000,

"fee" : -0.74000000,

"fee" : -0.75000000,

"fee" : -0.77000000,

"fee" : -0.79000000,

"fee" : -0.84000000,

"fee" : -0.87000000,

"fee" : -0.92000000,

"fee" : -0.95000000,

"fee" : -0.98000000,

"fee" : -0.63000000,

"fee" : -0.64000000,

"fee" : -0.65000000,

"fee" : -0.66000000,

"fee" : -0.68000000,

"fee" : -0.68000000,

"fee" : -0.69000000,

"fee" : -0.70000000,

"fee" : -0.71000000,

"fee" : -0.71000000,

"fee" : -0.72000000,

"fee" : -0.73000000,

"fee" : -0.74000000,

"fee" : -0.74000000,

"fee" : -0.74000000,

"fee" : -0.74000000,

"fee" : -0.74000000,

"fee" : -0.75000000,

"fee" : -0.75000000,

"fee" : -0.75000000,

"fee" : -0.75000000,

"fee" : -0.76000000,

"fee" : -0.78000000,

"fee" : -0.80000000,

"fee" : -0.83000000,

"fee" : -0.88000000,

"fee" : -0.92000000,

"fee" : -0.99000000,

"fee" : -0.98000000,

"fee" : -0.97000000,

"fee" : -0.87000000,

"fee" : -0.81000000,

"fee" : -0.86000000,

Our daemon is up to date so ill be going over the source to see if I can find anything that would cause this

Hello everyone,Im currently investigating an issue with our ANC wallet where the blockchain isnt picking up the majority of our send transactions. We apologize it took us so long to spot the issue. But we are working hard on correcting it and getting the unconfirmed transactions pushed to the blockchainSome of them get confirmed after a simple restart of the daemon but others do not/ Ill keep everyone informed when I find the solutionThank you for your patienceUPDATE:I think it comes down to transaction sizes. Our daemon is sending transactions that are too large to be accpeted into the chain. Im basing this on the fact that all unconfirmed send transactions have unusually high fees paid. Our default Txfee is .01 ANC and the mean over the last 1000 transactions is 0.10169169169169 which is why our withdrawal fee is set to .1 ANCOur daemon is up to date so ill be going over the source to see if I can find anything that would cause this

As you can see from my request to the daemon:



Code: anoncoind listtransactions "" 1000 | grep -A 1 -B 4 '"confirmations" : 0,' | grep fee

I grabbed the last 1000 transactions and searched for any with "confirmations" : 0, and grabbed the fee for the transaction.



All of the unconfirmed transactions in our wallet paid a high fee suggesting its due to block size.



To counteract this until the issue is resolved by the developers i have merged any input in our wallet less than .1 anc ( about 50k of them ) into inputs over 1 ANC. These may have broken down to some smaller ones now so ill likely have to run it again



Here are some others with the same problem



Quote from: shtako on August 23, 2014, 07:57:45 AM Quote from: SmokingSkull on August 21, 2014, 07:50:06 PM



It makes me mad all the time



And It's not good at all for beginners who want to buy into ANC when there are problems with Buying and Withdrawing.

Same Problem.It makes me mad all the timeAnd It's not good at all for beginners who want to buy into ANC when there are problems with Buying and Withdrawing.

Same problem. Tried to withdraw from bleutrade 2 days ago and the transaction still havent gone trough. To fix this should be highest priority.

Same problem. Tried to withdraw from bleutrade 2 days ago and the transaction still havent gone trough. To fix this should be highest priority.

Quote from: niteglider on August 22, 2014, 11:31:12 PM Quote from: TCB4728 on August 21, 2014, 06:32:52 PM Anyone else with the following problems with ANC? My multipool operator sent earned ANC to me on August 18 at 2:01AM CDT, was not received and posted to my wallet until August 21 at 13:58 CDT. The multipool operator states: "The transaction hasn't been included in a block yet. It should make it into a block eventually and be confirmed. I have no control over this. It's been an ongoing issue with the ANC network for a few weeks now." That would seem to be a very strong negative against this coin.









Yes, I am on the anonmining.com pool and it took a couple of days for an autotransfer to actually post to my wallet.



It was only 5 ANCs.



What gives?

Yes, I am on the anonmining.com pool and it took a couple of days for an autotransfer to actually post to my wallet.It was only 5 ANCs.What gives?

In conclusion this is not a problem with cryptsy or "craptsy" as it is being called. It seems meeh and k1773R are aware and getting these transactions to confirm eventually so i see no reason to suspend the wallet as suggested above

Ok lets clear this up once and for all.I have NOT modified our daemon in anyway. We have built directly from source with no changes. Anoncoind is creating these transaction and paying the large fee required. yet they are not being accepted into the chain. As you can see by my previous post.As you can see from my request to the daemon:I grabbed the last 1000 transactions and searched for any with "confirmations" : 0, and grabbed the fee for the transaction.All of the unconfirmed transactions in our wallet paid a high fee suggesting its due to block size.To counteract this until the issue is resolved by the developers i have merged any input in our wallet less than .1 anc ( about 50k of them ) into inputs over 1 ANC. These may have broken down to some smaller ones now so ill likely have to run it againHere are some others with the same problemIn conclusion this is not a problem with cryptsy or "craptsy" as it is being called. It seems meeh and k1773R are aware and getting these transactions to confirm eventually so i see no reason to suspend the wallet as suggested above SOMEONE PLEASE RESPOND TO THIS.The issue seems to be continually ignored and is of extreme importance for Anoncoin. Before Zerocoin is launced can we please try to fix whatever bug in the Anoncoin code that is causing transactions to get stuck?Cryptocurrencies are worthless if they cannot be used in transactions (without getting stuck). Merged inputs occur and are not an excuse to ignore the issue.

K1773R claims that the problem is with Cryptsy, and that he is not interested in fixing their problems. K1773R claims that the problem is with Cryptsy, and that he is not interested in fixing their problems.

newb4now



Offline



Activity: 686

Merit: 500







Hero MemberActivity: 686Merit: 500 Re: Official Anoncoin chat thread (including history) October 02, 2014, 09:09:05 AM #3066 Quote from: lunokhod2 on October 02, 2014, 09:03:25 AM Quote from: newb4now on October 02, 2014, 07:52:09 AM



The issue seems to be continually ignored and is of extreme importance for Anoncoin. Before Zerocoin is launced can we please try to fix whatever bug in the Anoncoin code that is causing transactions to get stuck?



Cryptocurrencies are worthless if they cannot be used in transactions (without getting stuck). Merged inputs occur and are not an excuse to ignore the issue.



Quote from: mullick on September 18, 2014, 03:45:34 AM



I have NOT modified our daemon in anyway. We have built directly from source with no changes. Anoncoind is creating these transaction and paying the large fee required. yet they are not being accepted into the chain. As you can see by my previous post.



Quote from: mullick on August 14, 2014, 07:45:14 PM



Im currently investigating an issue with our ANC wallet where the blockchain isnt picking up the majority of our send transactions. We apologize it took us so long to spot the issue. But we are working hard on correcting it and getting the unconfirmed transactions pushed to the blockchain



Some of them get confirmed after a simple restart of the daemon but others do not/ Ill keep everyone informed when I find the solution



Thank you for your patience



UPDATE:



I think it comes down to transaction sizes. Our daemon is sending transactions that are too large to be accpeted into the chain. Im basing this on the fact that all unconfirmed send transactions have unusually high fees paid. Our default Txfee is .01 ANC and the mean over the last 1000 transactions is 0.10169169169169 which is why our withdrawal fee is set to .1 ANC



Code: anoncoind listtransactions "" 1000 | grep -A 1 -B 4 '"confirmations" : 0,' | grep fee

"fee" : -0.82000000,

"fee" : -0.90000000,

"fee" : -0.98000000,

"fee" : -0.65000000,

"fee" : -0.69000000,

"fee" : -0.72000000,

"fee" : -0.74000000,

"fee" : -0.76000000,

"fee" : -0.77000000,

"fee" : -0.81000000,

"fee" : -1.00000000,

"fee" : -0.68000000,

"fee" : -0.72000000,

"fee" : -0.73000000,

"fee" : -0.74000000,

"fee" : -0.74000000,

"fee" : -0.74000000,

"fee" : -0.75000000,

"fee" : -0.75000000,

"fee" : -0.75000000,

"fee" : -0.75000000,

"fee" : -0.75000000,

"fee" : -0.75000000,

"fee" : -0.75000000,

"fee" : -0.75000000,

"fee" : -0.76000000,

"fee" : -0.76000000,

"fee" : -0.77000000,

"fee" : -0.77000000,

"fee" : -0.77000000,

"fee" : -0.78000000,

"fee" : -0.79000000,

"fee" : -0.85000000,

"fee" : -0.96000000,

"fee" : -0.64000000,

"fee" : -0.66000000,

"fee" : -0.67000000,

"fee" : -0.69000000,

"fee" : -0.71000000,

"fee" : -0.72000000,

"fee" : -0.73000000,

"fee" : -0.74000000,

"fee" : -0.75000000,

"fee" : -0.77000000,

"fee" : -0.79000000,

"fee" : -0.84000000,

"fee" : -0.87000000,

"fee" : -0.92000000,

"fee" : -0.95000000,

"fee" : -0.98000000,

"fee" : -0.63000000,

"fee" : -0.64000000,

"fee" : -0.65000000,

"fee" : -0.66000000,

"fee" : -0.68000000,

"fee" : -0.68000000,

"fee" : -0.69000000,

"fee" : -0.70000000,

"fee" : -0.71000000,

"fee" : -0.71000000,

"fee" : -0.72000000,

"fee" : -0.73000000,

"fee" : -0.74000000,

"fee" : -0.74000000,

"fee" : -0.74000000,

"fee" : -0.74000000,

"fee" : -0.74000000,

"fee" : -0.75000000,

"fee" : -0.75000000,

"fee" : -0.75000000,

"fee" : -0.75000000,

"fee" : -0.76000000,

"fee" : -0.78000000,

"fee" : -0.80000000,

"fee" : -0.83000000,

"fee" : -0.88000000,

"fee" : -0.92000000,

"fee" : -0.99000000,

"fee" : -0.98000000,

"fee" : -0.97000000,

"fee" : -0.87000000,

"fee" : -0.81000000,

"fee" : -0.86000000,

Our daemon is up to date so ill be going over the source to see if I can find anything that would cause this

Hello everyone,Im currently investigating an issue with our ANC wallet where the blockchain isnt picking up the majority of our send transactions. We apologize it took us so long to spot the issue. But we are working hard on correcting it and getting the unconfirmed transactions pushed to the blockchainSome of them get confirmed after a simple restart of the daemon but others do not/ Ill keep everyone informed when I find the solutionThank you for your patienceUPDATE:I think it comes down to transaction sizes. Our daemon is sending transactions that are too large to be accpeted into the chain. Im basing this on the fact that all unconfirmed send transactions have unusually high fees paid. Our default Txfee is .01 ANC and the mean over the last 1000 transactions is 0.10169169169169 which is why our withdrawal fee is set to .1 ANCOur daemon is up to date so ill be going over the source to see if I can find anything that would cause this

As you can see from my request to the daemon:



Code: anoncoind listtransactions "" 1000 | grep -A 1 -B 4 '"confirmations" : 0,' | grep fee

I grabbed the last 1000 transactions and searched for any with "confirmations" : 0, and grabbed the fee for the transaction.



All of the unconfirmed transactions in our wallet paid a high fee suggesting its due to block size.



To counteract this until the issue is resolved by the developers i have merged any input in our wallet less than .1 anc ( about 50k of them ) into inputs over 1 ANC. These may have broken down to some smaller ones now so ill likely have to run it again



Here are some others with the same problem



Quote from: shtako on August 23, 2014, 07:57:45 AM Quote from: SmokingSkull on August 21, 2014, 07:50:06 PM



It makes me mad all the time



And It's not good at all for beginners who want to buy into ANC when there are problems with Buying and Withdrawing.

Same Problem.It makes me mad all the timeAnd It's not good at all for beginners who want to buy into ANC when there are problems with Buying and Withdrawing.

Same problem. Tried to withdraw from bleutrade 2 days ago and the transaction still havent gone trough. To fix this should be highest priority.

Same problem. Tried to withdraw from bleutrade 2 days ago and the transaction still havent gone trough. To fix this should be highest priority.

Quote from: niteglider on August 22, 2014, 11:31:12 PM Quote from: TCB4728 on August 21, 2014, 06:32:52 PM Anyone else with the following problems with ANC? My multipool operator sent earned ANC to me on August 18 at 2:01AM CDT, was not received and posted to my wallet until August 21 at 13:58 CDT. The multipool operator states: "The transaction hasn't been included in a block yet. It should make it into a block eventually and be confirmed. I have no control over this. It's been an ongoing issue with the ANC network for a few weeks now." That would seem to be a very strong negative against this coin.









Yes, I am on the anonmining.com pool and it took a couple of days for an autotransfer to actually post to my wallet.



It was only 5 ANCs.



What gives?

Yes, I am on the anonmining.com pool and it took a couple of days for an autotransfer to actually post to my wallet.It was only 5 ANCs.What gives?

In conclusion this is not a problem with cryptsy or "craptsy" as it is being called. It seems meeh and k1773R are aware and getting these transactions to confirm eventually so i see no reason to suspend the wallet as suggested above

Ok lets clear this up once and for all.I have NOT modified our daemon in anyway. We have built directly from source with no changes. Anoncoind is creating these transaction and paying the large fee required. yet they are not being accepted into the chain. As you can see by my previous post.As you can see from my request to the daemon:I grabbed the last 1000 transactions and searched for any with "confirmations" : 0, and grabbed the fee for the transaction.All of the unconfirmed transactions in our wallet paid a high fee suggesting its due to block size.To counteract this until the issue is resolved by the developers i have merged any input in our wallet less than .1 anc ( about 50k of them ) into inputs over 1 ANC. These may have broken down to some smaller ones now so ill likely have to run it againHere are some others with the same problemIn conclusion this is not a problem with cryptsy or "craptsy" as it is being called. It seems meeh and k1773R are aware and getting these transactions to confirm eventually so i see no reason to suspend the wallet as suggested above SOMEONE PLEASE RESPOND TO THIS.The issue seems to be continually ignored and is of extreme importance for Anoncoin. Before Zerocoin is launced can we please try to fix whatever bug in the Anoncoin code that is causing transactions to get stuck?Cryptocurrencies are worthless if they cannot be used in transactions (without getting stuck). Merged inputs occur and are not an excuse to ignore the issue.

K1773R claims that the problem is with Cryptsy, and that he is not interested in fixing their problems.

K1773R claims that the problem is with Cryptsy, and that he is not interested in fixing their problems.

Well Mullick (Crytpsy rep) disagrees. The point is that it needs to be fixed. If ANC wants to attract new investors we cant have transactions getting stuck. Stuck transactions = unusable currency.



Zercoin is what we are looking forward to. But we need to fix our current codebase. If people start buying ANC during Zerocoin beta and get transactions stuck faith will be lost before public release. Since our code is open source, others will steal the hard work of Gnosis on Zerocoin and implement it without the bugs (stuck transactions) that are currently being ignored.



This needs to be top priority. Well Mullick (Crytpsy rep) disagrees. The point is that it needs to be fixed. If ANC wants to attract new investors we cant have transactions getting stuck. Stuck transactions = unusable currency.Zercoin is what we are looking forward to. But we need to fix our current codebase. If people start buying ANC during Zerocoin beta and get transactions stuck faith will be lost before public release. Since our code is open source, others will steal the hard work of Gnosis on Zerocoin and implement it without the bugs (stuck transactions) that are currently being ignored.This needs to be top priority.

niteglider



Offline



Activity: 126

Merit: 100



Lean into the curves.







Full MemberActivity: 126Merit: 100Lean into the curves. Re: Official Anoncoin chat thread (including history) October 02, 2014, 09:23:37 AM #3067 Quote from: newb4now on October 02, 2014, 09:09:05 AM

Well Mullick (Crytpsy rep) disagrees. The point is that it needs to be fixed. If ANC wants to attract new investors we cant have transactions getting stuck. Stuck transactions = unusable currency.



Zercoin is what we are looking forward to. But we need to fix our current codebase. If people start buying ANC during Zerocoin beta and get transactions stuck faith will be lost before public release. Since our code is open source, others will steal the hard work of Gnosis on Zerocoin and implement it without the bugs (stuck transactions) that are currently being ignored.



This needs to be top priority.



Are transactions getting stuck anywhere else besides Cryptsy?



If not, then the problem is obviously on Cryptsy's end.



And once zerocoin goes mainstream, other exchanges will see a rise in volume and Cryptsy won't be the only game in town anymore...



Then Mullick will see to it that the problem is fixed.



If, on the other hand, transactions are getting stuck elsewhere besides Cryptsy, then I have to agree that fixing the problem

ought to be priority #1 for the reason newb4now posted. Are transactions getting stuck anywhere else besides Cryptsy?If not, then the problem is obviously on Cryptsy's end.And once zerocoin goes mainstream, other exchanges will see a rise in volume and Cryptsy won't be the only game in town anymore...Then Mullick will see to it that the problem is fixed.If, on the other hand, transactions are getting stuck elsewhere besides Cryptsy, then I have to agree that fixing the problemought to be priority #1 for the reason newb4now posted. Anoncoin

lunokhod2



Offline



Activity: 249

Merit: 250







Sr. MemberActivity: 249Merit: 250 Re: Official Anoncoin chat thread (including history) October 02, 2014, 09:31:31 AM #3068 Quote from: newb4now on October 02, 2014, 09:09:05 AM Quote from: lunokhod2 on October 02, 2014, 09:03:25 AM Quote from: newb4now on October 02, 2014, 07:52:09 AM



The issue seems to be continually ignored and is of extreme importance for Anoncoin. Before Zerocoin is launced can we please try to fix whatever bug in the Anoncoin code that is causing transactions to get stuck?



Cryptocurrencies are worthless if they cannot be used in transactions (without getting stuck). Merged inputs occur and are not an excuse to ignore the issue.



Quote from: mullick on September 18, 2014, 03:45:34 AM



I have NOT modified our daemon in anyway. We have built directly from source with no changes. Anoncoind is creating these transaction and paying the large fee required. yet they are not being accepted into the chain. As you can see by my previous post.



Quote from: mullick on August 14, 2014, 07:45:14 PM



Im currently investigating an issue with our ANC wallet where the blockchain isnt picking up the majority of our send transactions. We apologize it took us so long to spot the issue. But we are working hard on correcting it and getting the unconfirmed transactions pushed to the blockchain



Some of them get confirmed after a simple restart of the daemon but others do not/ Ill keep everyone informed when I find the solution



Thank you for your patience



UPDATE:



I think it comes down to transaction sizes. Our daemon is sending transactions that are too large to be accpeted into the chain. Im basing this on the fact that all unconfirmed send transactions have unusually high fees paid. Our default Txfee is .01 ANC and the mean over the last 1000 transactions is 0.10169169169169 which is why our withdrawal fee is set to .1 ANC



Code: anoncoind listtransactions "" 1000 | grep -A 1 -B 4 '"confirmations" : 0,' | grep fee

"fee" : -0.82000000,

"fee" : -0.90000000,

"fee" : -0.98000000,

"fee" : -0.65000000,

"fee" : -0.69000000,

"fee" : -0.72000000,

"fee" : -0.74000000,

"fee" : -0.76000000,

"fee" : -0.77000000,

"fee" : -0.81000000,

"fee" : -1.00000000,

"fee" : -0.68000000,

"fee" : -0.72000000,

"fee" : -0.73000000,

"fee" : -0.74000000,

"fee" : -0.74000000,

"fee" : -0.74000000,

"fee" : -0.75000000,

"fee" : -0.75000000,

"fee" : -0.75000000,

"fee" : -0.75000000,

"fee" : -0.75000000,

"fee" : -0.75000000,

"fee" : -0.75000000,

"fee" : -0.75000000,

"fee" : -0.76000000,

"fee" : -0.76000000,

"fee" : -0.77000000,

"fee" : -0.77000000,

"fee" : -0.77000000,

"fee" : -0.78000000,

"fee" : -0.79000000,

"fee" : -0.85000000,

"fee" : -0.96000000,

"fee" : -0.64000000,

"fee" : -0.66000000,

"fee" : -0.67000000,

"fee" : -0.69000000,

"fee" : -0.71000000,

"fee" : -0.72000000,

"fee" : -0.73000000,

"fee" : -0.74000000,

"fee" : -0.75000000,

"fee" : -0.77000000,

"fee" : -0.79000000,

"fee" : -0.84000000,

"fee" : -0.87000000,

"fee" : -0.92000000,

"fee" : -0.95000000,

"fee" : -0.98000000,

"fee" : -0.63000000,

"fee" : -0.64000000,

"fee" : -0.65000000,

"fee" : -0.66000000,

"fee" : -0.68000000,

"fee" : -0.68000000,

"fee" : -0.69000000,

"fee" : -0.70000000,

"fee" : -0.71000000,

"fee" : -0.71000000,

"fee" : -0.72000000,

"fee" : -0.73000000,

"fee" : -0.74000000,

"fee" : -0.74000000,

"fee" : -0.74000000,

"fee" : -0.74000000,

"fee" : -0.74000000,

"fee" : -0.75000000,

"fee" : -0.75000000,

"fee" : -0.75000000,

"fee" : -0.75000000,

"fee" : -0.76000000,

"fee" : -0.78000000,

"fee" : -0.80000000,

"fee" : -0.83000000,

"fee" : -0.88000000,

"fee" : -0.92000000,

"fee" : -0.99000000,

"fee" : -0.98000000,

"fee" : -0.97000000,

"fee" : -0.87000000,

"fee" : -0.81000000,

"fee" : -0.86000000,

Our daemon is up to date so ill be going over the source to see if I can find anything that would cause this

Hello everyone,Im currently investigating an issue with our ANC wallet where the blockchain isnt picking up the majority of our send transactions. We apologize it took us so long to spot the issue. But we are working hard on correcting it and getting the unconfirmed transactions pushed to the blockchainSome of them get confirmed after a simple restart of the daemon but others do not/ Ill keep everyone informed when I find the solutionThank you for your patienceUPDATE:I think it comes down to transaction sizes. Our daemon is sending transactions that are too large to be accpeted into the chain. Im basing this on the fact that all unconfirmed send transactions have unusually high fees paid. Our default Txfee is .01 ANC and the mean over the last 1000 transactions is 0.10169169169169 which is why our withdrawal fee is set to .1 ANCOur daemon is up to date so ill be going over the source to see if I can find anything that would cause this

As you can see from my request to the daemon:



Code: anoncoind listtransactions "" 1000 | grep -A 1 -B 4 '"confirmations" : 0,' | grep fee

I grabbed the last 1000 transactions and searched for any with "confirmations" : 0, and grabbed the fee for the transaction.



All of the unconfirmed transactions in our wallet paid a high fee suggesting its due to block size.



To counteract this until the issue is resolved by the developers i have merged any input in our wallet less than .1 anc ( about 50k of them ) into inputs over 1 ANC. These may have broken down to some smaller ones now so ill likely have to run it again



Here are some others with the same problem



Quote from: shtako on August 23, 2014, 07:57:45 AM Quote from: SmokingSkull on August 21, 2014, 07:50:06 PM



It makes me mad all the time



And It's not good at all for beginners who want to buy into ANC when there are problems with Buying and Withdrawing.

Same Problem.It makes me mad all the timeAnd It's not good at all for beginners who want to buy into ANC when there are problems with Buying and Withdrawing.

Same problem. Tried to withdraw from bleutrade 2 days ago and the transaction still havent gone trough. To fix this should be highest priority.

Same problem. Tried to withdraw from bleutrade 2 days ago and the transaction still havent gone trough. To fix this should be highest priority.

Quote from: niteglider on August 22, 2014, 11:31:12 PM Quote from: TCB4728 on August 21, 2014, 06:32:52 PM Anyone else with the following problems with ANC? My multipool operator sent earned ANC to me on August 18 at 2:01AM CDT, was not received and posted to my wallet until August 21 at 13:58 CDT. The multipool operator states: "The transaction hasn't been included in a block yet. It should make it into a block eventually and be confirmed. I have no control over this. It's been an ongoing issue with the ANC network for a few weeks now." That would seem to be a very strong negative against this coin.









Yes, I am on the anonmining.com pool and it took a couple of days for an autotransfer to actually post to my wallet.



It was only 5 ANCs.



What gives?

Yes, I am on the anonmining.com pool and it took a couple of days for an autotransfer to actually post to my wallet.It was only 5 ANCs.What gives?

In conclusion this is not a problem with cryptsy or "craptsy" as it is being called. It seems meeh and k1773R are aware and getting these transactions to confirm eventually so i see no reason to suspend the wallet as suggested above

Ok lets clear this up once and for all.I have NOT modified our daemon in anyway. We have built directly from source with no changes. Anoncoind is creating these transaction and paying the large fee required. yet they are not being accepted into the chain. As you can see by my previous post.As you can see from my request to the daemon:I grabbed the last 1000 transactions and searched for any with "confirmations" : 0, and grabbed the fee for the transaction.All of the unconfirmed transactions in our wallet paid a high fee suggesting its due to block size.To counteract this until the issue is resolved by the developers i have merged any input in our wallet less than .1 anc ( about 50k of them ) into inputs over 1 ANC. These may have broken down to some smaller ones now so ill likely have to run it againHere are some others with the same problemIn conclusion this is not a problem with cryptsy or "craptsy" as it is being called. It seems meeh and k1773R are aware and getting these transactions to confirm eventually so i see no reason to suspend the wallet as suggested above SOMEONE PLEASE RESPOND TO THIS.The issue seems to be continually ignored and is of extreme importance for Anoncoin. Before Zerocoin is launced can we please try to fix whatever bug in the Anoncoin code that is causing transactions to get stuck?Cryptocurrencies are worthless if they cannot be used in transactions (without getting stuck). Merged inputs occur and are not an excuse to ignore the issue.

K1773R claims that the problem is with Cryptsy, and that he is not interested in fixing their problems.

K1773R claims that the problem is with Cryptsy, and that he is not interested in fixing their problems.

Well Mullick (Crytpsy rep) disagrees. The point is that it needs to be fixed. If ANC wants to attract new investors we cant have transactions getting stuck. Stuck transactions = unusable currency.



Zercoin is what we are looking forward to. But we need to fix our current codebase. If people start buying ANC during Zerocoin beta and get transactions stuck faith will be lost before public release. Since our code is open source, others will steal the hard work of Gnosis on Zerocoin and implement it without the bugs (stuck transactions) that are currently being ignored.



This needs to be top priority.

Well Mullick (Crytpsy rep) disagrees. The point is that it needs to be fixed. If ANC wants to attract new investors we cant have transactions getting stuck. Stuck transactions = unusable currency.Zercoin is what we are looking forward to. But we need to fix our current codebase. If people start buying ANC during Zerocoin beta and get transactions stuck faith will be lost before public release. Since our code is open source, others will steal the hard work of Gnosis on Zerocoin and implement it without the bugs (stuck transactions) that are currently being ignored.This needs to be top priority.



Everyone on this thread agrees that Cryptsy blows for reasons other than the stuck transactions. Have you ever dealt with their "customer services"? Have ever noticed the large number of scam coins they are dealing in? I wish that this were fixed as well. However, if the problem is Cryptsy, then investors should lose faith in them, not Anoncoin.Everyone on this thread agrees that Cryptsy blows for reasons other than the stuck transactions. Have you ever dealt with their "customer services"? Have ever noticed the large number of scam coins they are dealing in?

gunzeon



Offline



Activity: 73

Merit: 10





There's a new king in the streets







MemberActivity: 73Merit: 10There's a new king in the streets Re: Official Anoncoin chat thread (including history) October 02, 2014, 11:03:54 AM #3071 wrt Cryptsy Xactions, @K1773R knows how to fix them ....



One I had stuck had 400 inputs, I think K1773R rebroadcast it ... not sure, maybe that's something a cron script anywhere can do ... just my bit's worth BTC: 1gunzeo8X7iYznsnmgveUQDuRj6vhzyK6 ~~~

tomothy



Offline



Activity: 258

Merit: 250







Sr. MemberActivity: 258Merit: 250 Re: Official Anoncoin chat thread (including history) October 02, 2014, 01:20:34 PM #3073 Quote from: K1773R on October 02, 2014, 12:30:19 PM Quote from: gunzeon on October 02, 2014, 11:03:54 AM wrt Cryptsy Xactions, @K1773R knows how to fix them ....



One I had stuck had 400 inputs, I think K1773R rebroadcast it ... not sure, maybe that's something a cron script anywhere can do ... just my bit's worth

No, the person with the stuck tx (sent or recieved) has to rebroadcast it, so i recieve it. all i did was changing max tx size and block creation settings. i pointed this out at some other posts already.

No, the person with the stuck tx (sent or recieved) has to rebroadcast it, so i recieve it. all i did was changing max tx size and block creation settings. i pointed this out at some other posts already.

I've only had issues with transactions originating from cryptsy; never between wallets or friends. Just my $0.02. And I thought I saw a post about Darkcoin/ #drk, going open source? Does anyone else find it amusing that, (if it's true and they finally released the code) they took these steps now; with just a few weeks left until fill implementation of ANC/ZC? Just thought the timing was interesting... lols, there can be only one... I've only had issues with transactions originating from cryptsy; never between wallets or friends. Just my $0.02. And I thought I saw a post about Darkcoin/ #drk, going open source? Does anyone else find it amusing that, (if it's true and they finally released the code) they took these steps now; with just a few weeks left until fill implementation of ANC/ZC? Just thought the timing was interesting... lols, there can be only one...

BlindMayorBitcorn



Offline



Activity: 1260

Merit: 1107









LegendaryActivity: 1260Merit: 1107 Re: Official Anoncoin chat thread (including history) October 02, 2014, 01:49:51 PM #3074 Quote from: tomothy on October 02, 2014, 01:20:34 PM Quote from: K1773R on October 02, 2014, 12:30:19 PM Quote from: gunzeon on October 02, 2014, 11:03:54 AM wrt Cryptsy Xactions, @K1773R knows how to fix them ....



One I had stuck had 400 inputs, I think K1773R rebroadcast it ... not sure, maybe that's something a cron script anywhere can do ... just my bit's worth

No, the person with the stuck tx (sent or recieved) has to rebroadcast it, so i recieve it. all i did was changing max tx size and block creation settings. i pointed this out at some other posts already.

No, the person with the stuck tx (sent or recieved) has to rebroadcast it, so i recieve it. all i did was changing max tx size and block creation settings. i pointed this out at some other posts already.

I've only had issues with transactions originating from cryptsy; never between wallets or friends. Just my $0.02. And I thought I saw a post about Darkcoin/ #drk, going open source? Does anyone else find it amusing that, (if it's true and they finally released the code) they took these steps now; with just a few weeks left until fill implementation of ANC/ZC? Just thought the timing was interesting... lols, there can be only one...

I've only had issues with transactions originating from cryptsy; never between wallets or friends. Just my $0.02. And I thought I saw a post about Darkcoin/ #drk, going open source? Does anyone else find it amusing that, (if it's true and they finally released the code) they took these steps now; with just a few weeks left until fill implementation of ANC/ZC? Just thought the timing was interesting... lols, there can be only one...

I've been hearing 'within weeks of zerocoin implementation' for ever. Is there an actually date yet? I've been hearing 'within weeks of zerocoin implementation' for ever. Is there an actually date yet? Forgive my petulance and oft-times, I fear, ill-founded criticisms, and forgive me that I have, by this time, made your eyes and head ache with my long letter. But I cannot forgo hastily the pleasure and pride of thus conversing with you.