Testing reviewing and documenting the SMT hard forksteemCreated with Sketch.

in sps •  last month  (edited)

Hi,

You may recognize me for my work or steempress or on my previous proposal downvotecontrol which is coming to an end in a few days, so here I am with another proposal.

As you are probably aware Steemit recently released their testnet for SMTS This is great news because this means that it's also time for us (the community) to conduct tests and try to find all the problems beforehand, and this time it's special, this is the biggest hard fork that they have ever done. Basically every functionality is impacted one way or another. Which means there are lots of ways this can go wrong.

So it is crucial to test as much of it. Hence this proposal.

To me there are several components when it comes to "prepare for the hard fork"

Testing

Obviously testing, There are already some scripts that are running but I will be writing automated tests, spinning up various SMTS with various configurations to try to test as many SMTS (and others) configurations as possible.
I will test every functionality one by one and write complete test suites that anyone can run.

But testing doesn't stop here, we also need to test that the libraries are ready and up to date, so I will also test that libraries don't break when you execute those new endpoints. I will also test the most used libraries and submit pull requests to fix bugs that I find.

Reviewing the code

Reviewing the code is one of, if not the most important step, It's a long and tedious process that requires a lot of c++ knowledge in the case of the steem blockchain code. But if done correctly it allows you to spot bugs before they happen. It's important that the one reviewing the code is another person than the one who wrote the code because when coding you tend to tunnel vision and it's easy to miss that one edge case that will make the whole chain crash. This is why it is very important to have reviews from people outside of steemit to think outside the box and try to spot bugs, or not even bugs. It's also important if you want to suggest code improvements if you find a place where you believe there will be a scaling issue. It is also very important to do when writing tests because you can they find the pain points where you know the system might fail.

Writing documentation

A big part of testing is that you get to have first hand experience with all the end points, which can be turned into great pieces of documentation. This is very important because without documentation, a lot of features will go un-noticed or unused because developers won't know how to use them. It is also very important to make sure that we make it as easy as possible for developers to build on steem and on SMTS. This is a crucial step to the SMT's success !

I have a lot of experience writing documentation, I will probably write a lot of examples on the steemsnippets repository : https://github.com/drov0/steemsnippets It's a repository that I have maintained for two years now and I have always been adding examples for the latest hard fork updates. So I am quite used to it.

Deliverables :

I will test all of the new operations, review the code for each of them, write tests and document them. Once that's done, I will make an "SMT test factory" where I generate tests to try as many SMT configurations as possible and see if I can break them.

I will write reports on my progress every 7 to 10 days on chain, and you will be able to track my progress on a dedicated public github repository where I will share all of my code for the tests, my results and my reports.

Timespan

I expect to be working on this for the whole duration of the testnet, and I expect that it will last about 3 months. Starting from the 24th of october to the 24th of january. If the testnet ends sooner I will delete this proposal.

Funding

I am asking for 180 SBD per day.

Final words

Some might say that testing hard forks is the role of the witnesses but not all the witnesses have the technical capabilities or the time to perform a lot of tests. This kind of proposals are very important for the ecosystem because it means that they can then read on my reports to see what I tested, take my open source code and modify it to test other things or an edge case that they might have spotted or make a more educated decision on whether or not they should support this hard fork.

More testing is never a bad thing, especially when the chain's health is at stake. Nobody wants to see the chain stop like in hard fork 20 or spend another all nighter waiting for their nodes to replay like in hard fork 21. I think that this shouldn't be the only "test hf23" proposal.

Finally this is not only about making sure the hard fork works well and then throw everything out. It's also about making documentation that will be useful for the whole community for the months and years to come.

Voting

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

steemconnect
https://steemproposals.com/proposal/50

You can view all View all the proposals on:

https://steemproposals.com/proposals
https://steemitwallet.com/proposals
https://steempeak.com/proposals

If you have any questions or suggestions, feel free to leave a comment.

Thank you for reading,

@howo

Authors get paid when people like you upvote their post.
If you enjoyed what you read here, create your account today and start earning FREE STEEM!
Sort Order:  

There's an existing devportal issue from a while back to explore incorporating community tutorials, including some of yours:

https://github.com/steemit/devportal/issues/181

There is also this repository:

https://github.com/steemit/devportal-tutorials-py

These tutorials are intended to be included on the devportal, so they land here:

https://developers.steem.io/tutorials/#tutorials-python

It'd be great to get some pull requests for that repo.

Ah I didn't know there was an issue like this. I think devportal tutorials and steemsnippets fill a different niche though, but I don't see why I can't submit one or two PRs to port some smt functions there.

Yeah, totally.

Nice
but we will need more than one source for testing

千里之行,始於足下

Didn't know you spoke korean

  ·  last month Reveal Comment

Ack, I red google translate too quickly.

I completely agree, as I said in the final words, it shouldn't be the only testing proposal and I still expect witnesses to do their fair share of testing.

Ill support you

Thanks !

Wont there be dozens of witnesses, devs and Steemit.inc doing this exact thing?
And youre here asking for 180 SBD (Almost 20% of the daily fund) after you already receive 60SBD per day.

Id pretty much say no to this since there are those that wont charge SPS 180SBD per day and do the work.

Wont there be dozens of witnesses, devs and Steemit.inc doing this exact thing?

Tbh there isn't that much testing going on among the witness, most of them don't really have the technical capability. And as I said, more testing is a great thing. And steemit inc will do a lot of testing but they themselves said that they can't do it on their own because there are too many things to test.

And youre here asking for 180 SBD (Almost 20% of the daily fund) after you already receive 60SBD per day.

I won't really argue with the 180 sbd, it's my rate. and the daily fund is growing every day, so it is 20% now but over time it will be much less.

after you already receive 60SBD per day.

The proposal for 60 SBD will expire before this one starts.

Id pretty much say no to this since there are those that wont charge SPS 180SBD per day and do the work.

I disagree with this statement but I respect your opinion and hope you'll reconsider :)

Hm in all honesty I had the same thoughts than @lordbutterfly. But I also know that aside from steemit the majority of the top 20 either lacks the skills or time to properly test upcoming hard forks themselfs. As you wrote in your post a good understanding of code, c++ in particular, is needed. Do you have some references of your past work on C++ projects so that we can get an idea of what to expect from your testing? That said the proposal sounds good to me and I think I will vote for it. Not that my stake would make any difference :D

  ·  28 days ago (edited)

Developers making busy work for themselves as usual.

But look at how his down vote effort is improving the site so much! All this original content ... not.

I'm withdrawing and selling the small amount of Steem I sent here to get my posts some visibility.

@tipu curate

Posted using Partiko iOS

Upvoted 👌 (Mana: 0/4)

This post has been included in the latest edition of The Steem News - a compilation of the key news stories on the Steem blockchain.

So we can't promote any content on this site without getting downvoted into oblivion now?

I'm really impressed with all you have been doing for steem lately. It's like you were here but hiding for a while, now you seem like a rocket that just blasted free. Thank you.

Posted using Partiko Android

Thanks !

Congratulations @howo! You have completed the following achievement on the Steem blockchain and have been rewarded with new badge(s) :

You received more than 10000 upvotes. Your next target is to reach 15000 upvotes.

You can view your badges on your Steem Board and compare to others on the Steem Ranking
If you no longer want to receive notifications, reply to this comment with the word STOP

Vote for @Steemitboard as a witness to get one more award and increased upvotes!

It is great proposal and i am supporting your initiative dear @howo

Please what is SMT

nice proposal.

Resteem your posting

Great post thanks for share I enjiy your content.

Reel me more on downvote application control proposal that you mentioned above.