diff has dropped slightly to 35672.23 but why is it still so high?
Ok I think that person(s) was mining again because block count is higher than normal. Is there a way we can cut out such a person from the network ?
Topic: [ANN] [GLB]Globe – One Currency for One Globe - Polished and Ready for Action - page 48. (Read 113608 times)
December 20, 2013, 03:04:32 AM
Ok I think that person(s) was mining again because block count is higher than normal. Is there a way we can cut out such a person from the network ?
December 20, 2013, 02:41:58 AM
diff has dropped slightly to 35672.23 but why is it still so high?
December 19, 2013, 05:42:00 PM
Wanna to know how long it will take to solve a block for solo mining?
python -c "diff=38000; gb=1; print diff * 2**32 / gb / 10**9 / 60 / 60.0;"
(credit: https://en.bitcoin.it/wiki/Difficulty#How_soon_might_I_expect_to_generate_a_block.3F)
Replace diff by your difficult, and replace gb by your hash power in GHash/s.
In our case, the
1 GHash/s power can solve a block in 45 hours.
10 GHash/s power can solve a block in 4.5 hours.
...
python -c "diff=38000; gb=1; print diff * 2**32 / gb / 10**9 / 60 / 60.0;"
(credit: https://en.bitcoin.it/wiki/Difficulty#How_soon_might_I_expect_to_generate_a_block.3F)
Replace diff by your difficult, and replace gb by your hash power in GHash/s.
In our case, the
1 GHash/s power can solve a block in 45 hours.
10 GHash/s power can solve a block in 4.5 hours.
...
Nice.
We got one more block. Hopefully, we are one step closer.
December 19, 2013, 05:29:44 PM
Wanna to know how long it will take to solve a block for solo mining?
python -c "diff=38000; gb=1; print diff * 2**32 / gb / 10**9 / 60 / 60.0;"
(credit: https://en.bitcoin.it/wiki/Difficulty#How_soon_might_I_expect_to_generate_a_block.3F)
Replace diff by your difficult, and replace gb by your hash power in GHash/s.
In our case, the
1 GHash/s power can solve a block in 45 hours.
10 GHash/s power can solve a block in 4.5 hours.
...
python -c "diff=38000; gb=1; print diff * 2**32 / gb / 10**9 / 60 / 60.0;"
(credit: https://en.bitcoin.it/wiki/Difficulty#How_soon_might_I_expect_to_generate_a_block.3F)
Replace diff by your difficult, and replace gb by your hash power in GHash/s.
In our case, the
1 GHash/s power can solve a block in 45 hours.
10 GHash/s power can solve a block in 4.5 hours.
...
December 19, 2013, 05:22:17 PM
For the pool, you might contact Marty19 to see whether he is interested with our coin.
His info: https://cryptocointalk.com/user/630-marty19/
The pool: http://ispace.co.uk/
By the way, his computing power is at least 2,000 Ghash/s.
His info: https://cryptocointalk.com/user/630-marty19/
The pool: http://ispace.co.uk/
By the way, his computing power is at least 2,000 Ghash/s.
Wow Ok will get in touch see if he is interested. A pool will be a good way of making sure things like this don't happen in the future.
December 19, 2013, 05:21:08 PM
For the pool, you might contact Marty19 to see whether he is interested with our coin.
His info: https://cryptocointalk.com/user/630-marty19/
The pool: http://ispace.co.uk/
It's not very stable, but it should be very easy for them to add GLB to their SHA-256 pool.
By the way, his computing power is at least 2,000 Ghash/s.
This issue is common nowadays due to large deployment of ASICs. Another way to overcome this is to make a hard-fork if we can not make the coin recover in several days.
His info: https://cryptocointalk.com/user/630-marty19/
The pool: http://ispace.co.uk/
It's not very stable, but it should be very easy for them to add GLB to their SHA-256 pool.
By the way, his computing power is at least 2,000 Ghash/s.
This issue is common nowadays due to large deployment of ASICs. Another way to overcome this is to make a hard-fork if we can not make the coin recover in several days.
December 19, 2013, 05:09:45 PM
okay hopefully we will get some blocks and the difficulty will be reduced
December 19, 2013, 05:06:28 PM
Every 9 blocks, the difficulty will decrease by approximately 5%.
It means that after 387 (43*9) blocks, the difficulty will be 10%.
main.cpp:1203 static const int64 nFilteredTargetTimespan = nFilteredInterval * nTargetSpacing; // 1.5 hrs
nFilteredInterval is 9.
nTargetSpacing is 60.
It means that after 387 (43*9) blocks, the difficulty will be 10%.
main.cpp:1203 static const int64 nFilteredTargetTimespan = nFilteredInterval * nTargetSpacing; // 1.5 hrs
nFilteredInterval is 9.
nTargetSpacing is 60.
December 19, 2013, 05:03:34 PM
Also what is the nFilteredTargetTimespan ?
December 19, 2013, 05:01:44 PM
main.h:66:static const int DIFF_FILTER_THRESHOLD = 28336;
We are lucky because Freicoin changed their original difficulty adjustment algorithm.
Check this thread:
https://bitcointalksearch.org/topic/frc-difficulty-adjustment-fork-successful-202250
As GLB is a fork of Freicoin, we are also benefit their change.
BTW, they changed the algorithm because same issue as us in the early time of Freicoin.
We are lucky because Freicoin changed their original difficulty adjustment algorithm.
Check this thread:
https://bitcointalksearch.org/topic/frc-difficulty-adjustment-fork-successful-202250
As GLB is a fork of Freicoin, we are also benefit their change.
BTW, they changed the algorithm because same issue as us in the early time of Freicoin.
Ok fingers crossed. I think we might be in the clear.
December 19, 2013, 04:57:58 PM
main.h:66:static const int DIFF_FILTER_THRESHOLD = 28336;
We are lucky because Freicoin changed their original difficulty adjustment algorithm.
Check this thread:
https://bitcointalksearch.org/topic/frc-difficulty-adjustment-fork-successful-202250
As GLB is a fork of Freicoin, we are also benefit their change.
BTW, they changed the algorithm because same issue as us in the early time of Freicoin.
We are lucky because Freicoin changed their original difficulty adjustment algorithm.
Check this thread:
https://bitcointalksearch.org/topic/frc-difficulty-adjustment-fork-successful-202250
As GLB is a fork of Freicoin, we are also benefit their change.
BTW, they changed the algorithm because same issue as us in the early time of Freicoin.
December 19, 2013, 04:50:11 PM
For your information, I read the source code, and find the re-target interval.
If the block height is less than 28335, the re-target interval is 2016.
If the block height is greater than 28335, the re-target interval is 9.
As we are on the block#28381 now, so I think current re-target interval is 9.
If the block height is less than 28335, the re-target interval is 2016.
If the block height is greater than 28335, the re-target interval is 9.
As we are on the block#28381 now, so I think current re-target interval is 9.
And this is a very good news.............
Sarcasm ?
What do you mean? By the way, can you confirm that the re-target interval is 9 after 28335?
main.cpp: 1278
bool fUseFilter =
(fTestNet && pindexLast->nHeight>=(DIFF_FILTER_THRESHOLD_TESTNET-1)) ||
(!fTestNet && pindexLast->nHeight>=(DIFF_FILTER_THRESHOLD-1));
int64 nInterval = nFilteredInterval;
int64 nTargetTimespan = nFilteredTargetTimespan;
if ( !fUseFilter ) {
nInterval = nOriginalInterval;
nTargetTimespan = nOriginalTargetTimespan;
}
December 19, 2013, 04:48:18 PM
For your information, I read the source code, and find the re-target interval.
If the block height is less than 28335, the re-target interval is 2016.
If the block height is greater than 28335, the re-target interval is 9.
As we are on the block#28381 now, so I think current re-target interval is 9.
If the block height is less than 28335, the re-target interval is 2016.
If the block height is greater than 28335, the re-target interval is 9.
As we are on the block#28381 now, so I think current re-target interval is 9.
And this is a very good news.............
Sarcasm ?
No man, if bcfanminer is right, your coin is safe.
If block was < 28335 (ex 21500) globe was death
December 19, 2013, 04:46:53 PM
For your information, I read the source code, and find the re-target interval.
If the block height is less than 28335, the re-target interval is 2016.
If the block height is greater than 28335, the re-target interval is 9.
As we are on the block#28381 now, so I think current re-target interval is 9.
If the block height is less than 28335, the re-target interval is 2016.
If the block height is greater than 28335, the re-target interval is 9.
As we are on the block#28381 now, so I think current re-target interval is 9.
And this is a very good news.............
Sarcasm ?
What do you mean? By the way, can you confirm that the re-target interval is 9 after 28335?
main.cpp: 1278
bool fUseFilter =
(fTestNet && pindexLast->nHeight>=(DIFF_FILTER_THRESHOLD_TESTNET-1)) ||
(!fTestNet && pindexLast->nHeight>=(DIFF_FILTER_THRESHOLD-1));
int64 nInterval = nFilteredInterval;
int64 nTargetTimespan = nFilteredTargetTimespan;
if ( !fUseFilter ) {
nInterval = nOriginalInterval;
nTargetTimespan = nOriginalTargetTimespan;
}
December 19, 2013, 04:43:17 PM
For your information, I read the source code, and find the re-target interval.
If the block height is less than 28335, the re-target interval is 2016.
If the block height is greater than 28335, the re-target interval is 9.
As we are on the block#28381 now, so I think current re-target interval is 9.
If the block height is less than 28335, the re-target interval is 2016.
If the block height is greater than 28335, the re-target interval is 9.
As we are on the block#28381 now, so I think current re-target interval is 9.
And this is a very good news.............
Sarcasm ?
December 19, 2013, 04:40:42 PM
For your information, I read the source code, and find the re-target interval.
If the block height is less than 28335, the re-target interval is 2016.
If the block height is greater than 28335, the re-target interval is 9.
As we are on the block#28381 now, so I think current re-target interval is 9.
If the block height is less than 28335, the re-target interval is 2016.
If the block height is greater than 28335, the re-target interval is 9.
As we are on the block#28381 now, so I think current re-target interval is 9.
And this is a very good news.............
December 19, 2013, 04:39:20 PM
For your information, I read the source code, and find the re-target interval.
If the block height is less than 28335, the re-target interval is 2016.
If the block height is greater than 28335, the re-target interval is 9.
As we are on the block#28381 now, so I think current re-target interval is 9.
If the block height is less than 28335, the re-target interval is 2016.
If the block height is greater than 28335, the re-target interval is 9.
As we are on the block#28381 now, so I think current re-target interval is 9.
December 19, 2013, 04:34:48 PM
We need a pool. Then we can add up all our computing powers instead of solo mining. In that case, we can overcome such problem easier. 
Ok if this does not resolve itself by tomorrow, I will try and get a pool operator accepting Globe tomorrow.
December 19, 2013, 04:33:03 PM
Oh man don't you know the retarget system of your coin??? 
A coin can be retarget every block, every 2016 Blocks (like Bitcoin), every what you want!!!
If Globe is retarget every 2000 Blocks............have you understand?
If no-one continue mining (and no one will do if time to block is over 5 hours) result will be (if retarget is 2000, i made an example!)
2000*5 hours = 416 Days before the next retarget = COIN KILLED
A coin can be retarget every block, every 2016 Blocks (like Bitcoin), every what you want!!!
If Globe is retarget every 2000 Blocks............have you understand?
If no-one continue mining (and no one will do if time to block is over 5 hours) result will be (if retarget is 2000, i made an example!)
2000*5 hours = 416 Days before the next retarget = COIN KILLED
Hmm but why has it always happened daily then? and in the event globe is killed can we re-start?
You can create a Fork, but anyone can Re-Kill your coin
Actually we need a pool and some good boy with some Power Asic. but it's no good that you don't know your retarget system......
December 19, 2013, 04:30:29 PM
We need a pool. Then we can add up all our computing powers instead of solo mining. In that case, we can overcome such problem easier.
Jump to: