k4m4 retweeted
4,000 followers! Thank you to everyone supporting our goal of creating certainty in mission-critical systems.
k4m4 retweeted
Move $USDC across chains in seconds via Axelar.
Now available on Ethereum, Arbitrum, Avalanche and Base, with more routes coming soon.
app.axelar.network/tokens/us…
k4m4 retweeted
hello, @XRP.
Welcome to 𝕏.
k4m4 retweeted
Common Prefix's very own Nikolaos Kamarinakis, Dejan Cabrilo and Odysseas Sofikitis will serve as mentors and judges at the XRP Ledger Hackathon in New York on October 24–25.
Hosted by @xrpl_commons with @XRPLF & @RippleSwell.
Apply to participate: luma.com/xrpl-hackathon-nyc
k4m4 retweeted
Native $USDC is officially live on Axelar.
Users can now swap USDC across supported chains.
Get started: app.axelar.network/tokens/us…
🤖 Made with AI
k4m4 retweeted
You definitely want to attend this session!
Proof Over Trust: Formally Verifying the XRP Ledger by the heavy hitters Vito and Dejan.
Formal verification is the ongoing effort to bring the mathematical accuracy and correctness standards of military and aerospace systems to the XRP Ledger, ruling out worst case scenarios at a proof level.
AI made security practices like this viable for widespread use. Good example of AI cutting both ways, not only a threat but also a tool to harden systems.
One week to go! Technology driving AI breakthroughs in maths applied to secure XRP Ledger! @CommonPrefix , @RippleSwell
k4m4 retweeted
One week to go! Technology driving AI breakthroughs in maths applied to secure XRP Ledger! @CommonPrefix , @RippleSwell
Our very own Dejan Cabrilo and RippleX's Vito Tumas (@v_tumas) will be presenting "Proof Over Trust: Formally Verifying the XRP Ledger" at @RippleSwell.
Several members of our team will be there throughout the event. See you in New York.
k4m4 retweeted
Thank you to everyone who joined the Rust Meetup and made it a great evening.
See you at the next one.
k4m4 retweeted
Where is Axelar heading next?
Nikolas Kamarinakis, Co-Founder & CTO of @CommonPrefix, discusses the new era of Axelar on the Honest Majority season finale.
Read the full article.
xitter.cf/CommonPrefix/status/21…
A look back at the season finale of Honest Majority with Nikolas Kamarinakis (@nikolaskama), Co-Founder & CTO of Common Prefix.
Highlights from the conversation below.
k4m4 retweeted
A look back at the season finale of Honest Majority with Nikolas Kamarinakis (@nikolaskama), Co-Founder & CTO of Common Prefix.
Highlights from the conversation below.
k4m4 retweeted
Axelar's highlights from @kbwofficial and @token2049.
Read the full recap below.
k4m4 retweeted
Notice for AXL delegators.
We are migrating the axelar-core-0 validator to axelar-core-alpha. Delegators who have staked AXL with axelar-core-0 will need to redelegate to an active validator to continue earning staking rewards.
axelar-core-alpha address: axelarscan.io/validator/axel…
Full validator list: axelarscan.io/validators
k4m4 retweeted
Great work by the @RippleXDev team on a fast, well-coordinated response to the critical Payment Engine vulnerability.
In collaboration with RippleX and @XRPLF, we are formally verifying critical parts of the XRP Ledger in order to identify deeper issues that conventional testing may miss, and to bring stronger formal guarantees to the protocol.
Security remains our top priority for preserving trust in the XRP Ledger (XRPL). Sharing a few thoughts following yesterday's disclosure of the critical payments engine vulnerability reported by Veria AI.
First, this was a serious vulnerability, and we don't take that lightly. The bug had existed in the codebase for over a decade and could have allowed XRP to be created beyond its fixed supply. Fortunately, it was discovered through our bug bounty program before it could ever be exploited.
Second, our response was fast and coordinated. The team developed and thoroughly tested a fix, worked closely with validators to rapidly upgrade the network, and secured the ledger before public disclosure. I'm proud of how everyone came together to address the vulnerability and protect the XRPL network.
But there's a much bigger lesson here.
AI is fundamentally changing how quickly vulnerabilities can be discovered. We have to move even faster than before, especially with a codebase that's been around for over a decade.
This means we're doubling down in a few important areas:
* Proactive security: Strengthening our bug bounty programs, expanding AI-assisted vulnerability discovery/adversarial testing, and continuously improving testing across releases. This discovery reinforces why these investments matter.
* Addressing legacy tech debt: Working with our internal red team, external security researchers, and the XRPL Foundation to revisit longstanding assumptions in critical areas like payments engine, consensus, and P2P networking, guided by an updated threat model.
* Accelerating formal verification of critical areas: Continuing our work with CommonPrefix and the XRPL Foundation to apply formal verification to critical parts of the protocol, with the goal of uncovering deeper issues that other approaches could easily miss. We will build on the learnings from formal verification of the Lending Protocol and Single Asset Vault.
* Systemic hardening: Moving beyond individual bug fixes to identifying latent risks in older parts of the XRPL codebase and eliminating entire classes of vulnerabilities.
Our goal isn't simply to find more bugs. It's to systematically address the underlying risks and make the XRPL harder to exploit. As the XRPL's role in global financial infrastructure grows, so does our responsibility to protect it.
Security is never finished. We'll keep investing and improving alongside the broader XRPL community.
Full disclosure for the 3.4.1 release: xrpl.org/blog/2026/vulnerabi…
k4m4 retweeted
Heard about OMR? Privacy coins like @Zcash and @aztecnetwork mask senders, receivers, and transaction amounts and post everything on a public chain. As a receiver, how do you find your messages without scanning the whole chain?
The same problem applies to anonymous messaging 🧵
k4m4 retweeted
Security remains our top priority for preserving trust in the XRP Ledger (XRPL). Sharing a few thoughts following yesterday's disclosure of the critical payments engine vulnerability reported by Veria AI.
First, this was a serious vulnerability, and we don't take that lightly. The bug had existed in the codebase for over a decade and could have allowed XRP to be created beyond its fixed supply. Fortunately, it was discovered through our bug bounty program before it could ever be exploited.
Second, our response was fast and coordinated. The team developed and thoroughly tested a fix, worked closely with validators to rapidly upgrade the network, and secured the ledger before public disclosure. I'm proud of how everyone came together to address the vulnerability and protect the XRPL network.
But there's a much bigger lesson here.
AI is fundamentally changing how quickly vulnerabilities can be discovered. We have to move even faster than before, especially with a codebase that's been around for over a decade.
This means we're doubling down in a few important areas:
* Proactive security: Strengthening our bug bounty programs, expanding AI-assisted vulnerability discovery/adversarial testing, and continuously improving testing across releases. This discovery reinforces why these investments matter.
* Addressing legacy tech debt: Working with our internal red team, external security researchers, and the XRPL Foundation to revisit longstanding assumptions in critical areas like payments engine, consensus, and P2P networking, guided by an updated threat model.
* Accelerating formal verification of critical areas: Continuing our work with CommonPrefix and the XRPL Foundation to apply formal verification to critical parts of the protocol, with the goal of uncovering deeper issues that other approaches could easily miss. We will build on the learnings from formal verification of the Lending Protocol and Single Asset Vault.
* Systemic hardening: Moving beyond individual bug fixes to identifying latent risks in older parts of the XRPL codebase and eliminating entire classes of vulnerabilities.
Our goal isn't simply to find more bugs. It's to systematically address the underlying risks and make the XRPL harder to exploit. As the XRPL's role in global financial infrastructure grows, so does our responsibility to protect it.
Security is never finished. We'll keep investing and improving alongside the broader XRPL community.
Full disclosure for the 3.4.1 release: xrpl.org/blog/2026/vulnerabi…
k4m4 retweeted
Come join us at the Common Prefix offices for our last Rust Meetup to discuss why AI will replace all future Rust meetups and our future way of writing code (third talk)... or not. Also fingerfood and good people. Wednesday evening!
luma.com/l3j10puk
k4m4 retweeted
Blast has announced the shutdown of its network.
Users with remaining assets on Blast should move them to an active chain before October 26, 2026.
More information:
Blast will be shutting down.
We launched Blast with the goal of building a self-sustaining chain for users and developers. Unfortunately, the economics of operating the chain no longer make sense: the ongoing costs of maintaining Blast exceed the revenue generated by the L2, and we do not see a credible path to making the chain economically sustainable.
As a result, we've made the difficult decision to wind Blast down.
We're sorry to the users and developers who believed in Blast, built on it, and supported the ecosystem. Our priority now is making the shutdown as smooth and safe as possible.
We're asking all users to withdraw their assets from Blast to Ethereum mainnet, including any balances held in the Blast PWA.
To make this easier, we will be reducing the withdrawal delay to 24 hours.
As part of the shutdown process, we'll first begin withdrawing Blast's Lido assets. This process is expected to take approximately one week. During this period, withdrawals will temporarily be unavailable, even after the withdrawal delay is reduced to 24 hours.
Once that process is complete, withdrawals will resume with the new 24-hour delay.
Users will have until October 26, 2026 to withdraw through the normal Blast interface.
After October 26, assets will remain withdrawable, but users will need to interact directly with the Blast bridge contracts on Ethereum L1. We'll publish detailed instructions before then.
We strongly encourage everyone to withdraw their assets to Ethereum mainnet before October 26.