[ANN] FlutterCoin FLT Proof Of Transaction Cash Back for Sending & Recieving

[seattletu]

we should ask bitember if they will shut their pool down for a while that could definitely be the problem. i wouldn't mind chipping in some flt to the pool operator so they still collect some coin while it's down.

[seattletu]

just an fyi since nobody has mentioned it, we've been finding blocks for about 10 minutes now, the network is working

[seattletu]

and watch the coin price rise on bter 

[bullus]

What about the nethashrate vs total poolshashrate?

At stuck block 11302 it says 2092mH/s but the total poolshashrate is now about 926mH/s.
Shouldn't the nethashrate also be adjusted or is it fixed when started a new block?
http://explorer.fluttercoin.us/block_crawler.php

Still don't understand why the nethashrate isn't the same as the total poolshashrate.
If a pool can be offline and the nethashrate isn't drops than that pool isn't registered to the nethashrate?

http://explorer.litecoin.net/block/11302

http://explorer.litecoin.net/block/00000000019c7d2d21bcbe9d7ff2d9d5715c734229e13dc613b15ab63644a3b5

Pool Hash Rate491.136 MH/s
Pool Efficiency99.07 %
Current Active Workers339
Next Network Block11303    (Current: 11302)
Last Block Found11302
Est. Avg. Time per Round (Network)1 minute 5 seconds
Est. Avg. Time per Round (Pool)4 minutes 41 seconds
Est. Shares this Round32,932 (done: 9,441.60 %)
Time Since Last Block5 hours 31 minutes 47 seconds

again block was found by bitember but we are still finding block 11302.

This pool could be the issue if it's not updating...

the last time i checked it was cloudminers

https://bitcointalk.org/index.php?topic=509499.msg5725019#msg5725019

so it's not bitember only..

[marcje]

Code:

Pool Hash Rate	171267.000 KH/s
Pool Efficiency	99.80%
Current Active Workers	141
Current Difficulty	12.70692062
Est. Next Difficulty	12.70692062 (Change in 1 Blocks)
Est. Avg. Time per Round (Network)	2 minutes
Est. Avg. Time per Round (Pool)	5 minutes 19 seconds
Est. Shares this Round	52048 (done: 320.69%)
Next Network Block	11352    (Current: 11351)
Last Block Found	11351
Time Since Last Block	17 minutes 5 seconds

Crunch harder has it stuck

[bullus]

Is it already found or not (block 11351)?

http://explorer.fluttercoin.us/block_crawler.php?block_hash=0000000004cc8a5ab852fb32deebaa08a59e194b0afc2f67987878cf42766b78

Code:

Block Height: 11351

Block Time: March 17, 2014, 07:18:33

Block Version

6

Block Size

6258

# of Confirmations

1

Block Bits

1c14256d

Block Nonce

1969310720

Block Difficulty

12.70692062

http://explorer.litecoin.net/block/0000000004cc8a5ab852fb32deebaa08a59e194b0afc2f67987878cf42766b78

[seattletu]

its like its found but the coin server won't update/kick out a new block. faaaaaaack

[bullus]

I think it's related to net hashrate vs total poolshashrate. They are not the same and so it's not register al the hashrates(found blocks)?

[seattletu]

i think there's no way we average about 720 blocks for the next 24 hours

[freecoin22]

wow ,beautifull logo,i like it.

[ozie]

What about the nethashrate vs total poolshashrate?

At stuck block 11302 it says 2092mH/s but the total poolshashrate is now about 926mH/s.
Shouldn't the nethashrate also be adjusted or is it fixed when started a new block?
http://explorer.fluttercoin.us/block_crawler.php

Still don't understand why the nethashrate isn't the same as the total poolshashrate.
If a pool can be offline and the nethashrate isn't drops than that pool isn't registered to the nethashrate?

http://explorer.litecoin.net/block/11302

http://explorer.litecoin.net/block/00000000019c7d2d21bcbe9d7ff2d9d5715c734229e13dc613b15ab63644a3b5

