ok posted as promised: http://bitcoinlasvegas.net/xradon-coin-xrdn-scrypt-powpos-just-launched-now-at-block-50-launched-on-5252015/
For those of you not familiar with my site, here is more info:
Guys, for the past year I have worked extremely hard every day to build the best and most up to date website in the world for cryptocurrency. I update it ONLY with valuable information such as a new coin release,an updated wallet,coin swaps, addnodes, and wallets with trojans you should avoid, and ANYTHING that is useful. Most of the time, I post news within a few minutes after it happens. I post at least 5 valuable articles a day. Many people find it useful to subscribe to my blog, and then you will get an email within a minute after I post. I do NOT spam, and carefully choose quality information. My posts are right to the point including coin name and logo,specs,exchanges, addnodes,and wallet links, and I even list only 1 pool with all the hash , so you know right where to go! I also post a link to the main ann on bitcointalk to the coin. Its clean and very easy to read...AND Its all FREE!! I personally promise to NEVER send spam, or junk or offer to sell anything, and post ONLY QUALITY cryptocoin news! Thank you, and when you go to www.bitcoinlasvegas.net youll be glad you did!
Topic: [ANN] [XRDN] Project Radon - Rebrand update released - Hard fork at block 338000 - page 18. (Read 33227 times)
May 25, 2015, 07:15:59 PM
May 25, 2015, 07:03:18 PM
I think the best solution is for us ALL agree to back off this and limit the hashspeed. Say 500Mhs MAX
Vegas
The problem is getting past block 51. The network is working at finding block 52 @ 512 difficulty, but it can't. If the chain is stuck, that's a whole different issue but for now we need to get past this block. If the times prove to be this slow, I can set the fork to happen much earlier.Vegas
No, its not only the block 52... if you analise the pattern, after block 52 it will decrease the next 2 or 3 blocks to a minimum diff, than to a too high diff again, and it will take hours again...
May 25, 2015, 06:55:11 PM
I think the best solution is for us ALL agree to back off this and limit the hashspeed. Say 500Mhs MAX
Vegas
The problem is getting past block 51. The network is working at finding block 52 @ 512 difficulty, but it can't. If the chain is stuck, that's a whole different issue but for now we need to get past this block. If the times prove to be this slow, I can set the fork to happen much earlier.Vegas
Edit: We're looking at quite a long time to find the next block at this point.
May 25, 2015, 06:36:27 PM
I think the best solution is for us ALL agree to back off this and limit the hashspeed. Say 500Mhs MAX
Vegas
Vegas
May 25, 2015, 06:23:25 PM
OP updated with the new windows wallet. Please update before block 150.
https://mega.co.nz/#!0Z51BRwZ!pCSr30OiL47gfQo8nNN9u06HrD62F4sXBWyTa0ivzDg
https://mega.co.nz/#!0Z51BRwZ!pCSr30OiL47gfQo8nNN9u06HrD62F4sXBWyTa0ivzDg
The hardfork cant be done earlier, like 80-100?? More than 50min at block 52... at this way, we will reach block 150 in a week (or more)...
We cant even put more hashes (or the situation will be worse)....
May 25, 2015, 06:17:50 PM
OP updated with the new windows wallet. Please update before block 150.
https://mega.co.nz/#!0Z51BRwZ!pCSr30OiL47gfQo8nNN9u06HrD62F4sXBWyTa0ivzDg
https://mega.co.nz/#!0Z51BRwZ!pCSr30OiL47gfQo8nNN9u06HrD62F4sXBWyTa0ivzDg
May 25, 2015, 06:05:28 PM
Windows wallet will be up shortly. Hard fork at block 150.
Good job! But we will spend "a life" to reach block 150...
May 25, 2015, 06:03:53 PM
Windows wallet will be up shortly. Hard fork at block 150.
Ok.. I think I like this dev! right on top of things. Its not the fact you made an error, its how you deal with it. Well done!
+1000
Vegas
May 25, 2015, 05:59:35 PM
Windows wallet will be up shortly. Hard fork at block 150.
May 25, 2015, 05:30:38 PM
dev passed the first test
May 25, 2015, 05:28:39 PM
After github source is verified. Please post new windows binary on OP and report here. Thank you for your dedication. In the meantime Ill begin my article on the coin. 300-500 set of eyes per day will see it.
Vegas
Vegas
May 25, 2015, 05:24:44 PM
Github updated. Ocminer, can you verify the fork?
May 25, 2015, 04:39:07 PM
It's almost impossible continue mining with this crazy diff... We REALLY need an update much sooner!
May 25, 2015, 04:31:52 PM
We REALLY need it MUCH sooner than tomorrow afternoon, this diff is a nightmare
@dev, you have a development fund. I STRONGLY urge you to use some of it and hire OCMINER to expedite the new fork. He can get this done MUCH faster, and get everyone moving forward. I want to post your coin on my site that is ranked #1-3 for searches for every coin on google, but not in the condition its in. Google ANY recent coin released in the last few months, Ill be at the top of the page. www.bitcoinlasvegas.net
Vegas
May 25, 2015, 04:29:50 PM
@OCMiner @MinerPools, your pools are not mining to the network.
Not mining to the network? To what then? The wall?
Do you mean there is a fork again or what?
Dude, seriously.. Think before you write.. No one is jumping off or on the network, the problem is you have set a wrong nTargetTimespan in the source..
This variable is NOT setting the blocktime i.e. 60 seconds per block, it sets the "look over the last blocks in this timespan to calculate the next diff" in the coin.. if you set this to 1 minute, it only looks at the last block and sets a diff which is much too high, the IvugeoMeoShitCoin Dev had the same problem with his coin. You have to set this to at least 5 mins, better 10 mins to get a working diff recalculation.
If you don't know what you're talking about, its sometimes better to ask instead of writing anything that just comes into your mind..
Sounds good.. Please test the retarget before releasing an update or it will be a mess... you have to find the right value 5/10/15 minutes etc..
May 25, 2015, 04:25:55 PM
@OCMiner @MinerPools, your pools are not mining to the network.
Not mining to the network? To what then? The wall?
Do you mean there is a fork again or what?
Dude, seriously.. Think before you write.. No one is jumping off or on the network, the problem is you have set a wrong nTargetTimespan in the source..
This variable is NOT setting the blocktime i.e. 60 seconds per block, it sets the "look over the last blocks in this timespan to calculate the next diff" in the coin.. if you set this to 1 minute, it only looks at the last block and sets a diff which is much too high, the IvugeoMeoShitCoin Dev had the same problem with his coin. You have to set this to at least 5 mins, better 10 mins to get a working diff recalculation.
If you don't know what you're talking about, its sometimes better to ask instead of writing anything that just comes into your mind..
Sounds good.. Please test the retarget before releasing an update or it will be a mess... you have to find the right value 5/10/15 minutes etc..
May 25, 2015, 04:24:22 PM
@OCMiner @MinerPools, your pools are not mining to the network.
Not mining to the network? To what then? The wall?
Do you mean there is a fork again or what?
Dude, seriously.. Think before you write.. No one is jumping off or on the network, the problem is you have set a wrong nTargetTimespan in the source..
This variable is NOT setting the blocktime i.e. 60 seconds per block, it sets the "look over the last blocks in this timespan to calculate the next diff" in the coin.. if you set this to 1 minute, it only looks at the last block and sets a diff which is much too high, the IvugeoMeoShitCoin Dev had the same problem with his coin. You have to set this to at least 5 mins, better 10 mins to get a working diff recalculation.
If you don't know what you're talking about, its sometimes better to ask instead of writing anything that just comes into your mind..
May 25, 2015, 04:20:02 PM
Diff is jumping like a crazy rabbit...
May 25, 2015, 04:19:27 PM
looks like a joke already., any option for scrypt mine? dont want to waste time here
May 25, 2015, 04:15:08 PM
@OCMiner @MinerPools, your pools are not mining to the network.
Not mining to the network? To what then? The wall?
Do you mean there is a fork again or what?
Dude, seriously.. Think before you write.. No one is jumping off or on the network, the problem is you have set a wrong nTargetTimespan in the source..
This variable is NOT setting the blocktime i.e. 60 seconds per block, it sets the "look over the last blocks in this timespan to calculate the next diff" in the coin.. if you set this to 1 minute, it only looks at the last block and sets a diff which is much too high, the IvugeoMeoShitCoin Dev had the same problem with his coin. You have to set this to at least 5 mins, better 10 mins to get a working diff recalculation.
If you don't know what you're talking about, its sometimes better to ask instead of writing anything that just comes into your mind..
Jump to: