Philip Obiora
Philip Obiora
I would like to contribute on this aspect
Just created a Pr on this
is this issue still pending ? I would like to contribute if it is
@ptdatta did you tidy the go modules as you changed the go version
@awrichar is tis issue still open ?
Hello @tomponline, @ru-fu please I would like to work on this issue
Hello @tomponline, So i observed one has to restart a container instance before, one could get the actual logs from the `lxc console --show-log` , without getting the error message...
@nguyer I have been able to use the `firefly-signer` library to handle validation and parsing. what do you think of the changes I made ?
@nguyer please i would like you to review my code , i am still trying to figure out why the checks are failing i was able to tackle the compilation...
@nguyer, these are error messages i got from the e2e tests `DEBUG evmconnect: FF21040: Invalid listener options: FF23036: Invalid event filter: {"address":"783688521890864681654499112172336319967459785509","event":{"anonymous":false,"inputs":[{"indexed":true,"internalType":"address","name":"operator","type":"address"},{"indexed":true,"internalType":"uint256","name":"type_id","type":"uint256"},{"indexed":false,"internalType":"bytes","name":"data","type":"bytes"}],"name":"TokenPoolCreation","type":"event"}}:` It seems the error is related to an...