Hi,
As I said last week, those updates will almost always be super short, this is a good example.
This week I spent a bit of time gathering a first list of those who will get an airdrop https://gitlab.syncad.com/hive/hive/-/merge_requests/46
But I worked on rc delegations again, I did some extra testing, worked to update the old unit tests and added more. And I finally felt that it was ready.
So here it is :
https://gitlab.syncad.com/hive/hive/-/merge_requests/45/diffs
So what's next for that feature ? First I have created a pull request with the appropriate tag to notify other core devs that the feature is now ready to be peer tested and reviewed. I assume they will send me feedback, perhaps find bugs that I didn't notice and I will fix things. I assume we'll do a few iterations like this.
Then we'll run a proper testnet to mirror main net transactions to see how it behaves in the wild. And make fixes if needs be.
I am planning to submit it for hf25, so there is no rush.
Now I need to write documentation on the feature, update the old comments to make sure everything is up to date, provide examples in js and python on how to use that new feature for devs.
But the focus won't be that for a bit, hard fork 24 is very near and I will focus most of my attention towards reviewing and finishing it up.