Park Rate Voting

mhps 2016-04-19 18:17:08 UTC #377

If when the next block comes the oldest existing block in the window has a rate more than current rate (50% chance), then the sorted distribution will have one member less on the greater side of the median point. The median point of the distribution will be taken by the member on the smaller side of the previous median point member, which has an equal or smaller rate. If the oldest existing block in the window has a rate less than current rate, then nothing changes.

Nagalim 2016-04-19 18:28:51 UTC #378

Right. This is the case currently and will be so for another half week or so.

mhps 2016-04-19 18:55:15 UTC #379

OK I see. Park rate is really for the slow components (low frequency in Fourier space) of peg balancing. Don’t expect it to come or go quickly.

Realising this, it’s wrong to mandate that T4 reserve is used before park rate. T4 and park rates should always be used together as they cover different part in frequency space. The optimum park rate could be crafted from MA5 of e.g. buy/sell ratio. As the rate constantly changes, a bot can be used to update the park rate feed. This could save a lot of T4 reserve.

mhps 2016-04-19 19:00:08 UTC #380

@desrever and @willy,

It’s important to record how many NBT are parked as a functiion of park rates, so future models can be made to set the optimum park rates. Now the rates are non-zero. Can you configure your server and record them?

Nagalim 2016-04-19 19:08:10 UTC #381

I feel like that’s higher frequency than the standard. I really can’t think of a lower frequency smart trigger than the standard.

masterOfDisaster 2016-04-19 19:09:40 UTC #382

Right!

But for that you need a way to replenish T4 - which would be T6 in this case.
That’s why I prefer NSR sale to park rates.

mhps 2016-04-19 19:25:56 UTC #383

Probably right, except for two problems: the Standard is currently only measured once a week while MA5 is an integral. The Standard is absolute number instead of a ratio. Both problem can be solved.

Edit: I forgot the important and unsolvable part with the Standard: it is the spot ratio, not reflecting the low frequency component. MA5(Standard/circulating) might do.

Excellent. To which I replied

Nagalim 2016-04-20 00:44:21 UTC #384

My issue with this is that park rates already account for the circulating dependency. Meaning that we don’t really get x nbt parked given a certain rate, we get x% of circulating nbt parked. As the network grows, number of parked nubits per park % will grow.

mhps 2016-04-20 00:56:40 UTC #385

I agree. I imagine that the park rate will be continuously calculated based on MA5(Standard/circulating) where Standard and circulating calculations have had parked amount removed. As parked amount increases, Standard approaches 0.

Also if one is using the standard for the next week’s buyback, ideally one has to calculate the forward-looking standard, which takes into account of the to-be-freed-next-week parked amount.

Nagalim 2016-04-20 01:11:18 UTC #386

If you take standard/circulating you’re double counting the circulating. Lets imagine 2 circumstances, one where there are 1mil circulating nbt and one where there are 100k. Let’s say the standard is -$5k. So if we use your calculation the park trigger is 5% in one case and 0.5% in the other. Let’s pretend we use that as the park rate. Let’s also assume that for each park rate %, that % of the network nubits gets parked. So for both cases $5000 nbt gets parked.

Lol, i think i just convinced myself that you’re right and im wrong. Ill think about it some more.

mhps 2016-04-20 05:52:06 UTC #387

I don’t assume it’s a linear function. The function should ideally determined by testing/optimizing against past data. So it doesn’t matter if it is standard/circulating or just standard, it is f(standard, circulating, tolerance, many other parameters).
The question is : what is the goal of optimization? My rough guess is we optimize to minimize peg maintenance cost in a given period.

Nagalim 2016-04-20 12:41:40 UTC #388

I don’t believe the parking function is fundamentally repeatable because the structure of Nu, the blockchain, and the risk associated with Nu are all changing. Finding a function for this seems like an impossible task.

mhps 2016-04-20 14:18:07 UTC #389

There are methodologies. Parameterize and fit. Monte-Carlo simulation. It can make a pretty good MAster’s degree thesis. The problem is we don’t have a lot of data.

mhps 2016-04-21 01:02:42 UTC #390

The wall has been in more or less balanced state for almost two days. If the wall keeps balanced like now for another 15hr, I think shareholders can consider lowering voted park rates, knowing that it will take a few days to come down.

@willy, it’s likely that 5-day moving average gives important clue on how the park rates should be set. Could you add 5-day MA to https://alix.coinerella.com/charts/?select=48h_4h_15min_combined_ma_percent ? It doesn’t have to show by default to avoid cluttering.

willy 2016-04-21 04:29:56 UTC #391

Just to clarify. You want a five day moving average, not a five day window, right?

mhps 2016-04-21 05:05:46 UTC #392

Right, Five day moving average. See here and here

Since 5day MA changes slowly, you can sample the 4hr MA results every hour and average the latest 120 samples to get 5day MA ,so the cost of resource is small. There will be one new data point on the plot every hour.

mhps 2016-04-21 23:49:33 UTC #393

There are only 2000nbt parked but the wall is balanced. We need more parked nbt to help replenish the rreserve.
I suggest the park rate set to

32% @ 11 day
16% @ 23day
8% @ 1.5 mo
4% @ 3mo
0% @ 6mo

The above base-2 exponential distribution of park rates will give the same total premium to any none-zero period. It encourage choosing the shorter periods due to less opportunity cost. Shorter periods require frequent renewal which aligns with Nu’s need to adjust the total amount of parked NBT acccording to liquidity and Standard.

With the base-2 exponential distribution Nu has only one parameter to adjust re park rates: the total premium. This will make operation and analysis easier.

[NEW] Cryptog's Nu data feeds - BETA

masterOfDisaster's Nu datafeed - BETA

Nagalim 2016-04-22 00:01:46 UTC #394

This is in line with my analysis here:

cryptog 2016-04-22 01:29:31 UTC #395

that makes sense.

will modify my rates.

Cybnate 2016-04-22 07:00:40 UTC #396

This goes against my logic of the risks of parking and ensuring Nu gets the best deal.
With that setup, it would encourage people to park for very short amounts of time at a premium for Nu.
That is high maintenance for whoever wants to park and relative low returns. Not attractive. For Nu it means that the velocity of money parked is very high meaning that parked money is returned in shot periods. I believe that is not a good thing when we have low reserves. It encourages a yo-you effect which will cost more.

I will stick with:
3% for 23 days
6% for 1.5 months
12% for 3 months

I might add the 24% for 6 months when reserves continue to be low. This would provide an opportunity to set aside NuBits for longer, usually an attractive opportunity for investors spreading their risk profile.