node
node copied to clipboard
zeta-chain
ZetaChain’s blockchain node and an observer validator client
**Describe the Issue** Some different tasks that can be addresses in the same PR to make the naming in ZetaClient more consistent - We use “ob” for many variable name....
Add an option to the e2etest to use data exported from a mainnet or testnet node.
**Describe the Issue** - Add a new docker image in the localnet docker compose, representing an IBC enable chains - Whitelist the chains and add token deposit and withdraw tests
**Describe the Issue** - Process inbounds for IBC transfers performed to the module account - Send IBC transfers on new outbounds creation - Confirm outbounds upon acknowledgement reception More details...
**Describe the Issue** We currently always interact with `observer` related functionality When introducing https://github.com/zeta-chain/node/issues/2129 we might not want to interact with observer related code. We should check the related transport...
**Describe the Issue** Currently all chains use the observer/signer set to transport messages with the external chains. As we will enable IBC for some chains, and there might be other...
Each zetaclientd node needs a reliable RPC for each external chain and if that RPC fails it needs to connect a new one. If zetaclient can support multiple RPCs per...
`UpdateConfigFromCore` currently considers there is a single Bitcoin chain supported in ZetaClient and a chain is now a Bitcoin chain is an EVM chain ``` if common.IsBitcoinChain(coreParam.ChainId) { newBTCParams =...
**Describe the Issue** To outline this is the blockchain repository, and because it contains the node binary but also ZetaClient and the E2E testing suite
The logic to select which type of transaction to be signed is using a long chain of else if's. It is difficult to read or understand which tx type is...
Metadata
Owner
Metadata
ZetaChain’s blockchain node and an observer validator client