The base denom for wrapped tokens is prefixed with "b". Check for this
in GetWrappedCoinMeta so that we don't end up treating base denom tokens
as native tokens.
* changed minimum governance vaa length check
* remove double write of chain ID in token attest
* removed panics from vaa processing in token bridge
* added non-negative check to fee in transfer tokens
* simplify non-negative check
* make fee sign check nicer in msg_server_execute_vaa
Operationally identical
* 14->13 in proofOfAuthority.md
Co-authored-by: chase-45 <chasemoran45@gmail.com>
Co-authored-by: Csongor Kiss <ckiss@jumptrading.com>
This is a squashed commit of all the changes in the wormhole_chain
directory from the development branch with the following changes:
* Replace the vendored cosmos-sdk directory with a replace directive in
the go.mod file pointing to the wormhole-foundation/cosmos-sdk repo.
* Update the cosmos-sdk version to v0.45.7.
* Rename starport -> ignite
* Update to ignite version 0.23.0
* Update go version in dockerfile to 1.19.0
* Upgrade github.com/cosmos/ibc-go v1.2.0 => v1.2.2
* Upgrade github.com/tendermint/spm v0.1.5 => v0.1.9
* Add missing module names to the
SetOrder{BeginBlockers,EndBlockers,InitGenesis} functions.
* Fix the gentx memo in the genesis.json file.
* ethereum: add optimism testnet
* sdk/js: add optimism testnet
* ethereum: put back network id
* Revert "ethereum: put back network id"
This reverts commit 71f68c50d2.
* ethereum: put back network id
* ethereum: file cleanup
* Solitaire: Use sysvar for rent instead of default
Using default has some risks such as:
- Network having a different values (such as Pythnet)
- Network changes the value
It avoids using default as fallback to have Error more explicitly
avoid exposing above risks under rare conditions
that the sysvar might return Err.
* Update comments
* Format the code
* governor listen to quorum gossip
* governor listen to quorum gossip
* Fix build error in tests
* See p2p from other guardians in devnet
* Fix test broke during merge
* Change delete function being used
* Don't reload duplicates on startup
* node: eth publish immediately
Change-Id: I242f02d0ed5bcced5ed366a512c07d5757b300e8
* testing: immediate publish test
* Move magic number to the sdk
Change-Id: I806f73d4442af4736aa6e5fc1c8e48e434c4a6d4
Co-authored-by: Evan Gray <battledingo@gmail.com>
Commit "02cf08531 node: move watchers to dedicated package (#1647)"
removed a lot of packages from the node dependency list. Run `go mod
tidy` to clean up the go.mod and go.sum files.
* near-sdk-refactor: Fix attest
: Fix missing function calls
: make near on near
: renamed tryHexToNativeStringNear
* near-sdk-refactor: bumped near-sdk-js version
Co-authored-by: Josh Siegel <jsiegel@jumptrading.com>
* node: reorganize watchers into own package
Change-Id: Idda82def1c8e1e07376bdc46a50fc02bd6f2386d
* node: rename terra to cosmwasm
Change-Id: Iebe5ccc7c66b772962425a42997bd2cfb66c6908
* cloud_functions: near support
* cloud_functions: moonbeam support
* cloud_functions: fix lint issue
* Added algorand & near wormhole addresses for their tokens
* Added near tokens to tokenAddressExceptions
* Use wormhole go sdk
Co-authored-by: Kevin Peters <kpeters@jumptrading.com>
* Governor publish gossip
Change-Id: I2b8b1ea84a0c411101a7027acd3a27a6d6464d59
* Update the config publish time
Change-Id: Ic6abf84befb1c20756da2ff66b15a8325dc46067
* Not setting value on enqueued VAAs correctly
Change-Id: I9fd3a5d8fc574f8382125445fa688efdae45b88c
* Publish at most 20 VAAs, not 20 per chain
Change-Id: Ic9dff99c59ee89d57fd79158844a1fe1a0003112
* Switch to using signed messages
Change-Id: I66cddc7477cd477aa77bdadfc346b588f2ae645b
* Publish status only once per minute
Change-Id: I972fb0cf868e89c6f74ae4441471a55df389f4dd
* Minor comment change
Change-Id: I0d3e443cbec7edd282f89c1a5cce5d5ec8776d55
* Add command to purge pythnet VAAs
* Add test for purging a single emitter address
* Fix lint error
* Using the wrong delete primative
Change-Id: I80d5294c17279d4e49220d81807e5964a5591721
The per-watcher channels for reobservation requests don't have a
buffer, which means that if sending on any one channel blocks then _all_
reobservation requests get blocked. Make the send fallible and log if
it blocks instead.
We currently run the cleanup loop every 30 seconds, which means that
once 5 minutes have passed for an observation without quorum we will
send out re-observation requests to the p2p network every 30 seconds.
This is a bit excessive so limit sending these requests out to once
every 5 minutes.
Chirantan Ekbote
Csongor Kiss
Developer Experience team at Tendermint
Paul Noel
Ali Behjati
bruce-riley
Csongor Kiss
Evan Gray
Bruce Riley
kev1n-peters
Josh Siegel
Hendrik Hofstadt
ckeun
Paul Noel
Jeff Schroeder
Jonathan Claudius
tbjump
Kevin Peters