node icon indicating copy to clipboard operation
node copied to clipboard

ZetaChain’s blockchain node and an observer validator client

Results 454 node issues
Sort by recently updated
recently updated
newest added

**Describe the Issue** The ZRC20 staking feature would require to use a conversion rate for ZRC20s. The first and simplest solution is to set this values from authority messages. Since...

m:crosschain
m:authority

**Describe the Issue** https://github.com/zeta-chain/node/pull/2118#discussion_r1605252048 It doesn't seem this structure is still used, and can be removed from the codebase

m:crosschain
code-quality

**Describe the Issue** It doesn't seem this command is used anymore and can be removed

codebase-quality

**Describe the Issue** Add more linting rules and fix the errors that would arise from it. ``` - gosimple # Detect simpler code constructs - staticcheck # Provides robust checks...

code-quality

So that we can run this method as a fungible module: https://github.com/zeta-chain/protocol-contracts/blob/211e1d1303ec9b17c54dd015449852d1d240bf4f/contracts/zevm/SystemContract.sol#L167-L173 We talked about including this in v17.

m:fungible

The goal of this epic is to group the necessary tasks to complete to integrate the block header proof system ready to be used with adding trackers. It includes refactoring...

epic
m:lightclient

**Describe the Issue** We currently post block headers in the watch inbound routine for the observer client. This is confusing. This logic should be moved into it's own routine. Eventually...

zetacore

**Describe the Issue** Here is the [current code](https://github.com/zeta-chain/node/blob/feat-observe-blob-transaction/zetaclient/evm/evm_client.go#L1136) with the `TODO` notation. **Expected Outcome** Instead of embedding block header posting logic in function `observeTssRecvd`, we should have a separate/dedicated job...

**Describe the Issue** As part of general convention for messages involving observer voting: `MsgVoteX`

m:crosschain

Describe the Issue Make a search of methods marked as deprecated and remove those before v18 We will also need to remove the previous migration code