Package Details: rippled 1.9.4-1

Git Clone URL: (read-only, click to copy)
Package Base: rippled
Description: Ripple peer-to-peer network daemon
Upstream URL:
Keywords: cryptocurrency ledger node ripple xrp
Licenses: ISC
Submitter: robcat
Maintainer: None
Last Packager: 0b100100
Votes: 3
Popularity: 0.000073
First Submitted: 2016-12-30 14:50 (UTC)
Last Updated: 2022-09-25 19:41 (UTC)

Latest Comments

1 2 Next › Last »

0b100100 commented on 2021-12-24 18:27 (UTC)

rippled 1.8.2-2:

The rippled service now runs as a separate user called "rippled" as suggested by the upstream service file.

Furthermore the /var/lib/rippled and /var/log/rippled directories will automatically be created and change to the correct permissions with the help of "[State,Logs]Directory=" options added inside the service file.

At last I turned on as many of the sandboxing options as possible to limit the exposure of the system towards the rippled process.

I am open for any feedback.

lmartinez-mirror commented on 2021-07-19 06:39 (UTC)

Trying to fix this package, unfortunately there are errors with compiling the downloaded submodules.

robcat commented on 2018-12-03 17:27 (UTC)

I've updated the package with a temporary switch to the develop branch (the 1.1 version has problems detecting the latest boost library).

I've also removed the systemd .service file and moved the configuration files to the default location /etc/opt/ripple. Rippled can be started with "sudo rippled".

steinbuch commented on 2018-11-21 19:31 (UTC)

@robcat: Your problem is solved on github!

Has anyone experience where in the src directory the binary "rippled" is generated by the git version?

robcat commented on 2018-10-13 17:34 (UTC) (edited on 2018-10-13 17:36 (UTC) by robcat)

Can someone help me solve this problem with OpenSSL (both openssl and openssl-1.0 are installed)?

Could NOT find OpenSSL, try to set the path to OpenSSL root folder in the system variable OPENSSL_ROOT_DIR (missing: OPENSSL_CRYPTO_LIBRARY) (found suitable version "1.1.1", minimum required is "1.0.2")

kaythxbye commented on 2018-09-03 15:29 (UTC)

The PKGBUILD contains an error. Line 22 (the content of function check) should look like this:

"${srcdir}/rippled" --unittest

robcat commented on 2018-01-21 05:43 (UTC)

There is a new version, but it's not yet compatible with the current boost library:

pixelyte commented on 2018-01-13 17:20 (UTC)

Theres a PKGBUILD provided by the developers in the github tree.

r0qs commented on 2017-12-14 22:59 (UTC)

Thank you @robcat, I checked the version of protoc and looks like that the version of protoc is wrong, the protoc binary installed by package protobuf-3.4.1-1 is version 3.4.0 and not 3.4.1. But this is strange, because I installed the protobuf via pacman from the main repository, and nobody else had this problem.

:~ $ which protoc
:~ $ protoc --version
libprotoc 3.4.0
:~ $ pacman -Qo protoc
/usr/bin/protoc is owned by protobuf 3.4.1-1

Which version is the protoc in your machine?

robcat commented on 2017-12-14 03:11 (UTC)

I'm not aware of problems with protobuf 3.4.1 (rippled compiled successfully on my machine).

Can you double check which version of protobuf that is installed on your system? Your pacman output only shows that you have an up-to-date package db, but gives no info on the actual installed package.