Senior Software Engineer
@RippleXDev
- Interoperability |
@MIT
CS |
she/her/hers |
Seattle sports fan (Hawks, Storm, Reign, M's) |
all views are my own
Just dropped: A new spec for sponsored XRPL transaction fees/reserves, which would allow platforms to pay transaction fees/reserves on behalf of other accounts, without needing to give away free XRP. This makes it way easier to onboard onto the XRPL! 🔥
NFTs are live on the XRP Ledger via XLS-20!
I've seen a lot of common XRPL on-ledger errors while watching the ledgers go by, so here's a 🧵 for developers and developer-minded folks to shed some light on them.
I'll add more over time as I think of things (taking suggestions).
For all those following along with XLS-56d, I just published a huge update of the spec.
One of the new features it enables: multi-account batches 👀 This will enable new use-cases like atomic swaps.
I’m excited to release XLS-70d, On-Chain Verifiable Credentials. This is great for certifications and compliance, and unlocks the potential for a new wave of trust-based applications within the XRPL ecosystem.
Yesterday,
@RippleXDev
announced that the XRPL EVM Sidechain will be using
@axelarnetwork
for its bridge and will no longer be using XLS-38. I'd like to share some of my thoughts on that decision here with you. 🧵
3/ We're migrating to
@axelarnetwork
for its robust security and efficiency in cross-chain transactions.
"Axelar is a battle-tested, production-ready bridge to bring XRP as a native currency to the XRPL EVM Sidechain.” —
@FerranPrat12
,
@Peersyst
CEO.
Heads up:
@intelliot
and I just published a new spec for a rippled method that will allow users to “preview” or “dry-run” transactions without actually executing them. This is a game-changer for devs - they will be able to test out transactions much more easily and without
I just posted a pre-proposal discussion about XRPL plugins, a project to make it easier for devs to write new features for rippled in their language of choice. Looking to get some early community feedback as I continue to work out the details.
I've had some ideas for atomic and batch transactions for a few weeks now, but finally got around to putting it all on paper for you all to read.
I think this is game-changing for the XRPL and unlocks a lot of usecases.
#XRPL
#XRPLedger
We are getting ready for the best
#ApexDevSummit
yet!
Mark your calendars for September 6-8 and check out a great lineup of
#XRPL
builders speaking at this year's Apex.
Calling all XRPL devs! Come join my workshop at Apex on June 12 at 2pm. We’ll explore the inner workings of XRPL amendments and dive deep by designing and coding them live with XRPL plugins (in Python 👀). Let's unlock the power of amendments together! 🚀
BIG CHANGE COMING
for
#XRP
and the Ledger.
👉📺
#XRPL
Validators to Vote Soon on Another Amendment, co-authored by Sr. Software Engineer
@msvadari
An AMA Style Interview with Mayukha ~
Many of you have been asking lately about how XRPL source code (rippled) changes (amendments, fixes, new features, etc.) are written and tested, so here’s a thread.
How Code Gets Into Rippled: 🧵
Now that I've had enough time to recover, time for a real
@xrplapex
wrap post.
Thanks to the amazing team that put this whole event together - you really outdid yourselves this time!
Thanks to all the speakers who poured their hearts and souls into really cool and insightful
Excited to be presenting at Apex on XRPL plugins, a way to write Layer 1 XRPL features in the language of your choice (such as Python)! It'll be a 3-peat for me, presenting at every Apex that's happened so far. Looking forward to meeting everyone who'll be there!
I just posted a pre-proposal discussion about XRPL plugins, a project to make it easier for devs to write new features for rippled in their language of choice. Looking to get some early community feedback as I continue to work out the details.
I've seen a lot of hype about XLS-56d (atomic transactions) lately. So many interesting ideas flying around!
What excites you about atomic transactions on the XRP Ledger? I'd love to hear your potential uses.
Comment below!⬇️
Day 1 at the
@easya_app
#60DaysofXRPL
Hackathon - the room was packed, and everyone is working on super awesome ideas! Looking forward to hearing all the pitches tomorrow.
100%. Don't harass validators for having a different risk tolerance.
I've read a lot of UNL validators' explanations for voting "no" on this website, and all of them are reasonable.
If they were acting in bad faith then yes, they shouldn't be trusted, but I don't see that here.
Just like when NFTs where up for voting on the XRPL, a few people harassed operators to vote in favor of NFTs no matter what.
There is, still, no place for this harassment here!
🚨🚨
I'm seeing the first screenshots from people believing $RLUSD has already been issued on the $XRP Ledger ($XRPL).
It has NOT been issued. These are fake tokens issued by scammers trying to sell worthless assets on the DEX or through AMM.
⚠️⚠️⚠️ Do not engage.
Calling all XRPL devs! Come join my workshop at Apex on June 12 at 2pm. We’ll explore the inner workings of XRPL amendments and dive deep by designing and coding them live with XRPL plugins (in Python 👀). Let's unlock the power of amendments together! 🚀
Let's celebrate the brilliant women innovating on the
#XRPLedger
. ✨
Join us in spotlighting the women building and shaping the future of the
#XRPL
.👩💻
Show your support by RTing and tagging them in this post!
#InternationalWomensDay2024
Welcome to Apex, the XRPL Developer Summit where developers, contributors and thought leaders come together to learn, build, share, network and celebrate all things
#XRPLedger
. We'll be sharing big moments throughout the day, so follow along at
#ApexDevSummit
.
1/ Introducing the XRPL EVM Sidechain: We're excited to bring Ethereum Virtual Machine (EVM) compatibility to the XRP Ledger, enhancing interoperability and unlocking new opportunities in DeFi and RWA.
Excited to announce that I'll be speaking at
#ApexDevSummit
in Las Vegas next week! I'm going to be doing a talk and workshop focusing on sidechains.
It's not too late to sign up by visiting !
@CommonPrefix
Axelar also has features that XLS-38 simply doesn't have, such as their innovative GMP protocol that allows users to call smart contracts on other chains (or, in the XRPL’s case, interact with XRPL features such as the AMM or the DEX) without needing to leave their home chain.
@CommonPrefix
This unlocks so many more use cases for builders - you can truly get the best of all worlds. And they're always working on improving their network and adding more cool features!
@CommonPrefix
Regarding XLS-38, the Ripple UNL validator is voting “no” for now and will be engaging in extensive conversations about it to understand how the community feels, over the next 12-15 months. After collecting this feedback, the code could be removed from the rippled codebase (to
@MetaMan_X
There's a difference between opposing the amendment and waiting to enable it. I don't think any of the UNL validators have been against the amendment itself, they just want to make sure it won't break the ledger before enabling it.
This switch was made based on numerous factors. One is that the Axelar team has years of experience specifically building and securing bridges. They (alongside the
@CommonPrefix
team) already had an answer for every question or concern.
@CommonPrefix
Another is the level of decentralization that Axelar offers. Axelar already has 75 validators on their network, and continues to add more, while XLS-38 only supports a maximum of 32 witness servers.
New design, who dis? 🤩
A new proposal for XRPL sidechains introduces a piece of the puzzle called a “witness” to simplify implementation and improve efficiency.
Learn about what's changed👇
@BatTecking
@chintokkong
@WietseWind
@helicondarkstar
The network is still handling 50-60 tps admirably right now. The UNL validators and production-grade nodes are chugging along just fine, with only minor hiccups. It's mainly folks running underpowered servers that are running into issues due to the higher load.
IMO it’s a huge positive that everyone is so careful about amendments. We all want the XRPL to remain performant, error-free, and stable at all costs. There are major consequences to inadvertently introducing bugs, and that sometimes requires going slow.
Thanks for reading! /end
Tomorrow I’ll be discussing the XRPL Plug-Ins API with
@msvadari
from
@RippleXDev
It’s a must-know for Devs, making it easier to work on new sidechains and proof-of-concept launches
All without C++ experience!
📣 Appel à tous les développeurs aspirants à maitriser l'XRPL💥 Rejoignez-nous les 25 et 26 janvier pour une formation immersive de 2 jours pour apprendre à developper l'XRP Ledger !🤸Postulez ici:
🏹
#XRPLCommunity
#xrpl
#BlockchainEducation
Announcing the winners of the pitchathon at our
#60DaysofXRPL
hackathon! 📣
From the founder of a $100m FinTech company to PhDs at world-class universities, these devs are literally the best in their fields.
Let’s see what they built on the
#XRP
Ledger EVM Sidechain! 🧵👇
1/ RX engineering has identified a minor edge case in the XLS-40 decentralized identity spec, where users may be able to create empty DID objects. We have proposed and are reviewing a fix, that will be introduced as a new amendment:
Excited to be presenting at Apex on XRPL plugins, a way to write Layer 1 XRPL features in the language of your choice (such as Python)! It'll be a 3-peat for me, presenting at every Apex that's happened so far. Looking forward to meeting everyone who'll be there!
After ~2 years, the day has finally arrived – the AMM is live on XRPL mainnet! Thus begins a longer road from today’s initial rollout to future growth milestones for users, traders, devs, market makers and many more. Looking forward to the journey alongside all of you in the XRPL
I'm speaking at
@PyChainConf
next week! If you're interested in learning more about how to interact with the
#XRPL
in Python, you should register to attend (for free)!
🥁PyChain Program Agenda is out now! 🥁
Check out the amazing lineup talks we have installed for the first ever Python and blockchain developer conference
#PyChain
.
Meet our speakers 💪💪
Grab your FREE ticket here:
@jammes_nova
There's a (somewhat scammy) project selling inscriptions on the XRPL and their website creates a bunch of new accounts for each person so they can spam more. The account deletes mean that some folks are stopping, and hopefully the current high load will start to go down soon.
I've been tinkering with this spec for the last couple of months, and given the recent community discussions on the topic I decided it was time to go public 🙂 As always, any and all feedback on this proposal is greatly appreciated.
Now for the errors.
1) tecINSUFFICIENT_RESERVE
This error was incredibly common on the ledger in the first couple of hours.
This means that the account sending the transaction (usually a mint, sometimes an offer create) doesn't have the funds in reserve...
Even if you’re not a C++ engineer, there are ways to learn how to write amendments - for example, I’m working on a project called "plugins" that allows devs to write experimental amendments in languages like Python instead in a lower-stakes environment.
@sentosumosaba
@realSologenic
That's actually one thing I liked about the proposal: funding can come from diverse sources, including from businesses running on the XRPL. If they want to have a say in whatever this organization is, they need to pay - and some of those funds could be used for infra.
1/ The
#XRPLedger
’s primary use case is facilitating and settling cross-currency transactions, but there's some pretty sweet tech under the hood that makes it all happen
Tomorrow I’ll be discussing the XRPL Plug-Ins API with
@msvadari
from
@RippleXDev
It’s a must-know for Devs, making it easier to work on new sidechains and proof-of-concept launches
All without C++ experience!
First off, how do you view the errors? Most marketplaces likely don't show you the raw data of what's on the ledger - they don't really need to. They can show info at a higher level. However, you might need the raw data in order to figure out the issue.
To view the raw data...
for the NFT/offer they're creating (2 XRP per 32 NFTs).
You can determine your current reserve via the account_info command (the reserve is currently 10 XRP + 2 * the owner count).
5) tecOBJECT_NOT_FOUND on NFTokenAcceptOffer
This error means that the ledger can’t find the offer you’re trying to accept. It probably occurred because the ledger was already accepted or canceled. In this case, it was canceled 4 ledgers earlier.
I use , especially for data about specific NFTs (you can search by NFT ID). There's also
@bithomp
and
@xrpscan
, which are great, especially for aggregate data.
BREAKING:
@Ripple
will never ask you to send us XRP. Ever.
Neither will Brad, David, Monica, Stu, or anyone from Ripple.
Learn how to protect yourself from scams: