Author

Topic: [ANN] FlutterCoin FLT Proof Of Transaction Cash Back for Sending & Recieving - page 281. (Read 368097 times)

legendary
Activity: 1848
Merit: 1009
Next-Gen Trade Racing Metaverse
But it's frustrating if you leased a rig  Embarrassed
sr. member
Activity: 336
Merit: 250
the fact that the blocks get stuck means everyone gets less coins...so i guess in theory the price should go up. i mean, it won't, since it appears there's an overall problem with the network. BUT, if this difficulty re-adjustment issue gets squared away, the price should go up really quickly.
sr. member
Activity: 336
Merit: 250
but really if what you're saying is correct and it truly is a difficulty re-adjustment issue, then those numbers don't really mean anything and hopefully it can be tweaked to prevent everyone from being stuck.

what's strange though, is why each pool gets stuck and unstuck at the same time. so if the difficulty is way too high, and 1 pool finally finds their block, why is it that the other pools are able to find their block and move on? when one pool finds a block, submits it, and it brings the difficulty back down, does that affect the difficulty of the other pools that are still in the middle of mining their blocks?

it kind of seems like that's what it does, but i don't know if that's actually how it works.
sr. member
Activity: 378
Merit: 250

No the POB/POT calculations have no factor in the difficulty, etc.  Fact is there has been only 1 stuck block that was, or had a POB block adjacent (couldn't find any 10 blocks in each direction).

POB/POT looks for matches on all blocks except POS blocks (none happening yet) - if one is found, he reward is sent to 2 addresses.

If we didn't get stalled during fast mining in the beginning, it wouldn't happen now. 

There is nothing stalling the block - its just that a solution is not being found.  Its 100% difficulty adjustment related.  If I changed NVC to the present values for block time, difficulty windows etc, it would see the same issue IMHO.  See my post above.

I agree though we need P2P.


Again, not a programmer here, but what leads you to believe 100% this is diff related? The one post from earlier had something like a 0.8 change in diff when the block got stuck. There was no big change from the previous coin.

Are you still thinking that it's because people are dropping off mid block? b/c again if most people are like me, i've let it go to 1000% before giving up. it's not just switching as soon as it goes over 100%.

sr. member
Activity: 336
Merit: 250
it's not just 20 or 30 minutes and people are dropping off...it's when you hit 1500% and it's been going for 2 hours is when people drop off. we had a block at miningwith.us that went to 3300% and few at 1600%.

block 11230   1215%  2hrs 15 mins
block 11092   1546%  1 hr 34 mins
block 10872   1673%  3 hrs 9 mins
block 10439   2082%  5 hrs 55 mins
block 10415   3334%  1hr 48 mins
sr. member
Activity: 308
Merit: 250
FlutterCoin Developer
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?



No the POB/POT calculations have no factor in the difficulty, etc.  Fact is there has been only 1 stuck block that was, or had a POB block adjacent (couldn't find any 10 blocks in each direction).

POB/POT looks for matches on all blocks except POS blocks (none happening yet) - if one is found, he reward is sent to 2 addresses.

If we didn't get stalled during fast mining in the beginning, it wouldn't happen now. 

There is nothing stalling the block - its just that a solution is not being found.  Its 100% difficulty adjustment related.  If I changed NVC to the present values for block time, difficulty windows etc, it would see the same issue IMHO.  See my post above.

I agree though we need P2P.
sr. member
Activity: 378
Merit: 250
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?

sr. member
Activity: 308
Merit: 250
FlutterCoin Developer
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.  





full member
Activity: 126
Merit: 100

flutter.miningwith.us

0% Fee for life.
Finding blocks at a steady rate, come mine with us today!
sr. member
Activity: 336
Merit: 250
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
sr. member
Activity: 336
Merit: 250
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.
sr. member
Activity: 378
Merit: 250
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.

sr. member
Activity: 336
Merit: 250
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.
full member
Activity: 378
Merit: 101
Estimated.Pro - Crypto Signals. Free.
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

sr. member
Activity: 308
Merit: 250
FlutterCoin Developer
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...
member
Activity: 118
Merit: 10
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.
full member
Activity: 378
Merit: 101
Estimated.Pro - Crypto Signals. Free.
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
full member
Activity: 378
Merit: 101
Estimated.Pro - Crypto Signals. Free.
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.


legendary
Activity: 3108
Merit: 1029
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.
sr. member
Activity: 294
Merit: 250
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.
Jump to: