Skip to main content

Custom monitoring graphs for validator

emake -j1

If you can manually make, but always fail in src_compile(), look at your MAKEOPTS, if it is "-j2", consider using "emake -j1"


VxJasonxV said…
Could you tell us why?
I'm fairly interested in more information you can provide.
fiag said…
I look into some ebuilds. some use 'make' instead.
Zhang Le said…
to vxjasonxv:
-j2 means make will start two thread to make simultaneously, however the one thread(call it A)'s prerequisite may depends the other thread(call it B)'s output, and B's output maybe not ready when A is going to use it. This is my guess.

to fiag:
yes. A gentoo dev told me better to use emake -j1, :)

Popular posts from this blog Ripple validator upgraded to 0.81.0

Information about this version can be found here

This happened at about 1:45pm local time.

There were some behavior changes after the upgrade:

How exactly is XRP going to work as a bridging digital asset?

Maybe this is obvious all along to some people. Anyway, I just figured this out. So I thought maybe it's worth sharing.

Previously I thought the bridging consists of two transactions, both on XRP ledger. One from fiat currency A IOU to XRP, the other from XRP to fiat currency B IOU.

Then I saw this:

So Miguel Vias said in the pilot they used liquidity on bitstamp and bitso. However it's seems the trading volume of XRP/bitso.MXN since the beginning of 2017 is so low that it's virtually no liquidity there. See this:

Then I realized, just like bitstamp, bitso has its own exchange and the liquidity there is much better.

So now it's clear to me there is another way for XRP to bridge cross-border payments. The originat…

You have to know these about ripple wallet and secret key


It's possible to find out others' secret keys but it's so improbable that it's almost impossible. Make sure you have a good entropy source when generating your address/secret key.Use multi-sign
See the discussion here: