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

[bullus]

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.

[makishart]

unstaaaaaaaaaaaaaaaaaaaaaaaaaaaaaack!!!

we need p2pool now!!!!

[homeiss]

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

When will people learn, you don't put an exchange address as your payout address from a pool?

[seattletu]

if you do solo mining, will you have the same stuck block issues as the pools?

[homeiss]

unstaaaaaaaaaaaaaaaaaaaaaaaaaaaaaack!!!

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.

[bullus]

unstaaaaaaaaaaaaaaaaaaaaaaaaaaaaaack!!!

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.

Al the pools are getting stuck..

[bullus]

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

maybe it was orphaned blocks..got also 1500unconfirmed and suddenly only 1000unconfirmed. I looked at the blocks and it were orphaned.

[makishart]

if you do solo mining, will you have the same stuck block issues as the pools?

yes it just stucks the network.. no block is generated.

[jootn2kx]

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

When will people learn, you don't put an exchange address as your payout address from a pool?

when will you learn to read? I said here above I had never had any issues with transact from pool directly to exchange. I am 7 months into crypto and mined alot of different coins  and did alot of transactions.

Doing transactions directly from pool to an exchange shouldnt be any problem at all.

[jootn2kx]

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

maybe it was orphaned blocks..got also 1500unconfirmed and suddenly only 1000unconfirmed. I looked at the blocks and it were orphaned.

another one that cant read, I said on BTER exchange not on the pool

[homeiss]

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

When will people learn, you don't put an exchange address as your payout address from a pool?

when will you learn to read? I said here above I had never had any issues with transact from pool directly to exchange. I am 7 months into crypto and mined alot of different coins  and did alot of transactions.

Doing transactions directly from pool to an exchange shouldnt be any problem at all.

I don't care how many times you've done it, it's a bad practice and now you're seeing why.

[thekidcoin]

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

There was no fork...

[jootn2kx]

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

When will people learn, you don't put an exchange address as your payout address from a pool?

when will you learn to read? I said here above I had never had any issues with transact from pool directly to exchange. I am 7 months into crypto and mined alot of different coins  and did alot of transactions.

Doing transactions directly from pool to an exchange shouldnt be any problem at all.

I don't care how many times you've done it, it's a bad practice and now you're seeing why.

First of all the problems that only MIGHT occur is a SLOWER transaction, not a lost one.
All other transactions today from the coin came fine on bter, exept the one I did when the block was stuck.
Plz don't pretend your knowing stuff bcause you know shit

[seattletu]

so kidcoin, this hard fork you want to implement in a few days, what are you going to be changing? and do you think it will fix this stuck block issue? i know you think it's a non issue, but it sure seems like a problem to us, so we are losing confidence in mining the coin. sorry just the way it is.

[organizer]

There needs to be acknowledgement of an issue, perhaps call in some other coin devs to help and outline a plan to fix. We all want this to succeed, but we can't keep trying to blame hashrate and pools for this. This does not happen to most coins. 51% is really a fork issue, not a stall all pools on same block issue.

Again, it's either something in the POS or POB code probably gumming up the works somehow.

[seattletu]

Its very clear what it is, blocks don't just magically get stuck LOL, they are just too difficult to find when the hashrate drops 50% + what the calculated difficulty was (which is exactly what these exploits can do).

For example say hashrate is supposedly 2 gH, and a block is calculated to be 50 difficulty, then suddely the hash drops to 1 gH, what happens it is VERY difficulty to mine the block at 1gH

As i've been watching this, primarily on bitember and cloudminers... the hashrate isn't dropping right as the diff nudges up, people are sticking with it for 100's of percents above the target. When it gets to >500-1000% is when i'm seeing miners drop, not right on the switch.

I think the point of Bullus' posting of the blocks was that the difficulty inches up, the amount of shares needed climbs up as expected... but on block 10,870 it takes millions of shares vs. 10s of thousands... the difficulty change was .8ish.

So people aren't seeing a .8 diff change and immediately changing their miners causing what you are seeing in the hash drop. I think you're looking at only the raw numbers in the hash rate without realizing that people are leaving the pools AFTER it gets stuck, not at such a minute diff change.

I'm used to being on pools and getting the occassional 200-500% block.... but what i'm also used to seeing is the block number increasing as other pools (that i might not be mining on) are finding it. Here all pools get stuck on the same block until for whatever magic reason it unsticks.

i agree with this. the difficulty drops after a long stuck block because so many people drop out during the long stuck blocks.

[seattletu]

There needs to be acknowledgement of an issue, perhaps call in some other coin devs to help and outline a plan to fix. We all want this to succeed, but we can't keep trying to blame hashrate and pools for this. This does not happen to most coins. 51% is really a fork issue, not a stall all pools on same block issue.

Again, it's either something in the POS or POB code probably gumming up the works somehow.

i agree with this too. kidcoin you seem like a smart, competent guy and we want to help this coin succeed, but you have to acknowledge there is some kind of problem, even if the problem is only our perception that the coin isn't functioning correctly. There IS a problem at some point, or we wouldn't be having this discussion.

i totally agree with bringing other dev's in to look at it. we could even offer some dev's a flutter bounty to help incentivize them to get it functioning 100%. did i just invent the word incentivize? heh

[moonpool]

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

[thekidcoin]

Looking into some stuff to hopefully fix any issues.

Let me first say that nothing is broken - not much in the difficulty re-targeting is different from NVC or PPC.  Those coins however get a pretty stead hashrate.  Not everyone obviously is mining these listed pools.  Hashrate in the wallets isn't really accurate etc (its just a calculation).

Unless someone can show me a log from a pool showing that there are rejected blocks - this is the route I am going down.

What needs to be changed it the difficulty.  It seems its adjusting too high, then it takes a long time to find a block because it was likely too high even for the current hashrate, then it takes forever, then the cycle continues.

Heres what I need form anyone thats has been following this:

What blocks did this occur at?
What was the value of the next block? (the few that I know about were below 5K - could be guessing the value and dropping off if its not high enough)

Anything over say 20 minutes is too much.  I think I am starting to see a pattern... Here are the facts:

• This coin adjusts difficulty every block
• This coin's adjustment max difficulty adjustment of 200%
• This coin's adjustment window is 4 hours
• Block time is between 2 minutes and ? (trying to nail this down - debugging this part - 2 minutes isn't cut and dry with any PPC clone I now believe)

There are a few other things as well I am looking into adjusting.

In the meantime don't mine it if your going to drop off if a block hasn't been found in 20 or 30 minutes.  Please.  At least until I can make sense of this all.  When you do this it just makes the finding time even longer.  

[organizer]

Just throwing this out....aside from the forking issues early in the coin (which may or may not be related, just a sign of a new, small coin IMO)....

This issue gets severe at X amount of hashing power.... since these are almost all pool-based (I dont think there's p2p yet)... could this be an issue with the POB stuff and just getting "overloaded" (i'm no programmer)...

What i mean is, does the POB stuff happen on every transaction? So a block is mined....transaction to pool... then this block is split up between all miners (400+)... are each of those transactions that just might be crippling things? Like some sort of exponential shit happenning?