Search content
Sort by

Showing 20 of 116 results by canoe
Post
Topic
Board Announcements (Altcoins)
Re: [ANN] [V] Version - Rare Desirable NO PREMINE Store of Value -->> v0.8.9.9 FIX
by
canoe
on 26/03/2014, 04:12:54 UTC
I have 16k in my wallet. It syncs till about 3.5k blocks everyday (my guess it is about what zeuspool makes each day). New wallets (0 mined) work just fine and syncs 100%. Frustrated. Looks like Dev is in Hibernation, or found fatal error.  Is this old wallet with all found blocks permanently lost ? Any ides what to do?

My first guess:
If that 16k is 4000 blocks * 4V each then this could be your problem:
http://wiki.hobonickels.info/index.php?title=Coin_Control
Basically, if you have too many inputs in your wallet (more than a thousand), the proof-of-stake miner that is built into the wallet will use your entire cpu.
Encrypting your wallet will stop the proof-of-stake mining.  Then you can combine your V into larger chunks by sending it to a new address in amounts of say 50V.  Then you'd have 320 transaction inputs instead of 4000.  The proof-of-stake miner wouldn't use your whole cpu and the wallet would sync better.

Post
Topic
Board Announcements (Altcoins)
Re: [ANN] [V] Version - Rare Desirable NO PREMINE Store of Value -->> v0.8.9.9 FIX
by
canoe
on 18/03/2014, 15:37:49 UTC
I don't get it. Even with all this talk of broken chains people continue to mine why? In the off chance that their chain is the one they go for and then they have a huge stash of coins from the easy mining? Why keep mining a broken coin?

Difficulty has been rising ever since 0.8.9.9 was released.  So the problem where difficulty kept jumping to near zero is fixed (by removing KGW).  I don't think there are many chains anymore.  I think the chain forking happened when blocks were really fast and now there is one chain.  It was a normal insta-mine scenario like at coin launch.  Maybe you're right.  Maybe I'm right.  If everyone checked this blockhash, we could find out.  So how about it?

Code:
> getblockhash 116170
000000000037e5b31ddd26d24b9abe3739c89acbad6efa5cf4ee1be3acacf2e6

Make sure you move out your old config directory and use staycrypto's seed node when downloading the blockchain: "addnode=192.241.240.148"

I've updated the blockchain charts for version:
http://cryptometer.org/version_90_day_charts.html
You can see 4 empty days that were erased because of the KGW exploit followed by a couple days of blocks generated way above the target rate.  But it's levelling out now.  And difficulty won't go down anymore because the exploit is plugged.  The pools might even be able to handle the blockrate soon.

There are still some issues with the client:
1. It rejects blocks submitted by cgminer over RPC.
2. Mindfox says there is something wrong with PoS block transmission.
These could be fixed in an update that takes effect on a future block.

Also, canoe, I will give you my point of view, as a miner now. Not as zeuspool's admin team member, not as a member that tries to help out the coin.

I ceased all mining activity so I can help the developer of this coin revive it and make it stable. The reason I did it: I believe that this coin has potentials.
Is it fair for me, to have all those miners around me mining, while I'm just removing blocks, mining blocks, deleting wallet, so that I can help find the problem and probably a solution?

Then, why don't I just drop everything I do and start mining myself also?

Where is the community in that?

Also, the pools will not be able to handle the block rate. Not with this wallet... Period

Ugh.  It would have been nice if the dev had said to stop mining.  It still would be.  His last post shows how to increase performance of dblib which suggests mining is a go.

I want the coin to succeed also, so let me know if you need any help testing.  I'm in #version on freenode.  (Only two of us there!!)

FYI, I don't have "ERROR: CheckProofOfStake()" in my log but you explained why.  I do have the REORGANIZEs.  Mostly 1,2,and 3 blocks.  
Your 22000 REORGANIZE, wow!  
And I think the windows error was just that the new wallet doesn't like the old wallet's addr.dat.
Post
Topic
Board Announcements (Altcoins)
Re: [ANN] [V] Version - Rare Desirable NO PREMINE Store of Value -->> v0.8.9.9 FIX
by
canoe
on 18/03/2014, 14:52:05 UTC
I don't get it. Even with all this talk of broken chains people continue to mine why? In the off chance that their chain is the one they go for and then they have a huge stash of coins from the easy mining? Why keep mining a broken coin?

