DePIN

arweave

Unlike DeFi, a significant portion of DePIN activity can happen offchain ...and unless the DePIN has implemented and is reaching some forms of consensus, I would argue that DePINs need DA (data availability) as much as L2s

🤔 We currently use /arweave for this in the M3tering Protocol, a permanent log of all activity in the protocol, but for must projects (including M3tering), I think a @celestia or EigenDA might suffice.

The first modular blockchain network that makes it easy for anyone to securely launch their own blockchain. Build whatever 👉 https://celestia.org/build/

Depin Dev hosting /m3ter-heads & building M3tering protocol on Gnosis.
Spread the word; P2P energy is now as real as P2P money
https://m3tering.whynotswitch.com

Agree to a degree. That’s why we are using consensus behind our DePIN, but even for our gaming use case, we still need decentralized persistence.

Tashi Protocol

CTO of Tashi Protocol https://tashi.gg | Founder of LaunchBadge | Founding team of Hedera Hashgraph | Father, husband, Christian, BJJ blue belt, Army vet

Interesting 🤔 
How is consensus used in /tashi protocol? And why is it necessary to persist the data even after consensus has been reached?

Ahh, that is an interesting approach 
It's almost like it's a proper rollapp 😃

- state mutations or snapshot is persisted on a form of DA layer
- it can wind down and wind up at will, just like L2s were conceived to do 🤔

Do you have technical documentation I could check out. 
...and source codes too

Consensus doesn’t require persistence, but games may. Since /tashi only works while there are sufficient consensus nodes, we need to be able to persist game state and reload when the session restarts.