I think I saw what there is to do if compiling current master fails with a linking problem, but can't find it again in the backlog

In my case linking libwallet-crypto.so of current master as of today on Linux fails with error messages similar to this one:

relocation R_X68_64_PC32 against symbol `crypto_sign_ed25519_amd64_64_38` can not be used when making a shared object; recompile with -fPIC

in light of recent advancements in sneaky cooperation by TPTB, and anticipating an escalation of persecution, would it not be wise to have the capacity to run monero nodes *exclusively* over tor/i2p ?

correct me if i'm wrong, but right now only txs are propagated over anonymity networks. if things keep heading the way they're headed, soon it could become a liability for people to run nodes. at the extreme it becomes a liability to run tor/i2p too, but we're not quite there yet

that's a dumb question

we have no control over the carrying capacity of tor/i2p networks

i don't mean move the entire network there

you just said *exclusively*

i mean have the option for the operator to make a choice regarding higher lantencies etc, and run their node communications over tor/i2p

exclusively in the context of a single node

It was the goal. Default hybrid, with options to be clearnet only or i2p only.

So, patches welcome I guess.

A little hint for my linker problem on Linux trying to compile latest head, failing to link libwallet-crypto.so with errors like these:

relocation R_X86_64_PC32 against symbol `crypto_sign_ed25519_amd64_64_38' can not be used when making a shared object; recompile with -fPIC

Build debug-all or debug-static-all

Interesting. What's the difference between "build debug" that I did and "build debug-all"?

debug builds shared libs, the other two don't. It's in the Makefile.

Alright, thanks, will try. Are fixes for building shared libs on the way?

#6782

Nice.

Could anyone test if the "validate_address" method works in Wallet RPC?

tests/functional_tests/functional_tests.py /usr/bin/python tests/functional_tests ./build/.../release validate_address

moneromooo: thanks! :)

exit

moneromooo: what do you mean with "embeds your changes" ?

don't think sarang will rebase

The diff since last push had some changes I made.

Oh, wait, maybe this got merged and he rebased. Let me check now...

Right. I got confused. The diffs inlcude my changes, but they're just because of a rebase. It was just a tiny rebase so they looked like patch updates. Ignore that then.

.merges