Skip to content

Add ability to use LoomProvider with the /eth endpoint#299

Merged
enlight merged 39 commits intomasterfrom
loom-provider-eth-endpoint
Sep 24, 2019
Merged

Add ability to use LoomProvider with the /eth endpoint#299
enlight merged 39 commits intomasterfrom
loom-provider-eth-endpoint

Conversation

@redben
Copy link
Copy Markdown
Contributor

@redben redben commented Aug 15, 2019

No description provided.

@redben redben marked this pull request as ready for review August 20, 2019 13:30
Comment thread src/helpers.ts Outdated
Comment thread src/tests/helpers.ts Outdated
Comment thread src/tests/helpers.ts Outdated
Comment thread src/tests/e2e_tests.ts Outdated
Comment thread src/tests/e2e/loom-provider-web3-tests.ts Outdated
Comment thread src/tests/e2e/loom-provider-web3-tests.ts Outdated
Comment thread src/loom-provider.ts Outdated
Comment thread src/loom-provider.ts Outdated
Comment thread src/client.ts Outdated
Comment thread src/internal/ws-rpc-client.ts Outdated
Comment thread src/client.ts Outdated
redben added 2 commits August 21, 2019 17:40
- remove Client.readClient
- Client.sendWeb3MsgAsync
- Client.sendWeb3MsgAsync revert code in getevmfilterchanges
- update LoomProvider accordingly
Comment thread src/helpers.ts Outdated
Comment thread src/tests/e2e/loom-provider-web3-tests.ts Outdated
@redben
Copy link
Copy Markdown
Contributor Author

redben commented Aug 28, 2019

One test still fails... didn't we disable blueprint?

Calls via HTTP

contractAddr = await client.getContractAddressAsync('BluePrint')
>> Error: Failed to resolve contract address

@redben redben requested a review from enlight August 29, 2019 16:26
@enlight enlight changed the title Loom provider eth endpoint Add ability to use LoomProvider with the Loom /eth endpoint Sep 24, 2019
@enlight enlight changed the title Add ability to use LoomProvider with the Loom /eth endpoint Add ability to use LoomProvider with the /eth endpoint Sep 24, 2019
@enlight
Copy link
Copy Markdown
Contributor

enlight commented Sep 24, 2019

This is an intermediate step that will allow us to start using the Web3 JSON-RPC methods provided by Loom nodes on the /eth endpoint. The end goal is to switch over to a completely new version of LoomProvider that's being built in #303 but that still requires some work in loomchain, as well as extensive testing.

One annoying limitation of the changes in this PR is that a single Client instance can't be used to interact with both the /eth and /query endpoints, so any one Client instance can only interact with EVM contracts, or Go contracts, but not both at once.

Copy link
Copy Markdown
Contributor

@enlight enlight left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@enlight enlight merged commit 1123281 into master Sep 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants