Derived from The Crypto Basic, Ripple’s Chief Technology Officer, David Schwartz, stated during a recent X Spaces session that the company should have prioritized native smart contract capabilities on the XRP Ledger (XRPL) much earlier. He explained that Ripple’s initial skepticism toward smart contracts delayed their development at the Layer-1 level, which in turn slowed innovation in the XRPL ecosystem. The XRP Ledger, launched in 2012, was originally designed for payments and not for programmable applications. While Ethereum popularized smart contracts in 2015, Ripple remained hesitant, believing the feature had to be perfect before implementation. Schwartz acknowledged that developers currently face limitations in building on XRPL, as they must either propose new features for community approval or focus on wallets and front-end apps. He emphasized that even basic smart contract functionality could have enabled developers to create unique on-chain features and custom business logic. Although XRPL’s Automated Market Maker (AMM) is a strong feature, Schwartz noted that its impact is limited without smart contracts. Ripple has since begun exploring smart contract capabilities, with the feature recently deployed on XRPL’s AlphaNet for testing ahead of a mainnet rollout.
Ripple CTO David Schwartz Admits Delay in Smart Contract Development on XRP Ledger
TheCryptoBasicShare
Source:Show original
Disclaimer: The information on this page may have been obtained from third parties and does not necessarily reflect the views or opinions of KuCoin. This content is provided for general informational purposes only, without any representation or warranty of any kind, nor shall it be construed as financial or investment advice. KuCoin shall not be liable for any errors or omissions, or for any outcomes resulting from the use of this information.
Investments in digital assets can be risky. Please carefully evaluate the risks of a product and your risk tolerance based on your own financial circumstances. For more information, please refer to our Terms of Use and Risk Disclosure.