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
For now, the inherit constraints are required and explicit about the rules to accept a new transaction.
However, this can be annoying and slow down adoption of smart contract on Archethic.
We should propose a way to avoid the need of explicit rules, which are already in the actions block of the smart contract.
This is related to #925 (validation nodes will fetch the previous transaction to get the smart contract code and try to expect the next one to match the incoming transaction).
The inherit conditions could still be used for other purposes, such as origin family constraints, inherit exceptions (authorizations to upgrade code), etc...
The text was updated successfully, but these errors were encountered:
For now, the inherit constraints are required and explicit about the rules to accept a new transaction.
However, this can be annoying and slow down adoption of smart contract on Archethic.
We should propose a way to avoid the need of explicit rules, which are already in the actions block of the smart contract.
This is related to #925 (validation nodes will fetch the previous transaction to get the smart contract code and try to expect the next one to match the incoming transaction).
The inherit conditions could still be used for other purposes, such as origin family constraints, inherit exceptions (authorizations to upgrade code), etc...
The text was updated successfully, but these errors were encountered: