October 2018 Po.et Engineering Progress Report
Po.et is building the verifiable web: the decentralized protocol suite for content attribution, discovery, monetization and reputation.
The Po.et engineering team is beginning to transition from feature building to testing and debugging. We’re putting the finishing touches on the mainnet release. It’s an exciting time for us. We’ll soon be able to share what we’ve been working on behind the scenes for the last several months.
Here are some of the team’s accomplishments during the mainnet build:
- Implemented claim batching so we can scale to handle enterprise claim creation workloads.
- Redesigned how claims are structured and signed to improve reliability and ensure that your claims will continue to work correctly long into the future.
- Fixed a lot of bugs — specifically, some foreign language content resulted in broken claims. Those claims should work correctly in the mainnet release.
- Conducted an internal security review inspecting every aspect of the Po.et system for vulnerabilities.
- Strengthened our infrastructure and deployment automation.
- Made critical improvements to code quality and the process we use to monitor and ensure code quality on the Po.et project.
The team has done an outstanding job, and I’m very impressed by all of them. We’ll continue to polish things up over the course of the next few weeks as we prepare for the release.
What Works Now?
Because our mainnet push has been our primary focus, this hasn’t changed since June. We expect all of this to continue to work after the release:
- The Po.et Testnet
- Attribution
- An API
- Integrations
- Developer libraries
- A mobile app
Where Are We Going Next?
We’ve rounded the final corner on our road to mainnet! Here’s what that looks like in our progress charts:
Now the burndown chart is starting to indicate that work is beginning to wrap up. It’s much clearer now that the average ticket count is trending down. We’ll still see a it tick back up now and then as scope gets uncovered, but those tickets are getting closed faster than new tickets are being created. This looks like a really healthy chart.
As usual, you can really see how much work has been done since last month in the task progress graphs. Most of the broken out work is done or very near to being done. We’ve blasted through 300 completed tickets, and you can clearly see that the team is working at a healthy pace.
And now, the graph you’ve all been waiting for:
As expected, we’re fighting harder for the last remaining bits of progress, but we’re rallying and pushing hard to carry the ball across the goal line.
