node: Fix formatting with go 1.19
Produced by running `goimports -w .` in the node/ directory.
This commit is contained in:
parent
9e92f9dbbf
commit
d0eb7dd96c
|
@ -29,7 +29,7 @@ var (
|
|||
// MaxGuardianCount specifies the maximum number of guardians supported by on-chain contracts.
|
||||
//
|
||||
// Matching constants:
|
||||
// - MAX_LEN_GUARDIAN_KEYS in Solana contract (limited by transaction size - 19 is the maximum amount possible)
|
||||
// - MAX_LEN_GUARDIAN_KEYS in Solana contract (limited by transaction size - 19 is the maximum amount possible)
|
||||
//
|
||||
// The Eth and Terra contracts do not specify a maximum number and support more than that,
|
||||
// but presumably, chain-specific transaction size limits will apply at some point (untested).
|
||||
|
|
|
@ -11,7 +11,6 @@ import (
|
|||
// Wormhole guardian nodes.
|
||||
//
|
||||
// This list is duplicated a couple times across the codebase - make to to update all copies!
|
||||
//
|
||||
var PublicRPCEndpoints = []string{
|
||||
"https://wormhole-v2-mainnet-api.certus.one",
|
||||
"https://wormhole.inotel.ro",
|
||||
|
@ -58,7 +57,6 @@ type EmitterInfo struct {
|
|||
//
|
||||
// Wormhole is not permissioned - anyone can use it. Adding contracts to this list is
|
||||
// entirely optional and at the core team's discretion.
|
||||
//
|
||||
var KnownEmitters = buildKnownEmitters(knownTokenbridgeEmitters, knownNFTBridgeEmitters)
|
||||
|
||||
func buildKnownEmitters(tokenEmitters, nftEmitters map[vaa.ChainID]string) []EmitterInfo {
|
||||
|
|
Loading…
Reference in New Issue