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
Using different SDKs with WalletConnect, it's impossible to provide a consistent JSON representation of a Receipt or Record.
.stringify and .marshal in javascript and golang output differing results.
Solution
Add a toJson method to receipt and record which convert the object to a consistent JSON format (using the JS stringify as a reference) so that all SDKs can generate identical Json.
Alternatives
Let developers write their own equivalence libraries which is likely to go wrong with changes to receipts/records.
The text was updated successfully, but these errors were encountered:
Problem
Using different SDKs with WalletConnect, it's impossible to provide a consistent JSON representation of a Receipt or Record.
.stringify and .marshal in javascript and golang output differing results.
Solution
Add a toJson method to receipt and record which convert the object to a consistent JSON format (using the JS stringify as a reference) so that all SDKs can generate identical Json.
Alternatives
Let developers write their own equivalence libraries which is likely to go wrong with changes to receipts/records.
The text was updated successfully, but these errors were encountered: