Skip to content

Multi contract support for dApp and backend #368

@ashishjur

Description

@ashishjur

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

Metadata

Metadata

Labels

enhancementImprovement on existing feature

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions