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
We still need to have the populateTransactionPredicateData in place because there are some scenarios where predicate-fetched resources will not include the predicate and predicateData.
I believe this mostly happens within wallet connectors, where the connector Account is instantiated using the predicate address, and the predicate is instantiated only before submitting the TX.
The text was updated successfully, but these errors were encountered:
nedsalk
changed the title
Add predicateData Bytes To Predicate Respources And Inputs
Add predicateData Bytes To Predicate Resoources And Inputs
May 24, 2024
nedsalk
changed the title
Add predicateData Bytes To Predicate Resoources And Inputs
Add predicateData Bytes To Predicate Resources And Inputs
May 24, 2024
Now that we have dropped
V0
encoding logic, we can safely add thepredicateData
to the predicate resources and inputs since there is no need to handle the bytes padding within predicate arguments to handle the dynamic size of the array of policies.We still need to have the
populateTransactionPredicateData
in place because there are some scenarios where predicate-fetched resources will not include thepredicate
andpredicateData
.I believe this mostly happens within wallet connectors, where the connector
Account
is instantiated using the predicate address, and the predicate is instantiated only before submitting the TX.The text was updated successfully, but these errors were encountered: