Topic: [ANN][FLT] Fluttercoin Ƹ̵̡Ӝ̵̨̄Ʒ | Proof of Transaction 3.0 | Update v0.7.5.22 - page 38. (Read 151723 times)

Good to know.
Ofeefee : thanks for all your work on flt.

Friends, I want to thank ofeefee. He understood the situation and helped me to return the stolen coins mintpal, although almost a year has passed. This is the only developer of coins, which helped return stolen while on mintpal I have had many different coins.

ofeefee - many thanks!

------
Дpyзья, я xoчy пoблaгoдapить ofeefee. Oн paзoбpaлcя в cитyaции и пoмoг мнe вepнyть мoнeты yкpaдeнныe mintpal, xoтя yжe пpoшeл пoчти гoд.  Этo eдинcтвeнный paзpaбoтчик мoнeт, кoтopый пoмoг вepнyть yкpaдeннoe, xoтя нa mintpal y мeня былo мнoгo paзныx мoнeт.

ofeefee - oгpoмнoe cпacибo!

Over the next 30 days I am splitting up the old mintpal wallet into smaller address accounts of 1 million each, here was some I moved today.  I do not plan on posting every day that I am doing this, but if you wonder why #2 is shrinking this would be the reason...
5bf99209a5952540d49fc542ea674ace9910289f588fdec25f7432b588c401df

while reviewing code, and testing some things, I have identified that the current proof of stake is single threaded, and thus, when staking is enabled it only uses a single core, or single processor, single core.  While running in a VM environment I was able to monitor this.  I have the system assigned multiple vcpus and had one processor with 4 cores, or 4 single processors, or 2 processors 2 cores, and it always utilized a single core.  Tested XenServer, and HyperV.  Further research indicates that making this operate in parallel is the only option. 

Lightstake code from PressTab on HyperStake only uses 1-2% of the cpu occasionally and does not hog the processor so that is an option.  Their coin is different from ours.  I was able to match some to NovaCoin, and NovaCoin does have a new stake engine, which could be utilized.

Does anyone who stakes other coins notice that when staking it will utilize multiple cores?  if so please let me know, i would like to review options here. 

I am virtualizing all my systems currently, and the processor in my server is slower than my main system, but has a lot more cores, so I am seeing staking performance issues on the wallet.  If I use my main system, staking is quick and efficient, if I move it to an atom proc, or a celeron dual proc, or a old 2x quad xeon, the performance of the staking engine is obvious.  So my solution is to get faster procs so the cores are faster, or resolve this issue.  I plan to resolve.

much regard,
--o

Ok cool thanks for the info.

Nothing special to do, just make sure your wallet is unlock for staking when you have mature coins and it will stake eventually.

Another question folks after 30 day and i start staking do i have too do anything
with "block browser"? or it will just start staking on it own like all the other POS coins?

Wallet up and running with no problems thanks.

Ok i downloaded it now what i have to do with it? thanks for the help.

Edit: I think i have it working lets see.

Download my fix a page or so back, I don't have it up on github for download, unless you want to compile from source.

Is anyone else having this problem? i am synchronizing with the network and a few minutes later
the wallet just shuts down anyone knows what i should do? thanks.

Like adding a rpc call to set splithreshold?  Yes it won't split if it would create a block <1k

I would like to allow traders/investors make educated choices on what the coin is doing.  Right now trying to gauge things is extremely difficult, we have wide swings in inflation daily, its not something you can reliably estimate or plan.  Also makes planning for future like things we need to do and fix items that may be worthwhile we cannot determine.

I think if we can try to limit stake to no more than 1000 on blocks this will even this out some.  However I dont t really want to cap the subsidy, others do that, hyp, cap, hbn but it does work. For instance you cannot produce more than 1000 flt reward on a stake block.  This would mean if you can stake in 30 day maturity 50k works, if it takes 60 days you need to have 25k, and then have to adjust things further if diff changes and more.  

I really think that overly complicated things.  I would much rather say you don't need to optimize blocks or game it, just make them less than 20k or 10k, and you get full reward up to 90 days.

With that said, 50k @90 makes 3000flt, 25k 1500, 10k 600.  So I would like to limit this to a 1000 as much as possible.  50k@30 days might not be a bad block limit, and is much easier to manage and lets soomster keep kind of large blocks?

Soomster what are your thoughts.  Force smaller blocks or just truncate the reward at 1000?

Anyone else have some ideas they want to throw out in their experience of what works or doesn't in other coins.

Hi, ofeefee!
I support your idea: to penalize large block. But it will be great to increase splitthershold value (as I understand, current value is 2000) or enable manual setup of splitthershold value (like in Hobonickels or Bottlecaps). As for me ideal value is near 5000.

huge staking time is just part of the issue with staking coins in general unfortunately, the more blocks you have to stake the longer it takes.  Think if I reduce it to 10 days from 30.  That means that there is 3x as many blocks as there is now competing for stake.  So this will push blocks out further as well, I expect they still will take 60+ days if not more, just the way it is.  It does allow you to get returns faster, but we are a transaction type coin, so staking as good as it is, not primary goal of the coin, definitely a bonus!  Like i said earlier I think, Hyp has 8.8 days for maturity, but I have nice sized blocks that are 160+ days old...and it maxes rewards at 30 days if I recall, so lots of wasted stake going on there.

Orphans, yes you will have these.  just like in PoW mining that can create blocks from different miners, same can happen on PoS.  The block will stake again.  There is some code that you can run a checkwallet, and do a repair on these and it will remove them from the wallet so they don't take up space being recorded (it's on the TODO list).

The smaller blocks are useful when you want to spend too, so you don't affect the age of other blocks.  I will consider the staking time, that may be another fork necessary, that has lots of additional spots in the code where it can get complicated and will break things if you miss something.

cryptsy is not staking coins, if their address is tagged it may be something else, but I know they are not actively staking.

if age is over 90, it is possible it could stake, but that means that the max reward is 90days of coin age.

For instance if I had 100FLT, and interest was .02% for 30 day mature.  If the coin is aged 90 days, this will reward .06%, because it can pay out up to 90 days of maturity.  I have most of my blocks between 1-2k, and some have 60 days of age, but you don't have issues with the rewards never being seen until you are post 90.  But depends on the block size. I normally will grab anything

plz explain me if I open coin control an see some amount which age over 90 , that means I not can receive any rewards for stake this amount? but why near this amount show potential stake more than zero.
thanks

Actually that was for another holder that I know is doing this.  I used to do it too.

If coins are not participating and staking consistently the difficulty is low.  This can be used as an attack vector to take control of the chain easily.  Also the interest is based on the diff.  Low diff 100% interest, and lowers from there, for the last month or so we are at 25-30%.  Coin uses dynamic interest.

Free flutters are what this coin is about, however all the free flutters are built into the block values as part of the block total.  95% to miner, 5% to PoT.  And the free fluttershare is self funded through a staking wallet, or donation from the Team.

Fluttershare can be used as well but this is generated from part of your stake directly.

Important to know that these features do not produce additional coins but use the existing supply/creation mechanisms.  It is what makes fluttercoin unique out of all the coins in existence.

The staking system is indeed high, however we are not the only coin with the staking system, bottle caps, (200%) hobonickel (100%).  Hyperstake has a set interest rate of  750% and a limit on stake reward of 1000.

The good news in all of this is we haven't really changed anything, even the change I suggest is one to keep your blocks less than 10k if staking.  Other than this the mechanics are the same.  It allows someone who just wants to get started in flt to join in and use the same system that has been available.  I started with 200k flt.  And have added since.  And yes I am a stakeminer and do sell my stake above my set goal currently.

and to demo the PoTv3 changes, you can see as my blocks stake they share a little bit of FLT with others...If you have this in a 1 million block and you stake, I hope my address gets picked for PoT!  I get 5% of that reward.

https://chainz.cryptoid.info/flt/tx.dws?cda25821e4e95ac2cb4a30d1093e989d5680a1c93ce9bb2436c3adec48cefc12.htm

Yes you are exactly correct.  This puts the coin at risk. Yes, it's fun to be able to just start a 1+ million coin wallet and stake it a single day, then shut it down until next month, or do this once over the 90 day period (yes I know who you are, lol).  This is the entire reason I am looking at this.  Splitting the blocks to 500 blocks of 2000 means that it is much more likely that your client will participate in the network going forward.

The alternative to this, which I have not discussed is to reintroduce the original POS reward subsidy limit of 10 FLT, which was removed during the hardfork early on in FLT history with PoTv2 see kidcoins code below line 1056 of main.cpp.  I ran across this yesterday in the code, and am debating on just flipping the switch to enable this.  This means that it no longer really matters what size block you want to stake, it will only be able to produce a max of 10FLT going forward.  I don't' like this personally because it really limits the fluttershare, and PoTv3 staking changes, as you only have 10 to work with (see PoW PoT 5FLT transactions).  But I have to admit reducing the inflation to a maximum 10k/day does seem advantageous to us large holders.  But that's not really what this coin is about.

    if(nTime < FORK_FINAL)
    {
        if (fDebug && GetBoolArg("-printcreation") && nSubsidyLimit < nSubsidy)
            printf("GetProofOfStakeReward(): %s is greater than %s, coinstake reward will be truncated\n", FormatMoney(nSubsidy).c_str(), FormatMoney(nSubsidyLimit).c_str());

        nSubsidy = min(nSubsidy, nSubsidyLimit);
    }

this is not set in stone, but for one the inflation needs to be smoothed out, two we need more participation on the network, and limiting the coin creation spikes of 200k, 1.5 million, 600k, 495k etc. that pop up on the https://chainz.cryptoid.info/flt/#!overview which shows you the daily coin generation.

sounds like you have an older wallet that doesnt know how to handle PoTv3 type transactions.  When you stake or send coins, this is eligible for PoT if that is selected on a new block, paying you additional FLT for "using" the coin.

Generated but not accepted means that you created a block, but another block at the same time was selected instead of yours, these are what they call orphans.  Meaning your block was discarded by the network for a better one.  THe coins that generated this will generate another.