[ANN][FIND] FindCoin | Update Wallet If You Haven't! | Community Anti-Scam Token

[uki]

I had FindCoin in my wallet , i start staking but i didn't Findcoin every hour.

hold on, you are confusing two things: one was distribution phase, that was indeed each hour and that is OVER since many days, and other thing is staking (PoS phase) that is taking place now. PoS works as follows: you must have some coins already in the wallet and once they achieve maturity (after several hours - check OP for details) they are ready for staking (you must unlock the wallet for that). That doesn't mean you immediately receive the coins - you will be competing with others and only if your priority is higher you will get the coins. Priority is dependent on the number of coins and their age.

[1714688863]

1714688863

[1714688863]

1714688863

[1714688863]

1714688863

[anotherlateminer]

Guys, I think you need to re-check the annual PoS interest. Today I received just 0.9FIND for 27280FIND block. And this is for a period of 8 days.

Yep, it seems to be much lower than 25%.

[Quadmium]

Guys, I think you need to re-check the annual PoS interest. Today I received just 0.9FIND for 27280FIND block. And this is for a period of 8 days.

Yep, it seems to be much lower than 25%.

Hmm... I agree, it seems the POS reward code could have a bug. I'll look into it more and see if we need a fork.

Edit: Can you guys confirm if your POS earned per day is less than expected? Here is the code I believe is causing the problem:

Code:

int64_t nSubsidy = nCoinAge * nRewardCoinYear / 365 / COIN;

Should really be:

Code:

int64_t nSubsidy = nCoinAge * nRewardCoinYear / 365;

[uki]

Hmm... I agree, it seems the POS reward code could have a bug. I'll look into it more and see if we need a fork.

Edit: Can you guys confirm if your POS earned per day is less than expected? Here is the code I believe is causing the problem:

Code:

int64_t nSubsidy = nCoinAge * nRewardCoinYear / 365 / COIN;

Should really be:

Code:

int64_t nSubsidy = nCoinAge * nRewardCoinYear / 365;

if the nCoinAge is expressed in days, then the second formula is fine. Otherwise we will have problems as interest rate is scaled to days.
the first formula may be thus correct, if COIN is the scaling factor. Double check that.

[Kepasa]

We need to find Denkoma. He is Megamind. Satoshi Nakomoto 2.

[Inotanewbie]

We need to find Denkoma. He is Megamind. Satoshi Nakomoto 2.

Wow what a load of donkey poo, he is far from megamind, satoshi. he could not build a linux wallet he is not terrible by all means but stop trolling.

EDIT: Good riddance to someone that leaves a community and coin.

[Quadmium]

Hmm... I agree, it seems the POS reward code could have a bug. I'll look into it more and see if we need a fork.

Edit: Can you guys confirm if your POS earned per day is less than expected? Here is the code I believe is causing the problem:

Code:

int64_t nSubsidy = nCoinAge * nRewardCoinYear / 365 / COIN;

Should really be:

Code:

int64_t nSubsidy = nCoinAge * nRewardCoinYear / 365;

if the nCoinAge is expressed in days, then the second formula is fine. Otherwise we will have problems as interest rate is scaled to days.
the first formula may be thus correct, if COIN is the scaling factor. Double check that.

It seems FIND has nCoinAge calculated as follows:

Code:

CBigNum bnCoinDay = bnCentSecond * CENT / (24 * 60 * 60);
    if (fDebug && GetBoolArg("-printcoinage"))
        printf("coin age bnCoinDay=%s\n", bnCoinDay.ToString().c_str());
    nCoinAge = bnCoinDay.getuint64();

While the second example (HyperStake) has it like this:

Code:

CBigNum bnCoinDay = bnCentSecond * CENT / COIN / (24 * 60 * 60);
    if (fDebug && GetBoolArg("-printcoinage"))
        printf("coin age bnCoinDay=%s\n", bnCoinDay.ToString().c_str());
    nCoinAge = bnCoinDay.getuint64();

So at the moment I'm not sure where the mistake could be as they both divide by COIN, but FIND does it later in the calculation.

[uki]

Hmm... I agree, it seems the POS reward code could have a bug. I'll look into it more and see if we need a fork.

