@odysseas_eth Isn’t bandwidth a bigger bottleneck that state?
- Homestakers ISPs would likely flag if bandwidth usage >1 TB each month
- State growth is largely dealt with with growth of cheap NVMe SSDs
We are thrilled to share that our Ethereum ZK light client has officially been integrated to secure the Gnosis Omnibridge on Mainnet!
With this addition, our ZK Proof of Consensus secures over $40M TVL between Ethereum and Gnosis Chain.
https://t.co/XFsAlbsV2S
By using the same EL and CL clients as Ethereum, @gnosischain stays in step with Ethereum's development. GC also remains compatible with Ethereum's roadmap, distinguishing itself from other sidechains that could become incompatible due to EIP-4844 and Verkle trees. 😎
Something is coming... 🪄
We've been hard at work the past few months cooking up some circuits that we're excited to bring to the public.
To do so, we need to perform a trusted setup ceremony. If you would like to be a part of it, apply here:
https://t.co/xgEKiQuhjv
I might be slightly biased, but if you have 20 minutes, watch this @EthereumDenver talk by @koeppelmann on the right macro-architecture to help scale the #Ethereum ecosystem.
Spoiler: L2s alone are not enough, you need further trustlessly connected L1s like @gnosischain.
My talk about "The Limits of L2" is online:
It discusses technical limits, neutrality issues, challenges from missing L1 ossification, security of native assets, and proposed solutions towards an "Inter Ethereum protocol".
https://t.co/RvlJCt2FdA
I think it is worth listening to @koeppelmann from @gnosischain about the limits of l2 systems and the need for more credible space on L1. Also the arrival of zkBrdge will turn the ethereum ecosystem into something similar to cosmos.
https://t.co/Mhd03MKTgD
This is @gnosischain syncing on an ARM64 Rock 5B board running @nethermind and @sigp_io Lighthouse. To try it update to the latest clients and run:
sudo systemctl start nethermind-gnosis
sudo systemctl start lighthouse-beacon-gnosis
Logs on journalctl.
TLDR: @CoWSwap worked as intended! Unfortunately, a solver got attacked and the attacker withdrew the internal buffer for a more gas-efficient settlement ($160k).
Solvers are bonded to mitigate this potential attack. Result: No harm to users or the protocol itself.