[ANN] Noirbits Update required Improved algos !!!!

[barwizi]

Is it possible to get Noirbits off of coinchoose to prevent these difficulty / hashrate swings? I don't think they're very good for the success of the currency. It seems like bitgem was taken off of coinchoose, not sure how that happened.

that is an option, but it's being listed on coinchoose has caused the price to rise, i think a update to the algo to put it in the more stable bracket is a better idea. your thoughts?

[TheRickTM]

Is it possible to get Noirbits off of coinchoose to prevent these difficulty / hashrate swings? I don't think they're very good for the success of the currency. It seems like bitgem was taken off of coinchoose, not sure how that happened.

that is an option, but it's being listed on coinchoose has caused the price to rise, i think a update to the algo to put it in the more stable bracket is a better idea. your thoughts?

I think it would be better to adjust the algo for the coin as people regardless of the site will come and go based on profitability. What is the way we want to approach the algo for recalculating?

[JDDev]

I think making adjustments is the right way to go, but in 12 hours or so there probably will be another massive swing that might be averted by getting it off coinchoose temporarily. I think the interest generated by the listing on coinchoose won't go away if it is delisted for a while.

[barwizi]

Is it possible to get Noirbits off of coinchoose to prevent these difficulty / hashrate swings? I don't think they're very good for the success of the currency. It seems like bitgem was taken off of coinchoose, not sure how that happened.

that is an option, but it's being listed on coinchoose has caused the price to rise, i think a update to the algo to put it in the more stable bracket is a better idea. your thoughts?

I think it would be better to adjust the algo for the coin as people regardless of the site will come and go based on profitability. What is the way we want to approach the algo for recalculating?

retarget times and percentages
current

Code:

static const int64 nTargetTimespan = 1 * 2 * 60 * 60; // Noirbits: 2 hour
static const int64 nTargetSpacing = 120; // Noirbits: 2 minute blocks
static const int64 nInterval = nTargetTimespan / nTargetSpacing;

and

Code:

static const int64 nReTargetHistoryFact = 4; // look at 4 times the retarget
                                             // interval into the block history

also

Code:

// Limit adjustment step
    int64 nActualTimespan = 0;
    if (pindexLast->nHeight > COINFIX1_BLOCK)
        // obtain average actual timespan
        nActualTimespan = (pindexLast->GetBlockTime() - pindexFirst->GetBlockTime())/nReTargetHistoryFact;
    else
        nActualTimespan = pindexLast->GetBlockTime() - pindexFirst->GetBlockTime();
    printf("  nActualTimespan = %"PRI64d"  before bounds\n", nActualTimespan);
    if (nActualTimespan < nTargetTimespan/4)
        nActualTimespan = nTargetTimespan/4;
    if (nActualTimespan > nTargetTimespan*4)
        nActualTimespan = nTargetTimespan*4;

[stbgefltc]

Well I like oatmo's idea... aim for retargets every hour, with a max time until retarget... quite simple to implement :

Replace l. 878-879 in main.cpp

Code:

// Only change once per interval
if ((pindexLast->nHeight+1) % nInterval != 0)

With the following :

Code:

// Only change once per interval unless last retarget occurred more than nMaxTimeInterval seconds ago
unsigned int nMaxTimeInterval = 14400;
if ((pindexLast->nHeight+1) % nInterval != 0 && pindexLast->nTime + nMaxTimeInterval > time())

We would also need to adjust l. 836 of main.cpp, currently diff. retargets every two hours :

Code:

static const int64 nTargetTimespan = 1 * 2 * 60 * 60; // Noirbits: 2 hour
static const int64 nTargetSpacing = 120; // Noirbits: 2 minute blocks
static const int64 nInterval = nTargetTimespan / nTargetSpacing;

Would become

Code:

static const int64 nTargetTimespan = 3600; // Noirbits: 1 hour
static const int64 nTargetSpacing = 120; // Noirbits: 2 minute blocks
static const int64 nInterval = nTargetTimespan / nTargetSpacing;

Proposed changes here would give us retarget every hour, and a retarget on next block if no retarget happened for more than 4 hours. What do you think ?

