barwizi (OP)
Legendary
Offline
Activity: 882
Merit: 1000
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 02, 2013, 12:59:36 PM |
|
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
Newbie
Offline
Activity: 42
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 02, 2013, 01:04:47 PM |
|
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
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 02, 2013, 01:11:02 PM |
|
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 (OP)
Legendary
Offline
Activity: 882
Merit: 1000
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 02, 2013, 01:16:14 PM |
|
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 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 static const int64 nReTargetHistoryFact = 4; // look at 4 times the retarget // interval into the block history also // 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
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 02, 2013, 01:30:00 PM |
|
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 // Only change once per interval if ((pindexLast->nHeight+1) % nInterval != 0) With the following : // 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 : 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 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
Newbie
Offline
Activity: 42
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 02, 2013, 01:34:40 PM |
|
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 // Only change once per interval if ((pindexLast->nHeight+1) % nInterval != 0) With the following : // 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 : 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 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
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 02, 2013, 01:40:07 PM Last edit: July 02, 2013, 01:51:05 PM by 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
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 02, 2013, 03:00:31 PM |
|
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 (OP)
Legendary
Offline
Activity: 882
Merit: 1000
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 02, 2013, 04:28:55 PM |
|
LOOK at that PRICE RISE!!!!!!!!!!!!!!!!!!!!!!!!!!!!
|
|
|
|
bahamapascal
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 02, 2013, 05:00:54 PM |
|
LOOK at that PRICE RISE!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Yes that is amazing, happy I had bought at 0.000084 ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) 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 ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif)
|
|
|
|
whitepaint0909
Newbie
Offline
Activity: 46
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 02, 2013, 07:20:28 PM |
|
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 (OP)
Legendary
Offline
Activity: 882
Merit: 1000
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 02, 2013, 07:31:21 PM |
|
block rate is slow right now, we are working on a patch.
|
|
|
|
barwizi (OP)
Legendary
Offline
Activity: 882
Merit: 1000
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 02, 2013, 07:32:49 PM |
|
I think a retarget tme of 20 minutes is most ideal, with only a 80% change allowable
|
|
|
|
stbgefltc
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 02, 2013, 07:50:07 PM |
|
Speaking of that, I'm about to push the changes to Testing... ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif)
|
|
|
|
barwizi (OP)
Legendary
Offline
Activity: 882
Merit: 1000
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 02, 2013, 08:02:20 PM |
|
how many blocks to retarget?
|
|
|
|
stbgefltc
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 02, 2013, 08:05:42 PM |
|
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
Newbie
Offline
Activity: 42
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 02, 2013, 08:09:03 PM |
|
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 (OP)
Legendary
Offline
Activity: 882
Merit: 1000
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 02, 2013, 08:09:36 PM |
|
fork then i'll merge
|
|
|
|
barwizi (OP)
Legendary
Offline
Activity: 882
Merit: 1000
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 02, 2013, 08:13:30 PM |
|
whats your git name, i can add you to collaborators
|
|
|
|
stbgefltc
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 02, 2013, 08:19:00 PM |
|
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
|
|
|
|
|