Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

feature: support for multiple web3 providers #72

Merged
merged 6 commits into from
Sep 6, 2023
Merged

feature: support for multiple web3 providers #72

merged 6 commits into from
Sep 6, 2023

Conversation

lucasmenendez
Copy link
Collaborator

@lucasmenendez lucasmenendez commented Sep 1, 2023 •
edited
Loading

Explained in #58

Changes:

  • Update database schema and API endpoints to include the id of the chain of each token
  • Delete chain id from service matadata on the database and remove the checks about the chain id
  • Update the scanner and token related API endpoints to use the web3 provider associated to each token
  • Handle a list of supported web3 providers as cmd/census3 entrypoint flag
  • New endpoint (GET /api/info) to get api related information such as supported chain ids
  • Include support for list of web3 providers on env file and docker-compose.yml

@lucasmenendez
* Update datase schema and API endpoints to include the id of the cha…
f56ac6e 
…in of each token

* Delete chain id from service matadata on the database and remove the checks about the chain id
* Update the scanner and token related API endpoints to use the web3 provider associated to each token
* Handle a list of supported web3 providers as cmd/census3 entrypoint flag
@lucasmenendez lucasmenendez added the enhancement New feature or request label Sep 1, 2023
@lucasmenendez lucasmenendez added this to the v0.2.0 milestone Sep 1, 2023
@lucasmenendez lucasmenendez self-assigned this Sep 1, 2023
@lucasmenendez lucasmenendez linked an issue Sep 1, 2023 that may be closed by this pull request
Support multiple web3 providers and networks #58
Closed
@lucasmenendez lucasmenendez marked this pull request as ready for review September 1, 2023 16:08
p4u
p4u reviewed Sep 5, 2023
View reviewed changes
.env Outdated Show resolved Hide resolved
p4u
p4u reviewed Sep 6, 2023
View reviewed changes
state/providers.go Show resolved Hide resolved
p4u
p4u reviewed Sep 6, 2023
View reviewed changes
state/providers.go Show resolved Hide resolved
@lucasmenendez lucasmenendez merged commit 8d9fd54 into main Sep 6, 2023
6 checks passed
@lucasmenendez lucasmenendez deleted the feature/multiple_web3_providers branch September 6, 2023 08:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@p4u p4u p4u approved these changes

Assignees

@lucasmenendez lucasmenendez

Labels
enhancement New feature or request
Projects
None yet
Milestone
v0.2.0
Development

Successfully merging this pull request may close these issues.

Support multiple web3 providers and networks
2 participants
@lucasmenendez @p4u