Content pfp
Content
@
0 reply
0 recast
2 reactions

Wesley— oss/acc pfp
Wesley— oss/acc
@wslyvh.eth
What are the best ways to keep (offchain) profile/metadata in sync with a smart contract? Like a tokenuri with metadata.json on IPFS.. The data could get updated frequently tho and I'd like to avoid updating the hash every time. Any suggestions?
5 replies
0 recast
3 reactions

Andrew pfp
Andrew
@andrewgoldsky
Goldsky has a product called Mirror that lets you stream onchain data directly into your db with offchain data. Should be pretty easy to build a workflow that ties metadata back to chain events (in realtime). Goldsky.com
1 reply
0 recast
2 reactions

avi pfp
avi
@avichalp
how frequent do you expect data to change?
1 reply
0 recast
1 reaction

shazow pfp
shazow
@shazow.eth
I just store the block number since my last cache and replay the log events since then to catch up. I even do that on the client side, since it's one query and pretty quick if cache is recent enough.
1 reply
0 recast
1 reaction

ukstv pfp
ukstv
@
A month old, but still a valid question. One approach is to use Ceramic for storage. Another approach is to use CCIP aka EIP-3668, similar to how offchain ENS works.
1 reply
0 recast
1 reaction

Liang /degencast SOON🎩 pfp
Liang /degencast SOON🎩
@liang
whats the use case? can you thegraph?
1 reply
0 recast
0 reaction