00:12:30 How’s the research on anonymous account based cryptocurrencies looking as of today? 00:35:37 haven't heard of any so far 00:35:49 might be incompatible 00:37:38 Dero 00:37:41 Super anon 00:41:11 oh you're right 00:53:13 <321bob321:monero.social> still cant get over that name "dero" 01:03:51 i like it 01:15:49 <321bob321:monero.social> Are you one ? 01:20:06 Have they upgraded XMR yet? 01:20:42 With new addresses 01:20:53 I’m a normie 01:29:58 No 01:36:08 If I run monerod with tx-proxy intentionally set to an address that won’t work (ie a random localhost port), will that prevent it from broadcasting transactions? 01:36:51 I would think that it would, right? Otherwise if the tx-proxy is misconfigured or offline, then transactions would be broadcast directly…. 01:46:12 ? 01:47:20 Tx proxy takes --tx-proxy={network},{proxyhost:port}[,noise][,peercount] 01:47:48 So --tx-proxy=tor,127.0.0.1:9050 01:48:40 If the proxy is wrong, then it wont have peers 01:49:13 As in it shouldn’t be able to sync? Or just make transactions? 01:50:54 Sync will be fine 01:51:13 But it wont broadcast tx that were sent to your rpc port 01:51:52 It will throw errors like "unable to broadcast transactions. No available connections" 01:56:33 Is there any way to see if the tx-proxy is working correctly? 01:56:59 (Other than just sending a test transaction) 02:00:34 sync_info 02:01:06 You can only have onion peers if the proxy is working 02:02:49 Ah ok 02:04:37 I’m gonna try and see if I can get it to fail with an incorrect tx-proxy one more time; the past two times I tried it in the last hour just ended up going through without a hitch 02:12:57 Incorrect tx proxy such as? 02:14:43 not really possible 02:15:12 In my case I used tx-proxy i2p,127.0.0.1:8060 which normally is what I use for i2pd….but I killed i2pd and made sure it wasn’t running 02:15:14 It connect to onion/i2p nodes over the specified proxy 02:15:44 So unless something else happened to show up on that port and also happen to perfectly route I2P packets (in record time might I add)… 02:16:00 if the proxy wasnt working, then it cant connect to i2p nodes 02:16:02 Also print_cn showed no non clearnet connections 02:16:34 If there are no i2p nodes in the connections list, then the tx will sit in your local txpool and never be broadcasted 02:16:44 Hmm 02:17:25 s/Never/reattempt over and over but never succeed 02:19:37 check sync_info instead of print_cn 02:19:55 Of the tx was confirmed, then you had i2p peers 02:20:30 .. or you mined it yourself 🙃 02:21:45 Hadn’t considered the mined it myself possibility lol (though I don’t think it’s likely) 02:22:22 I’m going to try to replicate it again in a more sterile environment and see if the holidays are just making me crazy 02:24:21 Definitely crazy 02:24:56 Dont need a sterile env 02:25:32 Hi 02:25:45 Doyou have i2p peers? 02:25:46 No: tx wont be relayed 02:25:48 yes: tx will be relayed 02:28:40 Its not technically possible to have i2p peers or to relay a tx to i2p, if i2p is not running 02:57:00 I’m currently waiting on it to see what happens; it’s acting weird 02:57:02 There’s a significant disconnect between how it is shown on monerod and on the wallets. From the perspective of the wallets, nothing is wrong; not even an error is shown 02:57:41 To add even more confusion, this go around I was able to catch the monerod warning about there being no I2P connections—that warning didn’t happen the last two times 03:00:28 Correct 03:00:41 There is nothing wrong from the perspective of the wallet 03:00:46 I have made a programming language that compiles to C++ for bounties so I don't have to learn C++ 03:01:29 Have you actually gotten away with that? That sounds…more difficult than actually biting the bullet and learning c++ 03:01:44 That’s like something I would pull to get out of learning Python 03:01:50 There is no rpc response to tell wallets (especially restricted rpc) whether the node is running a tx-proxy 03:02:10 Ok, that makes sense I guess 03:02:25 Yes, I made the language, Still has to be "finished", I am still reading docs 03:02:31 But I have did it 03:02:48 Lol 03:03:03 https://matrix.monero.social/_matrix/media/v1/download/matrix.org/bpbOPYEgywNKsHXFUQxJuDov 03:03:13 Wrong screenshot 03:03:36 https://matrix.monero.social/_matrix/media/v1/download/matrix.org/RUWTpDfiZOPMAQLJXceCGdEM 03:03:47 Nice 03:03:54 ```asm 03:03:56 BITS 64 03:03:58 segment .text 03:04:00 dump: 03:04:02 mov r9, -3689348814741910323 03:04:04 sub rsp, 40 03:04:06 mov BYTE [rsp+31], 10 03:04:08 lea rcx, [rsp+30] 03:04:10 .L2: 03:04:12 mov rax, rdi 03:04:14 lea r8, [rsp+32] 03:04:26 I doubt the output would be human-friendly enough to just submit as is, though it can probably give enough boilerplate to fill in the blanks 03:04:56 Worse case senero I could just decompile the binary 03:05:19 into C++ 03:05:48 I don’t think anyone would want to review that, much less pay for the privilege of reviewing it lol 03:06:08 In my point as long as it works, Idk for everyone else 03:06:21 In general it was a good project 03:06:50 Yeah it’s definitely a good project, especially to learn c++ at an intimate level 03:07:09 Right 03:07:20 Now I can technically say I know C++ 03:07:36 And I know fully know assembly 03:08:08 https://matrix.monero.social/_matrix/media/v1/download/matrix.org/SxPNVFVaPbyItPJsubXSDvHb 03:08:28 https://matrix.monero.social/_matrix/media/v1/download/matrix.org/tViZhYRHuRBUqphFQLXyQYHd 03:08:49 https://matrix.monero.social/_matrix/media/v1/download/matrix.org/RpxsuhrtiRpDiZLLqyLlgpEB 03:09:12 https://matrix.monero.social/_matrix/media/v1/download/matrix.org/ojcJWKSzbkYpAgkDlIrVTdYG 03:13:59 https://github.com/end2endzone/bin2cpp 03:16:43 <123bob123:matrix.org> Paste code in a pastebin, rip nioc 03:29:06 +1 loeasy6 please dont paste like that again 03:29:17 Sorry 03:29:20 Well….the transaction went through. I’m not sure what to think now. 03:30:32 If the tx confirmed then it was sent over the specified proxy to an i2p node .... 03:30:38 sync_info 03:30:45 Do you have i2p peers? 03:31:12 That’s the funniest part of all: I don’t think there are any I2P peers *period* on stagenet currently 03:31:34 So the transaction got sent somehow through clearnet 03:31:36 sync_info 03:31:52 ^^^ 03:31:55 Are you asking me to send the output of sync_info? 03:32:39 I can do that if necessary 03:33:50 I'm asking you to check it for i2p/onion peers 03:34:02 I already did; none 03:35:12 And the tx was confirmed + youre not mining? 03:35:21 Correct 03:36:14 And your node is printing "unable to broadcast transactios. No available connections"? 03:36:26 And as a final sanity check I looked up the transaction hash on an external blockchain explorer and it showed up as good 03:37:25 It sent a single warning like that after submitting it yeah 03:37:48 It should be printing the warning every few mins 03:37:57 Hmm 03:38:35 Let me turn up my log level and see if I can find something else 03:39:26 You also have no onion peers, right? 03:39:32 Correct 03:39:39 Only clearnet 03:44:06 the only thing i can think is that you didnt pass tx-proxy to the node at startup 03:44:51 I can try to reproduce, but in my experience the tx will stay stuck on the local daemon until connections are established 03:48:01 I’m going to list the options out exactly as I had them so you can test it (or more likely, point at one of them and say “ah so that’s what’s happening”): monerod —stagenet —enable-dns-blocklist —out-peers 16 —no-igd —bootstrap-daemon-address auto —no-sync —check-updates disabled —max-concurrency 8 —tx-proxy i2p,127.0.0.1:8060 03:48:57 (In case you are wondering as to why some of these are here, I was originally testing adding the tx-proxy to the end of the settings used by the simple mode in monero-wallet-gui) 03:52:36 --bootstrap-daemon-address is probably overriding tx-proxy 03:53:11 Hmm 03:53:14 --no-sync means that your node isnt going to be the one relaying tx 03:53:37 And that would be the reason why 03:53:57 Yeah I just wasn’t thinking straight lol 03:53:59 --no-sync puts your daemon in a "not synced" status, snd bootstrap proxies your rpc to another node 03:54:37 So when your wallet syncs, its asking your node to relay to<>from another node 03:55:32 Yeah that’s right 03:55:35 Hmm 03:56:03 Well ig it’s back to the drawing board (though not as far back as the last 4 times lol) 04:01:52 if your node was reporting as synced, it _should_ stop using bootstrap. 04:01:54 --no-sync is an ugly hack to enable "simple mode", which is essentially a random node proxy w/o running a real node locally 04:01:56 I think the problem is bootstrap overriding tx-proxy. Maybe that can be changed so that it still uses tx-proxy even if bootstrap is enabled and active for wallet sync 04:03:55 Also makes me wonder if --proxy is enabled for bootstrap, or if bootstrap was just completely overlooke for --proxy and --tx-proxy edge cases 04:04:17 (making bootstrap a "leak") 05:22:18 My guess is that it was overlooked or assumed to not be an issue 13:11:46 https://github.com/arcanyx-org/nixium?tab=readme-ov-file#monero-node 13:11:48 Why is this returning: 13:11:50 Jan 01 12:22:32 mracek monerod[3579345]: 2025-01-01 12:22:32.108 W Unable to send transaction(s), no available connections 13:11:52 Jan 01 12:29:17 mracek monerod[3579345]: 2025-01-01 12:29:17.493 W Unable to send transaction(s) to tor - no suitable outbound connections at height 3315728 13:13:14 Using tx-proxy? 13:14:54 huh? 13:15:03 sounds like your tor daemon is down or falling to connect to onions 13:15:19 https://github.com/Arcanyx-org/NiXium/blob/central/src/nixos/machines/mracek/services/monero.nix#L40 13:15:20 ^ tx-proxy line 13:15:27 tor is up i am connecting to the server over it 13:17:14 `./monerod sync_info` 13:17:48 Also, why are you hardcoding this?? ` "anonymous-inbound=yobndiqy7b5umy434mhvj2u7zttr2ro2nshybrmu3c354qqykqtc7pid.onion:18083,${config.services.monero.rpc.address}:18083,64" # Advertise the onion service for an inbound requests` 13:17:56 [root@mracek:/var/lib/tor/onion/monero-p2p]# /nix/store/kx0vkg86azrbvs6rnk34akf5bvkjc7sx-monero-cli-0.18.3.4/bin/monerod sync_info 13:17:58 2025-01-01 13:17:46.116 I Monero 'Fluorine Fermi' (v0.18.3.4-unknown) 13:18:00 Error: Unsuccessful -- json_rpc_request: 13:21:15 ikr 13:21:48 shouldn't i be hardcoding this? 13:22:03 Oh 13:22:28 (cuz it was pain in the ass to anonymize over infra as code and people here told me it's fine since it's what the node uses to communicate with others) 13:22:44 `monerod --rpc-login username:pass sync_info` 13:23:49 [root@mracek:/var/lib/tor/onion/monero-p2p]# /nix/store/kx0vkg86azrbvs6rnk34akf5bvkjc7sx-monero-cli-0.18.3.4/bin/monerod --rpc-login "Monerochan:iL0VEMoNeRoChan<3" sync_inf 13:23:50 o 13:23:52 2025-01-01 13:23:40.656 I Monero 'Fluorine Fermi' (v0.18.3.4-unknown) 13:23:54 Error: Unsuccessful -- json_rpc_request: 13:24:06 If that onion is on your host and youre the only one using this code, sure 13:24:30 `monerod --rpc-login username:pass --log-level 1 sync_info` 13:25:02 it's public note that's not advertising as public node 13:25:32 and the onion is on the host 13:25:55 [root@mracek:/var/lib/tor/onion/monero-p2p]# /nix/store/kx0vkg86azrbvs6rnk34akf5bvkjc7sx-monero-cli-0.18.3.4/bin/monerod --rpc-login "Monerochan:iL0VEMoNeRoChan<3" --log-level 1 sync_info 13:25:56 2025-01-01 13:25:45.508 I Monero 'Fluorine Fermi' (v0.18.3.4-unknown) 13:25:58 2025-01-01 13:25:45.583 I Generating SSL certificate 13:26:00 2025-01-01 13:25:48.402 W SSL peer has not been verified 13:26:02 2025-01-01 13:25:48.402 W SSL peer has not been verified 13:26:04 2025-01-01 13:25:48.496 E RPC call of "sync_info" returned error: -32601, message: Method not found 13:26:06 Error: Unsuccessful -- json_rpc_request: 13:30:51 `monerod status`? 13:31:30 `cuprated status` ? 13:31:36 025-01-01 13:31:19.327 W SSL peer has not been verified 13:31:36 2025-01-01 13:31:19.420 I Failed to invoke http request to /mining_status, wrong response code: 404 13:31:38 Error: Problem fetching info-- rpc_request: 13:31:40 Height: 3315753/3315753 (100.0%) on mainnet, mining info unavailable, net hash 3.49 GH/s, v16, 0(out)+0(in) connections 13:31:45 `cuprated status` ? (this is a joke) 13:32:07 it's tor-only node that's not allowed to contact clearweb btw 13:36:04 this worked without issues up until 4 days ago btw 13:41:19 What's cuprated 13:41:22 <321bob321:monero.social> Soon™️ 13:41:50 https://github.com/Cuprate/cuprate oooo 13:42:00 <321bob321:monero.social> Rust version 13:42:17 <321bob321:monero.social> Version with crabs 13:42:34 rust all the things 13:47:53 Well wut did u change 4.1 days ago? 13:48:12 0 out, 0 in connections 13:48:20 literally nothing the whole system is bit by bit the same 13:48:43 (checked) 13:49:19 huh 13:49:40 3315761 is the current block height 13:49:45 <321bob321:monero.social> Ctrl alt defeat 13:49:55 Youre 8 blocks behind 13:50:03 oh it works now wtf 13:50:39 _Shane restarted tor_ 13:51:04 i restarted it like 6 times in the last 7 hours 13:51:24 also no i restarted monero, tor has uptime of 19 days rn 13:51:26 Mebbe isp doesnt like tor 13:52:07