Park Rate Voting

[tomjoad]

I have increased my votes rates as well.

[cryptog]

@assistant park rates

[assistant]

Hi @cryptog

The current park rates in the Nu network are:

32768 blocks: 0.000810% APR
65536 blocks: 0.001670% APR
131072 blocks: 0.008722% APR

[cryptog]

Even if park rates have been raised to 1.3% for 10 and 20 days, 2.3% for 1.5m and 4.5% for 3m, it seems the totally parked quantity has not increased yet, over the last 24 days.
I feel shareholders should vote for higher short term rates in order to incentivize nubits holders to park immediately.

[GLock]

I think that park rates should reach at least a range of 8 - 10 % for the 3months period to start to see more parked NBT
We saw that happening not long ago.

[cryptog]

I see. I am voting in my feeds for 15% regarding all periods btw.

[sigmike]

Note that voting for much higher rates doesn’t make the rates increase faster. The reason is we use median and not average. So voting for your target rate is enough to make the rates grow at its maximum speed.

Also note that there’s a maximum increase of 1% per day on each duration. For example on 3 months the current rate is 4.5% but the current result of the vote is actually 8%. So if if everybody keeps his vote as is, the rate will be at least 8% in 4 days.

[cryptog]

but the current result of the vote is actually 8%

Any easy way to get this info?

[sigmike]

Not sure it’s easy, but you can use the (very verbose) getparkvotes RPC on the NBT wallet. It will display the details of the votes on each duration. The median rate is the first rate for which the accumulated age percentage is above 50.

[cryptog]

tks for the info. getparkvotes with no arguments crashes the client…any typical values to input for block height and block quantity?

[sigmike]

The default values are fine because they match the protocol rules.

I don’t know why it crashes. The function may need a significant amount of memory. Are you running the daemon on a low memory system?

[cryptog]

Are you running the daemon on a low memory system?

I do not think so. It crashes on 2 machines btw:

• 4gb machine 2 gb left when Nu client is on
• 8gb machine: 2 gb left when Nu client is on

[sigmike]

We’ll investigate the problem.

[woolly_sammoth]

Assistant hasn;t been correctly reporting the APR for park rates. The figures returned by the getparkrates rpc call are the raw rates. There is an extra calculation to convert to APR (thanks for the information @sigmike).
I’ve just made the changes to Assistant and tested locally. I’ve moved the code to the server where assistant lives and (hopefully) this next call should give the correct park rates.

@assistant park rates

[assistant]

Hi @woolly_sammoth

The current park rates in the Nu network are:

32768 blocks: 0.001433 (2.30% APR)
65536 blocks: 0.002916 (2.34% APR)
16384 blocks: 0.000405 (1.30% APR)
131072 blocks: 0.011214 (4.50% APR)

[crypto_coiner]

I think that park rates should reach at least a range of 8 - 10 % for the 3months period to start to see more parked NBT

I think I would be interested in parking at these rates too.

[GLock]

I do not think so. It crashes on 2 machines btw:- 4gb machine 2 gb left when Nu client is on- 8gb machine: 2 gb left when Nu client is on

I have the same problem, on linux, tested on 2 different computers

[cryptog]

totalparked has increased from 54186.1098 to 54307.1098,

[desrever]

totalparked has increased from 54186.1098 to 54307.1098,

Δ0 ?

[sigmike]

getparkvotes with no arguments crashes the client

I just made a pull request to solve the problem: https://bitbucket.org/JordanLeePeershares/nubit/pull-request/219/fix-getparkvotes/diff
So it will be fixed in the next release (1.1.0). In the meantime, here’s the current result of the command: https://gist.github.com/sigmike/ae129bf8c80625652245