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
Recently, we've faced a scenario where just changing the version of a component (Rust, in this case) had the potential to disrupt our smart contract execution - cf. #292 (comment). Such cases can lead to disastrous problems if not detected early.
Proposal
To ascertain the proper functioning of the Smart Contracts within the OKP4 blockchain, I propose the addition of a new CI workflow designed to detect and resolve such disruption early in the development process. This workflow could incorporate a variety of tests, including on-chain deployment tests, as well as certain smart contract calls to validate the correct interaction of the contracts amongst themselves and with the entire blockchain.
The text was updated successfully, but these errors were encountered:
Background
Recently, we've faced a scenario where just changing the version of a component (Rust, in this case) had the potential to disrupt our smart contract execution - cf. #292 (comment). Such cases can lead to disastrous problems if not detected early.
Proposal
To ascertain the proper functioning of the Smart Contracts within the OKP4 blockchain, I propose the addition of a new CI workflow designed to detect and resolve such disruption early in the development process. This workflow could incorporate a variety of tests, including on-chain deployment tests, as well as certain smart contract calls to validate the correct interaction of the contracts amongst themselves and with the entire blockchain.
The text was updated successfully, but these errors were encountered: