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
Related to hashgraph/hedera-services#3640
Each contract that attempts (successfully or not) to deploy another contract should have its nonce field incremented.
This can happen multiple times during a top-level transaction execution and this information needs to be externalized by the consensus nodes to the mirror nodes in the transaction records.
Solution: add a map [ContractId: nonce] in message ContractFunctionResult that will be populated in the top-level transaction records.
The text was updated successfully, but these errors were encountered:
Related to hashgraph/hedera-services#3640
Each contract that attempts (successfully or not) to deploy another contract should have its nonce field incremented.
This can happen multiple times during a top-level transaction execution and this information needs to be externalized by the consensus nodes to the mirror nodes in the transaction records.
Solution: add a map [ContractId: nonce] in
message ContractFunctionResult
that will be populated in the top-level transaction records.The text was updated successfully, but these errors were encountered: