Hello everyone!
I have had the pleasure of working on Hive for four incredible years, and I am grateful for the support you have all given me. And I would like to carry on working as a core developer and contributing to Hive for a fifth year.
Who am I
I have been on this chain for more than 7 years now.
I went from regular blogging, to contributing to open source on hive to building dapps and running a top 20 witness (@steempress). I became much more involved in core development when we forked away from Steem, rising up to the occasion as we needed every manpower we could get to birth the chain. I contributed to the soft fork that locked Justin sun's funds and later the very first hard fork that created hive. Ever since, I've been working on hive as a core developer contributing to hive and hivemind implementing sensible requests from the community.
If you're interested in my full journey I made a throwback post retracing most of my activities on steem then hive here: @howo/my-hive-story
Notable examples of my work
If "core development" does not ring a bell to you here's two features that I shipped to give you an idea:
Recurrent transfers
Before if you wanted to subscribe to a service on hive you had to either pay upfront for a long period of time (eg: a year), send a transfer every month or worse: trust their active key with the service (NEVER DO THIS), which was a pretty terrible UX for want to build businesses on top of hive and benefit from one of our main selling points: fast feeless transactions. Now with recurrent transfers users can simply set a recurrent payment, and every time it hits their desired frequency, the money is sent from their account. It's a much simpler UX similar to one you're see on web2 payment solutions like paypal
New community types
Part of the roadmap for communities is to empower community owners to fine tune who can post or comment in a hands-off fashion as the software takes care of everything, when previously you'd need to be there all the time to moderate posts/comments. This enables them to create paid communities, enforce quality by vetting quality writers or whatever else you may find interesting ! This also means it's very easy for community owners to build systems on top of it, want your community to only be accessible if the user owns a specific NFT ? Or if they have an active recurrent payment to you ? No problems !
If you want to read a bit more about it:
@howo/communities-is-getting-an-update--what-to-expect
RC delegations
If you've joined hive in the past two years you probably heard a decent bit about this one. RC stands for resource credits, whenever you do a "free" transaction you spend RC, but unlike other chains like ethereum, it's free and recharges over time. The more Hive power you own, the more total RC you have to spend. And for the longest time Dapp developers had a bit issue when onboarding:
Either you make users pay for their hive power when you onboard them, which is going to drastically hinder your growth, or you have to delegate hive power to them, which means people will try to abuse it by registering hundreds of accounts to get free hp and self vote. We've seen this play out times and times again and the solution that most dapp developers has been to police and check every new subscribers. Which obviously is a lot of wasted time and money that should instead be spent on buidling.
Rc delegations allow you to delegate RC but not hive power. allowing users to execute transactions and try out dapps, but without any monetary power. It also can be executed with a posting key as opposed to an active key for hp delegations, so should this be executed by a bot, you no longer need to expose your active key to an online environment (eg: a server)
Other things
Obviously big features isn't the only thing I do. I also work on smaller things, low hanging fruits, bug fixes etc here's some examples:
- Improve recurrent transfers to allow multiple recurrent transfers to exist to the same account + some bug fixes: Recurrent transfer update to support multiple recurrent transfers to the same account
- Fix a long standing bug where beneficiaries were not included in the post payouts leading incorrect payout prices across all the api nodes (!!): https://gitlab.syncad.com/hive/hivemind/-/merge_requests/623
- Security improvement communities: https://gitlab.syncad.com/hive/hivemind/-/merge_requests/539
On top of regular core development, I host a monthly meeting where all the core hive devs sync on things and write recaps that you can find on my blog, eg: @howo/core-dev-meeting-55
Finally, when I get the chance I help developers or write documentation eg: Hivemind / HAF how to save and restore the database for development purposes
Payment
Despite rising inflation, I fel comfortable with the current pay and thus won't increase.
Therefore the proposal the same: 330 hbd a day for a year.
Voting:
Here is an easy link to vote on the proposal :
https://peakd.com/proposals/304
You can view all the proposals on: (make sure to vote on the upcoming one and not the old one though !)
https://wallet.hive.blog/proposals
https://peakd.com/proposals
Closing words
If you have any questions, please feel free to ask them in the comments !