Liang @ degencast.wtf 🎩
@degencast.eth
gm! thought on ceramic.network ?
4 replies
0 recast
0 reaction
Tayyab - d/acc
@tayyab
Great idea. Bad documentation. I think a Cosmos for Ceramic will be more successful. You need something a bit more customizable based on your data type. Also, it only enforces data types but not other “read/write” permissions. I like Tableland.xyz
6 replies
0 recast
0 reaction
Liang @ degencast.wtf 🎩
@degencast.eth
tableland access control is definitely superior than ceramic. just don't like the fact write need to be onchain.. https://i.imgur.com/NKI1rnr.jpg
1 reply
0 recast
0 reaction
cjqf
@carsonfarmer
Hey, member of the tableland team here. Would love to hear your thoughts on alternatives to on-chain mutations. We've been exploring alternatives like ipfs hashes and other forms of verifiable off-chain data "dumps". Would love to hear your usecases for this type of thing!
4 replies
0 recast
0 reaction
Liang @ degencast.wtf 🎩
@degencast.eth
data need to be: 1. verifieable (self authenticated as coming from a certain user) 2. availabile 3. consistent 4. could be private or public
1 reply
0 recast
0 reaction
cjqf
@carsonfarmer
Yeh nice to have very specific requirements like this! I think Tableland hits all of those, save for maybe "private" per se. We made a conscious decision to leave encryption/privacy to the application layer, and I'm really happy with this tradeoff.
1 reply
0 recast
0 reaction
cjqf
@carsonfarmer
But having a blockchain in the mix makes data availability and consistency a breeze, so this is pretty nice. Frees up engineering creativity for much important problems like verifiability etc
2 replies
0 recast
0 reaction
Liang @ degencast.wtf 🎩
@degencast.eth
yeah. totally. data on-chain solves 123 easily. But performance is limited by blockchain as well for sql write right query? I would expect read to be fast since it's offchain or does read has access control as well and thus need to hit rpc node for every read/write sql query?
1 reply
0 recast
0 reaction
cjqf
@carsonfarmer
no read does't need to go thru rpc. open network, so access control on reads would just be lying to ourselves 😜, so it is quite fast. And actually, writes are pretty fast when pushing via rollups/L2s.
1 reply
0 recast
0 reaction
Liang @ degencast.wtf 🎩
@degencast.eth
argh yes. rollups would fix that. especially with data availability layer offchain
0 reply
0 recast
0 reaction
