Yeah I get it... it's because the code they are going to use is just a basic extension of the current savings account system. Making the positions transferable would be a whole other thing. Certainly not the worst option so I guess we'll have to prove the theory in the field before it's taken more seriously.
You are viewing a single comment's thread from:
My sense is the general rule of thumb is to keep the base code as streamlined as possible by having basic features and pushing more onto L2. I think that is why we see Spk and HAF development.
But like you said, we will have to see how it works. Time vaults will start the process and is a good first step.
In the devs hands.