3c8b28d69f
### Description Tracking issue: https://github.com/wormhole-foundation/wormhole-explorer/issues/535. This pull request fixes an inconsistency between the endpoints `GET /api/v1/x-chain-activity` and `GET /api/v1/top-chain-pairs-by-num-transfers`. The inconsistency arose because the endpoints computed the data in slightly different ways. It was resolved by modifying the `GET /api/v1/top-chain-pairs-by-num-transfers` endpoint to use the same data source as `GET /api/v1/x-chain-activity`. |
||
|---|---|---|
| .github/workflows | ||
| analytics | ||
| api | ||
| common | ||
| contract-watcher | ||
| deploy | ||
| devnet | ||
| fly | ||
| jobs | ||
| parser | ||
| pipeline | ||
| spy | ||
| tx-tracker | ||
| .gitignore | ||
| LICENSE | ||
| Makefile | ||
| README.md | ||
| Tiltfile | ||
| go.work | ||
README.md
Wormhole Explorer
Background
WIP
It would be more efficient and reliable for...
- an indexer to be populated by an independent party (Fly) listening on the p2p network
- integrators to query a service for signed VAAs instead of round-robining the public guardian endpoints
More insight into Wormhole network status, stats, and messages would be great!
The service can even be extended to offer websockets or webhooks to stream new VAAs.