Topic: Official Anoncoin chat thread (including history) - page 100. (Read 530606 times)

Just days away from Zerocoin beta testing on Oct 15th! All code will be open sourced @github before public launch on Nov 1st

https://twitter.com/AnoncoinTeam/status/520955264145444864

Imminent hard fork will address the mining difficulty problems discussed above

https://pay.reddit.com/r/Anoncoin/comments/2ix6ny/a_hard_fork_is_imminent_pay_attention_to_forum/

I tried to browse through this thread but it's just huge so sorry if I missed it if this has been discussed already - has there been (and if so, what kind of) improvements made to the original zerocoin wrt scaling/performance, fixed denominations (no change transactions), or hiding tx amounts?

Welcome to the community. Feel free to ask any questions you would like about ANC. We have many knowledgeable users who have been around for a long time.

Our wiki page is a great place to start:
https://wiki.anoncoin.net/Anoncoin_Wiki

Here read this about SDC coin trolls and how they caused to Stealth Coin investors thousands of dollars and are trying the same bullshit in order to scare people over to ShadowCash. Don't let what happen to StealthCoin happen to you.

"STEALTHCOIN PRICE PLUMMETS AMID OVERT COMMUNITY CHAOS"

https://www.cryptocoinsnews.com/stealthcoin-price-plummets-amid-overt-community-chaos/

Theses very same trolls are Fuding your coin now. I am an investor in XST, and lost a lot of money. The reason I'm on this forum, is I am looking into other anon coins, and yours looks like a good bet.

I wouldn't listen to this guy. SDC completely shut down XST fourm, the dev condoned FUDing the XST thread brought the XST coin down to less than 5000 from a high of 14,000, and cost a lot of investors a lot of money. I hate to see that happen to ANONcoin, but those shadow guys are bad news. Don't feed them.

The link seems to be working now.

Can anyone comment about the reliability of this pool?

Actually Cryptsy thinks its is our fault
https://bitcointalksearch.org/topic/m.8869037

Quote from mullick (Cryptsy):

"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."

Quote from: mullick on August 14, 2014, 07:45:14 PM
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 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 Smiley

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

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
Same Problem.

It makes me mad all the time  Angry

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. 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?

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"

I think meeh, gnosis, Ian Miers and Matt Green are all trustworthy.  That being said aside from first mover advantage I think we all see our trustless RSA UFO project as our key advantage over a Zerocash setup that requires trust.

If Zerocash finds a way to become truly trustless then we lose that advantage.  As of right now it still sounds like Zerocash will require some element of trust in parameter generation.

Informed  anc.cryptotroll.com pool....... any ETA on the upgrade yet ?

One solution would just be to hold ANC and not trade it at all (on either Bleutrade or Cryptsy) right now. Hopefully the upcoming hard fork will fix all the issues above. If Zerocoin beta goes well then valuation may end up being a lot higher after the mining difficulty problems are fixed.  At that point it should be safe to send ANC to/from the exchanges again

Hahahahahaha........ Nice one!

Hi Anoncoin,

Don't feed these trolls they are not affiliated with Shadow. We respect the development going on here and wish you all the best.

That's how it goes bro.  SDC is the true winner in this game of anon.

That's thanks for support to SDC from one of our member??
I see few of you splits 6.5M SDC in few weeks, yeah, troll around for your free BTC!

https://bitcointalksearch.org/topic/xmr-monero-a-secure-private-untraceable-cryptocurrency-583449

"ANON"coin...what a joke....   

Get in a real coin... https://bitcointalksearch.org/topic/sdc-shadowcash-welcome-to-the-umbra-745352

Drakcoin,

Thanks for gathering facts to clarify the situation with facts !

Let's hope we can correct this situation ASAP because zANC will surely get an intense hammering from all angles by critics/competitors/sour-grapes when it goes live.

We'll need to batten down the hatches against attacks; difficulty, xaction storms, spam, ddos, whatever your imagination can come up with, they'll be out there trying to drag us down.

Awesome.  Looks like they are fixing the diff. algo before ZC implementation. Smart move.

Hello to anons, be ready!

gnosis post on reddit

https://pay.reddit.com/r/Anoncoin/comments/2ix6ny/a_hard_fork_is_imminent_pay_attention_to_forum/

Commonly known exploit/attack/bug/whatever-you-want-to-call-it of KGW. Most other coins that use KGW have patched/fixed. Think I mentioned this before sometime earlier in this thread. Have lived through it on other coins...search the forums for description/fix.

Hint: look for Heartbleed and TimeWarp vulnerabilities.
One possible solution is to add the digishield diff retarget:
https://github.com/casinocoin/casinocoin/commit/1f0b80e20aa13b8aa9146b61344131c5d555c709

Hehehe, ok more than a hint