Proposal: Core blockchain development, testing and documentation

Hi,

Hive has been going for a little more than a month now. We have a small team of core hive developers, pretty much @blocktrades' team, @netuoso and myself.

I have been involved in various tasks including the founding hive hard fork, slow conversion of hive on the dao to hbd, various api fixes and more recently I have ported the RC delegation feature from the SMT branch to the current branch, it was quite a hard task because the smt branch diverted quite a bit from the brand we currently use, and there was some changes that I made more on that on a future post.

RC delegations are working although it still needs some polishing, and there are some discussions to be had on various changes we may or may not want to do (this is where you come into play hive community).

That feature will probably go live in hardfork 25, it's been the missing piece to emboarding for the longest time and we will finally have it, All the account creation services will finally be able to stop focusing on preventing abuse from people farming hive power delegations and focus on getting as many new users as they can on hive.

I want to continue working to grow hive, so here's my proposal.

Core development

Most of the time spent will be focused on core hive developments, meaning blockchain improvements, optimizations, and feature requests, and of course SMTs. Having spent a significant amount of time testing them and reviewing the code on it thanks to my previous proposal, I am now quite familiar with the code.

I will be working with the rest of the core team on any feature that may be needed, here are some examples:

  • Light accounts (a wallet basically, that allows people to own and pay with hive way more easily)
  • RC improvements to help scale the chain
  • Partial replays and replay speed improvements, This would help witnesses, node owners and exchanges a lot.
  • Proposal system improvements like partial voting, instant vote display (instead of waiting an hour), payment to escrows etc
  • Transferable account claims
  • Better power down system to reward long holders while not driving investors away who don't want to lock their tokens for too long

Transparency

All of my work can be tracked on gitlab, I assign issues to myself so you can always see what I'm working on, and all of my code is made public and open source.

For instance right now I am working on :

RC delegations
Incoming delegation api
Api bug

I will also regularly be posting updates on chain to let you all know what I'm working on and how it's going. The how often is still be be determined, but it may be bi or tri weekly.

About me

If you don't know me this is my third proposal, I have worked previously thanks to the proposal system on a downvoting tool (https://downvotecontrol.io), and tested SMTs in great length, finding multiple chain breaking bugs.

I have been involved on hive/steem since june 2017, working on lots of aspects of the chain, I co-created @steempress (soon to be rebranded), made quite a few tools here and there to help people automate their tasks and made a lot of documentation to help devs back when you had to guess how the chain worked by trial and error. And more recently have been involved on core chain development.

funding

I am asking for 275 HBD a day for a year. I calculated the price to be about 100$ an hour. So I will be spending between 15 and 20 hours a week on it (assuming hbd stays at 1$ which it often doesn't).

Voting

Here is a few easy links to vote on the proposal :

https://hivedao.com/proposal/97
hivesigner

You can view all View all the proposals on:

https://hivedao.com/proposals
https://wallet.hive.blog/proposals
https://peakd.com/proposals

Final words

We used to rely on steemit inc to do all the core development before, they used the ninja mine to pay for devs and while this had the benefit that we could lay back and let them do all the work, and scream at them if we didn't like what they did. That also ment development happened mostly behind closed doors with little community involvement in feature definition, after all, their boss was steemit inc, not the community.

Now that we are on hive, we have the chance of having a decentralized dev team that, through proposal payments will work directly with and for the community. I think these are very exciting times and I can't wait to see what we'll all build together.

@howo

H2
H3
H4
3 columns
2 columns
1 column
37 Comments
Ecency