533b83ad28
### Summary Context: https://github.com/wormhole-foundation/wormhole-explorer/issues/154 This PR modifies all endpoints that receive an emitter/guardian address to accept a wider range of formats. After this pull request, all of these are equivalent: * `0x000000000000000000000000f890982f9310df57d00f659cf4fd87e65aded8d7` * `000000000000000000000000f890982f9310df57d00f659cf4fd87e65aded8d7` * `0xf890982f9310df57d00f659cf4fd87e65aded8d7` * `f890982f9310df57d00f659cf4fd87e65aded8d7` ### Testing plan * Added unit tests for the parsing code. * Tested manually a few of the affected endpoints. |
||
---|---|---|
.github/workflows | ||
api | ||
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.