* refund address handling improvement
* fix compilation error
* Remove unnecessary line
* restrict to view
* fix comment
* Improve handling of gas limits
* get test to pass - check that the return data is appropriately long before decoding
* modification to checking inequality
* modification to checking inequality - use unchecked
* clean functions around - add untrustedBaseDeliveryPrice
* make quote_length_bytes a constant
* seperate pay into two overloads
* change inequality to equality for checking return data length
* renaming functions
* allow override of refund per gas unused
* test modification
* note
* update clients.js version
* updates to clients/js
* update clients/js
* Generate modification
* prettier
* status change
* docs change
* add back the 'impossible's
* update sdk version
* better status check WIP
* WIP
* Improved status check and stringify function with times
* improvements to status printing
* prettier format
* Remove last console log
* prettier
* readme modify
* readme fix
* Readme fix
* readme changes
* don't rely on wormscan for status in devnet
* prettier
* Remove status check from integration testing - this is a helper that shouldn't interfere with contract testing
* prettier
* update clients.js version
* readme revert changes
* base default rpcs
* script improvements
* Add manual delivery helper
* remove console logs
* arbitrum needs a custom block range
* fix bug in testing if blocknumber is 0
* deliver fixes for manual delivery
* prettier
* fix default block tag
* pre-pend scripts with test
* review comments
* CCQ: Query Server
* More rework
* Clean up p2p code
* Health check change
* node: support http PUT or POST for new ccq queries
---------
Co-authored-by: Jeff Schroeder <jeffschroeder@computer.org>
* aptos: update upgrade script to support mainnet
Also factor out named_addresses into a separate helper script
* scripts: aptos support for gov proposal generation
* sdk/js: add aptos nft_bridge mainnet address
ubuntu-20.04 ships with GLIBC-2.31, but the latest foundry
nightly (which these CI actions use) link against 2.33+ (perhaps foundry
should statically link against something like musl...?)
So instead we run these two tests on ubuntu-latest
The hash preimages for storage calculations were wrong for two storage
slots. The updated preimages can be verified to be correct with e.g. the
`chisel` command line tool from the foundry suite.
The payload version 1 relayer has long been superceded by the more
modular relayer-engine and specialized / automatic relayers. The newer
relayers all rely on wormhole payload version 3 and no one is currently
running a payload version 1 relayer. Additionally, support for it has
been removed from portal bridge by the portal maintainers.
The code lives on in the better maintained and supported relayer-engine.