Pool Hash Rate491.136 MH/s
Pool Efficiency99.07 %
Current Active Workers339
Next Network Block11303    (Current: 11302)
Last Block Found11302
Est. Avg. Time per Round (Network)1 minute 5 seconds
Est. Avg. Time per Round (Pool)4 minutes 41 seconds
Est. Shares this Round32,932 (done: 9,441.60 %)
Time Since Last Block5 hours 31 minutes 47 seconds

again block was found by bitember but we are still finding block 11302.

This pool could be the issue if it's not updating...

It's per new block - it's a calculation

Does the difficulty retargeting depends on the Nethash value calculated by the Wallet?
If so at least the dropping diff after a Blockchainstale would make sense!

The diff would be always calculated by the hashrate working on the Pool that finds the next Block.
This is the only hashrate a Wallet would always calculate correct since its local.
Both big Pools have about 600 - 1000 mh/s which would be roughly a diff of 20-25. Makes sense imho.

Sadly this still doesn't explain why these stales are happening.

[bullus]

Pool miningwithus..let's see if we get a stuck block(its still early to say)

Pool Hash Rate138.674 MH/s
Pool Efficiency97.95 %
Current Active Workers99
Next Network Block11436    (Current: 11435)
Last Block Found11435
Current Difficulty16.25019372
Est. Next Difficulty15.47637497
Est. Avg. Time per Round (Network)1 minute 2 seconds
Est. Avg. Time per Round (Pool)8 minutes 23 seconds
Est. Shares this Round33,280 (done: 27.81 %)
Time Since Last Block2 minutes 47 seconds

edit
nope not stuck

[ozie]

its like its found but the coin server won't update/kick out a new block. faaaaaaack

There is no central coinserver is a decentralized envoirment.

A Wallet gets a solution from a miner and Broadcasts this possible new Block to all other Peers it knows. If other peers then agree on this new solution being valid it get integrated as the next Block in the Chain.

If you would be able to Block all Communication on the p2p Port of the Wallets of both big Pools simultaneously then the Blockchain might Stale as we see it.

But this could hardy be done without the Pool Operators noticing it. Given that they read their logs    

[seattletu]

Pool miningwithus..let's see if we get a stuck block(its still early to say)

Pool Hash Rate138.674 MH/s
Pool Efficiency97.95 %
Current Active Workers99
Next Network Block11436    (Current: 11435)
Last Block Found11435
Current Difficulty16.25019372
Est. Next Difficulty15.47637497
Est. Avg. Time per Round (Network)1 minute 2 seconds
Est. Avg. Time per Round (Pool)8 minutes 23 seconds
Est. Shares this Round33,280 (done: 27.81 %)
Time Since Last Block2 minutes 47 seconds

its been going just fine on there for a while now. finding blocks, nothing is stuck since block 11356 with 2300% and the time before that was block 11304 with 7299%

[seattletu]

we are definitely getting a lot of blocks, just like the dev said we would. even if we hit the daily 720 blocks like it's designed to do, it's still problematic to mine it when it goes into a block that takes forever to solve. people could switch over and mine another coin during the sometimes 6+ hours it takes to find that block, then jump back to fluttercoin once it gets solved. it punishes the miners who stick to fluttercoin.

it seems like slowly we are pinning the problem down. it's reassuring so many of you guys understand how the coin protocols work. it would be even more amazing to find some other competent dev's to take a peek and chime in their 2 cents. fluttercoin has all the right ingredients for success, i think we can all sense that.

[moonpool]

flutter.miningwith.us
0% Fee for life.
Finding blocks at a steady rate, come mine with us today!

[Fx911es]

Hello. I just started to mine this coin.. What's the IRC for this coin? and why does the bitember pool have 90% of the total coin's hashrate?

[B737]

WTF! Bitember is stealing coins?!?!

[seattletu]

what? i seriously doubt they are stealing coins. why do you say that? you know they do have a fee for using their pool, right?

[Fx911es]

Everything was orphaned? I am new here, Is it okay for me to mine this coin now or should i just come back again after a little while?