Difficulty has been rising ever since 0.8.9.9 was released.  So the problem where difficulty kept jumping to near zero is fixed (by removing KGW).  I don't think there are many chains anymore.  I think the chain forking happened when blocks were really fast and now there is one chain.  It was a normal insta-mine scenario like at coin launch.  Maybe you're right.  Maybe I'm right.  If everyone checked this blockhash, we could find out.  So how about it?

Code:
> getblockhash 116170
000000000037e5b31ddd26d24b9abe3739c89acbad6efa5cf4ee1be3acacf2e6

Make sure you move out your old config directory and use staycrypto's seed node when downloading the blockchain: "addnode=192.241.240.148"

I've updated the blockchain charts for version:
http://cryptometer.org/version_90_day_charts.html
You can see 4 empty days that were erased because of the KGW exploit followed by a couple days of blocks generated way above the target rate.  But it's levelling out now.  And difficulty won't go down anymore because the exploit is plugged.  The pools might even be able to handle the blockrate soon.

There are still some issues with the client:
1. It rejects blocks submitted by cgminer over RPC.
2. Mindfox says there is something wrong with PoS block transmission.
These could be fixed in an update that takes effect on a future block.
Post
Topic
Board Announcements (Altcoins)
Re: [ANN] [V] Version - Rare Desirable NO PREMINE Store of Value -->> v0.8.9.9 FIX
by
canoe
on 18/03/2014, 13:19:56 UTC
I'm having a lot of issues with my wallet updating.  I tried following the steps suggested by the dev and nothing.  Finally I renamed my Version folder (to Version_BU) launched the new waller and it created a new directory for everything and I did connect node etc and I still get stuck at block 70000

At this point im stuck and confued cause I pretty much did a fresh/clean install

The coin has not been completely fixed yet, don't worry about it.  There are multiple forks of the chain, and the devs are still trying to fix the problems.  Follow this thread and download the new wallet when they announce it, but until then, don't bother syncing or mining.
I apologize for not posting for that long, but I haven't talked to staycrypto since last update's release time.

From what I can understand from the endless debug logs I have created during that time, the problem is heavily connected with PoS blocks and how they are announced to and gets accepted by peers. I noticed that my wallet has many rejects to the PoS blocks announced by others. I believe the same happens to my wallet's PoS blocks announced to peers connected with me. This forces the wallet to keep relaying the transactions that created them until it get's banned by the connected pears. That's when wallet starts crawling to death, most probably because of the many reorganization and re-transmitting of those blocks.
That of course happens to wallets with many many blocks that have reached PoS maturity (either from mining or from transactions).

I'm posting this so I can share my suspicions and let anyone know that (at least I) still investigating and pinpointing the problem.

