David discussed how XRPL offers a variety of options for programability for different use cases and objectives: 1) protocol-native functionality (Eg Xls20 based NFT, smart transactors etc) 2) Hooks (on-chain smart contract like programmability) 3) EVM sidechain
For example, 80-90% of NFT use cases could be addressed by simpler yet robust and secure features of Xls20, while some very specific / bespoke use cases may need full programability with EVM smart contracts.
In the same way, a majority of DeFi use cases could be addressed by Hooks vs full EVM smart contracts, which come with complexity and security risks (Ie having to trust smart contract developers) etc.
However, XRPL still offers a full programability option through EVM sidechains for specific use cases.
It’s all about optionality and choosing the best method for implementation, considering the need for efficiency, cost, scalability and security.
• • •
Missing some Tweet in this thread? You can try to
force a refresh