* initial commit
* cleanup, spacing fixes
* update copy
* responsive footer
* logo link
* router link active underline
* fix side-by-side padding
* app card links
* initial network table
* sort guardians
* network selector
* add envs to unbreak deployment
* 404
* wip explorer
* recent messages list
* fix activeNetwork context init
* add Oasis and Avalanche utils
* add title to RecentMessages
* add explorer ChainOverviewCard
* add explorer PastWeekCard
* save exact versions of npm packages
* add explorer search functionality
* mvp
* remove dupe page
* add basic social images
* add social sharing metadata
* update development siteUrl
* test with example prod url
* fix social card name
* update number of chains
* decode payload with WASM
* updated copy
* fix index portal link
* prod .env variables
* show more recent messages for chain or contract
* fix decodePayload summary
* delete explorer v1
* fix explorer dockerfile
* fix explorer serve settings for devent
* remove proto-gen-web for explorer
* rm proto-gen-web for explorer
Co-authored-by: Evan Gray <battledingo@gmail.com>
Co-authored-by: Evan Gray <56235822+evan-gray@users.noreply.github.com>
Limitations:
- Only supported for Solana and for confirmation level Finalized,
which the token/NFT bridges use. Need to take a close look before
enabling it for both (since we're bypassing the tx fetcher and would
fetch and process accounts of the "wrong" confirmation levels).
- Rate limiting not implemented yet, will be done in a future release
when things are not currently on fire.
Test: https://gist.github.com/leoluk/bab3a18e922057109facea1cf1f26b2f
commit-id:6a0d4c32
It appears that GCP Cloud Logging cannot handle the volume of logs
we're throwing at it... full text search slows to a crawl (LOL)
Reduce log level until we can move to something else.
commit-id:b71c3467
Fixes https://github.com/certusone/wormhole/issues/685.
Example occurrence this fixes: https://i.imgur.com/gZWKf1n.png
Possible future optimizations include:
- Ignore late messages in the processor (but we can only ignore
them post settlement time, so we need the cleanup logic regardless).
- Ignoring late observations from other nodes.
- Using the stored VAA to calculate misses.
- Drop incomplete local observations. However, this is not trivial
since we do not know the message ID for those.
commit-id:47e1e59f
The current lifetimes 'a/'b restrict the &data and &program_id lifetimes which makes the
entrypoint unusable in solana_test_program's processor!() harness, which expects the more
relaxed (but equivelent for us) type of:
fn processor<'a, 'b: 'a, 'c, 'd>(
program_id: &'c Pubkey,
accounts: &'a [AccountInfo<'b>],
data: &'d [u8]
)
It has no effect on our current programs.
Change-Id: Ia657462141165064c629fdff02b5ec451aab50f0
Csongor Kiss
Leo
Justin Schuldt
Evan Gray
Hendrik Hofstadt
Kevin Peters
Csongor Kiss
kev1n-peters
justinschuldt
Hernán Di Pietro
Keone Hon
Reisen
victorshevtsov
