FLY COIN ANN.Swapping to "Las Vegas"coin,+Masternodes,Darksend,Stealth, instantX

[vegasguy]

Ill double check the pos rate again. I do agree, the math is way off. Ok im on it. Give us time to put a fix out. I may even consider a slightly higher POS% rate.



UPDATE: Ok.. We have looked at the code and there is certainly a major under calculation. It should be 10%, and is actually about .8%. So not even 1%. But we are fixing now. Thanks

Vegas

[1714825683]

1714825683

[vegasguy]

Flycoin wallet 2.4.2 (Mandatory update!!).

www.bitcoinlasvegas.net/files/FlyCoin_qt.exe

POS fix at block 90150 (VERY SOON!!!!)

Update NOW!!!!!!!!!!!!

*Only change/fix is fixes the POS to pay 10%.

Vegas

[indika]

im new to criptocurrency i have little question if i opend my fly wallet and stay online with network is there a any benefit for me.

[vegasguy]

im new to criptocurrency i have little question if i opend my fly wallet and stay online with network is there a any benefit for me.

Yes, to get the most benefits, you must have your wallet online and unlocked 24/7. Your first stake rewards wont start until 7 days.

Vegas

[cdajdk]

Doesn't want to compile on linux.    src/main.cpp line 1305.   Doesn't like mix between floating point (double) and CBigNum which looks to be integer based.  Could static_cast to a long long but not sure if you will lose precision doing that.

possible solution:

CBigNum bnSubsidy = CBigNum(static_cast<long long>( nCoingAge * (posRate_13 / maxTimesPerYear_13)));

Also,  could change the definitions of  postRate_13 and maxTimesPerYear_13  to be "const".    Lots of warnings and side effects of current definitions.

-JK

[BTC-BTC-BTC]

Flycoin wallet 2.4.2 (Mandatory update!!).

www.bitcoinlasvegas.net/files/FlyCoin_qt.exe

POS fix at block 90150 (VERY SOON!!!!)

Update NOW!!!!!!!!!!!!

*Only change/fix is fixes the POS to pay 10%.

Vegas

Updated to 2.4.2 and it has been running very smooth so far.

Thanks,

[HiggsBosunBlues]

Doesn't want to compile on linux.    src/main.cpp line 1305.   Doesn't like mix between floating point (double) and CBigNum which looks to be integer based.  Could static_cast to a long long but not sure if you will lose precision doing that.

possible solution:

CBigNum bnSubsidy = CBigNum(static_cast<long long>( nCoingAge * (posRate_13 / maxTimesPerYear_13)));

Also,  could change the definitions of  postRate_13 and maxTimesPerYear_13  to be "const".    Lots of warnings and side effects of current definitions.

-JK

Thanks for this, I've hit the same problem.

I'll try your suggestion. Cheers.

[cryptotech]

Doesn't want to compile on linux.    src/main.cpp line 1305.   Doesn't like mix between floating point (double) and CBigNum which looks to be integer based.  Could static_cast to a long long but not sure if you will lose precision doing that.

possible solution:

CBigNum bnSubsidy = CBigNum(static_cast<long long>( nCoingAge * (posRate_13 / maxTimesPerYear_13)));

Also,  could change the definitions of  postRate_13 and maxTimesPerYear_13  to be "const".    Lots of warnings and side effects of current definitions.

-JK

Thanks for this, I've hit the same problem.

I'll try your suggestion. Cheers.

I am trying to build daemon and running into compile errors as well.  vegasguy could you please update source.  Thanks

[presstab]

Yeah i see it too. Its actually a big no no to use doubles in the protocol level math. There is a reason why the code was designed that way, different compilers and systems can treat doubles differently (or so I have read) and this could lead to two different systems disagreeing over the math and forking. Its always better to use an int that is multiplied by 100 and then divide it by 100 at the end.

Will stand by for solution.

[vegasguy]

Ok I hate putting you guys through such quick updates    Ok.. Please give me some time.

Vegas

[Woody20285]

My understanding is the push of the code to
the git has been done. If anyone is having a
problem compiling now, let Vegas know right away.

[midnight_miner]

...

 There is a reason why the code was designed that way, different compilers and systems can treat doubles differently (or so I have read) and this could lead to two different systems disagreeing over the math and forking. Its always better to use an int that is multiplied by 100 and then divide it by 100 at the end.

Will stand by for solution.

I agree. Especially with:

Its always better to use an int that is multiplied by 100 and then divide it by 100 at the end.

Experience has taught me that whole numbers, float, real, etc. cause different results on different platforms.  That is why you only see integer math in finance and industrial process control calculations in 'qualified' code.
 

[Griffith]

Yeah i see it too. Its actually a big no no to use doubles in the protocol level math. There is a reason why the code was designed that way, different compilers and systems can treat doubles differently (or so I have read) and this could lead to two different systems disagreeing over the math and forking. Its always better to use an int that is multiplied by 100 and then divide it by 100 at the end.

Will stand by for solution.

deleted my last comment. will just retype new stance now.

my point about truncating a double back to an int will always result in the same number is correct.
however, presstab is also correct that two systems can disagree over the math. It is the original int that causes the trouble. The conversion from int to double may result in the compiler rounding the int to another value if it thinks it is needed before converting it into a double. The closer you are to zero the less likely this int rounding is going to occur (that rule doesnt apply to values between 0 and 1 or between -1 and 0).

i did not know that the compiler would ever round the int off.

i found the answer here: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2014/n4296.pdf

will adjust code accordingly.


thanks for pointing this out. i need to go change something else i coded recently now too XD


NOTE: always feel free to make a commit and request a merge if you see something that should be changed

[vegasguy]

Ok here is the new Windows Binary with Griffiths correction. Sorry for the trouble everyone.

V2.4.3.0

www.bitcoinlasvegas.net/files/FlyCoin_qt.exe

[Limx Dev]

Ok here is the new Windows Binary with Griffiths correction. Sorry for the trouble everyone.

V2.4.3.0

www.bitcoinlasvegas.net/files/FlyCoin_qt.exe

I think i have lose my coinage with a wrong staking calcultion or?



~ 120 days with 2000 Fly = ~ 233 Fly (35%) 

[vegasguy]

Chris, it changed to 10% POS and the superblock frequency is MUCH higher. I need to edit the OP to reflect the POS% change. Even though its 10%, the superblocks will make the rewards MUCH higher.

Vegas

[Limx Dev]

Chris, it changed to 10% POS and the superblock frequency is MUCH higher. I need to edit the OP to reflect the POS% change. Even though its 10%, the superblocks will make the rewards MUCH higher.

Vegas

Okay thank you but 10 % is than 66,5 Fly. I have received 5 Fly with superblocks.

[vegasguy]

The superblocks makes the % MUCH more than 10%. My superblocks have been non stop. The superblocks just started in the last 2 days, please give more time.

When Presstab updates to 2.4.3.0 on his explorer, it will actually show the superblocks and average POS rate. It will be MUCH higher than 10%.

Vegas

[cryptotech]

Flycoin Wallet Updated

You must first register to use faucets.  More faucets will be added soon.  If you would like your coin to have a faucet on TheCryptoChat contact us.

	FlyCoin
	Up to 0.03 FLY every 30 minutes

Visit Site Now

[crazyivan]

Both Avast and my antikeylogger recognize this new version as a threat and immediately delete it.

Also, do we have a functional exchange or not?