node
node copied to clipboard
ZetaChain’s blockchain node and an observer validator client
**Describe the Issue** Investigate Solana integration with the TSS Implement a new version for chain observer and signer
Depends on: https://github.com/zeta-chain/node/issues/2128 Add a IBC middleware https://ibc.cosmos.network/main/ibc/middleware/develop.html for ibc-crosschain to hook into ibc-transfer Follow: https://ibc.cosmos.network/main/ibc/middleware/develop.html
**Describe the Issue** Integrate Polygon blockchain. Enable Amoy testnet Investigate possibility of regular EVM integration with the TSS.
**Describe the Issue** Integrate Base blockchain. Investigate possibility of regular EVM integration with the TSS. We might also investigate for new solutions to integration OP chains with more scalability.
**Describe the Issue** Currently rpc folder in repo is forked from ethermint. Now when there is ethermint fork, changes can be moved there and folder can be deleted from main...
**Describe the Issue** Currently cosmos sdk 0.47.x is used, and priority mempool doesn't have a way to hook in custom signer extractors. This seems to be available on cosmos-sdk current...
**Describe the Issue** Here is an example of inbound cctx: https://explorer.zetachain.com/cc/tx/0x000abb86711bd720ac2eb5cc00cdd602ad56a2c21f8f64e7a21bec781f13b241 The receiver shown in ZetaScan is an irrelevant address:`0xe9d6b4Db5EDFD9e6b779AEdA6b5dbc6dCEFCEFCe`  The ture intended receiver is `0x6dA0217f2eA3ea7aA128bc7878507EdbD3847bBc` in the Blockscout:...
We build our release binaries for ubuntu/glibc. This means that we cannot use our release binaries in the alpine docker containers. We should just use ubuntu everywhere for consistency.
**Describe the Issue** - The EVM client and Bitcoin client structs have common data fields which can be grouped into a `BaseClient` struct. `BaseClient` can then be reused by EVM...
It seems like it's been very easy to break the upgrade tests. We need to run the upgrade tests in PR/mergequeue CI.