I don't check the Steemit code, but I don't see nothing hard to implement it. :)
For me has more sense to say to the system:
Me: I want to convert 300 steem power into Steem!
System: You will need 4 weeks to do that. Do you agree? (Yes/No)
Me: Yes.
Then, after 1 week: 80 Steem(that mean 1/13 of my total Steem power)
Second week: 80 Steems
Third week: 80 steems
And in 4th week only 60 steems.
You are viewing a single comment's thread from:
Ah, got it. It's a more specific use case. I think it can be implemented once we gather more user input. As it is right now, 13 weeks is an important number in regard to the total expected Steem on the market. It has to do with "maturation of shares" if you want, and it needs a bit of predictability (or so I understand).
Ok, I got the idea! It's not a coding limitation it's a business logic limitation. :)
Thanks for explanation!