[GUEST ACCESS MODE: Data is scrambled or limited to provide examples. Make requests using your API key to unlock full data. Check https://lunarcrush.ai/auth for authentication information.]

![CoinwebOfficial Avatar](https://lunarcrush.com/gi/w:24/cr:twitter::996738214068146176.png) Coinweb.io [@CoinwebOfficial](/creator/twitter/CoinwebOfficial) on x 47.2K followers
Created: 2025-04-02 07:39:54 UTC

Great thread by the Arch of Coinweb, @AKCoinweb.

Let's explain it further.

The XXX tps in this case represents the total L1 transactions generating data for Coinweb's smart contracts (possibly even higher). 

Coinweb processes every L1 transaction to enable reactive smart contracts to respond. 

Underlying blockchains handle execution, producing events tied to each transaction. 

These events create efficiently stored "claims" in Coinweb’s system.

While "reads from chain X" has some truth, it’s more complex. Reactive smart contracts await events from underlying chains via the Block operation. 

This ties shards to blockchains beyond casual data reads - event data must be processed into cryptographic proofs. 

Why? 

The proof system verifies not just that a transaction (e.g., Bitcoin) occurred, but also that it didn’t occur elsewhere, requiring all event data to be fully processed.


XXXXX engagements

![Engagements Line Chart](https://lunarcrush.com/gi/w:600/p:tweet::1907337177631281261/c:line.svg)

**Related Topics**
[tps](/topic/tps)
[blockchain](/topic/blockchain)
[events](/topic/events)
[l1](/topic/l1)
[coinweb](/topic/coinweb)

[Post Link](https://x.com/CoinwebOfficial/status/1907337177631281261)