The best place to learn about Radix is the Radix Full Stack site or the RadFi 2022 Keynote.
The core Radix belief is that the future of finance is decentralized.
But Web3 and DeFi today are afflicted by some serious problems. The platforms that launched DeFi, including Ethereum and others, will not be capable of supporting billions of users and trillions of dollars of assets.
Luckily, Radix is a Full Stack of technologies designed to solve precisely that - a platform that can underpin a $1,000+ trillion Web3/DeFi through to the end of this century and beyond. That’s the purpose of Radix - a platform that can propel DeFi into the mainstream.
The table below summarizes some of these problems and how Radix solves them.
# | Web3 & DeFi today offers | Radix Solutions and Reading |
1 | Poor User Experience as technically difficult and insecure practices such as blind signing and seed phrases are forced upon on end users. | • Mobile Radix Wallet that allows your friends and family to confidently use Web3 and DeFi. • Five core platform technologies introduced as part of the Radix Babylon Mainnet upgrade: • Personas Reading: |
2 | Poor Security with hacks, bugs, and exploits totalling billions of dollars being commonplace. | • Radix Engine v2 - Custom-built execution environment for DeFi. • Scrypto - Custom-built programming language with asset-orientedarchitecture • Blueprints and Components - Reusable, modular and more composable smart contracts • Transaction Manifest - Powerful transaction layer offering on-the-fly composability • Blueprint Catalog - On-ledger library of smart contract blueprints • Badges and native features for Role Based Access Control Reading: • The Problem with Smart Contracts Today • Radix Engine v2: An Asset-Oriented Smart Contract Environment • Scrypto: An Asset-Oriented Smart Contract Language • The Problem with Crypto Transactions Today • Radix’s Asset-Oriented Transactions • Comparing Virtual Machines: Message Only vs Asset-Oriented • See Rekt Retweet series linked in further reading below |
3 | Poor Developer Experience resulting in slow and hard-to-learn development because of unintuitive programming languages and lack of native in-built features for assets, transactions and access control. | |
4 | Developer incentives that overly rely on the issuance of tokens such as governance tokens. | • Radix Developer Royalties - Automated on-ledger royalty fees set by developers Reading: • On-ledger, Recurring Developer Revenue. Incentives to Buidl |
5 | Scalability that breaks atomic composability,sacrificing the compounding innovation of Web3andDeFi. | • Cerberus - Peer-reviewed consensus protocol offering unlimited linear scalability and atomic composability. Reading: |
Pulling it all together: The Radix Full Stack and the RadFi 2022 Keynote. | ||
Further reading:
- What is Radix?
- What is the Radix Protocol?
- What are the Radix Public Network and Radix Ledger?
- What is the Radix roadmap?
- Rekt Retweet #1 - Why the $48 million Cashio hack on Solana could NEVER happen on Radix
- Rekt Retweet #2 - Why the $120m Badger DAO hack could NEVER happen on Radix
- Rekt Retweet #3 - Why the $80m Qubit Finance hack could NEVER happen on Radix
- Rekt Retweet #4 - Why your Bored Apes (and all other NFTs) aren’t safe… except on Radix
- Rekt Retweet #5: Why the $30m Spartan Protocol hack could NEVER happen on Radix
- Rekt Retweet #6: Re-entrancy and Flash Loans - Why the $80m Fei / Rari hack could NEVER happen on Radix
- Rekt Retweet #7: Why Radix Blueprints and Components would have prevented the $11m Value DeFi hack on BSC
- Rekt Retweet #8: Why the $90m Mirror Protocol hack could NEVER happen on Radix
- Rekt Retweet #9: The Transaction Manifest - Why the $14m Furucombo hack could NEVER happen on Radix
- Rekt Retweet #10: Badges - Why the $326m Wormhole hack on Solana could NEVER happen on Radix
- Rekt Retweet #11: Re-entrancy - Why the $11m Agave and Hundred Finance hacks could NEVER happen on Radix
- Rekt Retweet #12: Native Token Validation - Why the $2.1m Gym Network hack could NEVER happen on Radix
- Rekt Retweet #13: Why a bug losing user funds on Uniswap is fixed by “Buckets”