You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
All the tables on the backend will have a column for contract address if it represents data point coming from blockchain
All the Connex calls in the dApp will be made to a specific contract address based on the same data.
Current Behavior
dApp only supports one contract address per asset.
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
The text was updated successfully, but these errors were encountered:
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.
Current Behavior
This is a futuristic issue. Will be addressed whenever the need arises
The text was updated successfully, but these errors were encountered: