To say that I’m really excited for the future of @kadena_io would be an understatement. We are determined to empower every human across the internet, from the blockchain to your device!
Here’s a small snippet of how we are going to do it: 🧵
Imagine combining the best of both worlds: the user experience of Web2 and the security of Web3. It's a powerful combination that can redefine how we interact with digital platforms and applications.
We want to bring the advantages of the crypto space and Pact (secure by default, password-less logins, ZK privacy) to Web2 developers for an exceptional user experience.
Kadena’s L2 Solution
Crypto projects benefit from L2 efficiency and ZK-powered privacy to scale and speed up transactions. A Kadena-powered, scalable, multichain L2 on Pact changes the game entirely.
With the simplicity & security of Pact, developers can tap into the power of L2 solutions & ZK roll-ups while ensuring that users' assets & data are protected.
We are working hard with our partners to enable projects to add privacy as a feature when building their applications.
Learning Pact means not only staying at the forefront of both blockchain engineering and software development. It also means you can create apps that you know are secure, safe, and efficient.
There’s no better time to learn Pact than now!
#Kadena has the technology to build a truly decentralized internet that is open, inclusive, and accessible to all. It's never been a better time to build on Kadena!
• • •
Missing some Tweet in this thread? You can try to
force a refresh
Scalability is the proving ground where clever designs go to die. One thing we talk about at @kadena_io is the "earnings report problem" to illustrate how so many seemingly attractive approaches fall over in real world use, coming from experience scaling trading exchanges. \1
Next time somebody's touting a system design that magically handles any load, the earnings report problem will usually reveal the weaknesses therein. Remember that scalability isn't raw speed but the ability to throw more resources at a problem without falling over. \2
A fundamental problem in scaling is data localization. (This is the real "sharding" problem in distributed systems, not the tortured crypto version). A stock exchange might scale on symbol: one node does the As (AAPL etc), one does Bs, Cs etc. Simple and effective right? \3
It's how crypto realizes its full potential.
It's how builders don't have to start from scratch when innovating.
It's how code stays on the blockchain, not in unsafe offchain apps.
It's only possible with Pact and @kadena_io . \1
Today on EVM platforms, the simplest contract requires reams of copypasted code. This is bad for devs but worse for users and auditors: every contract must be audited line-for-line, every time. It's confusing, bloated, slow and expensive, but most importantly, unsafe. \2
Copypaste prevents interop -- every project is an island. This harms ecosystem development, by fragmenting markets and inventory. And it's not just DeFi: NFT minters are usually trapped in a single market, while fractionals cannot benefit from placement on multiple exchanges. \3
Smart contracts are key to success. It sounds obvious, but Ethereum and Kadena are two of a surprisingly small number of platforms that support real smart contracts. Many other platforms have gone a different way. Here's why they're wrong. \1
At a low level, Pact follows the EVM's (and Bitcoin's) lead: provide a limited interpreter to execute logic that populates the blockchain ledger. In Bitcoin, this is UTXOs, whereas in Kadena and Ethereum, it's a "state DB". \2
This model is integral to Ethereum's success: EVM bytecode does exactly what it is specified to do. (Whether Solidity does is another question :) ). Pact is even more faithful, in that the code you write in your editor is exactly what executes on the blockchain. \3