I've been solo mining with the new client and having some success:
1. "set generate true" works in the client.  (CPU mining)
2. Pointing cgminer directly at the daemon does NOT work.  Everything is rejected.
3. Putting stratum server between cgminer and the daemon works.
(https://github.com/Crypto-Expert/stratum-mining.git)

The chain I'm on is at a height of 116170 with difficulty at 700 and rising slowly.  I have 35 connected peers all running v0.8.9.9.  They are confirming my blocks and I am confirming their blocks.  For a while, blocks were so fast that my blocks were always orphaned.  But now things are slow enough that some of mine stick.  I've had some Proof of Stake blocks too (which are "mined" by the client) and they've been confirmed by others.  The seed node specified by StayCrypto is one of my peers and it has not banned me.

Is anyone else on a different chain?  Run this in the debug console to confirm:
Code:
> getblockhash 116170
000000000037e5b31ddd26d24b9abe3739c89acbad6efa5cf4ee1be3acacf2e6

Mindfox, so I'm not noticing this problem.  Can you give me something to search for in the debug log.  What does "rejects to the PoS blocks announced by others" look like in the log?
Post
Topic
Board Service Announcements (Altcoins)
Re: [ANN] Launch-time charts - 58 currencies - cryptometer.org
by
canoe
on 14/03/2014, 19:45:51 UTC
Post
Topic
Board Announcements (Altcoins)
Re: [ANN] [V] Version - Rare Desirable NO PREMINE Store of Value -->> v0.8.7 URGENT
by
canoe
on 13/03/2014, 17:04:20 UTC
I've added Version to my blockchain charts website: http://cryptometer.org

First 96 hours after launch:
http://cryptometer.org/version_96_hour_charts.html

First 90 days after launch: (currently 19 days)
http://cryptometer.org/version_90_day_charts.html

I'm using the 0.8.7 client which new blocks seem to be appearing on.  

You can see the difficulty hack on Day 16 caused the block generation rate to hit 262% of the target rate.  Today, we're at 185% of target so far.  Is that just because difficulty started low or is the hack still occurring?

Also, interesting: the supply chart shows that stake generation has started and about 18000 V have been generated from stake so far.  
Post
Topic
Board Service Announcements (Altcoins)
Re: [ANN] Launch-time charts - 57 currencies - cryptometer.org
by
canoe
on 13/03/2014, 16:42:34 UTC
Post
Topic
Board Announcements (Altcoins)
Re: Vertcoin-Adaptive N-factor Scrypt-No more ASICs-[EXCHANGES/AMAZON/ATM/MERCHANTS]
by
canoe
on 21/02/2014, 19:45:48 UTC

I've added vertcoin to my blockchain charts website:

http://cryptometer.org/vertcoin_96_hour_charts.html (First 96 hours)
http://cryptometer.org/vertcoin_90_day_charts.html (First 90 days)

Donations: Vxjgn1NJEGiwD6mp2gKNon1vmaCpKBfKMC
Post
Topic
Board Service Announcements (Altcoins)
Re: [ANN] Launch-time charts - 56 currencies - cryptometer.org
by
canoe
on 21/02/2014, 19:43:25 UTC
Post
Topic
Board Service Announcements (Altcoins)
Re: [ANN] Launch-time charts - 53 currencies - cryptometer.org
by
canoe
on 14/02/2014, 23:53:33 UTC
Post
Topic
Board Announcements (Altcoins)
Re: [ANN] 42 | + | + super rare + | + | + | + only 42 coins to be mined + | + | + |
by
canoe
on 13/02/2014, 22:37:18 UTC
What a pathetic lot !

Hendo, SHOW US THE PREMINE !

I dont really understand - is there something hinting at a large premine??

You can see a premine on my total supply chart:
http://cryptometer.org/42coin_90_day_charts.html

Premine was .42
Total Supply is 1.36
So the premine is 30% of total supply right now.  It will be 1% when all 42 coins are mined.  Is that large?  Who knows these days....
Post
Topic
Board Announcements (Altcoins)
Re: [ANN] 42 | + | + super rare + | + | + | + only 42 coins to be mined + | + | + |
by
canoe
on 13/02/2014, 21:17:58 UTC
I've added 42Coin to my blockchain charts website:

http://cryptometer.org/42coin_96_hour_charts.html (First 96 hours)
http://cryptometer.org/42coin_90_day_charts.html (First 90 days)
Post
Topic
Board Service Announcements (Altcoins)
Re: [ANN] Launch-time charts - 50 currencies - cryptometer.org
by
canoe
on 11/02/2014, 19:00:38 UTC
Add request

42coin, Potcoin and Craftcoin please

Thanks!

edit: didn't see Craftcoin

I've added 42coin charts to the site.  It's the first 2014 coin.

http://cryptometer.org/42coin_96_hour_charts.html
http://cryptometer.org/42coin_90_day_charts.html

Note: I made the "Minted Currency" chart use micro-42s.  This is because the logarithmic scale does weird things to numbers between 0 and 1 and that's where all the data for this currency falls.  The numbers near 0 end up with large bars and the numbers near 1 end up with small bars.  This is the opposite of what we're used to seeing and makes my brain hurt.  Using mircro-42s scales the data by one million and gets nearly all of it out of 0 to 1 range.  Then the chart looks normal.

Post
Topic
Board Service Announcements (Altcoins)
Re: [ANN] Launch-time charts - 50 currencies - cryptometer.org
by
canoe
on 04/02/2014, 02:00:38 UTC
Buy the way, did you manage to remove the coin creation from the transaction chart, as we talked about before ?

Ok.  I just did it and it was quite easy.  The coinbase transactions are now excluded from the Transactions chart.  I should have done it ages ago.  It really didn't make sense to count the coinbase transactions because the first chart which counts blocks is the same thing as the number of coinbase transactions.  It's much more interesting now.  As I update the different currencies on the site, it will gradually take affect.  Right now, I've only run it on Bitcoin.  To make the transition clear, the old chart is called "Transactions" and the new chart is called "Transactions (non coinbase)".  That way you know if it's applied to a particular currency yet.  Are there any currencies you want me to update first?

Great, thanks, this is funny to see 0 transaction a week at the very beginning of BTC.

Well my next choice would be MMC and XPM.

MMC and XPM are updated.
Post
Topic
Board Service Announcements (Altcoins)
Re: [ANN] Launch-time charts - 50 currencies - cryptometer.org
by
canoe
on 01/02/2014, 03:58:14 UTC
Buy the way, did you manage to remove the coin creation from the transaction chart, as we talked about before ?

Ok.  I just did it and it was quite easy.  The coinbase transactions are now excluded from the Transactions chart.  I should have done it ages ago.  It really didn't make sense to count the coinbase transactions because the first chart which counts blocks is the same thing as the number of coinbase transactions.  It's much more interesting now.  As I update the different currencies on the site, it will gradually take affect.  Right now, I've only run it on Bitcoin.  To make the transition clear, the old chart is called "Transactions" and the new chart is called "Transactions (non coinbase)".  That way you know if it's applied to a particular currency yet.  Are there any currencies you want me to update first?
Post
Topic
Board Announcements (Altcoins)
Re: [ANN] MemoryCoin | CPU Mining | Pool Mining From GUI
by
canoe
on 31/01/2014, 22:40:49 UTC
I've added MemoryCoin to my blockchain charts website: http://cryptometer.org

First 96 hours after launch:
http://cryptometer.org/memorycoin_96_hour_charts.html

First 90 days after launch:
http://cryptometer.org/memorycoin_90_day_charts.html
Post
Topic
Board Service Announcements (Altcoins)
Re: [ANN] Launch-time charts - 50 currencies - cryptometer.org
by
canoe
on 31/01/2014, 22:17:14 UTC
Could you add MemoryCoin (MMC).

They used a bad parameter at the beginning which resulted in quite a big funny fluctuation, they then changed the algorithm, it's smooth now. Could be interesting.


Added MemoryCoin charts to the site:
http://cryptometer.org/memorycoin_96_hour_charts.html
http://cryptometer.org/memorycoin_90_day_charts.html

Yes, that's interesting.  You can see the fluctuation on the first chart.  I guess they hard-forked at Hour 71?  Sounds stressful!  I'm going to read that giant thread and see what parameter they changed.


I found the fix in github.  They replaced the entire algorithm.  It's not a simple parameter change.  I also compared the old algorithm in MemoryCoin with the current algorithms in Unobtanium and Zetacoin.  They are the same.  So that's the problem and how to fix it.

https://github.com/memorycoin/memorycoin/commit/05d26375cb17804bf2fa233678d0bb2dbea6321f

The old algorithm:
Code:
unsigned int static OldGetNextWorkRequired(const CBlockIndex* pindexLast, const CBlockHeader *pblock)
{
    unsigned int nProofOfWorkLimit = bnProofOfWorkLimit.GetCompact();

    // Genesis block
    if (pindexLast == NULL)
        return nProofOfWorkLimit;

    //Change difficulty every block based on the previous nInterval blocks

    //Timewarp bug fix
        // Go back the full period unless it's the first retarget after genesis. Code courtesy of Art Forz
     int nBlocksBack = nInterval-1;
    if((pindexLast->nHeight+1) != nInterval)
        nBlocksBack = nInterval;

     const CBlockIndex* pindexFirst = pindexLast;
    for (int i = 0; pindexFirst && i < nBlocksBack; i++)
         pindexFirst = pindexFirst->pprev;

     //assert(pindexFirst);
        if(pindexFirst==NULL){
        return nProofOfWorkLimit;
        }

    // Limit adjustment step
    int64 nActualTimespan = pindexLast->GetBlockTime() - pindexFirst->GetBlockTime();
    printf("  nActualTimespan = %"PRI64d"  before bounds\n", nActualTimespan);

    if (nActualTimespan < nTargetTimespan*0.8)
        nActualTimespan = nTargetTimespan*0.8;

    if (nActualTimespan > nTargetTimespan*1.2)
        nActualTimespan = nTargetTimespan*1.2;

    // Retarget
    CBigNum bnNew;
    bnNew.SetCompact(pindexLast->nBits);
    bnNew *= nActualTimespan;
    bnNew /= nTargetTimespan;

    if (bnNew > bnProofOfWorkLimit)
        bnNew = bnProofOfWorkLimit;

    /// debug print
    //printf("\n");
    printf("nTargetTimespan = %"PRI64d"    nActualTimespan = %"PRI64d"\n", nTargetTimespan, nActualTimespan);
    printf("Before: %08x  %s\n", pindexLast->nBits, CBigNum().SetCompact(pindexLast->nBits).getuint256().ToString().c_str());
    printf("GetNextWorkRequired RETARGET After:  %08x  %s\n", bnNew.GetCompact(), bnNew.getuint256().ToString().c_str());

    return bnNew.GetCompact();
}

The new algorithm:
Code:
unsigned int static KimotoGravityWell(const CBlockIndex* pindexLast, const CBlockHeader *pblock, uint64 TargetBlocksSpacingSeconds, uint64 PastBlocksMin, uint64 PastBlocksMax) {
    /* current difficulty formula, Anoncoin - kimoto gravity well */
    const CBlockIndex *BlockLastSolved = pindexLast;
    const CBlockIndex *BlockReading = pindexLast;
    const CBlockHeader *BlockCreating = pblock;
BlockCreating = BlockCreating;
    uint64 PastBlocksMass = 0;
    int64 PastRateActualSeconds = 0;
    int64 PastRateTargetSeconds = 0;
    double PastRateAdjustmentRatio = double(1);
    CBigNum PastDifficultyAverage;
    CBigNum PastDifficultyAveragePrev;
    double EventHorizonDeviation;
    double EventHorizonDeviationFast;
    double EventHorizonDeviationSlow;

    if (BlockLastSolved == NULL || BlockLastSolved->nHeight == 0 || (uint64)BlockLastSolved->nHeight < PastBlocksMin) { return bnProofOfWorkLimit.GetCompact(); }

    for (unsigned int i = 1; BlockReading && BlockReading->nHeight > 0; i++) {
        if (PastBlocksMax > 0 && i > PastBlocksMax) { break; }
        PastBlocksMass++;

        if (i == 1) { PastDifficultyAverage.SetCompact(BlockReading->nBits); }
        else { PastDifficultyAverage = ((CBigNum().SetCompact(BlockReading->nBits) - PastDifficultyAveragePrev) / i) + PastDifficultyAveragePrev; }
        PastDifficultyAveragePrev = PastDifficultyAverage;

        PastRateActualSeconds = BlockLastSolved->GetBlockTime() - BlockReading->GetBlockTime();
        PastRateTargetSeconds = TargetBlocksSpacingSeconds * PastBlocksMass;
        PastRateAdjustmentRatio = double(1);
        if (PastRateActualSeconds < 0) { PastRateActualSeconds = 0; }
        if (PastRateActualSeconds != 0 && PastRateTargetSeconds != 0) {
        PastRateAdjustmentRatio = double(PastRateTargetSeconds) / double(PastRateActualSeconds);
        }
        EventHorizonDeviation = 1 + (0.7084 * pow((double(PastBlocksMass)/double(144)), -1.228));
        EventHorizonDeviationFast = EventHorizonDeviation;
        EventHorizonDeviationSlow = 1 / EventHorizonDeviation;

        if (PastBlocksMass >= PastBlocksMin) {
            if ((PastRateAdjustmentRatio <= EventHorizonDeviationSlow) || (PastRateAdjustmentRatio >= EventHorizonDeviationFast)) { assert(BlockReading); break; }
        }
        if (BlockReading->pprev == NULL) { assert(BlockReading); break; }
        BlockReading = BlockReading->pprev;
    }

    CBigNum bnNew(PastDifficultyAverage);
    if (PastRateActualSeconds != 0 && PastRateTargetSeconds != 0) {
        bnNew *= PastRateActualSeconds;
        bnNew /= PastRateTargetSeconds;
    }
    if (bnNew > bnProofOfWorkLimit) { bnNew = bnProofOfWorkLimit; }

    /// debug print
    printf("Difficulty Retarget - Kimoto Gravity Well\n");
    printf("PastRateAdjustmentRatio = %g\n", PastRateAdjustmentRatio);
    printf("Before: %08x %s\n", BlockLastSolved->nBits, CBigNum().SetCompact(BlockLastSolved->nBits).getuint256().ToString().c_str());
    printf("After: %08x %s\n", bnNew.GetCompact(), bnNew.getuint256().ToString().c_str());


    return bnNew.GetCompact();
}

unsigned int static NeoGetNextWorkRequired(const CBlockIndex* pindexLast, const CBlockHeader *pblock)
{
    static const int64 BlocksTargetSpacing = 6 * 60; // 6 minutes
    unsigned int TimeDaySeconds = 60 * 60 * 24;
    int64 PastSecondsMin = TimeDaySeconds*0.25;
    int64 PastSecondsMax = TimeDaySeconds*1;
    uint64 PastBlocksMin = PastSecondsMin / BlocksTargetSpacing;
    uint64 PastBlocksMax = PastSecondsMax / BlocksTargetSpacing;

    return KimotoGravityWell(pindexLast, pblock, BlocksTargetSpacing, PastBlocksMin, PastBlocksMax);
}

Post
Topic
Board Service Announcements (Altcoins)
Re: [ANN] Launch-time charts - 50 currencies - cryptometer.org
by
canoe
on 31/01/2014, 21:25:48 UTC
Could you add MemoryCoin (MMC).

They used a bad parameter at the beginning which resulted in quite a big funny fluctuation, they then changed the algorithm, it's smooth now. Could be interesting.


Added MemoryCoin charts to the site:
http://cryptometer.org/memorycoin_96_hour_charts.html
http://cryptometer.org/memorycoin_90_day_charts.html

Yes, that's interesting.  You can see the fluctuation on the first chart.  I guess they hard-forked at Hour 71?  Sounds stressful!  I'm going to read that giant thread and see what parameter they changed.
Post
Topic
Board Announcements (Altcoins)
Re: [ANN] Unobtanium: Updated 0.9.2 Build Available NOW + Faucet Fixed!
by
canoe
on 30/01/2014, 20:21:02 UTC
Could someone suggest a good mining pool for unobtanium guys? Many thanks in advance.

I'm using http://un.coinmine.pl and it's working fine.

And there's a list of them here: https://bitcointalk.org/index.php?topic=313126.msg3358654

Canoe,

Do you get a lot of rejects there? HW errors??

Thanks!

Here's some of my cgminer stats:
GetWorks: 1131
Accepted: 2063
Rejected: 414
So that's 20% reject.  Is that high?  I'm making the projected amount of UNO per day so perhaps if everyone gets 20% rejects it works out to the same thing?

As for HW errors, I don't think that's affected by which pool you use.
Post
Topic
Board Announcements (Altcoins)
Re: [ANN] Unobtanium: Updated 0.9.2 Build Available NOW + Faucet Fixed!
by
canoe
on 30/01/2014, 17:01:04 UTC
Could someone suggest a good mining pool for unobtanium guys? Many thanks in advance.

I'm using http://un.coinmine.pl and it's working fine.

And there's a list of them here: https://bitcointalk.org/index.php?topic=313126.msg3358654