Skip to content
This repository has been archived by the owner on Jan 9, 2020. It is now read-only.

stprofileuns stored in RAM or vRAM #14

Open
DenisCarriere opened this issue Mar 16, 2019 · 3 comments
Open

stprofileuns stored in RAM or vRAM #14

DenisCarriere opened this issue Mar 16, 2019 · 3 comments

Comments

@DenisCarriere
Copy link
Contributor

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 😉 ?

@piecesnbits
Copy link
Collaborator

I totally agree.

@DenisCarriere
Copy link
Contributor Author

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.

@piecesnbits
Copy link
Collaborator

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 free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants