This article was first published on Po.et Blog - Medium
Po.et is building the better web: the decentralized protocol suite for content attribution, discovery, monetization and reputation.
April has been a much more smooth, calm month as opposed to the flurry of developments that March brought us. We’ve taken the time to sit back and work through the first parts of our “Connecting the Dots” milestone that we announced two weeks ago (and rest a little bit, too).
Connecting the Dots
The first phase of the milestone focuses on expanding some of the core functionalities of Po.et that exist, but we’ve not exposed via the Works Explorer or API from poetnetwork.net. Our most requested feature to implement has been the ability to use non-text file types like audio, video, and PDFs. We’re going to be adding those features and making that functionality available to people who connect a wallet that can prove ownership of POE tokens.
The primary goal for “Proof of POE” is to reward token holders with additional features from poetnetwork.net applications. This will not affect any other services that use Po.et, like the Poet Publisher from Bryan Isbell. Also, this is not meant to be a long term strategy to drive adoption as the core team doesn’t want to be the main source of application development in the future.
In order to get ready for this work plus some of the additional functionalities that come right after, we’ve taken April to refactor some of the code in frost-api. The largest part of that refactor comes down to how we’re creating UUIDs, but it shouldn’t affect any end users at this point.
Responsible Disclosures & Bug Bounty Program
Since we opened up the bug bounty program on April 15th, we’ve had 11 disclosures submitted. We’re still working out some of the kinks in how we evaluate submissions but pleased ...
To keep reading, please go to the original article at:
Po.et Blog - Medium