Hello Steemians, welcome to the 3rd installment of our progress report on SMT development. In addition to the 0.20.6 release on Wednesday, we’ve had steady progress on SMTs this week.
SMT scope added this week:
- https://github.com/steemit/steem/issues/3100 - Remove vesting_liquid_less Class
- https://github.com/steemit/steem/issues/3103 - Basic Functionality of Delegation Pools
- https://github.com/steemit/steem/issues/3113 - Transaction Status Plugin State
SMT work completed last week:
- https://github.com/steemit/steem/issues/2886 - NAI Generation
- https://github.com/steemit/steem/issues/3057 - Bug in Asset
- https://github.com/steemit/steem/issues/2558 - Transaction Polling API
- https://github.com/steemit/steem/issues/3085 - Plugin State Information
- https://github.com/steemit/steem/issues/2870 - Generate Blocks With Automated Actions
- https://github.com/steemit/steem/issues/2725 - Create a New Token
- https://github.com/steemit/steem/issues/2720 - Automated Action Validators
- https://github.com/steemit/steem/issues/3113 - Transaction Status Plugin State
The blue dots symbolize the number of points that we have completed for SMT development. For those who don’t know, assigning “Story Points” is part of Agile Software Development. They are a “unit of measure for expressing an estimate of the overall effort that will be required to fully implement a product backlog item or any other piece of work” and determined by using a Fibonacci Scale.
As you can see, with HF20 even farther in the rear view mirror, we have been able to accelerate our SMT development velocity toward the desired trend line which would result in an on-time delivery for the SMT TestNet in January.
Our goal with this series is to bring even more transparency to the development process of Smart Media Tokens. In addition to these weekly reports, you can follow along on our GitHub project organization and tracking system for SMT development which is (usually) updated daily.
The Steem Blockchain Team