hashpower is going back up. i wouldn't be surprised if we hit 5gh today
We would be at that already if there wasn't a block problem seems to be putting people off. There is no block problem... look at the difficulty of the stuck blocks when they are finally found, and the next block immediately after. Note the difficulty drop (which means hashrate drop) - ID 1,288 Height 10,867 Amount 6,061 Confirmations Confirmed
Difficulty 41.25640906 Time 2014-03-16 07:34:46 Shares 26,453 Finder anonymous
- ID 1,290 Height 10,869 Amount 1,786 Confirmations Confirmed
Difficulty 41.8433359 Time 2014-03-16 07:36:21 Shares 71,847 Finder anonymous
- ID 1,291 Height 10,870 Amount 2,488 Confirmations Confirmed
Difficulty 42.6003626 Time 2014-03-16 10:33:45 Shares 11,233,453 Finder anonymous
- ID 1,292 Height 10,871 Amount 5,028 Confirmations Confirmed
Difficulty 17.38400962 Time 2014-03-16 10:33:49 Shares 2 Finder anonymous
- ID 1,296 Height 10,873 Amount 8,018 Confirmations Confirmed
Difficulty 17.51475139 Time 2014-03-16 10:37:05 Shares 113,764 Finder
How come block 10867,10869 is normal than with the same diff? [/list][/list][/list][/list] Don't follow what your saying |
|
|
|
hashpower is going back up. i wouldn't be surprised if we hit 5gh today
We would be at that already if there wasn't a block problem seems to be putting people off. There is no block problem... look at the difficulty of the stuck blocks when they are finally found, and the next block immediately after. Note the difficulty drop (which means hashrate drop) |
|
|
|
|
Its getting stuck only because hashrate is dropping off FYI all, no other reason.
For example:
For example look at NVC. It had 10 minute blocks and a 24 hour 200% adjustment max window (max difficulty can go is 200% increase in 144 blocks)
FLT had 2 minute blocks and a 4 hour 200% max adjustment window (max difficulty can go is 200% increase in 144 blocks).
A lot of the hashrate may not even be legit - I remember someone remarking that one pool had a lot of hashrate, yet the network didn't report it (but it did earlier) - and they thought they were forked, but they weren't.
I have contacted all pool operators that I know of with the reason for this. If you see anyone mining in a pool with a HUGE hashrate, report them - they have no business being in a pool, and just may not have that hashrate at all.
|
|
|
|
What about just putting a warning instead of removing them?
been there done that LOL |
|
|
|
@thekidcoin
Can you temporarily remove pools with a lot of hash from OP?
At least new people will join smaller pools that way.
can do that - just keep in mind I cant watch the thread/pools 24/7 so people please share with others if things look lopsided or maybe we need to remove/re-add a pool |
|
|
|
I've notified all (let me know if there any pools besides page 1 of the thread) pool operators I think, of a possible reason why the difficulty drops, hashrate is so high, etc - I don't think its an issue with FLT... Effected other coins in recent days. Don't want to go into it until its fixed. Explains why you all saw pools that clearly wren't forked (to determine fork look at block height and reward - the reward must match the explorer) have huge hashrate that mysteriously was no longer showing on the main network.
Also because of my fear of block spamming to try and win POT/POB or whatever blocks rewards (I saw huge number of TX's in some blocks - and they didn't win a block reward LOL), I am going to introduce some additional parameters which will eliminate the possibility of sending a ton of transactions back and forth just to try and win. Its a VERY simple fix that will not effect its difficulty. Not to say someone can't get lucky, but if they are lucky, they would likely waste a day and a lot of tx fees in the process.
Should probably do it sooner rather than later, as more exchanges are going to like seeing the action here.... keep up the good work Kid... ! But please post a time if/when it's going to affect mining. I hate leaving things running when maintenance is being conducted. It wont be a fire drill type of fork (it needs a fork to ensure older protocol is dropped as of X date, then the fix will start as of Y block - ensures everyone is upgraded, and is ready for the fork/fix. It will be released at least 7 days in advance notice - its not super critical - they few cases i saw of clearly trying to export it all failed - not POT/POB reward. Again its not easy. You can have a bunch of addresses that wouldn't win for 100K blocks even if you sent a transaction every block. Other addresses will win more. But there is no possible way to exploit, guess etc. The block hash dictates the finder, likely a bigger factor. This is why I am torn on POB/POT - it goes hand in hand |
|
|
|
|
tx 835937b919e8d1d53b33c4a2c830f628efa05fb7ca3cc8c15c958af20bec4d0e doesn't exist - was never sent - like I said export your keys, create new wallet and import.
|
|
|
|
|
I've notified all (let me know if there any pools besides page 1 of the thread) pool operators I think, of a possible reason why the difficulty drops, hashrate is so high, etc - I don't think its an issue with FLT... Effected other coins in recent days. Don't want to go into it until its fixed. Explains why you all saw pools that clearly wren't forked (to determine fork look at block height and reward - the reward must match the explorer) have huge hashrate that mysteriously was no longer showing on the main network.
Also because of my fear of block spamming to try and win POT/POB or whatever blocks rewards (I saw huge number of TX's in some blocks - and they didn't win a block reward LOL), I am going to introduce some additional parameters which will eliminate the possibility of sending a ton of transactions back and forth just to try and win. Its a VERY simple fix that will not effect its difficulty. Not to say someone can't get lucky, but if they are lucky, they would likely waste a day and a lot of tx fees in the process.
|
|
|
|
I have deleted the whole Roaming/Fluttercoin folder and did a wallet backup. Now i get this error  try running: repairwallet Unfortunately repairconsole doesn´t work :/  Does anybody have a idea how i can get them back? I have sent them to my Bter deposit address, but under address theres just (n/a) and the coins never arrived at bter. Not save to transfer coins trough the network  post the tx  copy/paste the tx id lol i cant type all that |
|
|
|
you do have a copy before it went bad right??? you also ran this command: repairwallet ? (you mentioned repairconsole???) You can try this nonetheless, keep a copy, don't touch it. make another copy and try to run: https://github.com/gavinandresen/bitcointools/blob/master/fixwallet.py or like I said export keys you think you used (if you didn't make a bunch of addresses in they wallet, you only need a few - there are 101 i think pre-allocated) getaccountaddress 0 get that address, then run: dumpprivkey [the address from above] repeat for each address you added (1, 2, 3 etc etc) then run the wallet with NO wallet.dat, let it create a new wallet file - then import the keys. |
|
|
|
I have deleted the whole Roaming/Fluttercoin folder and did a wallet backup. Now i get this error try running: repairwallet Unfortunately repairconsole doesn´t work :/ Does anybody have a idea how i can get them back? I have sent them to my Bter deposit address, but under address theres just (n/a) and the coins never arrived at bter. Not save to transfer coins trough the network post the tx |
|
|
|
|
Export the keys, create a new wallet, import the keys, rescan.
real transactions don't get lost... If we ever get a block explorer that can search by address, you would see this.
You have deleted all files except for the wallet and conf correct?
|
|
|
|
Who said earlier another coin had stalled blocks today? 365 coin or something?
I am investigating something, definitely a major issue (not with FLT), not sure though if it could effect our network itself though.
I believe it was darkcoin Ok think then I'm on the right track, think there was another too. This isn't coincidence I don't think |
|
|
|
According to the Block Crawler the current nethash is 2068.26355306 mH/s.
This should mean that all the current pool's are in the clear.
Is just checked the pool's and they are +/- 600mH/s
bitembers at 890 mhs I'm in car, can't see the pools,did any pool actually fork??? |
|
|
|
|
Who said earlier another coin had stalled blocks today? 365 coin or something?
I am investigating something, definitely a major issue (not with FLT), not sure though if it could effect our network itself though.
|
|
|
|
|
They could be stuck because of the check pointing - all forks will die eventually they would error out with invalid checkpoint.
In any event they need to just fix the issue and politely ask people with large hash rates to mine elsewhere.
|
|
|
|
bitember and cloudminers are on different forks, AND BOTH FORKS HAVE SAME ISSUE...  They show the same current block 10435. The Bitember's dashboard doesn't auto refresh, hit F5 from time to time. Might be the same block number, but bitember reports network hashrate and pool hashrate as identical, so they are on a separate fork. Any clue if cloudminers is on the proper one? This doesn't necessarily mean a fork, I've seen similar things happen on other pools and it was due to crons fuckup or some such, wasn't actually a fork. That being said, this coin had a ton of forks before it was posted here, so I wouldn't be surprised if it started happening again. The only forks that occurred were because of lopsided hashrate. These things don't just happen without reason. These delays are likely hashrate/difficulty related. They could be forked also. The fork is purely hashrate related. You can't run a pool with 75% of the hashrate. Not only does it cause forks, but if it goes down the block chain stalls as the difficulty target for the next block it way too high. |
|
|
|
|
I take that back about btember, I'm on a cell phone lol.
Verify using block explorer...
|
|
|
|
Thanks, that's the way to go, that other pool had 75 of all hashrate |
|
|
|
|
Anyone know how to get P2Pool setup?
|
|
|
|
|
Show Posts
