Navigate:
All Reposrippled
~$RIPPLE0.1%

rippled: XRP Ledger blockchain daemon in C++

Peer-to-peer consensus node for XRP Ledger network.

LIVE RANKINGS • 06:52 AM • STEADY
OVERALL
#210
4
NETWORKING
#7
30 DAY RANKING TREND
ovr#210
·Netwo#7
STARS
5.1K
FORKS
1.6K
DOWNLOADS
7D STARS
+3
7D FORKS
+1
See Repo:
Share:

Learn more about rippled

./rippled --conf=/path/to/rippled.cfg ./rippled server_info


1

Byzantine Fault Tolerant Consensus

Settles transactions in 4-5 seconds without central authority using a novel consensus algorithm. Achieves up to 1500 transactions per second with validator agreement across distributed nodes.

2

Multi-Mode Operation

Runs as validator, full history node, or API server from a single codebase. Configure operational mode based on network role without separate implementations, with Clio available for dedicated API serving.

3

Flexible Cryptographic Support

Supports ECDSA and Ed25519 digital signatures with extensible architecture for adding algorithms. Enables cryptographic schemes to evolve with standards without protocol redesign.


from xrpl.clients import JsonRpcClient
from xrpl.models.requests import ServerInfo

client = JsonRpcClient("http://localhost:5005")
response = client.request(ServerInfo())
print(f"Server state: {response.result['info']['server_state']}")

v2.6.1

Maintenance release downgrades Boost to 1.83 and disables the unsupported PermissionDelegation feature.

  • Rebuild against Boost 1.83 if you compiled from source; the 2.6.0 Boost version caused compatibility issues.
  • Note that PermissionDelegation is now explicitly marked unsupported and should not be used in production.
v2.6.1-rc2

Marks PermissionDelegation feature as unsupported; no breaking changes or migration steps specified in release notes.

  • Verify that your deployment does not rely on PermissionDelegation, now marked unsupported.
  • Release notes do not specify version requirements, security fixes, or other functional changes.
v2.6.1-rc1

Downgrades Boost dependency from 1.85 to 1.83 to resolve compatibility issues in the 2.6 series.

  • Ensure your build environment provides Boost 1.83 instead of 1.85 before compiling this release candidate.
  • Release notes do not specify whether this change affects runtime behavior or only build-time compatibility.

See how people are using rippled

Loading tweets...


[ EXPLORE MORE ]

Related Repositories

Discover similar tools and frameworks used by developers