unstaaaaaaaaaaaaaaaaaaaaaaaaaaaaaack!!!
we need p2pool now!!!!
we need p2pool now!!!!
+1 I just want to set up my own node! Till then though, flutter.miningwith.us has been working good for me.
Topic: [ANN] FlutterCoin FLT Proof Of Transaction Cash Back for Sending & Recieving - page 282. (Read 368097 times)
March 16, 2014, 05:26:28 PM
+1 I just want to set up my own node! Till then though, flutter.miningwith.us has been working good for me.
March 16, 2014, 05:25:02 PM
unstaaaaaaaaaaaaaaaaaaaaaaaaaaaaaack!!!
we need p2pool now!!!!
we need p2pool now!!!!
+1 I just want to set up my own node! Till then though, flutter.miningwith.us has been working good for me.
March 16, 2014, 05:24:35 PM
if you do solo mining, will you have the same stuck block issues as the pools?
March 16, 2014, 05:23:03 PM
lost 2700 flt in transaction from pool to bter during the fork so be careful when doing transactions
edit: There was also 1300 pending on bter... then when accepted it was sudden only 700??
Man sorry but i'm stopping giving support on this coin until problems sorted
edit: There was also 1300 pending on bter... then when accepted it was sudden only 700??
Man sorry but i'm stopping giving support on this coin until problems sorted
When will people learn, you don't put an exchange address as your payout address from a pool?
March 16, 2014, 05:18:06 PM
unstaaaaaaaaaaaaaaaaaaaaaaaaaaaaaack!!!
we need p2pool now!!!!
we need p2pool now!!!!
March 16, 2014, 04:49:28 PM
Another stuck block 11214.
What about the 51%poolhashrate? If the block get stuck the net hashrate seems to go to 1431Mh/s
Bitember got 721Mh/s, thats more than 51%.
Before the stuck block the net hashrate was about 1100Mh/s. So if a pool gets more than 51% hashrate u get a stuck block? The net-hashrate moves up to about 50% of a pools hashrate..
It is just theory..need to check or somebody else, cause i'm gonna sleep.
The total net-hashrate is also not the same as the total poolhashrates. If I don't count bitember or cloudminers than the nethashrate is almost the same as the total poolhashrates.
Also saw a miner with 100mh/s who jumps over to another pool if the block get stuck.
first at miningwithme then to bitember and now to crunchharder i think.
What about the 51%poolhashrate? If the block get stuck the net hashrate seems to go to 1431Mh/s
Bitember got 721Mh/s, thats more than 51%.
Before the stuck block the net hashrate was about 1100Mh/s. So if a pool gets more than 51% hashrate u get a stuck block? The net-hashrate moves up to about 50% of a pools hashrate..
It is just theory..need to check or somebody else, cause i'm gonna sleep.
The total net-hashrate is also not the same as the total poolhashrates. If I don't count bitember or cloudminers than the nethashrate is almost the same as the total poolhashrates.
Also saw a miner with 100mh/s who jumps over to another pool if the block get stuck.
first at miningwithme then to bitember and now to crunchharder i think.
March 16, 2014, 04:08:14 PM
I am gonna have to start dumping some coins as a hedge in case the coin loses all momentum. 
March 16, 2014, 03:52:28 PM
nevermind...
March 16, 2014, 03:46:03 PM
lost 2700 flt in transaction from pool to bter during the fork so be careful when doing transactions
edit: There was also 1300 pending on bter... then when accepted it was sudden only 700??
Man sorry but i'm stopping giving support on this coin until problems sorted
edit: There was also 1300 pending on bter... then when accepted it was sudden only 700??
Man sorry but i'm stopping giving support on this coin until problems sorted
It's not a good idea make transactions from pools to exchanges.
Pool -> Wallet -> Exchange
I am 7 months into crypto and mined alot of different coins I think the issue lays in the block forks, something is very wrong
March 16, 2014, 03:42:58 PM
i'm hopping off this coin too. i'll check back to see if the issue gets fixed
March 16, 2014, 03:39:36 PM
lost 2700 flt in transaction from pool to bter during the fork so be careful when doing transactions
edit: There was also 1300 pending on bter... then when accepted it was sudden only 700??
Man sorry but i'm stopping giving support on this coin until problems sorted
edit: There was also 1300 pending on bter... then when accepted it was sudden only 700??
Man sorry but i'm stopping giving support on this coin until problems sorted
It's not a good idea make transactions from pools to exchanges.
Pool -> Wallet -> Exchange
March 16, 2014, 02:41:44 PM
lost 2700 flt in transaction from pool to bter during the fork so be careful when doing transactions
edit: There was also 1300 pending on bter... then when accepted it was sudden only 700??
Man sorry but i'm stopping giving support on this coin until problems sorted
edit: There was also 1300 pending on bter... then when accepted it was sudden only 700??
Man sorry but i'm stopping giving support on this coin until problems sorted
March 16, 2014, 02:36:43 PM
You should also consider PM'ing the devs that took over (and troubleshooted) the issues with GPUC. They were super cool talking to people in IRC and might be willing to lend a hand as well.
I think these are their names here:
Coin Dev - micryon (led the repair for the final launch)
Coin Dev - cryptowest
I think these are their names here:
Coin Dev - micryon (led the repair for the final launch)
Coin Dev - cryptowest
March 16, 2014, 02:33:53 PM
I bet if these pools didn't allow near 1/2 of the network more to hash, we would not have this issue.
You can't blame the pools and I still think this is something specific in the code of the coin. Even though we've had a big pool since BTER, we've also had a "kind of" big one that was around 50%-70% of biggest one... The blocks stalling with large hashing going on is a symptom, not the problem.
If it was simply a network hash percentage issue, we'd be getting forks (like before). We aren't getting forks, we're getting stalls, which again leads me to believe it's something tied to either the POB or POW (or combined)... The coin has never had this type of load before...
March 16, 2014, 02:30:45 PM
Something wrong with bter? Seems like I'm missing a lot of deposits there...
March 16, 2014, 02:29:59 PM
If there were an issue with the blockchain, the pools would see rejected blocks for invalid work or other issues - are they seeing blocks rejected? If so, thats a problem with FLT.
The only possible issue is changing the way FLT changes difficulty, how it adjusts it etc.
We are stuck again - watch the hashrate reported by the network, and watch what the pools report. Note how the network hashrate will go up matching what the pools are showing, then it will get stuck again. Why is that? Is that hashrate valid (see my post regarding a stratum exploit that has actually stalled other coins in the past week)? Is the pool itself stuck?
I bet if these pools didn't allow near 1/2 of the network more to hash, we would not have this issue.
Seems like net hashrate is oke now 2197.40MH/s, it did takes about 30min to get at this point from 1300Mh/s i think when I last saw it.The only possible issue is changing the way FLT changes difficulty, how it adjusts it etc.
We are stuck again - watch the hashrate reported by the network, and watch what the pools report. Note how the network hashrate will go up matching what the pools are showing, then it will get stuck again. Why is that? Is that hashrate valid (see my post regarding a stratum exploit that has actually stalled other coins in the past week)? Is the pool itself stuck?
I bet if these pools didn't allow near 1/2 of the network more to hash, we would not have this issue.
block 11170...so we gonna get stuck again as u mention kidcoin
edit
yep, your theory is right, but when I check the poolhashrate all together it is now less than the net-hashrate. The net-hashrate is still the same (2197.4MH/s)
I also notice at miningwithus, the poolhashrate drops from 200Mh to 125Mh
March 16, 2014, 02:15:26 PM
I am going to contact my friend @BryceWeiner from twitter to come in and look at the problem kidcoin. He most likely will be able to collaborate on a solution with you.
March 16, 2014, 01:29:00 PM
also note how after the block is solved, blocks are found in rapid succession
Noted the hashrate here - currently in block 11112 its 594 mH
http://explorer.fluttercoin.us/block_crawler.php
Noted the hashrate alone at the same block at bitember which is 600 mH
http://flt.bitember.com/
Noted the hashrate alone at the same block at cloudminers which is 800 mH
How is that possible? Sure hashrate could be off a bit, but not that much.
Maybe https://bitcointalk.org/index.php?topic=513382.20
Not sure
Noted the hashrate here - currently in block 11112 its 594 mH
http://explorer.fluttercoin.us/block_crawler.php
Noted the hashrate alone at the same block at bitember which is 600 mH
http://flt.bitember.com/
Noted the hashrate alone at the same block at cloudminers which is 800 mH
How is that possible? Sure hashrate could be off a bit, but not that much.
Maybe https://bitcointalk.org/index.php?topic=513382.20
Not sure
March 16, 2014, 01:20:54 PM
If there were an issue with the blockchain, the pools would see rejected blocks for invalid work or other issues - are they seeing blocks rejected? If so, thats a problem with FLT.
The only possible issue is changing the way FLT changes difficulty, how it adjusts it etc.
We are stuck again - watch the hashrate reported by the network, and watch what the pools report. Note how the network hashrate will go up matching what the pools are showing, then it will get stuck again. Why is that? Is that hashrate valid (see my post regarding a stratum exploit that has actually stalled other coins in the past week)? Is the pool itself stuck?
I bet if these pools didn't allow near 1/2 of the network more to hash, we would not have this issue.
The only possible issue is changing the way FLT changes difficulty, how it adjusts it etc.
We are stuck again - watch the hashrate reported by the network, and watch what the pools report. Note how the network hashrate will go up matching what the pools are showing, then it will get stuck again. Why is that? Is that hashrate valid (see my post regarding a stratum exploit that has actually stalled other coins in the past week)? Is the pool itself stuck?
I bet if these pools didn't allow near 1/2 of the network more to hash, we would not have this issue.
March 16, 2014, 12:39:23 PM
same here… should I switch pool ?
Jump to: