<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Ajit Kulkarni</title>
    <description>The latest articles on DEV Community by Ajit Kulkarni (@ajitkulkarni).</description>
    <link>https://dev.to/ajitkulkarni</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F934810%2Fa94758e8-1355-43a9-bca6-c6ee6d398d0e.jpg</url>
      <title>DEV Community: Ajit Kulkarni</title>
      <link>https://dev.to/ajitkulkarni</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/ajitkulkarni"/>
    <language>en</language>
    <item>
      <title>Strengthening XRPL EVM Sidechain: Key Takeaways from Informal Systems Security Audit</title>
      <dc:creator>Ajit Kulkarni</dc:creator>
      <pubDate>Thu, 03 Apr 2025 22:43:46 +0000</pubDate>
      <link>https://dev.to/ripplexdev/strengthening-xrpl-evm-sidechain-key-takeaways-from-informal-systems-security-audit-4dme</link>
      <guid>https://dev.to/ripplexdev/strengthening-xrpl-evm-sidechain-key-takeaways-from-informal-systems-security-audit-4dme</guid>
      <description>&lt;p&gt;The &lt;a href="https://www.xrplevm.org/" rel="noopener noreferrer"&gt;XRPL EVM Sidechain&lt;/a&gt;—bringing &lt;a href="https://docs.xrplevm.org/pages/developers/developing-smart-contracts/develop-a-smart-contract" rel="noopener noreferrer"&gt;smart contract capabilities&lt;/a&gt; to the XRP Ledger ecosystem—recently underwent a rigorous security audit conducted by Informal Systems, a team of world-class researchers, engineers and operators who specialize in security audits for blockchain products.. The audit, carried out in February of 2025, assessed the correctness, security, and reliability of the XRPL EVM Sidechain implementation, including both the core node diff and its customized &lt;a href="https://medium.com/ripplexdev/ripple-and-peersyst-utilize-evmos-to-enable-evm-and-cosmos-interoperability-fded0d212cf4" rel="noopener noreferrer"&gt;Cosmos EVM fork&lt;/a&gt;. &lt;/p&gt;

&lt;p&gt;As &lt;a href="https://dev.to/ripplexdev/a-proposed-vision-for-xrp-ledger-programmability-1gdj"&gt;programmability expands across the XRP Ledger&lt;/a&gt; ecosystem, ensuring a secure foundation is paramount. The XRPL EVM Sidechain is built with Cosmos SDK and its consensus layer is enabled by CometBFT. It has full EVM compatibility, including all Ethereum libraries, smart contracts and EVM development tools like Open Zeppelin and Hardhat, and it supports institutional use cases and cross-chain flow of digital assets. This audit helps validate the robustness of the sidechain’s architecture as it scales for real-world financial applications. &lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fvjn6j6o8e764q84vvtf0.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fvjn6j6o8e764q84vvtf0.png" alt="Image description" width="800" height="613"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;The diagram above illustrates the architecture of Cosmos SDK using Evmos/Cosmos EVM as the EVM execution layer and CometBFT as the consensus layer.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Exploring Audit Findings&lt;/strong&gt;&lt;br&gt;
The audit identified only one critical issue overall, which was tied to the use case of the crisis module for invariant enforcement. Other issues were rated low or informational and are largely related to architectural clarity and best practices. All of these findings have since been resolved by the Peersyst and RippleX engineering teams, with Informal Systems designating them as such. Let’s dive into a breakdown of the aforementioned findings:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://drive.google.com/file/d/1QLUm_bvFyDDKPmkz0RbNXHaVPxyFAUid/view" rel="noopener noreferrer"&gt;Reference material for the report&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Critical Finding: Crisis module Ineffectiveness&lt;/strong&gt;&lt;br&gt;
The audit identified that the crisis module does not reliably halt the chain upon detecting invariant violations, which could allow unnoticed security issues. This behaviour is consistent with a broader Cosmos SDK advisory. &lt;/p&gt;

&lt;p&gt;RippleX and building partner Peersyst are actively considering alternative approaches for checking invariants, and have since added a relevant &lt;a href="https://github.com/xrplevm/node/pull/61" rel="noopener noreferrer"&gt;fix&lt;/a&gt; which has been acknowledged by Informal Systems.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;PoA with Guardrails: A Secure Validator Set&lt;/strong&gt;&lt;br&gt;
The audit outlines that the XRPL EVM Sidechain’s &lt;a href="https://docs.xrplevm.org/pages/operators#consensus-and-proof-of-authority" rel="noopener noreferrer"&gt;Proof-of-Authority (PoA) consensus&lt;/a&gt; is enforced with strong and stable safeguards that include the fact that validators can only be added or removed via a transparent governance process. A key aim in building the XRPL EVM Sidechain was the preservation of the XRP Ledger’s focus on security and trust, where consensus participants define their own Unique Node List (UNL) and as a consequence the XRPL network minimizes the risk of a single point of failure or centralized control.&lt;/p&gt;

&lt;p&gt;The PoA Consensus is built on CometBFT’s PoS: The XRPL EVM sidechain adapts CometBFT’s PoS consensus by introducing specific restrictions to enforce PoA:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;Validators are added and removed exclusively through the governance process.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;A special BondDenom token is used solely for staking:&lt;br&gt;
-- When a validator is created, a predefined amount is minted as stake.&lt;br&gt;
-- When a validator is removed, the staked amount is burned.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;The system does not contain any unstaked (free) BondDenom tokens.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Re-delegations and un-delegations are not permitted.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Each validator has only a single self-delegation (created at the moment of adding the validator, when the staking amount is minted).&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Slashing penalties do not apply, meaning staking amounts remain unchanged.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;No BondDenom token rewards are distributed (no inflationary rewards), and since there are no delegations, rewards distribution and commission rate settings are irrelevant.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;These parameters reinforce predictable validator behaviour and reduce governance and consensus risk, which is of course critical for institutional-grade applications. &lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Strengthened Token Management via Cosmos EVM Fork&lt;/strong&gt; &lt;br&gt;
The Evmos fork introduced enhancements to ERC-20 token precompiles, allowing minting, burning, and ownership transfer. The audit confirmed that only authorized token owners can mint or burn assets. Ownership is gated through governance or EVM precompiles with strict checks, and no unauthorized token actions are possible through the Cosmos SDK or EVM paths. &lt;/p&gt;

&lt;p&gt;The audit also suggested separating ownership revocation from transfer logic to avoid unintentional contract lockouts- an improvement the team has acknowledged and will consider for future releases. &lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Low-Risk and Informational Observations Roundup&lt;/strong&gt; &lt;br&gt;
Most other findings related to other informational aspects that  did not pose immediate risks but offer opportunities for streamlining and ensuring further clarity in future development cycles. &lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;Minimum and maximum validator number validation &lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Unnecessary token burning on validator removal &lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Cosmos SDK v0.50 upgrade housekeeping&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Separate revoke ownership from transfer ownership &lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Messages MsgDelegate and MsgCancelUnbondingDelegation should be disabled &lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Refactoring suggestions (For example, separating logic in mint.go) &lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Building on the Audit&lt;/strong&gt;&lt;br&gt;
The RippleX engineering team and Peersyst have since addressed all relevant recommendations, as outlined in the final report, and will continue to strengthen the XRPL EVM Sidechain ahead of production-grade adoption. This audit reaffirms the XRPL EVM Sidechain’s willingness and readiness to support enterprise-grade tokenization, smart contract deployment, and real-world asset applications. &lt;/p&gt;

&lt;p&gt;To learn more you can explore the official XRPL EVM Sidechain &lt;a href="https://www.xrplevm.org/" rel="noopener noreferrer"&gt;website&lt;/a&gt; and reach out to the &lt;a href="https://x.com/Peersyst" rel="noopener noreferrer"&gt;Peersyst team&lt;/a&gt; and broader &lt;a href="https://twitter.com/RippleXDev" rel="noopener noreferrer"&gt;RippleX team&lt;/a&gt; via X  to stay up to date on future developments, open source contributions, and production rollout plans. You can also reach out to the masterminds at Peersyst who have been instrumental in the development of the XRPL EVM Sidechain.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Results from the Bishop Fox Security Audit and Remediation of the Cross-Chain Bridge and EVM Sidechain</title>
      <dc:creator>Ajit Kulkarni</dc:creator>
      <pubDate>Thu, 16 Nov 2023 19:46:42 +0000</pubDate>
      <link>https://dev.to/ripplexdev/results-from-the-bishop-fox-security-audit-and-remediation-of-the-cross-chain-bridge-and-evm-sidechain-3eld</link>
      <guid>https://dev.to/ripplexdev/results-from-the-bishop-fox-security-audit-and-remediation-of-the-cross-chain-bridge-and-evm-sidechain-3eld</guid>
      <description>&lt;p&gt;As new and exciting developments are made on the &lt;a href="https://xrpl.org/"&gt;XRP Ledger&lt;/a&gt;, comprehensive security audits remain an important part of ensuring innovations remain rigorous and secure.&lt;/p&gt;

&lt;p&gt;On July 24, the cyber security firm Bishop Fox completed an extensive security audit of the EVM sidechain. The team specifically assessed the EVM sidechain implementation, its consensus mechanism and the bridging implementation between the XRPL and the EVM that uses the cross-chain bridging (&lt;a href="https://github.com/XRPLF/XRPL-Standards/discussions/92"&gt;XLS-38d&lt;/a&gt;) specification for the XRPL.  &lt;/p&gt;

&lt;p&gt;On October 6, Bishop Fox delivered remediation reports for both the EVM Sidechain and the XLS-38 Cross-Chain Bridge. All of the reports are listed below, followed by a summary of the findings.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Reference material for the reports:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://ripple.com/reports/Ripple-Side-Chains-Assessment-Report-XRPL.pdf"&gt;Original XLS-38 Cross-Chain Bridge Report&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://xrplresources.org/hubfs/Files/Ripple%20-%20Side%20Chains%20Security%20Assessment%202023%20-%20XRP%20-%20Remediation%20Report%20-%2020231006.pdf"&gt;XLS-38 Cross-Chain Bridge Remediation Report&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://xrplresources.org/hubfs/Files/Ripple%20-%20Side%20Chains%20Security%20Assessment%202023%20-%20Assessment%20Report%20-%20EVM%20-%2020230724.pdf"&gt;Original EVM Sidechain Report&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://xrplresources.org/hubfs/Files/Ripple%20-%20Side%20Chains%20Security%20Assessment%202023%20-%20EVM%20-%20Remediation%20Report%20-%2020231006.pdf"&gt;EVM Sidechain Remediation Report&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Audit Findings, EVM Sidechain&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The auditor determined that “RPC networking interfaces were well-protected against injection-based attacks and identified no core issues with the bridging functionality.” &lt;/p&gt;

&lt;p&gt;Overall, the audit didn’t find any critical or high severity issues. There were 11 total findings - 3 of “medium” risk, and 8 of “low” risk. The audit found minor issues related to the use of outdated dependencies and the use of some unsafe command and code execution patterns. Bishop Fox recommended that the developer team firstly update software dependencies, and secondly remove unsafe execution patterns. &lt;/p&gt;

&lt;p&gt;The PeerSyst team has since addressed these issues in the latest implementation and these fixes will be part of the Mainnet launch of the EVM sidechain. &lt;/p&gt;

&lt;p&gt;The latest remediation report underlines the relevant progress that has been made. Partial and complete remediations, as can be viewed in the document, have in turn ensured that relevant risk levels have been downgraded for highlighted vulnerabilities. &lt;/p&gt;

&lt;p&gt;Notably, Bishop Fox added in the initial report that “despite attempting multiple potential attack paths against the EVM bridge, the team did not identify mechanisms for a remote attacker to violate the operational integrity of the EVM bridge applications or forge bridging transactions.” While the initial report findings were reassuring, the PeerSyst team’s remediation efforts have ensured the implementation is even more robust.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Audit Findings, XLS-38 Cross-Chain Bridge&lt;/strong&gt;&lt;br&gt;
The RippleX engineering team also fixed the issues brought out by the Bishop Fox team during their audit of the XLS-38 Cross-Chain Bridge changes in rippled code. The Bishop Fox team conducted remediation testing and has published a remediation report verifying these fixes.  &lt;/p&gt;

&lt;p&gt;&lt;strong&gt;About the EVM Sidechain&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The EVM sidechain is being developed by Peersyst in partnership with Ripple and is effectively optimized for DeFi. Users have already enjoyed the sidechain which has been available on a new version of Devnet (v2), as of June 2023. &lt;/p&gt;

&lt;p&gt;As a result of the development, builders will have the opportunity to be one of the first to market their DeFi app on a new chain that is home to a user base of over 4.5M XRP wallet holders. Builders will be able to utilize familiar smart contract languages to build and deploy cross-chain dApps seamlessly. EVM sidechain is built with CometBFT to enable 3.5 second block times and low gas fees that are paid for in XRP. You are also able to utilize the secure bridge, based on the &lt;a href="https://github.com/XRPLF/XRPL-Standards/discussions/92"&gt;XLS-38&lt;/a&gt; cross-chain bridging specification, to transfer funds seamlessly between XRPL Mainnet and the EVM sidechain, ensuring easy navigation.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Connect to the EVM sidechain Devnet here:&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Name: EVM Sidechain&lt;br&gt;
RPC URL: &lt;a href="https://rpc-evm-sidechain.xrpl.org"&gt;https://rpc-evm-sidechain.xrpl.org&lt;/a&gt;&lt;br&gt;
Network identifier: 1440002&lt;br&gt;
Digital Asset: XRP&lt;br&gt;
EVM Block Explorer URL: &lt;a href="https://evm-sidechain.xrpl.org"&gt;https://evm-sidechain.xrpl.org&lt;/a&gt;&lt;br&gt;
Bridge URL: &lt;a href="https://bridge.devnet.xrpl.org"&gt;https://bridge.devnet.xrpl.org&lt;/a&gt;&lt;/p&gt;

</description>
    </item>
  </channel>
</rss>
