Proposal #47
Runtime Upgrades and Capacity Model
Democracy
3 Comments
Tabled

This is a combination of three runtime upgrades that have already been enacted on kintsugi:

For more details, please see the linked referenda above, and:

https://github.com/interlay/interbtc/releases/tag/1.23.1
https://github.com/interlay/interbtc/compare/1.20.1...1.23.1

The latest compatible clients release for this version is v1.21.0:
https://github.com/interlay/interbtc-clients/releases/tag/1.21.0

As a vault operator and collator that is here from the start I strongly support the quick introduction of the capacity model on Interlay.
I am aware that it is lowering the APR for some and I am one of these in Interlay.
It makes vault operation fair for everyone and prevents some entities "gaming the system" by bridging through their nodes and redeeming through others.
On Kintsugi my vault was "emptied" so many times and I had less than 5% APR for half a year and would have been better off just staking the collateral.
I hope all my fellow operators share this vision and support the initiative.

Edited
Reply
Up 3
Share
Second
No current seconds
This proposal has been turned into referendum.
Metadata
hash
0xb92d7c803ae267ee0297b81b58af0a484ff1f4adc374e58158fdf5733a4c3b68
deposit
0 INTR
proposer
Call
Table
Json
callIndex0x0302
sectionutility
methodbatchAll
args
calls
0
callIndex0x5502
sectionparachainSystem
methodauthorizeUpgrade
args
codeHash0x130b0b9ac802b3db074f304ddc428950e80ee3e2a14d9f009d8376fdff493b7d
1
callIndex0x4501
sectionclientsInfo
methodsetPendingClientRelease
args
clientName0x666175636574
release
uri0x68747470733a2f2f6769746875622e636f6d2f696e7465726c61792f696e7465726274632d636c69656e74732f72656c65617365732f646f776e6c6f61642f312e32312e302f6661756365742d70617261636861696e2d6d657461646174612d696e7465726c6179
checksum0xddd2248445c76b34451a2e9183d8c0fb024c51a92d08cd963a22493a7275f638
2
callIndex0x4501
sectionclientsInfo
methodsetPendingClientRelease
args
clientName0x6f7261636c65
release
uri0x68747470733a2f2f6769746875622e636f6d2f696e7465726c61792f696e7465726274632d636c69656e74732f72656c65617365732f646f776e6c6f61642f312e32312e302f6f7261636c652d70617261636861696e2d6d657461646174612d696e7465726c6179
checksum0xa905f1e69c346744174e1c1612ad323e17e14f7ae750a9978e42575b3c0cfab1
3
callIndex0x4501
sectionclientsInfo
methodsetPendingClientRelease
args
clientName0x7661756c74
release
uri0x68747470733a2f2f6769746875622e636f6d2f696e7465726c61792f696e7465726274632d636c69656e74732f72656c65617365732f646f776e6c6f61642f312e32312e302f7661756c742d70617261636861696e2d6d657461646174612d696e7465726c6179
checksum0xb4c886c1cbb915cc6aca6ba0b63489f769d6cb81bdab8afeaf5263205f8e8cdd
TimelineLatest activity undefined
2023-03-24 19:05:24
Proposed
Index
#47
2023-03-27 09:00:12
Tabled
Referenda Index
#45
Deposit
250 vINTR
2023-03-27 09:00:12
Started
referendumIndex
45
voteThreshold
SuperMajorityAgainst
2023-04-04 06:30:00
Passed
referendumIndex
45
2023-04-05 09:33:24
Executed
result
ok
Comments

This is a great,

Reply
Up

Thanks Sik for pushing this forward faster! Down with vault competition and can't wait for the capacity model! --spaz

Reply
Up

I am a vault and I can't wait for the new model to be included on the mainnet. All arguments are correct. Thank you Sik for pushing process forward!

Reply
Up