coinculture.com
On Saturday (13 August), Sebastien Guillemot, the chief technology officer (CTO) of blockchain business dcSpark, stated that the L1 blockchain Cardano ($ADA) is among the worst blockchains for storing data and went on to explain why.
You might also like
Vitalik Buterin: ZK-Rollups To Outperform Optimistic Rollups
Charles Hoskinson Predicts No Further Delays In Cardano’s Vasil Hard Fork
If you’re wondering what dcSpark has done, its development team says its primary objectives are to:
- “Extend Blockchain Protocol Layers”
- “Implement First-Class Ecosystem Tooling”
- “Develop and Release User-Facing Apps”
In April 2021, Nicolas Arqueros, Sebastien Guillemot, and Robert Kornacki co-founded the company. In the Cardano community, dcSpark is known for its sidechain project Milkomeda.
One Cardano supporter tweeted on Friday (12 August) that Cardano is an excellent blockchain for storing massive volumes of on-chain data.
One of the most interesting innovations that Cardano brings with the EUTXO model is how data can now be stored on chain which means it can never be destroyed. We are testing it right now in Ethiopia to store schooling documentation but the possibilities are endless.
— Lucid (@LucidCiC) August 12, 2022
The CTO of dcSpark said that Cardano’s present architecture makes it one of the worst blockchains for data storage.
“Really strange tweet. Cardano is definitely one of the worst blockchains for storing data and this was an explicit design decision to avoid blockchain bloat and it’s the root cause of many design decisions like plutus data 64-byte chunks, off-chain pool & token registry, etc…
Vasil improve this with inline datums, but they are indirectly discouraged because of the large cost of using them. I do agree that having the blockchain provide data availability is an important feature, but having a good solution will require changes to the existing protocol.“
Then, another $ADA holder questioned Guillemot if this design decision may make it more difficult for teams developing roll-up solutions (such as Orbis), to which Guillemot responded:
“Yes, trying to provide data availability for use cases like rollups, mithril, input endorsers and other similar>Some Brief Comments on Vasil