[TheRickTM]

Well I like oatmo's idea... aim for retargets every hour, with a max time until retarget... quite simple to implement :

Replace l. 878-879 in main.cpp

Code:

// Only change once per interval
if ((pindexLast->nHeight+1) % nInterval != 0)

With the following :

Code:

// Only change once per interval unless last retarget occurred more than nMaxTimeInterval seconds ago
unsigned int nMaxTimeInterval = 14400;
if ((pindexLast->nHeight+1) % nInterval != 0 && pindexLast->nTime + nMaxTimeInterval > time())

We would also need to adjust l. 836 of main.cpp, currently diff. retargets every two hours :

Code:

static const int64 nTargetTimespan = 1 * 2 * 60 * 60; // Noirbits: 2 hour
static const int64 nTargetSpacing = 120; // Noirbits: 2 minute blocks
static const int64 nInterval = nTargetTimespan / nTargetSpacing;

Would become

Code:

static const int64 nTargetTimespan = 3600; // Noirbits: 1 hour
static const int64 nTargetSpacing = 120; // Noirbits: 2 minute blocks
static const int64 nInterval = nTargetTimespan / nTargetSpacing;

Proposed changes here would give us retarget every hour, and a retarget on next block if no retarget happened for more than 4 hours. What do you think ?

I have been thinking about this as well, but how will this change work across timezones as well as machines that have modified date times that could attach the retarget if the block is found?

[stbgefltc]

Hum... good point, however, blocks do carry a timestamp. Just need to find out how it's generated, and use the same method...

Edit Looks like transaction times are generated using a call to GetAdjustedTime(). I'll check up on that later, but that could be the good call instead of time()

[sal002]

Is it possible to get Noirbits off of coinchoose to prevent these difficulty / hashrate swings? I don't think they're very good for the success of the currency. It seems like bitgem was taken off of coinchoose, not sure how that happened.

that is an option, but it's being listed on coinchoose has caused the price to rise, i think a update to the algo to put it in the more stable bracket is a better idea. your thoughts?

BitGem was removed due to inability to calc the true reward for the next block (or the fact that no one could give me a good formula).  As an aside, variable block rewards give CoinChoose the most fits.

[barwizi]

LOOK at that PRICE RISE!!!!!!!!!!!!!!!!!!!!!!!!!!!!   

[bahamapascal]

LOOK at that PRICE RISE!!!!!!!!!!!!!!!!!!!!!!!!!!!!   

Yes that is amazing, happy I had bought at 0.000084
Can I ask what the NRB bank is doing? When do you think will it be released? Sometime soon or still weeks or month till release?
By the way, nice coin you made, like it

[whitepaint0909]

Is it normal for the confirmations to be taking hours currently?  I sent some Noir to Crypsy 2 hours and 30 min ago and so far it has 1 confirmation...?

[barwizi]

block rate is slow right now, we are working on a patch.

[barwizi]

I think a retarget tme of 20 minutes is most ideal, with only a 80% change allowable

[stbgefltc]

Speaking of that, I'm about to push the changes to Testing...

[barwizi]

how many blocks to retarget?

[stbgefltc]

Well I have not changed blocks till retarget, only the 4 hour max retarget time... it's there on Testing, you can review the changes (can't do that either). I wanted to create a new branch, but I can't, don't have permissions.

[TheRickTM]

Well I have not changed blocks till retarget, only the 4 hour max retarget time... it's there on Testing, you can review the changes (can't do that either). I wanted to create a new branch, but I can't, don't have permissions.

Just fork it in github and make it public. That is typically how branches work for github until you are added to the dev team.

[barwizi]

fork then i'll merge

[barwizi]

whats your git name, i can add you to collaborators

[stbgefltc]

Well I have not changed blocks till retarget, only the 4 hour max retarget time... it's there on Testing, you can review the changes (can't do that either). I wanted to create a new branch, but I can't, don't have permissions.

Just fork it in github and make it public. That is typically how branches work for github until you are added to the dev team.

Yeah I'm an SVN guy... Fork done you should see it from your repo...

Edit. ftcminer67