Hot out of the Oven: 'The Baking Sheet' - Issue #224. This Week in the Tezos Ecosystem:.
11 Oct 2024, 19:04
🔥 Hot out of the Oven: 'The Baking Sheet' - Issue #224
This Week in the Tezos Ecosystem:
➡️ 1 Day Left to Vote for Qena: The Qena proposal, which focuses on technical improvements without making economic changes, is in its final voting stage. Qena brings 8-second block times and improved delegation calculations. Bakers, cast your vote today!
➡️ Hidden Gems of the Tezos Ecosystem: Discover 10 lesser-known Tezos tools that could transform your experience!
➡️ ComPilot Launches on Tezos: The compliance platform, ComPilot, is now live on Tezos! It streamlines AML/KYC processes, helping developers build without worrying about regulatory hurdles.
🎮 Game Spotlight – BattleTabs: Jump into BattleTabs, a naval warfare card-based Web3 game! Whether you’re in for quick five-minute games or strategic multi-day battles, BattleTabs offers a fresh spin on classic gameplay with collectible cards and tournaments.
👉 Read the full newsletter | Subscribe
Same news in other sources
211 Oct 2024, 19:11
Reporting it here for your convenience:
> If the problem stays, you can attack the network simply deploying multiple idling contracts. The security assumption would not be 2/3rd of honest node anymore, but 2/3rd of honest node+economic state viability. For the costs of deploying 10,000 contracts (around €50,000 in gas costs at today's value) you could slow down the VM for half a second. Slow it down for 5 seconds and the amount of time taken to accept a block will degrade the consensus. Slow it down for 10s and you get the whole network to a halt
Please note that while the index is the most impacted by contracts, it is in no way exclusive to them. Deploying contracts flushed out the problem with the index (tracked here: but it is in no way affecting solely the contracts but the overall global state. In a way it was a blessing to include contracs on Mainnet since upgrading the VM after the launch would be possible, but certainly dangerous and quite painful. It is much better to address the problem now.
Reporting it here for your convenience:.
Reporting it here for your convenience:
> If the problem stays, you can attack the network simply deploying multiple idling contracts. The security assumption would not be 2/3rd of honest node anymore, but 2/3rd of honest node+economic state viability. For the costs of deploying 10,000 contracts (around €50,000 in gas costs at today's value) you could slow down the VM for half a second. Slow it down for 5 seconds and the amount of time taken to accept a block will degrade the consensus. Slow it down for 10s and you get the whole network to a halt
Please note that while the index is the most impacted by contracts, it is in no way exclusive to them. Deploying contracts flushed out the problem with the index (tracked here: https://github.com/dusk-network/piecrust/issues/396) but it is in no way affecting solely the contracts but the overall global state. In a way it was a blessing to include contracs on Mainnet since upgrading the VM after the launch would be possible, but certainly dangerous and quite painful. It is much better to address the problem now.
11 Oct 2024, 19:07
telegram news 11 October 2024 19:07
https://x.com/PolySwarm/status/1844816614094422522