Curious about the motivations behind this project, and how those motivations could shape Rosetta’s future adoption.
The motivation was to grow the crypto-economy by speeding up integration time for both developers and crypto platforms!
Some initial metrics we will track are:
- Number of blockchains with validated Rosetta implementations
- Total time for technical integration (at Coinbase and externally)
- Number of apps built on top of Rosetta APIs
To add on to @jai.prasad’s point, the tooling we’ve worked on thus far has been focused on optimizing these initial metrics.
- Write a Rosetta implementation without working about server boilerplate code using the server package.
- Read data from any Rosetta implementation with the client package.
- Reliably a sync a range of blocks from any implementation (handling re-orgs) using the syncer package. This one is SUPER useful for building a block explorer.
- Verify all balance changes are present in a Rosetta implementation using the reconciler package.
- Easily view a block (
rosetta-cli view:block X) or account balance (
rosetta-cli view:account Y) while debugging an implementation.
- Make it easy for anyone to run a suite of checks (
rosetta-cli check) against any implementation to ensure it adheres to the rosetta-specifications and represents all balance changes.
We are actively working on a few more tools to make everyone’s life easier and look forward to sharing those soon!