HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
XRPLF
rippled
C++2013–2026
XRPLF / rippled

rippled

Decentralized cryptocurrency blockchain daemon implementing the XRP Ledger protocol in C++

7Distinct people
11Mentions
0Explicit recommenders
5.2KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Decentralized cryptocurrency blockchain daemon implementing the XRP Ledger protocol in C++

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year11 dated mentions

Observed mentions: 2013-09-26 02:17:07 UTC to 2026-02-25 18:37:54 UTC.

0122013-01-01 00:00:00 UTC to 2014-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments20132014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20132013-01-01 00:00:00 UTC2014-01-01 00:00:00 UTC211
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC202
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC000
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC101
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC000
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC202
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC000
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC000
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC101
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC202
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC000
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC000
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC000
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC110

What Hacker News says

11 sources
Ripple | REMOTE or ONSITE | full-time Hi, I'm a C++ software engineer at Ripple. I work on the XRP Ledger, a peer-to-peer decentralized payment server (see https://github.com/ripple/rippled). If you like working with C++, you'll be very happy here. We use `17 and intend to move to `20 soon. Our software is cross platform, and you're welcome to use your preferred tools. The team is split pretty evenly across Windows, Linux, and Mac. We're a "remote first" team, spread across the U.S. Almost all communication is done through slack/email. Ripple is growing fast. We've got great funding, and a great team. Feel free to email me with any questions: determan at ripple.com (My name is Scott). Our open jobs are listed here: https://boards.greenhouse.io/ripple/ and we're looking to hire many roles, not just C++ roles (although I have less visibilit
Read the rest
y into the non-C++ roles). I truly like the people I work with - we're a great place to work. Come join us!
In Ask HN: Who is hiring? (March 2022)
Ripple | REMOTE or ONSITE | full-time Hi, I'm a C++ software engineer at Ripple. I work on the XRP Ledger, a peer-to-peer decentralized payment server (see https://github.com/ripple/rippled). If you like working with C++, you'll be very happy here. We use `17 and intend to move to `20 soon. Our software is cross platform, and you're welcome to use your preferred tools. The team is split pretty evenly across Windows, Linux, and Mac. We're a "remote first" team, spread across the U.S. Almost all communication is done through slack/email. Ripple is growing fast. We've got great funding, and a great team. Feel free to email me with any questions: determan at ripple.com (My name is Scott). Our open jobs are listed here: https://boards.greenhouse.io/ripple/ and we're looking to hire many roles, not just C++ roles (although I have less visibili
Read the rest
ty into the non-C++ roles). I truly like the people I work with - we're a great place to work. Come join us!
In Ask HN: Who is hiring? (February 2022)
These are not smart contracts. Its a functionality of the software that each nodes run. It can be updated if it has bugs. As longs as there is consensus that something actually is a bug. So to use the example above, you would not be able to change the signing threshold of 4 to 3 because that's what you set it to be. Its not a bug if you messed up and lost too many keys. But if the software itself actually handles some edge case wrong then the part of the code can be found fixed and added to the running ledger via amendment. But since its not a smart contract in the first place, the burden for code to be added is high. While everyone can code something, it has to go trough the amendment process and reach 80% support for 2 weeks before it actually would be applied. There is basically zero chance that something would get 80% support if the a
Read the rest
ctive developer team would question the code quality. Every code goes trough audits and runs on the test net first before people even consider to make the amendment. Still bugs happen and if you look at the change logs [1] you can see bug fixes are common for each new release. Most of these bug fixes dont affect the ledger logic but are just bugs in the node software. So funds can not be lost but in a worst case scenario it could temporary halt the network if such a bug crashes multiple nodes at the same time. [1] https://github.com/ripple/rippled/releases >At what point is switching to a more classical database both worth the increase in efficiency by several orders of magnitude,.... Thats a strange question. That point "is reached" whenever you dont need a blockchain/distributed ledger but instead have situation where the whole system is run by one entity or by a few who have legal agreements with each other. Its like asking at what point you simply write data to a file instead of to a database. There are tons of config files out there and no one suggests that we instead use a database. So why would someone ever switch back from the database to a simple file? Its p much a made up situation that never happens. There must have been a reason to use a database and that reason would need to go away. Same for DLT. If you dont need it there is mostly no point in using it. There are a few exceptions for example you could use the XRPL to store tiny bits of data for communication between otherwise autonomous systems. The benefit here isn't blockchain/DLT tech but rather that fact that you dont need to maintain servers and the fact that the XRPL has probably the highest uptime of any public internet "storage" you could use. If that is critical then it may be a valid reason. You get the 5 9s (99.999%) uptime that you simply can not buy for cheap anywhere. But again if you dont need any of the specific properties of a DL there is no point using it and comparing it to other tech with other properties.
In Ethereum community has solved a major problem of the Internet: Single Sign-On
Ripple | San Francisco, CA or REMOTE | full-time Hi, I'm a C++ software engineer at Ripple. I work on the Ripple XRP Ledger, a peer-to-peer decentralized payment server (see https://github.com/ripple/rippled). We're looking to hire a Senior C++ Software Engineer. The official ad is here: https://ripple.com/company/careers/all-jobs/#senior-software... The team knows the C++ language well. Two members regularly attend committee meetings and one member has made substantial contributions to the language. If you like working with C++, you'll be very happy here. We use `14 and intend to move to `17 soon. Our software is cross platform, and you're welcome to use your preferred tools. The team is split pretty evenly across Windows, Linux, and Mac. We're a "remote first" team, spread across the U.S. Almost all communication is done through slack/e
Read the rest
mail/skype. Ripple is growing fast. We've got great funding, and a great team. Feel free to email me with any questions: determan at ripple.com (My name is Scott).
In Ask HN: Who is hiring? (May 2018)
Ripple | San Francisco, CA or REMOTE | full-time Hi, I'm a C++ software engineer at Ripple. I work on the Ripple Protocol, a peer-to-peer decentralized payment server (see https://github.com/ripple/rippled). We're looking to hire a Senior C++ Software Engineer. The official ad is here: https://ripple.com/company/careers/all-jobs/#senior-software... The team knows the C++ language well. One member is on the committee and I believe three have submitted proposals. If you like working with C++, you'll be very happy here (we use `14). Our software is cross platform, and you're welcome to use your preferred tools. The team is split pretty evenly across Windows, Linux, and Mac. We're a "remote first" team, spread across the U.S. Almost all communication is done through slack/email/skype. Ripple is growing fast. We've got great funding (inc. Goog
Read the rest
le Ventures & Andreessen Horowitz), and a great team. Feel free to email me with any questions: monk.scott at google's mail (My name is Scott).
In Ask HN: Who is hiring? (May 2016)
Software Engineer - Ripple Identity Platform | Ripple Labs | San Francisco, CA | careers@ripple.com ========= Our team: The Ripple Identity team is revamping the way digital identity works on the Internet. We’re operating on two core beliefs: 1) that individuals - not social networks, governments, or corporations - should control their own data and 2) that access to the traditional banking system is broken. If you want to fix these problems, then we should talk! ========= About Ripple Labs: Ripple Labs is a 60+ person seed-stage startup backed by investors like Google Ventures, Andreessen Horowitz, Lightspeed Venture Partners and IDG Capital Partners. We developed Ripple (www.github.com/ripple/rippled), an open-source, distributed payments protocol that enables the exchange of value in any currency, instantly and for free. Ripple is the
Read the rest
world’s first distributed currency exchange, where you can trade any store of value, including dollars, yen, euros, bitcoins, and even loyalty points. Our code is open-source and has been forked by thousands of developers around the world. ========= About you: You’re committed to our mission of empowering consumers to access the financial system, and control their data and who they share it with. You are an engineering leader. You take pride in each commit, knowing that your work is public and you’re setting the standard for the Ripple community You are self-directed and are pro-active about asking for input You enjoy mentoring software engineers, and consider Ripple’s developer community an extension of your team You enjoy working on small teams, and managing your time without direct supervision ========= Your background: Javascript experience, especially Node.js (Angular.js, Less, or Jade experience are an added bonus) Professional experience with backend web development, in any language Professional experience with test driven development Preferred experience implementing open standards for authentication and authorization, such as OAuth and OpenID Connect Ability to communicate effectively with a scientific mindset - empirically test your hypotheses Startup experience or past work with distributed systems or cryptocurrencies are an added bonus Interests: open-source, entrepreneurship, economics and financial markets, strong work ethic, creative thinking, systems architecture thinking, cryptography, creative logic, fast-paced environment ========= What we offer: Competitive salary and compelling seed stage equity Fully paid medical and dental insurance for employees, 50% contribution for spouses and dependents Take time off when you need it - unlimited vacation policy Industry-leading maternity and paternity leave policies Open source projects 100% of the time A learning environment where you can dive into the latest technologies and engineering principles as well as mentor our upcoming engineers Work with some of the best - early Bitcoin pioneers and cryptographers, ex-NASA engineers, ex-Fed regulators ========= To apply, email careers@ripple.com
In Ask HN: Who is hiring? (October 2014)
Senior Software Engineer - Front End | Ripple Labs | San Francisco, CA | careers@ripple.com ========= Our team: The Ripple Client team is responsible for taking Ripple’s groundbreaking new technology and making it usable. Our code is open-source and has been forked by thousands of developers around the world. ========= About Ripple Labs: Ripple Labs is a 60+ person seed-stage startup backed by investors like Google Ventures, Andreessen Horowitz, Lightspeed Venture Partners and IDG Capital Partners. We developed Ripple (www.github.com/ripple/rippled), an open-source, distributed payments protocol that enables the exchange of value in any currency, instantly and for free. Ripple is the world’s first distributed currency exchange, where you can trade any store of value, including dollars, yen, euros, bitcoins, and even loyalty points. ======
Read the rest
=== About you: You are an engineering leader. You take pride in each commit, knowing that your work is public and you’re setting the standard for the Ripple community. You create intuitive user interfaces that make our users smile. You enjoy mentoring software engineers, and consider Ripple’s developer community an extension of your team. You are self-directed and are pro-active about asking for input. You’re a true team player, willing to sacrifice for the greater good of our team. You’re committed to our mission of making value move like how information moves today. ========= You’ll get to: Architect and build Angular.js applications for traders and consumers around the world Collaborate with UX and product designers on building the best user experiences possible Optimize engineering processes so that our team can produce as quickly as possible Share our approach and principles with developer communities both in San Francisco and worldwide Build out a global open -source community who will look up to you for guidance and support ========= Your background: Experience building beautiful consumer user web applications Expert knowledge in Javascript Extensive knowledge about version control systems (Git preferred) Angular.js, Node.js, Less, or Jade experience are an added bonus Professional engineering experience in a diverse set of languages and understanding of engineering concepts: Object-oriented and classical inheritance paradigms Unix process and concurrency models Server application deployment and infrastructure automation Design patterns Unit and end-to-end testing Ability to communicate effectively with a scientific mindset - empirically test your hypotheses. Startup experience or past work with distributed systems or cryptocurrencies are an added bonus Interests: open-source, entrepreneurship, economics and financial markets, strong work ethic, creative thinking, systems architecture thinking, cryptography, creative logic, fast-paced environment ========= What we offer: Competitive salary and compelling seed stage equity Fully paid medical and dental insurance for employees, 50% contribution for spouses and dependents Take time off when you need it - unlimited vacation policy Industry-leading maternity and paternity leave policies Open source projects 100% of the time A learning environment where you can dive into the latest technologies and engineering principles as well as mentor our upcoming engineers Work with some of the best - early Bitcoin pioneers and cryptographers, ex-NASA engineers, ex-Fed regulators State-of-the-art penthouse facility with a private rooftop deck and private elevator in the heart of San Francisco’s Financial District and flexibility to work remotely ======== To apply, email careers@ripple.com
In Ask HN: Who is hiring? (October 2014)

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.