relayer ropsten network integration not working about gravity-bridge

[denalimarsh]

Instead of using provider wss://ropsten.infura.io/, can you attempt to start the relayer with provider wss://ropsten.infura.io/ws as described in section 'Running the relayer service' of the README?

Here's a screenshot which shows the issue reproduced, and then resolved by using the recommended provider:

Thank you for the screenshots which allowed for a quick diagnosis of this issue. Please let us know if you continue having difficulty with the relayer service.

[Arunhfb]

Thank you for your quick response.Its working fine now.But i saw there is some issue with the truffle_config.js it doesnt inject the .env parameters properly.So to make things work i hard coded the parameters i.e. MNEMONIC & INFURA_PROJECT_ID into the js file directly.

And also in the below command it accepts only cosmos_recipient addresses or it can accept any other customised prefix addresses?

yarn peggy:lock --network ropsten [HASHED_COSMOS_RECIPIENT_ADDRESS] [TOKEN_CONTRACT_ADDRESS] [WEI_AMOUNT]

[Arunhfb]

I tried doing transaction after starting automatic relayer service but facing issues.I have attached screenshot for your reference.

[denalimarsh]

I've opened PR #85 which addresses both issues. Once it's merged, you'll be able to send the lock transaction with the following process:

1. Migrate the contracts to the ropsten network with yarn migrate --network ropsten
2. Send lock transaction to contract with yarn peggy:lock [HASHED_COSMOS_RECIPIENT_ADDRESS] [TOKEN_CONTRACT_ADDRESS] [WEI_AMOUNT]

As the production version of the Bridge currently supports only Ethereum -> Cosmos transfers, only hashed Cosmos recipient addresses are valid. For your initial test of the system, I recommend using the testuser address from the Bridge blockchain. You can get the testuser's address in plain text with the command ebcli keys show testuser -a.