Input Output Share their Parameter Update About Cardano (ADA) Network Capacity

Input-Output shared: NETWORK UPDATE: Today, we have proposed the next parameter update as we continue to increase Cardano network capacity in line with the plan. The proposal will increase the block size by a further 8KB taking it from 72KB to 80KB.

This latest adjustment represents an increase of c. 11%. In addition, an updated proposal has also today been triggered to increase #Plutus script memory units per transaction on the Cardano mainnet from the current 12.5M to 14M – an increase of 1.5M.

The increases to block size and memory units will both take effect at the boundary of epoch 319 on 4 Feb at 21:44:51 UTC and are in line with our announced plan to scale and optimize Cardano network throughput.

Together, these enhancements will provide additional resources for Plutus scripts to improve the DApp user experience while increasing overall network capacity.

This adjustment forms part of a planned series of network optimizations. Cardano will continue to be steadily optimized in a series of measured steps this year, carefully & methodically scaling Cardano for future growth as demand increases.

Continuing observation of ‘real world’ performance & the cumulative impact of parameter changes is key throughout this process. Following each update, we carefully monitor & assess network response over at least one epoch (5 days) before continuing with further adjustments.

The network has been designed to safely manage high peak loads and throughput will steadily improve as we continue to optimize. This latest change will continue to improve the user experience.

Please expect to see increased and often significant load around highly-anticipated new DApp launches and large NFT drops. Remember, there are no failed transaction fees on Cardano.

We’re committed to delivering the ‘Basho’ scaling phase of the Cardano roadmap through 2022 as the ecosystem grows; improving speed & additional network capacity all the while maintaining security and an ongoing commitment to secure decentralization.

Community Response:

Will it be enough? This week we learned how poorly the Cardano network scaled is. While programmers on the three big sites (MELD, SundaeSwap, MuesliSwap) are responsible for their poor coding, a big chunk of the blame goes to Cardano.

I’m sure you guys know what you’re doing, but I don’t understand why you don’t just increase the block size to the target amount all at once instead of this little by little approach.

Increasing the block size is the last resort, it cannot be changed back later. Every increase in block size compromises decentralization, so it’s vital to assess all other options before doing so. There are many other ways to scale which are being implemented this year.

What are your plans for the storage of the blockchain due to larger block sizes?

Oh, thank you Need those transactions to go through. Any news about K?

More ignoring on K but hey it’s only been a year since they said they were doing research.

Remind me, is K the max amount of stake of a stake pool before being saturated?

It’s not exactly the max amount of stake, but this parameter is directly affecting the saturation level of stake pools.

The question is, what would happen if you just bump it up to 1MB?

The block may not be able to traverse the network in 5s, which is necessary for the security guarantees of Ouroboros.

So, how much can they increase the block size till they can’t anymore?  It won’t matter as much when other optimizations come into play with script referencing and compression and finally Hydra giving theoretical millions of TPS over time.

Fantastic news! The chain congestion is a good sign. More people are using Cardano than ever before. Bullish!

Until the ETH maxis come in and tell you it’s DDoS when it’s just congested.  This happens all of the time with Solana, and how everyone always says because the TPS fall below 900 per minute, it’s an automatic DDoS attack. It’s irritating.

Well, I do not see the difference between congestion and DDoS. In some specific dApp in both cases, we have huge problems. Am I wrong?  DDOS is not the same as congestion, in fact for you to say that I must implore you to please Google what a DDOS is.

Post Views: 8