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
{{ message }}
This repository has been archived by the owner on Jan 9, 2020. It is now read-only.
If profile JSON's would be stored in RAM, it would make it way easier to fetch Profile data directly on chain.
It does cost a bit of extra RAM to store this data, however being able to fetch Profile directly from the custodian contracts prevents hosting an off-chain solution simply to fetch JSON files.
Maybe vRAM 😉 ?
The text was updated successfully, but these errors were encountered:
Even if the JSON data has different standards or changes over time, it's not a big deal, you can handle most of the edge cases directly in the UI with some simple logic.
the reason why we pass the json data through chain and capture it via the action data is to save ram and to make the data queryable in our off chain database.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
If profile JSON's would be stored in RAM, it would make it way easier to fetch Profile data directly on chain.
It does cost a bit of extra RAM to store this data, however being able to fetch Profile directly from the custodian contracts prevents hosting an off-chain solution simply to fetch JSON files.
Maybe vRAM 😉 ?
The text was updated successfully, but these errors were encountered: