01:28:55 weird monerod can talk to rpc with username but curl fails 01:29:22 have you checked what protocol is it using? 01:29:33 how? 01:29:34 Hm? 01:29:43 think it is using randomx 01:29:44 ?mH 01:30:03 protocol as in port? 01:30:56 RPC protocol 01:31:07 RPC is http 01:31:13 i can access info with monerod with --rpc-login but trying to use curl gives unauthorized access 01:31:25 ah 01:31:33 do i need to open port 80 then? 01:32:12 lexonight no unrelated 01:32:24 RPC by default is http on port 18081. 01:32:32 i don't know, you kids really screwed the inernet with javascript 01:32:38 18089 lol 01:32:58 It is perfectly possible that monerod implemented a login system that do not rely on standard http headers 01:33:08 Have to use login when using rpc too 01:33:15 digest auth 01:33:23 When using curl* 01:33:28 yeah that don't work AI 01:34:01 but can tell sync by monerod with proper --rpc-login 01:34:26 from my other computer 01:34:36 while ssh'd 01:35:10 and p2pool needs it quoted to work 01:35:13 ` -u username:password --digest ` 01:35:36 is m-relay AI? 01:35:38 Use 01:35:50 Sentences 01:35:52 Yes 01:35:59 drr 01:36:14 xmrAI 01:36:20 wow 01:36:29 amazzzzing AI? 01:37:04 m-relay is such an advanced AI 01:37:11 that it actually emulates humans down to a T 01:37:33 Thank you! You are wonderful too! 01:40:30 Your session will end in 3 minutes. Are you still there? 01:42:55 Unable to load event that was replied to, it either does not exist or you do not have permission to view it. 01:44:28 never there 01:45:06 well just figuring out a vash file to check syncronization before running p2pool 01:45:24 bash too vash is to far in the future 01:46:10 been writting down the journy, hopefully make a jiffy bash install file 01:47:02 so far : monerod_url="" 01:47:02 monero_user="" 01:47:02 # get monerod binaries 01:47:02 #update and install git nano 01:47:02 dnf update -y 01:47:03 dnf install git nano 01:47:05 # resize the disk from default instalation 01:47:07 lvextend -l +100%FREE /dev/mapper/fedora_commadore64-root 01:47:09 xfs_growfs /dev/mapper/fedora_commadore64-root 01:47:11 #add monero user for the blockchain 01:47:13 # array of foldres /etc/monero /var/lib/monero /var/log/monero 01:47:15 useradd --system monero 01:47:19 mkdir -p /etc/monero # config 01:47:21 mkdir -p /var/lib/monero # blockchain 01:47:23 mkdir -p /var/log/monero # logs 01:47:25 chown monero:monero /etc/monero 01:47:27 chown monero:monero /var/lib/monero 01:47:28 are you running fedora in a commodore64? 01:47:29 chown monero:monero /var/log/monero 01:47:31 #doewnlod monero binaries with wget if you want 01:47:33 tar -xvf monero-linux-x64-.tar.bz2 01:47:35 rm monero-linux-x64-.tar.bz2 01:47:37 mv monero-x86_64-linux-gnu-v0.18.3.4/* /usr/local/bin/. 01:47:38 also like stop before you get K-lined 01:47:39 chown monero:monero /usr/local/bin/monero* 01:47:41 #set up the config file for systemd 01:47:43 # /etc/monero/monerod.conf 01:47:44 or kicked 01:47:45 # 01:47:49 # Configuration file for monerod. For all available options see the MoneroDocs: 01:47:51 # https://docs.getmonero.org/interacting/monerod-reference/ 01:47:53 # Data directory (blockchain db and indices) 01:47:55 data-dir=/var/lib/monero/bitmonero # Blockchain storage location 01:47:57 # Optional pruning 01:47:59 #prune-blockchain=1 # Pruning saves 2/3 of disk space w/o degrading functionality but contributes less to the network 01:48:02 #sync-pruned-blocks=1 # Allow downloading pruned blocks instead of prunning them yourself 01:48:04 # Centralized services 01:48:06 check-updates=disabled # Do not check DNS TXT records for a new version 01:48:08 enable-dns-blocklist=1 # Block known malicious nodes 01:48:10 # Log file 01:48:12 log-file=/var/log/monero/monero.log 01:48:14 log-level=0 # Minimal logs, WILL NOT log peers or wallets connecting 01:48:18 max-log-file-size=2147483648 # Set to 2GB to mitigate log trimming by monerod; configure logrotate instead 01:48:21 # P2P full node 01:48:23 #p2p-bind-ip=0.0.0.0 # Bind to all interfaces (the default) 01:48:25 #p2p-bind-port=18080 # Bind to default port 01:48:27 #no-igd=1 # Disable UPnP port mapping 01:48:29 # RPC open node 01:48:31 #public-node=1 # Advertise to other users they can use this node for connecting their wallets 01:48:34 rpc-restricted-bind-ip=0.0.0.0 # Bind to all interfaces (the Open Node) 01:48:36 rpc-restricted-bind-port=18089 # Bind to a new RESTICTED port (the Open Node) 01:48:38 # RPC TLS 01:48:40 rpc-ssl=autodetect # Use TLS if client wallet supports it (Default); A new certificate will be regenerated every restart 01:48:43 # ZMQ 01:48:45 #zmq-rpc-bind-ip=127.0.0.1 # Default 127.0.0.1 01:48:49 #zmq-rpc-bind-port=18082 # Default 18082 01:48:51 zmq-pub=tcp://127.0.0.1:18083 # ZMQ pub 01:48:53 #no-zmq=1 # Disable ZMQ RPC server 01:48:55 # Mempool size 01:48:57 max-txpool-weight=2684354560 # Maximum unconfirmed transactions pool size in bytes (here ~2.5GB, default ~618MB) 01:49:00 # Database sync mode 01:49:02 #db-sync-mode=safe:sync # Slow but reliable db writes 01:49:04 # Network limits 01:49:06 out-peers=24 # This will enable much faster sync and tx awareness; the default 8 is suboptimal nowadays 01:49:09 in-peers=48 # The default is unlimited; we prefer to put a cap on this 01:49:11 limit-rate-up=1048576 # 1048576 kB/s == 1GB/s; a raise from default 2048 kB/s; contribute more to p2p network 01:49:14 limit-rate-down=1048576 # 1048576 kB/s == 1GB/s; a raise from default 8192 kB/s; allow for faster initial sync 01:49:19 # Tor/I2P: broadcast transactions originating from connected wallets over Tor/I2P (does not concern relayed transactions) 01:49:22 #tx-proxy=i2p,127.0.0.1:4447,16.disable_noise # I2P 01:49:24 #tx-proxy=tor,127.0.0.1:9050,16,disable_noise # Tor 01:49:26 # Tor/I2P: tell monerod your onion address so it can be advertised on P2P network 01:49:28 #anonymous-inbound=PASTE_YOUR_I2P_HOSTNAME,127.0.0.1:18085,64 # I2P 01:49:30 #anonymous-inbound=PASTE_YOUR_ONION_HOSTNAME:18084,127.0.0.1:18084,64 # Tor 01:49:32 # Tor: be forgiving to connecting wallets 01:49:34 disable-rpc-ban=1 01:49:36 #end config 01:49:38 #enable service 01:49:40 systemctl daemon-reload 01:49:42 #selinux 01:49:44 ausearch -c '(monerod)' --raw | audit2allow -M my-monerod 01:49:48 semodule -X 300 -i my-monerod.pp 01:49:50 systemctl enable monerod 01:49:52 systemctl restart monerod 01:49:54 i'm surprised you haven't even gotten kicked yet 01:49:54 systemctl status monerod 01:49:56 tail -n100 /var/log/monero/monero.log 01:49:58 #open ports 01:50:00 18080/tcp 01:50:02 18089/tcp 01:50:04 # easy open ports function 01:50:06 for i in 18080 18089 01:50:08 do 01:50:10 firewall-cmd --permanent --add-port=${i}/tcp 01:50:12 done 01:50:14 #build xmrig 01:50:18 sudo dnf install -y git make cmake gcc gcc-c++ libstdc++-static libuv-static hwloc-devel openssl-devel 01:50:20 git clone https://github.com/xmrig/xmrig.git 01:50:22 #nano donate.h 01:50:24 nano src/donate.h 01:50:26 change the 1 to 0 01:50:28 cd 01:50:30 mkdir xmrig/build && cd xmrig/build 01:50:32 cmake .. 01:50:34 make -j$(nproc) 01:50:36 #build xmrig proxy 01:50:38 dnf install -y git make cmake gcc gcc-c++ libstdc++-static libuv-devel openssl-devel libuuid-devel 01:50:40 git clone https://github.com/xmrig/xmrig-proxy.git 01:50:42 mkdir xmrig-proxy/build 01:50:44 cd xmrig-proxy/build 01:50:48 cmake .. -DUUID_LIBRARY=uuid 01:50:50 make -j$(nproc) 01:50:52 #p2pool neeeds password quoted 01:50:54 p2pool --rpc-login 'igor:Weaponx93$$' --wallet 4AQRNe71kf15qZpKNWGCZh3ezv2dm8DX7P1M8AYNWKQoepTWwmaRYup1Xj5uptZoapMTwqGGJ6hLViCJPiL3AqVpMWyqGKV --rpc-port 18089 --data-dir /etc/p2pool 01:50:57 #build p2pool 01:50:59 sudo dnf install -y git @development-tools cmake libuv-devel zeromq-devel libsodium-devel openpgm-devel krb5-devel libcurl-devel libidn2-devel libnormaliz-devel 01:51:02 git clone --recursive https://github.com/SChernykh/p2pool 01:51:04 mkdir p2pool/build && cd p2pool/build 01:51:06 cmake .. 01:51:08 make 01:51:10 # will have to impliment all the configs and systemd files 01:51:12 # once node is synced backup to other computer 01:51:14 you literaly leaked your rpc login and public wallet address 01:51:14 scp -r @: 01:51:18 idk i copied this 01:51:19 haven't you copied ENOUGH 01:51:20 fedora server 01:51:22 hostname commadore64 lol 01:51:24 so no dell 01:51:28 i guess ai understands i need help configuring this 01:51:30 got the node day and a 3/4 day 01:51:32 nope steal it 01:51:35 reset it 01:52:17 that config looks clean 01:52:31 nice try though 01:52:50 lol oh shit oh no 01:54:58 well changed the user password 01:55:10 but the wallet dont matter 01:55:50 2025-01-29 01:55:30.342 I Monero 'Fluorine Fermi' (v0.18.3.4-release) 01:55:50 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 01:56:29 anywho have a good night Cindy :P 01:57:53 LMAO 02:00:04 Input too large, please use www.zerobin.net 05:55:47 hey all, 05:56:39 I find cake wallet bit bloated and also hate their approach to support all currencies despite their scaminess, 05:56:57 do we have feature-rich (monero-wise) app on Android? 05:57:02 PC I have feather and all good 05:57:07 monerujo isn't enough? 05:57:23 that's the only one that i've used on android but it works 05:57:28 do they support polyseed? last time they didnt 05:57:32 works great if you have a hardware wallet 05:58:08 I see not much point of having hardware wallet tbh 05:58:24 if monerojuo supports polyseed will try again 06:03:43 is there a reason why they not supporting polyseed? 06:03:48 maybe devtime? 10:06:15 viscous24 J0J0XMR has a PR adding polyseed to monerujo. their team are just not active 10:09:08 funded by a bounty @ https://bounties.monero.social/posts/116/2-200m-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 10:21:19 hi 10:29:33 <3​21bob321:monero.social> Why are they so slow 10:29:46 <3​21bob321:monero.social> Debian updates more 10:31:50 r/rareinsults 10:33:11 can someone tell me what does monero-cpp mean when it says "m_w2->multisig()" in some of its code 10:33:15 GCC doesn't know either 10:33:36 i can't find that function anywhere 10:46:41 Cindy, ripgrep is your best friend 10:46:55 that's what I've done since 1987 10:47:14 abandon LSP navigation. Embrace substring searching 10:47:27 i've tried grep 10:47:49 multisig is not a function whatsoever in monero-cpp's code 10:47:56 and monero's wallet2 and wallet header files 10:48:34 💀 10:49:48 lemme check some more 11:30:30 i just realized where the multsig function exists 11:31:08 monero-project/monero: src/wallet/api/wallet2_api.h 11:31:13 and monero-cpp doesn't include this file 11:32:03 well, #include 11:34:15 (also seems to be a seperate struct?) 11:35:09 shit, i need help 14:45:18 aremor which pr discussion were you referring to 15:07:50 https://old.reddit.com/r/Monero/comments/1icon4z/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? 15:16:31 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. 15:17:28 The standard Monero wallet code has some protections against malicious nodes giving an incorrect output distribution. AFAIK, the countermeasures have not been evaluated comprehensively. 15:18:26 Running a node on android is fine, just not on your daily driver 15:19:30 Reason: battery, bandwidth, inconsistent connectivity. 15:19:30 Run on a secondary device = profit 15:20:03 My android node ran for > 2 years straight. Recently had to shut it doen because it ran out of storage 15:20:37 (ran out because it has other stuff on it, and only 128gb total) 15:20:49 Then wallet2 can check the elements after N aren't too crazy. 15:33:39 Couldn't I create transactions though and then feed you my decoys, strategically trying to evade the counter measures in the wallet's check? 15:33:43 sorry for being stupid here, i realized i had monero set to the HEAD commit instead of the release-v0.18 tag 15:36:03 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. 15:36:40 However, it might be enough for the attacker, since they won't need to add the tx to the chain. 15:37:14 The wallet includes the output it wants to spend among the data it asks for. 15:38:03 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. 15:38:25 So the node has to alter only some of the data, and hope it doesn't alter the real one. 15:38:50 I guess if such a trigger happens, the wallet ought to remember never to use that node again... 15:39:10 There is no long lived dynamic ban system atm. 15:40:07 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. 15:40:11 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. 15:40:21 Off the top of my head so I might be off. 15:42:31 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 15:44:52 Have you seen the "Breaking Monero" episode on remote nodes? 15:45:17 It's old and may be out of date, but it's worth a look 15:46:40 I have watched some of it, but it is long and yes I saw it was 6years old so was worried about outdated information 15:47:53 A convo with tobtob (sp?) about some PRs getting reviewed. 15:48:16 was in -dev 15:49:28 There are a few diff discussions tho. Merge criteria and dormant pr's and issues, for example 15:55:50 @m​oneromooo i appreciate your commentary as well and did in fact read it 18:02:48 does proxy config setting on the node mean that the chain will be downloaded over the proxy? tor or i2p or whatever? 18:23:05 `--proxy` ? 18:23:22 I2p = no. Tor = yes, exit nodes only 18:23:55 It just sends outgoing connections over the socks proxy. Blocks incoming connections, since you cant have inc over tor 18:24:30 We dont do blockchain sync over onion/i2p at all 19:03:25 ty 19:19:07 Hello frens, does anyone happen to know the pruned and/or full blockchain sizes for stagenet and/or testnet? 19:23:36 I'm not sure if this is available somewhere, I only found https://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. 19:46:12 full - stagenet: 14 GB, testnet: 7.7 GB 19:55:50 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) 19:57:51 meson seems to do this a lot better, considering its cmake subproject interpreter exposes all targets regardless of them being exported or not 19:59:36 exposes all targets to the top-level project's build file*