Hi, I’m Kris Dangerfield.
🛠️ 30 years solving real problems for real customers using code as my sword.
🔗 9 years grinding in blockchain & Web3 trenches.
Going forward, I’ll be sharing:
• XRPL deep-dives, commentary & educational content
• Developer tips & architecture patterns
• Founder lessons, AI experiments & edge-tech updates
• What life looks like balancing entrepreneurial + family life.
Let’s build smart things together. 🚀
(👇 Drop what you’re working on in the replies!)
Been quite unwell this last few days and spent some time hanging out in spaces - had great fun with @Stone_XRPL and his peeps, thought I’d return the love for a while.
This is awesome 👇
and now it’s finally over a little humour… why is it that the typesetting on these documents are like it was done on a typewriter in 1970?
How do you not already have 5000 followers?
If you’re not following @CryptoQueenAU please do so now; it’s follow Friday #FF so get on it 👍 and I’ll try and join that space, I love a good giveaway 🤪
I will be attending this free workshop today by @DanielPriestley, I attended a previous workshop and it was very interesting, this one today is all about AI and how to use it. I would 100% recommend following this guy, especially if you’re running a business or thinking of starting one. Check the video and register… it’s free and yes there is a sales angle but… there was no pressure, I just got a ton of value last time.
I’m not paid to post this, just a fan.
It’s clear from this response that as a community we need to do way more to promote the value of the firewall amendment. If someone as significant to our community has never heard of firewall, we need to do much more. please retweet and tag all the largest accounts you follow. What we need now more than anything is momentum as we’re about to enter the next phase of the project, more on this next month.
Lots of talk today about security. When a well-known XRPL community member gets compromised it’s a reminder: hacks, scams & worse happen far more often than we’d like to believe.
Progress on XRPL Firewall continues…. it was always going to be a long process, and we were right.
If you haven’t joined the waitlist, now’s the time. Go read about it & register. Denis (@angell_denis) & I hope to have a meaningful update in 6 weeks.
https://t.co/uIIdTp35UQ
If you’d like a Space on firewall/security, like & RT — more sign-ups = good signal to schedule it.
Apps made with this kind of technology should be forced to declare it on the App Store. It’s only a matter of time before one of these things goes horribly wrong.
Don’t get me wrong AI is amazing but it should be used by developers to enhance and speed up development, not given freely to anyone to just have a go. It’s like giving the keys to a car to a toddler right now, what do you think is gonna happen?
Maybe one day, maybe sooner than I’d like, but not today.
Well @OpenAI just launched GPT-5 and in the promo ad one of the things it’s boasts, is re-write my entire codebase in Rust… hmmm I wonder. @angell_denis
Thanks to djatlantic for sharing the opinion. 👇
I quoted this tweet as i feel like it sums up how most moderate people feel... irritated.
I think that the biggest issue is that when David aka @JoelKatz speaks, he has an authority that goes beyond pretty much anyone else in the XRPL community. People cling to what he says and sadly unless he is extremely clear, what he says gets taken out of context and used to suit other peoples own agenda.
It's worth noting that he was addressing a group of trainee core developers, not a community of non-devs. It was probably a mistake in hindsight to publish such a video, given the nuance of the conversation will be lost on many; its also worth noting that he was answering a question on the fly, without prep, so just gave a response, this was not an announcement of moving the code to Rust; he merely acknowledged that this has been discussed and how he saw such a thing working. For the record, this whole Rust discussion has been going on for over a year or more. This is not news.
Summing up, this is why i wrote my longer piece; nothing is decided; sensible discussion is good and welcomed, hyping this up or fudding it down, is what i aim to help calm, along with other sensible people like @msvadari@angell_denis and others.
So i don't blame people for wanting to understand it, I don't blame anyone for getting excited, but I do call out anyone who bends this type of news to suit an agenda. especially those touting this as the latest reason XRP is gonna "pump".
We are not porting rippled to Rust! not today anyway.
To my knowledge all that is happening is Rust is being talked about in the context of how it could be used to enhance the current tech stack and benefit the chain. If anything does progress with this, it will be a big deal but equally from the perspective of 99.9% of people, it will be a total nothing burger, cus the goal of such a change would be to do it so that nothing actually changes outwardly. No new xrp, xrp is xrp. No airdrops, Nothing to download or install or upgrade, no changes needed to existing code. A total nothing burger, beyond low level benefits and no... moving to rust is not (on its own) going to make the xrpl process 10x more transactions per second, LMAO. C++ is actually an extremely efficient language, this is not like comparing rust to javascript.
If after evaluation, the benefits outweigh the negatives, I'd fully support it in whatever form it takes, but to the best of my knowledge we are a long way from any kind of announcement, in fact there may not even be an announcement, this is low level engineering, it makes no difference to most people and you wouldn't really know when its been done anyway.
I really hope that future discussions around this can stick to facts and be meaningful, as opposed to turning this into yet another drama.
Thanks to anyone that read my second rather long post on this subject, if you got something from it, please share it.
Today I’ve seen 2 tweets from DS @JoelKatz, 1 about introducing Rust to the XRPL stack and another about running his own infra.
As per instructions from @dazzlingxrpl today’s @xrplceo I’m hearby tweeting bullish positive news, which is… of David’s 2 tweets, running a commercial grade Hub in NYC is way more bullish to me… cus it’s tangible, very doable and beneficial to the network TODAY…
#BullishSignal #XRPL
Lots of talk about re-writing rippled in Rust. Thanks @sentosumosaba for promoting the conversation. For those interested in the perspective of a dev, here it is…
Rewriting rippled in Rust sounds like a smart move at first glance. Rust is safe, modern, and quickly becoming the language of choice for blockchain infra. It has advantages such as memory safety and generally accepted better tooling so the advantages feel compelling. I can understand the excitement.
But here’s the problem: rippled is a deeply complex, performance-critical system. The codebase has been battle-tested for over a decade, with optimisations that only come from years of iteration. Rewriting that in a new language, no matter how good that language is, isn’t just about porting code. Trust me, I’ve done this on smaller scale projects and believe me, it will become a re-write, it’s just the nature of refactoring as you go, the opportunity to rebuild it better will be too much; it’ll take twice as long as anyone thinks and cost three times as much, plus the reputational risk alone for potentially a trillion dollar chain by the time this is complete is staggering.
Best-case, this is a multi-year, multi-million-dollar effort. And worse, during that time, progress on actual XRPL features, the stuff users care about, slows to a crawl because people know we’re counting down time until the inevitable switch.
There’s also the people factor which in my view is massive. The devs who know the internals of rippled are mostly C++ veterans. Asking them to drop what they know and switch to Rust en masse isn’t trivial. You either lose them or spend time retraining which removes forward progress of the current codebase. Either way you lose progress or people, neither of which is good.
A better approach might be to selectively bring Rust into the ecosystem, which in my view is likely what @JoelKatz is thinking… start with tooling, test infrastructure, or isolated modules. Use it where it makes sense, bring in a new breed of developer and if Rust proves itself inside the XRPL stack, maybe a Rust-based node emerges organically and if not it probably shouldn’t.
What I do agree with though, that I read into from what David said is that there is recognition of work to be done, such as architectural documentation and evaluation and this doesn’t require moving to rust. Replacing C or Rust outright, right now would be like rebuilding the engine of a race car while you’re in the middle of a Grand Prix season, where you’re in a leading position, the risk isn’t worth it for the potential gains.
Whatever way you shape this, it will cost millions so what I’d rather see that money invested into a properly funded core dev team and slowly iterate to the same place; this is safer and smarter for all the reasons I’ve outlined.
Above all though, I’m supportive of the underlying reasons for the conversation and whatever route we end up going, it will have my support. I’d very much love the opportunity to flesh this out with other devs on a space and hear both sides. @angell_denis up for it?
See Daniel interviewed by me about all things XRPL infra. It’s a really interesting interview, great perspective and some great advice too and this is only 25 mins of about 6 hours of XRPL content. 👇