02:08:55 <TrasherDK> Yes, I'm back. The revert thingy did the trick. Let's se how it runs :)
02:18:48 <TrasherDK> 2022-05-20 02:17:50.521   I Monero 'Oxygen Orion' (v0.17.0.0-ccfd75de0)
02:18:48 <TrasherDK> 2022-05-20 02:17:50.521        I Initializing cryptonote protocol...
02:18:48 <TrasherDK> 2022-05-20 02:17:50.521        I Cryptonote protocol initialized OK
02:18:48 <TrasherDK> 2022-05-20 02:17:50.522        I Initializing core...
02:18:48 <TrasherDK> 2022-05-20 02:17:50.522        I Loading blockchain from folder /var/lib/monero/data/testnet/testnet/lmdb ...
02:18:50 <TrasherDK> 2022-05-20 02:17:54.956        I Current top block <6bbcca2a0c75a3ca3901c6bef81b14e45e95297667828ecba2970857e2935f49> at height 1984049 has version 14 which disagrees with the ideal version 16
02:18:53 <TrasherDK> 2022-05-20 02:17:54.956        I Popping blocks... 1984049
02:18:55 <TrasherDK> 2022-05-20 02:18:10.688        I Popping blocks... 1983949
02:30:11 <TrasherDK> You are now synchronized with the network.
02:34:10 <jeffro256[m]> LFG
03:12:37 <TrasherDK> Who's the other guy on testnet? I have 1 (one) outgoing, and that's it.
03:24:24 <HenryHollingwort> That would be me :D
03:31:18 <gingeropolous> xmrchain is on testnet as well
03:36:59 <TrasherDK> I'm up to 1 in / 1 out :)
04:03:41 <jeffro256[m]> Hey y'all I opened a PR here: https://github.com/monero-project/monero/pull/8344
04:05:58 <jeffro256[m]> I want your opinions on this: is having a file which contains the SSL fingerprint of your node and which is compatable with our SSL options (e.g. `--daemon-ssl-allowed-fingerprints`) a useful feature?
05:59:55 <moneromooo> It can be done already by putting it in a config file fwiw.
06:00:03 <moneromooo> (AFAIK, I never used one)
06:39:24 <moneroextremist[> Any update on seraphis ?
06:45:45 <moneroextremist[> ilgatu: hey
06:46:05 <ilgatu> moneroextremist[: Tell me, pal
06:46:18 <moneroextremist[> you have an update on seraphis for me ? ilgatu 
06:46:52 <ilgatu> It depends, moneroextremist[ 
06:48:48 <moneroextremist[> what do you have
06:48:56 <moneroextremist[> give me everything u got ilgatu 
06:53:32 <ilgatu> Ok, give me ur address
06:53:44 <ilgatu> moneroextremist[: 
06:55:30 <moneroextremist[> im talking about info about seraphis not money ilgatu 
06:55:42 <ilgatu> :V
06:55:59 <ilgatu> Sorry, that's confidential.
06:56:11 <ilgatu> NDA til 2025
07:00:58 <moneroextremist[> ilgatu: but seraphis planned for 2023 not 2025
07:13:32 <ilgatu> moneroextremist[: Just in a year, damn, time flies
09:46:19 <willshu[m]> ./monero-wallet-rpc --rpc-bind-port 18082 --disable-rpc-login --log-level 2 --wallet-file /Monero/wallets/iew-only --prompt-for-password  --daemon-address node.monero.net:18081 --trusted-daemon
09:46:30 <willshu[m]> hello, I started a wallet rpc with the above command
09:46:57 <willshu[m]> But when I tried to query information - `curl -X POST localhost:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"incoming_transfers","params":{"transfer_type":"all"}}' -H 'Content-Type: application/json'`
09:47:40 <willshu[m]> It returns: `curl: (7) Failed to connect to localhost port 18082: Connection refused`
09:49:04 <moneromooo> Did you check whether monero-wallet-rpc is listening ?
09:49:42 <moneromooo> (eg, netstat)
09:50:28 * willshu[m] uploaded an image: (397KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.org/LHxoDzCoUDSeuXTGNhZksXuc/middle_img_v2_c20dd8ad-7aa2-4fb2-9634-0bb22afa163h.png >
09:54:52 <willshu[m]> How do you check with netstat?
09:55:58 <moneromooo> netsat -a | grep 18082
09:56:41 <willshu[m]> it doesn't return anything
09:57:52 <willshu[m]> It's weird because: 1. I used to start the wallet rpc with this command and curl request doesn't have any problems. 2. The wallet seems to work fine, syncing blocks.
09:58:08 <willshu[m]> `./monero-wallet-rpc --rpc-bind-port 18082 --disable-rpc-login --log-level 2 --wallet-file /Monero/wallets/iew-only --prompt-for-password  --daemon-address node.monero.net:18081 --trusted-daemon`
09:58:16 <willshu[m]> Is this command wrong?
09:58:37 <moneromooo> Possibly the wallet filename.
09:58:56 <moneromooo> It also starts listening after it's finished syncing from the daemon.
09:59:09 <moneromooo> IIRC it prints JOINING all threads once it's listening.
09:59:23 <moneromooo> Though that might be at level 2, not sure...
09:59:40 <moneromooo> I assume you made no changes to the code that could be related ?
10:01:03 <willshu[m]> `./monero-wallet-rpc --rpc-bind-port 18082 --disable-rpc-login --log-level 2 --wallet-file /Monero/wallets/view-only/view-only --prompt-for-password  --daemon-address node.monero.net:18081 --trusted-daemon`
10:01:11 <willshu[m]> This is the original code
10:02:11 <moneromooo> Is your daemon responding (I'm assuming this is your daemon, since you use --trusted-daemon, which you clearly would not do if it weren't) ?
10:02:44 <moneromooo> If not, the wallet is probably timing out waiting for it and hasn't started listening yet.
10:02:47 <willshu[m]> If I understand it correctly, I connect to a remote daemon right?
10:03:00 <willshu[m]> `node.monero.net:18081`
10:04:28 <willshu[m]> Must the wallet sync to the latest height?
10:04:41 <willshu[m]> and then start listening?
10:05:17 <moneromooo> Yes, the wallet connects to that daemon. You may want to ask in #monero if you're just having connection issues and not seeing a bug.
10:06:03 <willshu[m]> Well, the wallet is constantly syncing, how does it determine which is the latest height?
10:07:24 <moneromooo> Syncing is the process which gets the wallet the latest height as a byproduct.
10:10:17 <willshu[m]> Did I remember it wrong? I remember it used to be: as long as I start the wallet rpc, I can curl balance, it's just not up to date...
10:11:24 <moneromooo> AFAIK it syncs first. Always was that way. I remember complaints about it, so maybe someone did something about it. 
10:13:08 <willshu[m]> moneromooo: ok then it must mistaken it with some other chains. Thanks. From the wallet terminal it is at height 2621980. I will wait until it hits 2627467.
10:21:19 <willshu[m]> Yes. You are right. Thank you.
10:26:31 <willshu[m]> BTW, the result of `get_transfer_by_txid` has `amount: String` and `amounts: String[]` even though the address is just a string? For my wallet all txs have `amounts` that have only 1 item. Under what circumstances will there be multiple items in `amounts`?
13:25:34 <mrr|LibertyPool[> Can someone confirm me that it's safe to send in one transaction different amounts to +50 different addresses? and make the view key of that transaction public
13:32:18 <moneromooo> Unless special case, 16 outs max. Enforced by consensus.
13:33:31 <mrr|LibertyPool[> moneromooo: wasn't aware about that. Thanks.
14:07:43 <rbrunner> Testnet could really use a few more people compiling master and joining the network again after the hardfork ... my daemons see only 4 or 5 peers.
15:05:54 <sethforprivacy> <rbrunner> "Testnet could really use a few..." <- I have two nodes up, node.sethforprivacy.com and node2.sethforprivacy.com
15:05:58 <sethforprivacy> Feel free to add as peers manually if necessary
15:06:58 <sethforprivacy> sethforprivacy in apps in ~/nodes on  master [!?] took 7s ❯ docker exec -ti monerod-testnet monerod --testnet status
15:06:58 <sethforprivacy> 2022-05-20 15:06:45.650	I Monero 'Oxygen Orion' (v0.17.0.0-8349cfe4a)
15:06:58 <sethforprivacy> Height: 1985346/1985346 (100.0%) on testnet, not mining, net hash 3.52 kH/s, v16, 2(out)+4(in) connections, uptime 3d 2h 23m 9s
15:07:27 <sethforprivacy>  * ```... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/9bf0a706107c6cb0c73680138497128b382048c8)
15:07:41 <sethforprivacy> Is that height correct still? Seem like they're on v16 properly.
15:09:57 <sethforprivacy> I also have 1k tXMR if anyone needs some for testing 😛
15:10:54 <rbrunner> Yup, have the same height. And one of my daemons already sees your 2 nodes. Maybe the two of us together are about 1/3 of all of testnet :)
15:11:31 <rbrunner> I have 11 peers now after running for 1.5 hours, a bit better.
15:13:58 <sethforprivacy> Anyone can easily run on testnet using my v0.18.0.0 Docker image: https://paste.sethforprivacy.com/?6691e864c7a162c0#Djr1CPu2m3uMy1XQT21Jq1js7BEk3hi5W8aGxhechKMp
15:14:12 <sethforprivacy> (Ignore the UFW stuff if on another OS/can do firewall rules yourself/etc)
15:14:18 <rbrunner> I was trying to come up with some free but fun "trophy" or "bounty" for anybody who can show that they re-join now, but wasn't successful.
15:17:50 <sethforprivacy> Pushing a new image as there were some new commits since I initially pushed
15:36:08 <sethforprivacy> Pushed, latest available under the same tag
15:36:44 <sethforprivacy> If you already have Docker installed it's as easy as `docker run -d --restart unless-stopped --name="monerod-testnet" -p 28080:28080 -p 28089:28089 -v bitmonero-testnet:/home/monero sethsimmons/simple-monerod:v0.18.0.0 --rpc-restricted-bind-ip=0.0.0.0 --rpc-restricted-bind-port=28089 --testnet --add-peer=node.sethforprivacy.com:28080 --add-peer=node2.sethforprivacy.com:28080` then just following logs with `docker logs --follow
15:36:44 <sethforprivacy> monerod-testnet
15:36:49 <sethforprivacy>  * If you already have Docker installed it's as easy as `docker run -d --restart unless-stopped --name="monerod-testnet" -p 28080:28080 -p 28089:28089 -v bitmonero-testnet:/home/monero sethsimmons/simple-monerod:v0.18.0.0 --rpc-restricted-bind-ip=0.0.0.0 --rpc-restricted-bind-port=28089 --testnet --add-peer=node.sethforprivacy.com:28080 --add-peer=node2.sethforprivacy.com:28080` then just following logs with \`docker logs --follow
15:36:49 <sethforprivacy> monerod-testnet`
15:37:09 <sethforprivacy>  * If you already have Docker installed it's as easy as:
15:37:09 <sethforprivacy>  `docker run -d --restart unless-stopped --name="monerod-testnet" -p 28080:28080 -p 28089:28089 -v bitmonero-testnet:/home/monero sethsimmons/simple-monerod:v0.18.0.0 --rpc-restricted-bind-ip=0.0.0.0 --rpc-restricted-bind-port=28089 --testnet --add-peer=node.sethforprivacy.com:28080 --add-peer=node2.sethforprivacy.com:28080` then just following logs with:
15:37:09 <sethforprivacy> `docker logs --follow monerod-testnet`
15:37:14 <sethforprivacy>  * If you already have Docker installed it's as easy as:
15:37:14 <sethforprivacy> `docker run -d --restart unless-stopped --name="monerod-testnet" -p 28080:28080 -p 28089:28089 -v bitmonero-testnet:/home/monero sethsimmons/simple-monerod:v0.18.0.0 --rpc-restricted-bind-ip=0.0.0.0 --rpc-restricted-bind-port=28089 --testnet --add-peer=node.sethforprivacy.com:28080 --add-peer=node2.sethforprivacy.com:28080`
15:37:14 <sethforprivacy> Then just following logs with:
15:37:14 <sethforprivacy> `docker logs --follow monerod-testnet`
15:37:50 <sethforprivacy> s/6691e864c7a162c0/01e229010d9ec798/, s/Djr1CPu2m3uMy1XQT21Jq1js7BEk3hi5W8aGxhechKMp/GdHh6a7JcnqYsPNz8pUyxFgY5F3mzZq2ZbTK2f9sYdmN/
15:43:18 <gingeropolous> how else can we break this thing
15:45:15 <sethforprivacy> Asked for more testers on Twitter, will do the same on Reddit shortly: https://twitter.com/sethforprivacy/status/1527676723948552197
15:47:08 <rbrunner> There was this about 3 days ago: https://old.reddit.com/r/Monero/comments/uqznue/help_test_the_upcoming_major_monero_release_for/
15:47:30 <sethforprivacy> https://www.reddit.com/r/Monero/comments/utzyyz/help_test_out_the_upcoming_monero_network_upgrade/
15:47:56 <rbrunner> However, your docker image should lower the barrier considerably
15:48:19 <sethforprivacy> rbrunner: Yeah, sadly very few people will take the time to compile from source for this -- which will at the very least limit our wallet testing considerably.
15:48:27 <sethforprivacy> But hopefully the Docker config will bring in more nodes at the very least.
15:51:53 <sethforprivacy> Tested a forked-off node and it popped blocks/synced perfectly
15:52:20 <sethforprivacy> https://paste.sethforprivacy.com/?dc536d78297dec98#E34rc2wu4BNfRV1Q6GyzSUHrFam99Tr9fZzmL1nmmbw1
15:55:32 <sethforprivacy> Kicking off a bunch of Linode testnet nodes using ref credits as well 🙂
15:59:04 <belak_> linode will steal all your testnet coins
16:11:18 <jeffro256[m]> rbrunner You can add 47.218.218.3 as well
16:12:40 <jeffro256[m]> I'll DM you my peer list. That's weird you only see like 6 because my node has connected to 30+ in the last 3 days 
16:12:55 <sethforprivacy> Are you running the latest master?
16:13:06 <sethforprivacy> There are lots of nodes still on the old chain, but very few that properly updated/forked
16:13:27 <sethforprivacy> You should be on height 1985369/1985369
16:14:54 <jeffro256[m]> Oh shoot, I thought I was...
16:15:12 <jeffro256[m]> Haha too many different versions of monerod on my path lol
16:15:57 <sethforprivacy> heh
16:31:33 <jeffro256[m]> Ah there we go. I might have actually been running a new enough commit but i didn't notice I didn't connnect to any new peers 
16:39:02 <rbrunner> "rbrunner You can add 47.218.218.3 as well" have that already as well :) I am now standing at 14, after 3 hours of uptime. Not as bad as I originally feared.
16:40:24 <jeffro256[m]> Seth For Privacy You're my only outgoing connection right now <3
16:40:57 <jeffro256[m]> rbrunner 14s a crowd 
16:43:06 <sethforprivacy> I've got 3out/6in 😛
20:27:00 <mrr|LibertyPool[> If someone had a list, big enough of proved transactions, he could see what input are decoys, right? 
20:27:00 <mrr|LibertyPool[> How big should that list be?
20:27:25 <mrr|LibertyPool[>  * If someone had a list, big enough of proved transactions, he could see what input are decoys, right? This could break Ring Signatures
20:27:25 <mrr|LibertyPool[> How big should that list be?
20:27:59 <mrr|LibertyPool[>  * If someone had a list, big enough of proved transactions, he could see what input are decoys, right? This could break Ring Signatures
20:27:59 <mrr|LibertyPool[> how big that list must be?
20:34:23 <xxfedexx[m]> > <@mrr:monero.social> If someone had a list, big enough of proved transactions, he could see what input are decoys, right? This could break Ring Signatures
20:34:23 <xxfedexx[m]> > how big that list must be?
20:34:23 <xxfedexx[m]> You would need to flood the network in order to know enough transactions
20:34:53 <xxfedexx[m]> An attack like this was already attempted in the past if I am correct
20:35:03 <mrr|LibertyPool[> There are some pools that publish the transaction viewkey, they make a lot of payments to miners. Is that dangerous? 
20:35:33 <xxfedexx[m]> But the attacker gave up because you need to send an impressive number of transactions to break Ring Signatures
20:35:49 <xxfedexx[m]> mrr|LibertyPool[: A lot of payments? No, I don't think so
20:35:57 <Rucknium[m]> mr.r | Liberty Pool: This is an interesting conversation, but it belongs in #monero-research-lounge:monero.social  , not -dev
20:36:04 <xxfedexx[m]> Monero has (let me check) transactions every day
20:36:14 <xxfedexx[m]> Miners reward won't make too much difference
20:37:00 <xxfedexx[m]> s/(let/over/, s/me/20/, s/check)/000/
20:40:50 <xxfedexx[m]> That kind of attack could've been feasible with smaller ring sizes such as 5
20:42:12 <MikeyG> syncing the testnet chain.  dumb question / sanity check: `monerod --version` is outputting "Monero 'Oxygen Orion' (v0.17.0.0-6e60919e6)" -- is this legit?
20:51:34 <dEBRUYNE> MikeyG: Tags are set on the release branch, so that's normal as far as I know