Conversation

Replying to
I think Web3 is waiting for its cgi moment. Web1 went from memoryless to stateful over ~5 years with cookies+cgi. Web3 is coming from the other extreme, from only immutable memory towards stateful.
Quote Tweet
Replying to @vgr
@ricmac’s Web History Project is the best thing like this that I am aware of webdevelopmenthistory.com/1993-cgi-scrip
1
35
It’s not just gas fees. The whole persistence model is like eeprom. Write operations are like flashing in embedded programming. Need a throwaway state on top that gives up some trustless verifiability for convenience for the less critical stuff.
1
24
Like if you wanted to use NFTs as tokens in a decentralized wallet-to-wallet game, where do hold game state? In a Web2 style db layer? That seems wrong. But it also seems silly to store game state on chain.
2
19
Okay fine not necessarily state, but *some* controlled transient persistence model that’s decoupled from browser session but is less expensive/permanent than on-chain, while still being Web3 native paradigm-wise.
Quote Tweet
State is usually bad. What you really want in most situations are values and references (see infoq.com/presentations/ and infoq.com/presentations/).
Show this thread
3
17
This seems like the beginnings of an answer, though you need opensea to be a TTP temporarily. It’s not quite p2p decentralized state.
Quote Tweet
Replying to @vgr
you store it off chain with each user signing, and if match, execute on chain. That's how opensea works under the hood: docs.opensea.io/reference/term
1
7
This keeper model seems more in harmony with Web3 architectural vibes
Quote Tweet
Replying to @_callil and @vgr
need something like keeperDAO: docs.keeperdao.com/reference/#wha @vgr i think you'd like this concept of keepers
1
8
Well, I guess I had to dabble in at least 1 memecoin. Sent 0.042E (about $200 rn) to the project that's trying to buy a copy of the US constitution at auction. tx succeeded and I claimed my tokens, but I don't see tx or message on the juicebox feed yet 🧐
5
23