As I promised, I'm announcing the release date and time one day before.
Onecoin will be released tomorrow, 17.05.13 at 12:00 GMT
Topic: [ANN][ONC] Onecoin - CPU only - Pools opened! - page 24. (Read 74872 times)
As of scrypt-jane,i advise Nfactor starts with more than 4,or FPGA will be available like yac did.
yeah i was going to ask, do you have a launch date,
please no GMT 6:30PM lol
please no GMT 6:30PM lol
why no gpu tough? I mean I get the no fpga and no asic deal since they are not everywhere yet but everyone has a gpu right? If you can't afford a nice gpu than you probably cant afford a nice cpu too
sounds good too, but could we not have gpu not cpu? or a mix? some days it favours cpu others gpu? is it possible?
I doubt this is possible. 
I've just made some improvements:
Difficulty retargets each block (PPCoin's implementation).
Blocks 0-999 will get no reward. Blocks 1000-1499 will receive 10 nano-OTC, 1500-1999 - 20 nano-OTC and so on, the subsidy increasing by 10 nano-OTC every 500 blocks, until block 25500, which will receive the full reward of 500 nano-OTC. The total money amount remains the same - a bit less than one coin.
Difficulty retargets each block (PPCoin's implementation).
Blocks 0-999 will get no reward. Blocks 1000-1499 will receive 10 nano-OTC, 1500-1999 - 20 nano-OTC and so on, the subsidy increasing by 10 nano-OTC every 500 blocks, until block 25500, which will receive the full reward of 500 nano-OTC. The total money amount remains the same - a bit less than one coin.
sounds good too, but could we not have gpu not cpu? or a mix? some days it favours cpu others gpu? is it possible?
I've just made some improvements:
Difficulty retargets each block (PPCoin's implementation).
Blocks 0-999 will get no reward. Blocks 1000-1499 will receive 10 nano-OTC, 1500-1999 - 20 nano-OTC and so on, the subsidy increasing by 10 nano-OTC every 500 blocks, until block 25500, which will receive the full reward of 500 nano-OTC. The total money amount remains the same - a bit less than one coin.
Difficulty retargets each block (PPCoin's implementation).
Blocks 0-999 will get no reward. Blocks 1000-1499 will receive 10 nano-OTC, 1500-1999 - 20 nano-OTC and so on, the subsidy increasing by 10 nano-OTC every 500 blocks, until block 25500, which will receive the full reward of 500 nano-OTC. The total money amount remains the same - a bit less than one coin.
i have error compiling your sources:
My bad, didn't clean up makefile. Should be fixed now. Code:
/bin/sh ../share/genbuild.sh obj/build.h
make: *** No rule to make target `obj/scrypt.o', needed by `onecoind'. Stop.
make: *** Waiting for unfinished jobs....
lol are you mining his semi finished git?
stupid
Try to remove "onecoin" dir, then "git clone" it again.
Onecoin is scrypt-jane based, scrypt has been removed: https://github.com/cre8r/onecoin/commit/2428b0650182adaeed8bb23ec494aff19df1eac8
Onecoin is scrypt-jane based, scrypt has been removed: https://github.com/cre8r/onecoin/commit/2428b0650182adaeed8bb23ec494aff19df1eac8
CPU-only again? So what is the difference between YAC and Onecoin, apart of block reward?
https://github.com/cre8r/onecoin/commits/master
Sounds to me this is is like Bitbar for CPU mining.
Try to remove "onecoin" dir, then "git clone" it again.
Onecoin is scrypt-jane based, scrypt has been removed: https://github.com/cre8r/onecoin/commit/2428b0650182adaeed8bb23ec494aff19df1eac8
Onecoin is scrypt-jane based, scrypt has been removed: https://github.com/cre8r/onecoin/commit/2428b0650182adaeed8bb23ec494aff19df1eac8
CPU-only again? So what is the difference between YAC and Onecoin, apart of block reward?
Try to remove "onecoin" dir, then "git clone" it again.
Onecoin is scrypt-jane based, scrypt has been removed: https://github.com/cre8r/onecoin/commit/2428b0650182adaeed8bb23ec494aff19df1eac8
Onecoin is scrypt-jane based, scrypt has been removed: https://github.com/cre8r/onecoin/commit/2428b0650182adaeed8bb23ec494aff19df1eac8
yep, i am compiling by:
and still getting error "no rules for obj/scrypt.o"
Code:
git clone git://github.com/cre8r/onecoin.git
cd onecoin/src
make -f makefile.unix
and still getting error "no rules for obj/scrypt.o"
Quote
-D_FORTIFY_SOURCE=2 -MMD -MF obj/rpcnet.d -o obj/rpcnet.o rpcnet.cpp
g++ -c -O2 -pthread -Wall -Wextra -Wformat -Wformat-security -Wno-unused-parameter -g -DUSE_IPV6 -DBOOST_SPIRIT_THREADSAFE -I/home/otc/onecoin/src -I/home/otc/onecoin/src/obj -DUSE_UPNP=0 -DSCRYPT_KECCAK512 -DSCRYPT_CHACHA -DSCRYPT_CHOOSE_COMPILETIME -DHAVE_BUILD_INFO -fno-stack-protector -fstack-protector-all -Wstack-protector -D_FORTIFY_SOURCE=2 -MMD -MF obj/rpcrawtransaction.d -o obj/rpcrawtransaction.o rpcrawtransaction.cpp
g++ -c -O2 -pthread -Wall -Wextra -Wformat -Wformat-security -Wno-unused-parameter -g -DUSE_IPV6 -DBOOST_SPIRIT_THREADSAFE -I/home/otc/onecoin/src -I/home/otc/onecoin/src/obj -DUSE_UPNP=0 -DSCRYPT_KECCAK512 -DSCRYPT_CHACHA -DSCRYPT_CHOOSE_COMPILETIME -DHAVE_BUILD_INFO -fno-stack-protector -fstack-protector-all -Wstack-protector -D_FORTIFY_SOURCE=2 -MMD -MF obj/script.d -o obj/script.o script.cpp
make: *** Brak reguł do zrobienia obiektu `obj/scrypt.o', wymaganego przez `onecoind'. Stop.
g++ -c -O2 -pthread -Wall -Wextra -Wformat -Wformat-security -Wno-unused-parameter -g -DUSE_IPV6 -DBOOST_SPIRIT_THREADSAFE -I/home/otc/onecoin/src -I/home/otc/onecoin/src/obj -DUSE_UPNP=0 -DSCRYPT_KECCAK512 -DSCRYPT_CHACHA -DSCRYPT_CHOOSE_COMPILETIME -DHAVE_BUILD_INFO -fno-stack-protector -fstack-protector-all -Wstack-protector -D_FORTIFY_SOURCE=2 -MMD -MF obj/rpcrawtransaction.d -o obj/rpcrawtransaction.o rpcrawtransaction.cpp
g++ -c -O2 -pthread -Wall -Wextra -Wformat -Wformat-security -Wno-unused-parameter -g -DUSE_IPV6 -DBOOST_SPIRIT_THREADSAFE -I/home/otc/onecoin/src -I/home/otc/onecoin/src/obj -DUSE_UPNP=0 -DSCRYPT_KECCAK512 -DSCRYPT_CHACHA -DSCRYPT_CHOOSE_COMPILETIME -DHAVE_BUILD_INFO -fno-stack-protector -fstack-protector-all -Wstack-protector -D_FORTIFY_SOURCE=2 -MMD -MF obj/script.d -o obj/script.o script.cpp
make: *** Brak reguł do zrobienia obiektu `obj/scrypt.o', wymaganego przez `onecoind'. Stop.
i have error compiling your sources:
Code:
/bin/sh ../share/genbuild.sh obj/build.h
make: *** No rule to make target `obj/scrypt.o', needed by `onecoind'. Stop.
make: *** Waiting for unfinished jobs....
And what kind of compiling instructions might it be?
Just compiled, like for any other coin:
Code:
git clone git://github.com/cre8r/onecoin.git
cd onecoin/
qmake
make
Code:
git clone git://github.com/cre8r/onecoin.git
cd onecoin/src
make -f makefile.unix
i have error compiling your sources:
Code:
/bin/sh ../share/genbuild.sh obj/build.h
make: *** No rule to make target `obj/scrypt.o', needed by `onecoind'. Stop.
make: *** Waiting for unfinished jobs....
Recommendation. Start with a reasonable difficulty so that even a low adoption won't totally block the coin, but that it doesn't fly with 3-5 blocks / sec either. Then make the retargeting for difficulty happen very fast initially with gradual slowdown until it comes to where you think it'll be mature.
I'd recommend starting off with retarget every 10 blocks, then at 100 blocks every 25 blocks, then at 500 blocks every 100 blocks, then at 2000 blocks every 250 blocks etc. This way a spike in hashrate will quickly change difficulty and the coins won't be minted like nuts meaning that a delay of 5 min in launch won't mean a difference of 10k blocks. It will also make the blockchain easier to access as initially most coins that fly with loads and loads of blocks per sec make later adopters lose a lot of time and blocks because of pure blockchain catchup.
Secondly don't reward the first 1k blocks at all. By that time the difficulty estimate should give a more stable rate, then make a gradual buildup until 25k blocks or what ever you planned.
Thirdly. Implement a failsafe. If you target the blocks at every 2.5min. Then if a block isn't found in N * 2.5 min the difficulty halves (you'll have to figure out what a good N is). Rinse and repeat. This way if for whatever reason the diff is driven up by someone in a short timeframe and then he leaves the rest can still continue to mine it and not be abandoned at high difficulty.
If I think of something else I'll post. And make sure you don't fuck up the launch. Try to choose a time that is mostly reasonable in all populated timezones. Probably late evening Asia, day EU, morning US is something that might work so that the maximum amount of people can be online for the launch. Give the time at least 24h in advance and then also launch it at the time. Giving people a countdown with 2h to go ... 1h to go, 30 min to go etc would be useful too.
Thanks for your advices! I'll do my best to follow them. I'd recommend starting off with retarget every 10 blocks, then at 100 blocks every 25 blocks, then at 500 blocks every 100 blocks, then at 2000 blocks every 250 blocks etc. This way a spike in hashrate will quickly change difficulty and the coins won't be minted like nuts meaning that a delay of 5 min in launch won't mean a difference of 10k blocks. It will also make the blockchain easier to access as initially most coins that fly with loads and loads of blocks per sec make later adopters lose a lot of time and blocks because of pure blockchain catchup.
Secondly don't reward the first 1k blocks at all. By that time the difficulty estimate should give a more stable rate, then make a gradual buildup until 25k blocks or what ever you planned.
Thirdly. Implement a failsafe. If you target the blocks at every 2.5min. Then if a block isn't found in N * 2.5 min the difficulty halves (you'll have to figure out what a good N is). Rinse and repeat. This way if for whatever reason the diff is driven up by someone in a short timeframe and then he leaves the rest can still continue to mine it and not be abandoned at high difficulty.
If I think of something else I'll post. And make sure you don't fuck up the launch. Try to choose a time that is mostly reasonable in all populated timezones. Probably late evening Asia, day EU, morning US is something that might work so that the maximum amount of people can be online for the launch. Give the time at least 24h in advance and then also launch it at the time. Giving people a countdown with 2h to go ... 1h to go, 30 min to go etc would be useful too.
Recommendation. Start with a reasonable difficulty so that even a low adoption won't totally block the coin, but that it doesn't fly with 3-5 blocks / sec either. Then make the retargeting for difficulty happen very fast initially with gradual slowdown until it comes to where you think it'll be mature.
I'd recommend starting off with retarget every 10 blocks, then at 100 blocks every 25 blocks, then at 500 blocks every 100 blocks, then at 2000 blocks every 250 blocks etc. This way a spike in hashrate will quickly change difficulty and the coins won't be minted like nuts meaning that a delay of 5 min in launch won't mean a difference of 10k blocks. It will also make the blockchain easier to access as initially most coins that fly with loads and loads of blocks per sec make later adopters lose a lot of time and blocks because of pure blockchain catchup.
Secondly don't reward the first 1k blocks at all. By that time the difficulty estimate should give a more stable rate, then make a gradual buildup until 25k blocks or what ever you planned.
Thirdly. Implement a failsafe. If you target the blocks at every 2.5min. Then if a block isn't found in N * 2.5 min the difficulty halves (you'll have to figure out what a good N is). Rinse and repeat. This way if for whatever reason the diff is driven up by someone in a short timeframe and then he leaves the rest can still continue to mine it and not be abandoned at high difficulty.
If I think of something else I'll post. And make sure you don't fuck up the launch. Try to choose a time that is mostly reasonable in all populated timezones. Probably late evening Asia, day EU, morning US is something that might work so that the maximum amount of people can be online for the launch. Give the time at least 24h in advance and then also launch it at the time. Giving people a countdown with 2h to go ... 1h to go, 30 min to go etc would be useful too.
I'd recommend starting off with retarget every 10 blocks, then at 100 blocks every 25 blocks, then at 500 blocks every 100 blocks, then at 2000 blocks every 250 blocks etc. This way a spike in hashrate will quickly change difficulty and the coins won't be minted like nuts meaning that a delay of 5 min in launch won't mean a difference of 10k blocks. It will also make the blockchain easier to access as initially most coins that fly with loads and loads of blocks per sec make later adopters lose a lot of time and blocks because of pure blockchain catchup.
Secondly don't reward the first 1k blocks at all. By that time the difficulty estimate should give a more stable rate, then make a gradual buildup until 25k blocks or what ever you planned.
Thirdly. Implement a failsafe. If you target the blocks at every 2.5min. Then if a block isn't found in N * 2.5 min the difficulty halves (you'll have to figure out what a good N is). Rinse and repeat. This way if for whatever reason the diff is driven up by someone in a short timeframe and then he leaves the rest can still continue to mine it and not be abandoned at high difficulty.
If I think of something else I'll post. And make sure you don't fuck up the launch. Try to choose a time that is mostly reasonable in all populated timezones. Probably late evening Asia, day EU, morning US is something that might work so that the maximum amount of people can be online for the launch. Give the time at least 24h in advance and then also launch it at the time. Giving people a countdown with 2h to go ... 1h to go, 30 min to go etc would be useful too.
yep, like the sound of all that.
Recommendation. Start with a reasonable difficulty so that even a low adoption won't totally block the coin, but that it doesn't fly with 3-5 blocks / sec either. Then make the retargeting for difficulty happen very fast initially with gradual slowdown until it comes to where you think it'll be mature.
I'd recommend starting off with retarget every 10 blocks, then at 100 blocks every 25 blocks, then at 500 blocks every 100 blocks, then at 2000 blocks every 250 blocks etc. This way a spike in hashrate will quickly change difficulty and the coins won't be minted like nuts meaning that a delay of 5 min in launch won't mean a difference of 10k blocks. It will also make the blockchain easier to access as initially most coins that fly with loads and loads of blocks per sec make later adopters lose a lot of time and blocks because of pure blockchain catchup.
Secondly don't reward the first 1k blocks at all. By that time the difficulty estimate should give a more stable rate, then make a gradual buildup until 25k blocks or what ever you planned.
Thirdly. Implement a failsafe. If you target the blocks at every 2.5min. Then if a block isn't found in N * 2.5 min the difficulty halves (you'll have to figure out what a good N is). Rinse and repeat. This way if for whatever reason the diff is driven up by someone in a short timeframe and then he leaves the rest can still continue to mine it and not be abandoned at high difficulty.
If I think of something else I'll post. And make sure you don't fuck up the launch. Try to choose a time that is mostly reasonable in all populated timezones. Probably late evening Asia, day EU, morning US is something that might work so that the maximum amount of people can be online for the launch. Give the time at least 24h in advance and then also launch it at the time. Giving people a countdown with 2h to go ... 1h to go, 30 min to go etc would be useful too.
I'd recommend starting off with retarget every 10 blocks, then at 100 blocks every 25 blocks, then at 500 blocks every 100 blocks, then at 2000 blocks every 250 blocks etc. This way a spike in hashrate will quickly change difficulty and the coins won't be minted like nuts meaning that a delay of 5 min in launch won't mean a difference of 10k blocks. It will also make the blockchain easier to access as initially most coins that fly with loads and loads of blocks per sec make later adopters lose a lot of time and blocks because of pure blockchain catchup.
Secondly don't reward the first 1k blocks at all. By that time the difficulty estimate should give a more stable rate, then make a gradual buildup until 25k blocks or what ever you planned.
Thirdly. Implement a failsafe. If you target the blocks at every 2.5min. Then if a block isn't found in N * 2.5 min the difficulty halves (you'll have to figure out what a good N is). Rinse and repeat. This way if for whatever reason the diff is driven up by someone in a short timeframe and then he leaves the rest can still continue to mine it and not be abandoned at high difficulty.
If I think of something else I'll post. And make sure you don't fuck up the launch. Try to choose a time that is mostly reasonable in all populated timezones. Probably late evening Asia, day EU, morning US is something that might work so that the maximum amount of people can be online for the launch. Give the time at least 24h in advance and then also launch it at the time. Giving people a countdown with 2h to go ... 1h to go, 30 min to go etc would be useful too.
Jump to: