v1.0.11

modify lock config

v1.0.10

update:
github.com/ethereum/go-ethereum v1.10.8 => v1.10.9
github.com/celer-network/goutils v0.1.34 => v0.1.37

v1.0.9

Modify transfer in report related chainId.
No much effect.

v1.0.8

update

v1.0.7

update

v1.0.6

modify confirm check

v1.0.5

Modify config and version check

v1.0.4

（1）Update github.com/celer-network/goutils -> v0.1.34
（2）We add new config "transactorConfig" and “watchConfig”. It will help to monitor on-chain event, especially for arbitrum.
------ Please use our recommend config for each chain, it will raise your transfer success rate.
------ https://github.com/celer-network/cBridge-node/blob/main/env/config.json.
------ You can find the recommended chain config by chainId in this file. And more detail of the config is already updated in README.
Example:

"transactorConfig": {"gasLimit": 3200000,"addGasGwei": 2,"addGasEstimateRatio": 1.0}
"watchConfig": {"pollingInterval": 10,"maxBlockDelta": 1000000,"blockDelay": 80,"forwardBlockDelay": 500}

v1.0.3

（1）Update github.com/celer-network/goutils -> v0.1.33
（2）Update github.com/ethereum/go-ethereum ->  v1.10.8
（3）As it seems not safe enough, we remove key store config file and key store password from config.json.
          Now, please use the new command below(add "-ks" and "-pwddir"). You can also find the detail in Readme

         ./cbridge-node -p 8088 -c ./env/config.json -ks ./env/ks/yourKeyStore.json -pwddir ./env/ks/yourPasswordFile.

（4）Add WaitMined for approving allowance when start your relay-node.
          This will guarantee that the approved allowance will succeed and will not block the relay-node to do TransferIn/Confirm/Refund.

v1.0.2

1. Fix monitor will be blocked by getting transactions by hash failed.
2. Check src chain tx confirm before refund dst chain tx refund. If the src chain tx is confirmed, then confirm dst chain tx instead of refunding it. (corner case, and will be fix by go util monitor upgrade.)
3. Submit version when register to gateway, gateway will reject relay node with invalid version.
4. Please add a new index on transfer db table. "CREATE INDEX IF NOT EXISTS transfer_related_tid_idx ON transfer (relatedtid);"