Marco Chen - The first validation client natively integrated with DVT written in Rust

Transcript

all right welcome back all right welcome back everyone here we've got um one more talk and then an excellent panel coming up that I think a lot of people are getting excited for let me take this time right now to go ahead and introduce Marco Chen Marco Chen is with safe stake and he's going to be talking about the first validation client natively integrated oh with DVT written in Rust Marco yeah good afternoon everyone I'm Marco uh Project Lead at safe state uh thanks for the host uh having us to be saf uh today uh before uh start the presentation I would like to ask how many people in this room is running your

own solo stickers please raise your hand wow that's many many even even in when I ask uh in in in in in the uh dep uh Eon in uh in in in July there's only one or two people okay uh what is safe St uh safe St is a uh just minimize uh middle layer fostering uh decentralization of ether uh two sticking uh when ethereum uh switch uh from P to post since last

September uh it's uh critical to manage the validation PR key uh securely online uh and at this moment there are more than 95% of validator are running solo sticking infer on Crown uh what would be the problem uh first there is uh single point Fair uh in the existing uh sticking ecosystem because once the solo uh low is uh get compromise or offline uh the vator uh get selction or penalty right away uh the second issue is uh especially for solo sticker the capital efficiency is

very low uh most of the solo sticker IFRS uh is running less than 10 validators on their uh uh sticking infrastructure uh uh with with their own funding and that's how uh the safe de uh comes in I would like to present a shock tutorial to you guys how easily a validator can be on boarding on safe dat right now importing a validator to save stake is fast easy and secure start by going to test net. safestate doxyz then click

run validator now click import existed and drag and drop your validator key store file into safe Stakes browser based dat enter the password for the key store file then click next now choose four operators you want to attest on behalf of your validator click next when you are finished check the box on the slashing warning screen then click next ensure the monthly payment option is selected and confirm the DVT payment to The Operators here and in your wallet now click run validator welcome to Safe stake click view validator to see your validator status it will take 15 to 20 minutes for your validator to become

active on the safe stake Network the page will Auto refresh indicating success the operator comedy is now attesting on the validator behalf uh so in saf St uh there are uh three major roles validators operators and saf St now validators are the party who deposit e uh on the Bon chain to register as a validator and delegate the validation task to a operator committee selected uh by this validator during setup and operator is the party who run all the hardware do the dir job fulfill uh validation task on behalf

of this validator uh safe down is the party uh who build and maintain the NW workk so what's uh what's a a DVT actually uh in safe stake uh the DVT actually we uh is replace the uh single uh sticking L with with a operator committee uh comprised by four uh different independ uh independent operator no and the valid validator priv key is doing key share and distribute to uh this four different operational uh among this committee so uh L of a single party uh can hold the

entire uh prior key uh in it would moove the current uh single point or fair and besides that uh we run a kind of uh uh uh for tolerance uh protocol among this committee uh in order to achieve consensus and aggregate uh the slat equivalent to the original and allowing one single lad to be offline uh without any penalty and selection so it will uh improve the resilience of the whole ecosystem uh

so uh what's the benefit why a user will choose uh safy uh because we leverage DVT to uh to do keyar of the original rator uh private key uh to spit and distribute to multiple operator node it can uh mitigate the current single point Fair improve security and and uh second uh by leveraged saf activity uh it can help uh minimize the penalty and maximize uh uh sticking reward uh because uh we Implement H Stu consensus among the

operator committee uh uh to achieve consensus and agregate uh the key equivalent to the original to attach to the beacon chain uh so this is a for for tolerance uh mechanism so uh allowing one single loow to be off line uh without any uh uh penalty it uh it can enhance the uh sticking uh resilience and uh for the exe for the uh solo sticker they can uh upgrade their current uh single uh uh operator node to become a

distributed validator and join uh safe State uh to accept any third party validator dedication uh so with the same Hardware uh investment they can actually uh run up to 100 200 validator uh and to earn uh subscription fee uh to enable the with the same Hardware investment but profitable to maximize their uh Capital efficiency uh what's the uh technical Advantage comparing uh with other P project uh saf uh validation client is

written in Rust rust is King uh in parenting memory uh with latb and while always uh bat goals in runtime B and we leverage H sta as the BF consensus among the operator committee uh it's more robust than ibft QBs qbf and to help uh minimize the selection offs and in the stage two of the mad we will introduce a uh a two tier sticking and liquid sticking uh to empower the LSD uh protocol on top uh imagine this

model is just like a rocky Pool Plus DVT we will introduce a new roll call illustrator this illustator will deposit for if to activate a mini pool validator registration process uh and to pick other fre operator node to organize the operator committee and this four e will bear the full liability for any selection penalty and other 28 if will be pair from the LST pool on top uh provided by a retail sticker this liquid sticking uh prodction is indeed running a risk-free uh

sticking uh in the meanwhile uh we will introduce a uh minimal cated uh uh mechanism to guide the how how to organize the the the operator committee because the operator committee is running for tolerance uh consensus if the uh operative committee comprised by all the bad guys uh the the mini asset would be uh still uh uh be compromised so we Define uh basic uh three different tier reputational uh mechanism for the uh for the operator NOS uh the highest

reputation uh highest one is the Dow Dow no and the second one is the verify operator which uh have been uh uh a kyc just like the current Lio curated operator Set uh and the West one is the alow limit uh operators so uh under this uh framework uh even there is a u Monopoly uh LST pool on top we can still ensure a diversifi committee base and the leaf uh to maintain the decentralization and and and healthy of the sticking ecosystem uh we Define safe as a uh decentralized SCE platform uh everyone

can join permission is as a uh operator uh on safe dech to accept uh third party validator dedication and uh yeah we are running a testl right now more than 50 professional staking service provider had join so come join us thank you yeah how many minute left for question yeah we do have um uh uh time for a couple of questions oh perfect in the back here hey thanks for the talk um maybe I

missed it or didn't understand so for a not operator who's looking to join do they need to bring their own bonding so some eth themselves to to run as part of the safe State Pool uh no actually uh you you you can see uh we Define free major role on the saf dech nwork uh that operator is just the party who run the hardware uh they don't need to deposit any e on the pick and chain okay thanks hey in your demo you showed someone uploading a key store file and

splitting it and sending it out to the operators where does that encrypted key store file go and how does it end up on the operator's machine uh yeah uh at the when when you see the demo that uh people upload uploading the uh key uh key key store on their own uh uh browser and so this step uh our protocol is running the uh uh sh SEC sharing uh protocol to spit the original key uh uh key store file to spit the private key and and then to uh uh uh uh we we have a uh with just G uh smart contract uh to manage

this key share and then uh because uh you can see the user pick four different operator no on our nwork to organize the uh uh operator committee right so each key share are encryp by these op uh operators public key so only to that ensure that uh uh only this operator can uh uh re from the smart contract to achieve the the the the piece of the uh uh prior key uh to run uh uh uh Hot Stuff consensus and then aggregate the key to run MPC exor to do a testation sweet thanks um sorry if I can do one more um

a node operator this is a client right so you're not going to be running your normal execution clients and and consensus clients as a node operator you're just running safe stank is that right uh yeah the approach we uh Implement DVT is we build our propriety uh proprietary uh validation client uh but uh and then to work with uh cons other consens client and the execution client so uh you you you you just uh lie running a laal uh solo sticker to run this uh El and cl but you need to uh pair our own uh validation client okay thanks any other questions from the

audience here all right please join me in giving our speaker a round of applause here thank you so much