Dev sync

As usual, there is a lot there, it's better if you listen to that one.

Here are links to the documents mentioned:
https://docs.google.com/spreadsheets/d/1hOjJiT8eXncopc3hbpANOVzck7yUshF5VceFbMojKRE/edit?usp=sharing
https://hive.pages.syncad.com/-/HAfAH/-/jobs/446503/artifacts/wdir/dashboard/index.html (the dashboard is down at the moment of publishing)
https://gitlab.syncad.com/hive/haf/-/merge_requests/213

Recurrent transfers update :

I published a full documentation on recurrent transfers not too long ago: @howo/recurrent-transfer-documentation

Now I'm working on an upgrade to allow multiple recurrent transfers (with different values / timings) to be set with the same sender/receiver pair.

We also discussed adding a feature to allow you setting a date in the future so that the first recurrent transfer doesn't execute instantly so that you can set a transfer in the future. It's a low hanging fruit and might as well ship it with the changes.

Finally, we spoke about creating a unified API for representing all transfers whether they are recurrent or not which would allow exchanges and dapps to integrate way easier with all transfer types.

When HF 28

We tentatively discussed what we want to add in our next big release:

The recurrent transfer updates I mentioned above
More optimizations for core hive.
Fixing an issue where an account which has used the decline_voting_rights op can still vote on proposals.
A unified API for representing all transfers whether they are recurrent or not which would allow exchanges and dapps to integrate way easier with all transfer types.

We are tentatively targeting a date in 3 months. But keep in mind it's going to depend on how fast we make progress on this and other actors from the ecosystem (witnesses/exchanges/dapps)