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

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

Wesley— oss/acc pfp
Wesley— oss/acc
@wslyvh.eth
Depends. Consider it to be a project registry, where owners can update info, metadata but also post updates
1 reply
0 recast
0 reaction

avi pfp
avi
@avichalp
frequent metadata updates is something we had in mind while building tableland. you may want to checkout tableland.xyz
2 replies
0 recast
2 reactions

Danny pfp
Danny
@ds
Piqued my interest. How is decentralized? I see you can execute operations on chain, but are queries executed onchain? Wouldn’t block gas limits limit scale there? My gut tells me this is distributed.
2 replies
0 recast
1 reaction

Wesley— oss/acc pfp
Wesley— oss/acc
@wslyvh.eth
Following up on that.. Is there an overview or any stats on network, health, activity? E.g. How many validators are running? Is it just tableland (for now)? Are there any explorers to see network activity?
1 reply
0 recast
0 reaction

Wesley— oss/acc pfp
Wesley— oss/acc
@wslyvh.eth
And what are the incentives for running a validator? If I understand it correctly, mutations happen on the host chain. How does the tableland protocol or validators earn fees? Or what's the business model?
1 reply
0 recast
0 reaction

avi pfp
avi
@avichalp
yup, currently there is only the tableland validator. we are trying to figure out the incentive mechanism to add more validators to the network
0 reply
1 recast
2 reactions