Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - turtletastic2

Pages: [1]
1
General Discussion / Re: news?
« on: February 04, 2015, 02:29:37 pm »
I sure hope this project will be officially released one day, too!  :) It would surely attract many new miners and thus new people to the bitshare universe.

Judging by his unresponsiveness, its current creator "sparkle" could have been hit by a bus for all we know though....  :(

2
General Discussion / Re: news?
« on: January 28, 2015, 11:23:47 pm »
Are you still there sparkle? Over a month now with no replies...   :(

3
General Discussion / Re: news?
« on: January 11, 2015, 05:20:57 pm »
Where do you have this information from? Starting after bitshares 1.0 release would be very reasonable! But I'd wager that its currently a tough time to launch new coins anyway.

4
General Discussion / Re: news?
« on: January 11, 2015, 04:21:39 pm »
Well at least sparkle hasnt responded in a while. Would be nice if you you could respond sparkle and tell us if you still want to launch this coin!

5
network_get_peer_info returns these for me:

66.172.27.88:1766
85.214.126.216:1766
104.131.0.131:36666
66.172.27.128:1766
192.99.246.148:1766
66.172.11.125:1766

I'm on block 55987 (2014-12-19T00:29:22)

Hope that helps!

6
I've noticed that the new commit doesn't even check the difficulty every 20 blocks for blocks < 20000 anymore. I was thinking, I might as well take us to block no. 20000 on my own and do something good with all those blocks instead of giving them to some idiot. So, either we don't honor these blocks at all, or we do it: In that case, I don't want them and I would use them for project bounties (starting services, building exchanges, etc.).

For the record: It wasn't me who exploited it in first place. But I got tired of waiting until we hit 20000 or restart.

Btw, difficulty is at 3342778 and we havn't found a single block after number 20000.

yeah seems stalled out, been over 30 mins now with no block 20001, with increasing diff to 3409633. I'm starting to think the new chain may be needed.

Thats what I wanted to show by taking us to 20000 quicker ;)
Starting the new chain today would be nice, as most people would have the chance and time to recompile and restart it on a sunday instead of a work day.

The problem is, you've created a fork that isn't valid for all the clients still on alpha.5 so they ignore your branch.
I think there needs to be a change in alpha.7 to put back the 20th block difficulty check for blocks under 20000 (and of course keep the difficulty check on every block as in alpha.6)

Hard fork has been made and I was just using the new rules. Forking again the way you described it would not help at all, it would just give the original attacker those last 500-600 blocks I've mined. Either way, we're stuck at some irrationaly high difficulty and block 20000, it is probably wiser to just start a new chain, like the last time we got stuck with a high difficulty.

7
I've noticed that the new commit doesn't even check the difficulty every 20 blocks for blocks < 20000 anymore. I was thinking, I might as well take us to block no. 20000 on my own and do something good with all those blocks instead of giving them to some idiot. So, either we don't honor these blocks at all, or we do it: In that case, I don't want them and I would use them for project bounties (starting services, building exchanges, etc.).

For the record: It wasn't me who exploited it in first place. But I got tired of waiting until we hit 20000 or restart.

Btw, difficulty is at 3342778 and we havn't found a single block after number 20000.

yeah seems stalled out, been over 30 mins now with no block 20001, with increasing diff to 3409633. I'm starting to think the new chain may be needed.

Thats what I wanted to show by taking us to 20000 quicker ;)
Starting the new chain today would be nice, as most people would have the chance and time to recompile and restart it on a sunday instead of a work day.

8
I've noticed that the new commit doesn't even check the difficulty every 20 blocks for blocks < 20000 anymore. I was thinking, I might as well take us to block no. 20000 on my own and do something good with all those blocks instead of giving them to some idiot. So, either we don't honor these blocks at all, or we do it: In that case, I don't want them and I would use them for project bounties (starting services, building exchanges, etc.).

For the record: It wasn't me who exploited it in first place. But I got tired of waiting until we hit 20000 or restart.

Btw, difficulty is at 3342778 and we havn't found a single block after number 20000.


9
Yep, you're right Frodo +5% for the fast reaction.

I'm also for starting a new chain. Since we have to wait every 20 blocks until we can proceed and diff stands at 1317968 now, it will probably take longer than Dec 14 to sort this out. And that waiting time would make the shares of this attacker even more valuable.

Might also make sense to slightly raise the difficulty amount that can be changed downwards every 20 blocks, e.g. from 2% to 5% or 10%, so that we can adjust quicker downwards than upwards.

10
Issue might be that miners turn their miners off, because they don't earn the same amount anymore with their hash power and would wait until this issue is over... it'll probably take a lot longer than 3 days until we have regular 20s blocks. I'm turning my miners off until this is over.

11
Diff was at ~100000 before it started and is now over 1mill. Hard to say what it will be when we hit 20000 blocks, but reverting back from 1mill to 100000 will take us:

wolframalpha.com/input/?i=1000000+*+0.98^x+%3D+100000

114 diff adjustments, which come every 20 blocks. Means it will take 2280 blocks.

I'd ball park the avg block time to be 5x higher over these 2280 blocks, so it will take us 100 seconds * 2280, to get there, i.e. ~
3 days. Not too bad actually, but your call on how to proceed.

12
Ok, that explains why the attackter had to wait every 20 blocks for a real block to show up...

Since the difficulty is sky high now, once we're at 20000 for the hard fork, it will take nearly forever to revert back to lower diff, wouldn't it? What is the max diff reduction now, 3%?

Could make sense to either start with a new blockchain then and honor all blocks up to whatever block it was were the truoble started, or allow for a faster diff correction downwards.

13
The dampen difficult adjustment hack is probably not what you want to solve the difficult problem. (commit 7c649ebdbaf6fa378a9c25023d531986e1745484 @ github)

There is a reason bitcoin adjusts after a number of blocks, the time between two single blocks is not a very reliable indicator of network strength.

There should be one block every minute and hours went by again without one. Right now, the network will never compensate for that. There could always be an unlucky sequence of two blocks being very close after each other (just some miliseconds) and difficulty would shoot to the moon. Damping it 10x is still a very naive way of solving this improbable but very much possible outcome and eventually the blockchain will still get stuck like it has now.

Do it as bitcoin does it, adjust after a number of blocks. Have some kind of moving average over the last n blocks, as all alt-coins do it that adjust every block. Don't just base the difficulty equation on the difference of two single blocks alone, that is just asking for trouble.

Pages: [1]