Vertex
Overview
An API to get raw, block-level data from a variety of blockchains.
i.e. getting the raw Ethereum block at a given height (with the authorization header containing an API key):
https://api.vertex.flipsidecrypto.xyz/chains/bsc/mainnet/blocks?height=9595182
Where is the Code?
Ownership
- Jim Myers, Paul Mikulskis
- Slack Channel: #team-product-eng
Where does it Run?
Cloudflare
Where is data stored?
The whole point of Vertex is to make raw block-level data available for a variety of blockchains.
As a result, this block-level data is cached in multiple places, defined as sources in the code.
Each Integration object within Vertex (e.g. the Ethereum integration) has a list of networks we track, such as mainnet.
Each Network object has a list of sources, which define all the places where Vertex stores its data for any given chain+network.
This lets us maintain a variety of different sources for each chain, as well as having the ability to configure different data storage options for each and every integration:
How is it deployed?
Github actions using the Cloudflare wrangler cli
What DNS addresses are supported?
- https://api.vertex.flipsidecrypto.xyz (production)
- https://api-staging.vertex.flipsidecrypto.xyz (staging)
Additional Documentation
To test playing with Vertex, you can get started with the variety of make commands, documented in the repo.
Using make test-dev, a local suite replicating our Cloudflare environment will boot up on your local machine, letting you hit endpoints such as https://127.0.0.1:8787/chains/bsc/mainnet/blocks?height=9595182 to grab block data.