Edit: Can you guys confirm if your POS earned per day is less than expected? Here is the code I believe is causing the problem:

Code:

int64_t nSubsidy = nCoinAge * nRewardCoinYear / 365 / COIN;

Should really be:

Code:

int64_t nSubsidy = nCoinAge * nRewardCoinYear / 365;

if the nCoinAge is expressed in days, then the second formula is fine. Otherwise we will have problems as interest rate is scaled to days.
the first formula may be thus correct, if COIN is the scaling factor. Double check that.

It seems FIND has nCoinAge calculated as follows:

Code:

CBigNum bnCoinDay = bnCentSecond * CENT / (24 * 60 * 60);
    if (fDebug && GetBoolArg("-printcoinage"))
        printf("coin age bnCoinDay=%s\n", bnCoinDay.ToString().c_str());
    nCoinAge = bnCoinDay.getuint64();

While the second example (HyperStake) has it like this:

Code:

CBigNum bnCoinDay = bnCentSecond * CENT / COIN / (24 * 60 * 60);
    if (fDebug && GetBoolArg("-printcoinage"))
        printf("coin age bnCoinDay=%s\n", bnCoinDay.ToString().c_str());
    nCoinAge = bnCoinDay.getuint64();

So at the moment I'm not sure where the mistake could be as they both divide by COIN, but FIND does it later in the calculation.

ok, let's see if I can help with this one.
Both formulas lead to the same solution, the difference however is the order of operations.
in the first version you have division by COIN after converting to int, in the second before.
That may have importance.

[Quadmium]

-snip-

ok, let's see if I can help with this one.
Both formulas lead to the same solution, the difference however is the order of operations.
in the first version you have division by COIN after converting to int, in the second before.
That may have importance.

Yea I guess, its the only thing I can see affecting the calculation. I'll go ahead and run some tests and check if there is actually a difference.

[fantoos]

I was away little so dont have any idea how the things are moving in Find. I will keep regularly visiting the thread to keep the thread more active.

[Kartaba]

slow progress is better than no progress 

[okae]

slow progress is better than no progress 

jaja +1, i hope there is more movement with this coin in next days...

[uki]

-snip-

ok, let's see if I can help with this one.
Both formulas lead to the same solution, the difference however is the order of operations.
in the first version you have division by COIN after converting to int, in the second before.
That may have importance.

Yea I guess, its the only thing I can see affecting the calculation. I'll go ahead and run some tests and check if there is actually a difference.

Did you manage to check that? Please, let me know what the outcome was.

[HarryPotHead]

slow progress is better than no progress 

This is a wise man ^^^ After the Denkoma left we are lucky that we are making progress, hope he is ok though he seemed to be into this project 

Alot of us need to help this in anyway we can once we get moving again it is a community coin after all

[mirador17]

You're trying a dead cat bouncing before the definitely end of find coin. 

[uki]

You're trying a dead cat bouncing before the definitely end of find coin. 

Sorry, can you correct English in your post? Otherwise it is hard to understand what you mean.

[mirador17]

You're trying a dead cat bouncing before the definitely end of find coin. 

Sorry, can you correct English in your post? Otherwise it is hard to understand what you mean.

I'm meaning this: http://en.wikipedia.org/wiki/Dead_cat_bounce

[jtalk]

slow progress is better than no progress 

Things always should be in move it doesn't matter upward or downward as moving is sing of life. I am happy development is undergoing and sooner will seen some change.

[Inotanewbie]

You're trying a dead cat bouncing before the definitely end of find coin. 

End of Findcoin? Not while there is a community my friend. End of you're btc you invested in crypto alliance on the other hand is a sure thing 

[Quadmium]

-snip-

ok, let's see if I can help with this one.
Both formulas lead to the same solution, the difference however is the order of operations.
in the first version you have division by COIN after converting to int, in the second before.
That may have importance.

Yea I guess, its the only thing I can see affecting the calculation. I'll go ahead and run some tests and check if there is actually a difference.

Did you manage to check that? Please, let me know what the outcome was.

Sorry for the late response, I am very busy during the week. However, in ~2 days I will have a lot of time to test and can look into this properly - I'll be sure to report once I check it out.