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
2 reactions

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

Wesley— oss/acc pfp
Wesley— oss/acc
@wslyvh.eth
Not sure I understand. You store the block nr client side to fetch latest log updates? But that still means you're relying on onchain actions, right? I'm building a project registry, where it's mainly the project Id that is important on chain. Owners should be able to edit, post updates/milestones, etc. (offchain)
1 reply
0 recast
0 reaction

shazow pfp
shazow
@shazow.eth
Ah thought you meant you need to track onchain updates for offchain stuff, not the other way around.
1 reply
0 recast
1 reaction

Wesley— oss/acc pfp
Wesley— oss/acc
@wslyvh.eth
Got it. I thought I was missing something 😅 Thanks tho!
0 reply
0 recast
0 reaction