Add relay service listeners and handlers #56
Conversation
packages/relayer/README.md
Outdated
|
|
||
| ### Redis | ||
|
|
||
| We use redis two track two things |
There was a problem hiding this comment.
| We use redis two track two things | |
| We use redis to track two things |
packages/relayer/src/evm.ts
Outdated
| contractInstance: any; | ||
| validatorAddress: string; | ||
| bridgeAddress: string = Config.address; | ||
| bridgeHash: string = Config.brigdgeHash; |
packages/relayer/start.ts
Outdated
|
|
||
| const startQueue = async () => { | ||
| const qname = Config.address; | ||
| console.log("This is the quee", qname); |
There was a problem hiding this comment.
| console.log("This is the quee", qname); | |
| console.log("This is the queue", qname); |
| Functionality to listen for events and relay them across chains | ||
|
|
||
| ### Redis | ||
|
|
There was a problem hiding this comment.
Please add instructions on Redis version to use, as well as configuration like the port here.
Add instructions on what version of TS node to use.
A longer description of the Relayer service is missing here, all instructions on how to run the service should be able to be found in this file.
Provide clear instructions on how to provide the Bridge Address.
|
|
|
Does not use current childchain start script
|
|
i've executed all steps as described above. I see the script producing transactions: but console.log is never triggered: |
|
getting negative block numbers suddenly. stopped everything and did a redeployment, still same. |
|
Negative block numbers is because we don't reset the redis db when service stops Forked out the bug since its taking long #59 |
How to test
ts-node deploy.ts. Copy value of address from address.json to key address in config.jsonts-node start.ts.ts-node /src/utils/transaction.ts. Will create 3 separate burn events that should be captured and recordedCloses #26 Closes #40