A place for talking about the Ethereum Virtual Machine on Farcaster.

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?

Events @Ethereum 🦄 Indie Hacker 🛠️

A doodler and computerer. I like permissive/permissionless open source, smart contracts, p2p systems, room-scale VR, and NixOS.

shazow.net

Currently: WhatsABI

Ah thought you meant you need to track onchain updates for offchain stuff, not the other way around.

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)

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.

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

Bringing Decentralized AI to the People.

Global Director of Marketing @gaianet 🌱 
Formerly Marketing Lead @goldskyio ☀️

Looks interesting, but probably a bit overkill..

It's a simple project registry, where owners can update their info, metadata and post updates. Only the project Id needs to be onchain. Everything else can be offchain - as long as it's somehow linked. I don't want to send txs for every update

Still haven't been able to rive in yet. So still relevant 😄

Thanks! Both would work I guess. Will keep you posted

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.

frequent metadata updates is something we had in mind while building tableland. you may want to checkout tableland.xyz

Depends. Consider it to be a project registry, where owners can update info, metadata but also post updates

how frequent do you expect data to change?

building degencast.wtf /degencast, ex-synfutures, binance, bitmain

Chiang Mai, Mueang Chiang Mai District, Chiang Mai, Thailand

See https://warpcast.com/wslyvh.eth/0x459251