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.

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

Multi contract support for dApp and backend #368

Open
ashishjur opened this issue Jul 31, 2020 · 0 comments
Open

Multi contract support for dApp and backend #368

ashishjur opened this issue Jul 31, 2020 · 0 comments
Assignees
Labels
enhancement Improvement on existing feature

Comments

@ashishjur
Copy link

Refactor dApp and backend to support contact versioning (address) as the first-class citizen.

Expected Behavior

dApp and backend should support multiple versions (contract address) of the same contract (asset name). This means that every data point related to blockchain always has its contract address coupled with it.

  1. All the tables on the backend will have a column for contract address if it represents data point coming from blockchain
  2. All the Connex calls in the dApp will be made to a specific contract address based on the same data.

Current Behavior

  1. dApp only supports one contract address per asset.
  2. Backend loses ref to original smart contract which generated that data point in most of the cases.

This is a futuristic issue. Will be addressed whenever the need arises

@ashishjur ashishjur added the enhancement Improvement on existing feature label Jul 31, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Improvement on existing feature
Projects
None yet
Development

No branches or pull requests

3 participants