867f1c2962
* Fix analytic vaa metric and close metric client * Add analytic component manifest * Add metrics for cross chain activity endpoint * Feature/add endpoint get vaa count (#171) * Add trasaction controller + service * Init getLastTrx endpoint * Add endpoint for chain activity * Add configmap and secrets for influx Change Dockerfiles to support common library * Add vaa_count endpoint * Add cross-chain activity endpoint * Fix vaa_count endpoint * Add influx to api-service manifest * Make response and add docs for chain activity endpoint * Fix api deploy * Fix lasl-trx json name * Fix chain activity endpoint * Fix doc and endpoint route last-txs --------- Co-authored-by: Agustin Pazos <agpazos85@gmail.com> |
||
|---|---|---|
| .github/workflows | ||
| analytic | ||
| api | ||
| common | ||
| deploy | ||
| devnet | ||
| fly | ||
| onchain_data | ||
| parser | ||
| pipeline | ||
| server | ||
| spy | ||
| web | ||
| .gitignore | ||
| LICENSE | ||
| Makefile | ||
| README.md | ||
| Tiltfile | ||
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.