weird monerod can talk to rpc with username but curl fails

have you checked what protocol is it using?

how?

<o​frnxmr:xmr.mx> Hm?

think it is using randomx

<s​yntheticbird:monero.social> ?mH

protocol as in port?

RPC protocol

<s​yntheticbird:monero.social> RPC is http

i can access info with monerod with --rpc-login but trying to use curl gives unauthorized access

ah

do i need to open port 80 then?

<s​yntheticbird:monero.social> lexonight no unrelated

<s​yntheticbird:monero.social> RPC by default is http on port 18081.

i don't know, you kids really screwed the inernet with javascript

18089 lol

<s​yntheticbird:monero.social> It is perfectly possible that monerod implemented a login system that do not rely on standard http headers

<o​frnxmr:xmr.mx> Have to use login when using rpc too

<o​frnxmr:xmr.mx> digest auth

<o​frnxmr:xmr.mx> When using curl*

yeah that don't work AI

but can tell sync by monerod with proper --rpc-login

from my other computer

while ssh'd

and p2pool needs it quoted to work

<o​frnxmr:xmr.mx> ` -u username:password --digest `

is m-relay AI?

<o​frnxmr:xmr.mx> Use

<o​frnxmr:xmr.mx> Sentences

<o​frnxmr:xmr.mx> Yes

drr

<o​frnxmr:xmr.mx> xmrAI

wow

amazzzzing AI?

m-relay is such an advanced AI

that it actually emulates humans down to a T

<o​frnxmr:xmr.mx> Thank you! You are wonderful too!

<o​frnxmr:xmr.mx> Your session will end in 3 minutes. Are you still there?

Unable to load event that was replied to, it either does not exist or you do not have permission to view it.

never there

well just figuring out a vash file to check syncronization before running p2pool

bash too vash is to far in the future

been writting down the journy, hopefully make a jiffy bash install file

so far : monerod_url=""

monero_user=""

# get monerod binaries

#update and install git nano

dnf update -y

dnf install git nano

# resize the disk from default instalation

lvextend -l +100%FREE /dev/mapper/fedora_commadore64-root

xfs_growfs /dev/mapper/fedora_commadore64-root

#add monero user for the blockchain

# array of foldres /etc/monero /var/lib/monero /var/log/monero

useradd --system monero

mkdir -p /etc/monero # config

mkdir -p /var/lib/monero # blockchain

mkdir -p /var/log/monero # logs

chown monero:monero /etc/monero

chown monero:monero /var/lib/monero

are you running fedora in a commodore64?

chown monero:monero /var/log/monero

#doewnlod monero binaries with wget if you want

tar -xvf monero-linux-x64-<version>.tar.bz2

rm monero-linux-x64-<version>.tar.bz2

mv monero-x86_64-linux-gnu-v0.18.3.4/* /usr/local/bin/.

also like stop before you get K-lined

chown monero:monero /usr/local/bin/monero*

#set up the config file for systemd

# /etc/monero/monerod.conf

or kicked

#

# Configuration file for monerod. For all available options see the MoneroDocs:

# docs.getmonero.org/interacting/monerod-reference

# Data directory (blockchain db and indices)

data-dir=/var/lib/monero/bitmonero # Blockchain storage location

# Optional pruning

#prune-blockchain=1 # Pruning saves 2/3 of disk space w/o degrading functionality but contributes less to the network

#sync-pruned-blocks=1 # Allow downloading pruned blocks instead of prunning them yourself

# Centralized services

check-updates=disabled # Do not check DNS TXT records for a new version

enable-dns-blocklist=1 # Block known malicious nodes

# Log file

log-file=/var/log/monero/monero.log

log-level=0 # Minimal logs, WILL NOT log peers or wallets connecting

max-log-file-size=2147483648 # Set to 2GB to mitigate log trimming by monerod; configure logrotate instead

# P2P full node

#p2p-bind-ip=0.0.0.0 # Bind to all interfaces (the default)

#p2p-bind-port=18080 # Bind to default port

#no-igd=1 # Disable UPnP port mapping

# RPC open node

#public-node=1 # Advertise to other users they can use this node for connecting their wallets

rpc-restricted-bind-ip=0.0.0.0 # Bind to all interfaces (the Open Node)

rpc-restricted-bind-port=18089 # Bind to a new RESTICTED port (the Open Node)

# RPC TLS

rpc-ssl=autodetect # Use TLS if client wallet supports it (Default); A new certificate will be regenerated every restart

# ZMQ

#zmq-rpc-bind-ip=127.0.0.1 # Default 127.0.0.1

#zmq-rpc-bind-port=18082 # Default 18082

zmq-pub=tcp://127.0.0.1:18083 # ZMQ pub

#no-zmq=1 # Disable ZMQ RPC server

# Mempool size

max-txpool-weight=2684354560 # Maximum unconfirmed transactions pool size in bytes (here ~2.5GB, default ~618MB)

# Database sync mode

#db-sync-mode=safe:sync # Slow but reliable db writes

# Network limits

out-peers=24 # This will enable much faster sync and tx awareness; the default 8 is suboptimal nowadays

in-peers=48 # The default is unlimited; we prefer to put a cap on this

limit-rate-up=1048576 # 1048576 kB/s == 1GB/s; a raise from default 2048 kB/s; contribute more to p2p network

limit-rate-down=1048576 # 1048576 kB/s == 1GB/s; a raise from default 8192 kB/s; allow for faster initial sync

# Tor/I2P: broadcast transactions originating from connected wallets over Tor/I2P (does not concern relayed transactions)

#tx-proxy=i2p,127.0.0.1:4447,16.disable_noise # I2P

#tx-proxy=tor,127.0.0.1:9050,16,disable_noise # Tor

# Tor/I2P: tell monerod your onion address so it can be advertised on P2P network

#anonymous-inbound=PASTE_YOUR_I2P_HOSTNAME,127.0.0.1:18085,64 # I2P

#anonymous-inbound=PASTE_YOUR_ONION_HOSTNAME:18084,127.0.0.1:18084,64 # Tor

# Tor: be forgiving to connecting wallets

disable-rpc-ban=1

#end config

#enable service

systemctl daemon-reload

#selinux

ausearch -c '(monerod)' --raw | audit2allow -M my-monerod

semodule -X 300 -i my-monerod.pp

systemctl enable monerod

systemctl restart monerod

i'm surprised you haven't even gotten kicked yet

systemctl status monerod

tail -n100 /var/log/monero/monero.log

#open ports

18080/tcp

18089/tcp

# easy open ports function

for i in 18080 18089

do

firewall-cmd --permanent --add-port=${i}/tcp

done

#build xmrig

sudo dnf install -y git make cmake gcc gcc-c++ libstdc++-static libuv-static hwloc-devel openssl-devel

git clone github.com/xmrig/xmrig.git

#nano donate.h

nano src/donate.h

change the 1 to 0

cd

mkdir xmrig/build && cd xmrig/build

cmake ..

make -j$(nproc)

#build xmrig proxy

dnf install -y git make cmake gcc gcc-c++ libstdc++-static libuv-devel openssl-devel libuuid-devel

git clone github.com/xmrig/xmrig-proxy.git

mkdir xmrig-proxy/build

cd xmrig-proxy/build

cmake .. -DUUID_LIBRARY=uuid

make -j$(nproc)

#p2pool neeeds password quoted

p2pool --rpc-login 'igor:Weaponx93$$' --wallet 4AQRNe71kf15qZpKNWGCZh3ezv2dm8DX7P1M8AYNWKQoepTWwmaRYup1Xj5uptZoapMTwqGGJ6hLViCJPiL3AqVpMWyqGKV --rpc-port 18089 --data-dir /etc/p2pool

#build p2pool

sudo dnf install -y git @development-tools cmake libuv-devel zeromq-devel libsodium-devel openpgm-devel krb5-devel libcurl-devel libidn2-devel libnormaliz-devel

git clone --recursive github.com/SChernykh/p2pool

mkdir p2pool/build && cd p2pool/build

cmake ..

make

# will have to impliment all the configs and systemd files

# once node is synced backup to other computer

you literaly leaked your rpc login and public wallet address

scp -r <user>@<computer-where-node is>:

idk i copied this

haven't you copied ENOUGH

fedora server

hostname commadore64 lol

so no dell

i guess ai understands i need help configuring this

got the node day and a 3/4 day

nope steal it

reset it

that config looks clean

nice try though

lol oh shit oh no

well changed the user password

but the wallet dont matter

2025-01-29 01:55:30.342 I Monero 'Fluorine Fermi' (v0.18.3.4-release)

Height: 3335607/3335607 (100.0%) on mainnet, not mining, net hash 3.73 GH/s, v16, 24(out)+0(in) connections, uptime 0d 0h 0m 47s

anywho have a good night Cindy :P

<s​yntheticbird:monero.social> LMAO

<o​frnxmr:xmr.mx> Input too large, please use www.zerobin.net

hey all,

I find cake wallet bit bloated and also hate their approach to support all currencies despite their scaminess,

do we have feature-rich (monero-wise) app on Android?

PC I have feather and all good

monerujo isn't enough?

that's the only one that i've used on android but it works

do they support polyseed? last time they didnt

works great if you have a hardware wallet

I see not much point of having hardware wallet tbh

if monerojuo supports polyseed will try again

is there a reason why they not supporting polyseed?

maybe devtime?

<p​lowsof:matrix.org> viscous24 J0J0XMR has a PR adding polyseed to monerujo. their team are just not active

<p​lowsof:matrix.org> funded by a bounty @ bounties.monero.social/posts/116/2-…polyseed-support-for-monerujo-0-25m . i suspect they will just wait until polyseed is added to monero-core so they dont have to review the patch themselves

hi

<3​21bob321:monero.social> Why are they so slow

<3​21bob321:monero.social> Debian updates more

<s​yntheticbird:monero.social> r/rareinsults

can someone tell me what does monero-cpp mean when it says "m_w2->multisig()" in some of its code

GCC doesn't know either

i can't find that function anywhere

<s​yntheticbird:monero.social> Cindy, ripgrep is your best friend

<s​yntheticbird:monero.social> that's what I've done since 1987

<s​yntheticbird:monero.social> abandon LSP navigation. Embrace substring searching

i've tried grep

multisig is not a function whatsoever in monero-cpp's code

and monero's wallet2 and wallet header files

<s​yntheticbird:monero.social> 💀

lemme check some more

i just realized where the multsig function exists

monero-project/monero: src/wallet/api/wallet2_api.h

and monero-cpp doesn't include this file

well, #include

(also seems to be a seperate struct?)

shit, i need help

<o​frnxmr:xmr.mx> aremor which pr discussion were you referring to

<o​hchase:envs.net> old.reddit.com/r/Monero/comments/1i…how_to_run_your_own_node_on_android this comment is incomplete correct? Any usage of a remote node even if you obfuscate your initial connection still means you are liable to get your transactions tainted with already used decoys, correct?

<r​ucknium:monero.social> ohchase: Decoys are used many times anyway. Probably close to 16 times if everyone spends their outputs at the same rate that they create them.

<r​ucknium:monero.social> The standard Monero wallet code has some protections against malicious nodes giving an incorrect output distribution. AFAIK, the countermeasures have not been evaluated comprehensively.

<o​frnxmr:monero.social> Running a node on android is fine, just not on your daily driver

<o​frnxmr:monero.social> Reason: battery, bandwidth, inconsistent connectivity.

<o​frnxmr:monero.social> Run on a secondary device = profit

<o​frnxmr:monero.social> My android node ran for > 2 years straight. Recently had to shut it doen because it ran out of storage

<o​frnxmr:monero.social> (ran out because it has other stuff on it, and only 128gb total)

Then wallet2 can check the elements after N aren't too crazy.

<o​hchase:envs.net> Couldn't I create transactions though and then feed you my decoys, strategically trying to evade the counter measures in the wallet's check?

sorry for being stupid here, i realized i had monero set to the HEAD commit instead of the release-v0.18 tag

The wallet chooses indices, then asks for the data. Ring members are refered to by index. If you subsitute your known decoys for one the wallet asked for, the verification will fail because the data hte verifier gets from the index will not match the data you gave, leading to a bad signature.

However, it might be enough for the attacker, since they won't need to add the tx to the chain.

The wallet includes the output it wants to spend among the data it asks for.

The node doesn't know which one it is, and the wallet will reject data if the claimed data for that output does not match the wallet's idea.

So the node has to alter only some of the data, and hope it doesn't alter the real one.

I guess if such a trigger happens, the wallet ought to remember never to use that node again...

There is no long lived dynamic ban system atm.

So if the node replaces 50% of requested outputs, the wallet has 50% chance of detecting something is wrong, and if it doesn't, the daemon will halve (on average) the ring size of the resulting tx.

<r​ucknium:monero.social> Nodes don't send decoys to wallets. They send an age distribution of outputs. Then the wallet picks the decoys from the distribution. A common misconception.

Off the top of my head so I might be off.

<o​hchase:envs.net> thank you, I'll take more time to figure all this out. Trying to wrap my head around the malicious spy node significance more; the black marble attack was more easy for me to understand

<r​ucknium:monero.social> Have you seen the "Breaking Monero" episode on remote nodes?

<r​ucknium:monero.social> It's old and may be out of date, but it's worth a look

<o​hchase:envs.net> I have watched some of it, but it is long and yes I saw it was 6years old so was worried about outdated information

<a​remor:matrix.org> A convo with tobtob (sp?) about some PRs getting reviewed.

<o​frnxmr:xmr.mx> was in -dev

<o​frnxmr:xmr.mx> There are a few diff discussions tho. Merge criteria and dormant pr's and issues, for example

<o​hchase:envs.net> @m​oneromooo i appreciate your commentary as well and did in fact read it

<l​za_menace:monero.social> does proxy config setting on the node mean that the chain will be downloaded over the proxy? tor or i2p or whatever?

<o​frnxmr:xmr.mx> `--proxy` ?

<o​frnxmr:xmr.mx> I2p = no. Tor = yes, exit nodes only

<o​frnxmr:xmr.mx> It just sends outgoing connections over the socks proxy. Blocks incoming connections, since you cant have inc over tor

<o​frnxmr:xmr.mx> We dont do blockchain sync over onion/i2p at all

<l​za_menace:monero.social> ty

Hello frens, does anyone happen to know the pruned and/or full blockchain sizes for stagenet and/or testnet?

I'm not sure if this is available somewhere, I only found localmonero.co/blocks/stats/blockchain-growth which shows the mainnet blockchain is at about 150 GB and I have a pruned mainnet blockchain at 98 GB so it seems to make sense.

<l​za_menace:monero.social> full - stagenet: 14 GB, testnet: 7.7 GB

after a few days of trial and error, i've now finally managed to build monero and monero-cpp within ONE meson.build file (which is more stricter than cmake due to the fact it has a path sandboxing which would break onion explorer or monero-cpp's way of getting monero libraries normally)

meson seems to do this a lot better, considering its cmake subproject interpreter exposes all targets regardless of them being exported or not

exposes all targets to the top-level project's build file*