Regarding the 3 projects we've submitted in the February report, here are the most recent updates.
Previous Project Roadmap (February):
https://gist.github.com/aaroncox/f694a270f4b94fd6b3fa43e4e4ba0f30
- NEW (In Progress) Final release for anchor-link and its associated protocols
- Started protocol specification document
- Improved same-device UX flow within anchor-link
- Rebuilt entire UI for anchor-link
- NEW (In Progress) Coordinate development of Android SDK for ESR and anchor-link protocol
- We have began conversations with multiple other wallet developers to coordinate the release of an ESR library for Android.
- NEW (In Progress) Finalize v1 release of ual-anchor
- Updated UAL to newest version after issues reported to B1 were fixed.
- The UI has been rebranded using new Anchor brand.
- NEW (In Progress) Finalize and release transit provider for ESR Protocol
- Started working with EOS New York to do the final integration steps to merge our transport provider into Transit.
- UPDATE (In Progress) REV2 of the specification to include further details of identity requests and update all examples to modern code.
- Progress has begun on the finalization of REV2 of the ESR specification, progress of which can be tracked: https://github.com/greymass/EEPs/blob/eep-7-rev2/EEPS/eep-7.md
-
Spring:
- (In Progress) Finalize v1 release of ual-anchor
- (In Progress) Final release for anchor-link and its protocol
- (In Progress) Finalize and release transit provider for ESR Protocol
- (In Progress) Coordinate development of Android SDK for ESR
- (In Progress) Preparing presentation materials and scheduling talks around this subject to introduce it to the developer community.
- (In Progress) Documentation around the UAL plugin demo
- (In Progress) Release of a standalone UI Kit for ESR integration (https://github.com/greymass/anchor-link-browser-transport)
- (In Progress) REV2 of the specification to include further details of identity requests and update all examples to modern code.
- (In Progress) Release of Transit plugin (https://github.com/greymass/eos-transit/tree/provider/anchor-link/packages/eos-transit-anchorlink-provider)
- (In Progress) Documentation portal on our website linking all this information in one place.
-
Summer:
- Finalize ESR v1 and publish the formal specification, moving out of the draft stage
- Rewrite our callback service layer in a compiled language for scalability (https://github.com/greymass/buoy-nodejs)
- Contribute development time to assist in integration of the ESR protocol with various open source signature providers and dapps.
-
Unscheduled:
- Rebuild the eosio.to viewer utility (https://eosio.to)
- Rebuild the ESR Payload Builder (https://greymass.github.io/eosio-uri-builder/)
- UPDATE - (In progress) Release of Anchor Desktop 1.0.0 (RC9 now available)
- Released RC7, RC8 and RC9 as final round of bug testing continues.
- UPDATE - (In progress) Version 1 release of Anchor Mobile for iOS (currently in the hands of beta testers via TestFlight, invitations available upon request)
- Released 2 new versions of the mobile app with various fixes and improvements to the UI/UX.
- UPDATE - (In progress) New website related to Anchor with guides/tutorials to help users understand the wallet software they are using.
- The integration of a documentation engine into Gatsby has begun, with initial layouts/build processes being established.
-
Spring
- (In progress) A complete rebrand of Anchor before a final 1.0.0 release.
- (In progress) Release of Anchor Desktop 1.0.0 (RC9 now available)
- (In progress) Version 1 release of Anchor Mobile for iOS (currently in the hands of beta testers via TestFlight, invitations available upon request)
- (In progress) New website related to Anchor with guides/tutorials to help users understand the wallet software they are using.
-
Summer
- Start moving most of our in-app interfaces out to web-based applications.
- Integrate ESR session and session management interfaces into the desktop build.
- Start work on the prototype of Anchor Mobile for Android to match the iOS experience.
- Building of an kotlin/java library that matches out swift-eosio implementation.
- Custom v1 History Implementation
- No changes to report, systems remain stable and discussions around next steps is being debated.
-
Spring
- (In Progress) Move trace retrieval process and compilation out of nodeos.
- (In Progress) Move all microservices into a containerized deployment and open up for testing
-
Summer
- Release a version 1 implementation that others are able to run.
- Start drafting a new API specification to improve on call structures, while maintaining v1 reverse compatibility.
- Deploy the custom history solution to WAX and other EOSIO chains