Yes, I'm back. The revert thingy did the trick. Let's se how it runs :)

2022-05-20 02:17:50.521 I Monero 'Oxygen Orion' (v0.17.0.0-ccfd75de0)

2022-05-20 02:17:50.521 I Initializing cryptonote protocol...

2022-05-20 02:17:50.521 I Cryptonote protocol initialized OK

2022-05-20 02:17:50.522 I Initializing core...

2022-05-20 02:17:50.522 I Loading blockchain from folder /var/lib/monero/data/testnet/testnet/lmdb ...

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

2022-05-20 02:17:54.956 I Popping blocks... 1984049

2022-05-20 02:18:10.688 I Popping blocks... 1983949

You are now synchronized with the network.

LFG

Who's the other guy on testnet? I have 1 (one) outgoing, and that's it.

That would be me :D

xmrchain is on testnet as well

I'm up to 1 in / 1 out :)

Hey y'all I opened a PR here: monero-project/monero #8344

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?

It can be done already by putting it in a config file fwiw.

(AFAIK, I never used one)

Any update on seraphis ?

ilgatu: hey

moneroextremist[: Tell me, pal

you have an update on seraphis for me ? ilgatu

It depends, moneroextremist[

what do you have

give me everything u got ilgatu

Ok, give me ur address

moneroextremist[:

im talking about info about seraphis not money ilgatu

:V

Sorry, that's confidential.

NDA til 2025

ilgatu: but seraphis planned for 2023 not 2025

moneroextremist[: Just in a year, damn, time flies

./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

hello, I started a wallet rpc with the above command

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'`

It returns: `curl: (7) Failed to connect to localhost port 18082: Connection refused`

Did you check whether monero-wallet-rpc is listening ?

(eg, netstat)

How do you check with netstat?

netsat -a | grep 18082

it doesn't return anything

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.

`./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`

Is this command wrong?

Possibly the wallet filename.

It also starts listening after it's finished syncing from the daemon.

IIRC it prints JOINING all threads once it's listening.

Though that might be at level 2, not sure...

I assume you made no changes to the code that could be related ?

`./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`

This is the original code

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) ?

If not, the wallet is probably timing out waiting for it and hasn't started listening yet.

If I understand it correctly, I connect to a remote daemon right?

`node.monero.net:18081`

Must the wallet sync to the latest height?

and then start listening?

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.

Well, the wallet is constantly syncing, how does it determine which is the latest height?

Syncing is the process which gets the wallet the latest height as a byproduct.

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...

AFAIK it syncs first. Always was that way. I remember complaints about it, so maybe someone did something about it.

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.

Yes. You are right. Thank you.

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`?

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

Unless special case, 16 outs max. Enforced by consensus.

moneromooo: wasn't aware about that. Thanks.

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.

<rbrunner> "Testnet could really use a few..." <- I have two nodes up, node.sethforprivacy.com and node2.sethforprivacy.com

Feel free to add as peers manually if necessary

sethforprivacy in apps in ~/nodes on  master [!?] took 7s ❯ docker exec -ti monerod-testnet monerod --testnet status

2022-05-20 15:06:45.650 I Monero 'Oxygen Orion' (v0.17.0.0-8349cfe4a)

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

* ```... (full message at libera.ems.host/_matrix/media/r0/do…706107c6cb0c73680138497128b382048c8)

Is that height correct still? Seem like they're on v16 properly.

I also have 1k tXMR if anyone needs some for testing 😛

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 :)

I have 11 peers now after running for 1.5 hours, a bit better.

Anyone can easily run on testnet using my v0.18.0.0 Docker image: paste.sethforprivacy.com/?6691e864c…3uMy1XQT21Jq1js7BEk3hi5W8aGxhechKMp

(Ignore the UFW stuff if on another OS/can do firewall rules yourself/etc)

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.

Pushing a new image as there were some new commits since I initially pushed

Pushed, latest available under the same tag

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

monerod-testnet

* 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

monerod-testnet`

* 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 monerod-testnet`

* 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 monerod-testnet`

s/6691e864c7a162c0/01e229010d9ec798/, s/Djr1CPu2m3uMy1XQT21Jq1js7BEk3hi5W8aGxhechKMp/GdHh6a7JcnqYsPNz8pUyxFgY5F3mzZq2ZbTK2f9sYdmN/

how else can we break this thing

Asked for more testers on Twitter, will do the same on Reddit shortly: twitter.com/sethforprivacy/status/1527676723948552197

There was this about 3 days ago: old.reddit.com/r/Monero/comments/uq…e_upcoming_major_monero_release_for

However, your docker image should lower the barrier considerably

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.

But hopefully the Docker config will bring in more nodes at the very least.

Tested a forked-off node and it popped blocks/synced perfectly

Kicking off a bunch of Linode testnet nodes using ref credits as well 🙂

linode will steal all your testnet coins

rbrunner You can add 47.218.218.3 as well

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

Are you running the latest master?

There are lots of nodes still on the old chain, but very few that properly updated/forked

You should be on height 1985369/1985369

Oh shoot, I thought I was...

Haha too many different versions of monerod on my path lol

heh

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

"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.

Seth For Privacy You're my only outgoing connection right now <3

rbrunner 14s a crowd

I've got 3out/6in 😛

If someone had a list, big enough of proved transactions, he could see what input are decoys, right?

How big should that list be?

* If someone had a list, big enough of proved transactions, he could see what input are decoys, right? This could break Ring Signatures

How big should that list be?

* If someone had a list, big enough of proved transactions, he could see what input are decoys, right? This could break Ring Signatures

how big that list must be?

> <@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

> how big that list must be?

You would need to flood the network in order to know enough transactions

An attack like this was already attempted in the past if I am correct

There are some pools that publish the transaction viewkey, they make a lot of payments to miners. Is that dangerous?

But the attacker gave up because you need to send an impressive number of transactions to break Ring Signatures

mrr|LibertyPool[: A lot of payments? No, I don't think so

mr.r | Liberty Pool: This is an interesting conversation, but it belongs in #monero-research-lounge:monero.social , not -dev

Monero has (let me check) transactions every day

Miners reward won't make too much difference

s/(let/over/, s/me/20/, s/check)/000/

That kind of attack could've been feasible with smaller ring sizes such as 5

syncing the testnet chain. dumb question / sanity check: `monerod --version` is outputting "Monero 'Oxygen Orion' (v0.17.0.0-6e60919e6)" -- is this legit?

MikeyG: Tags are set on the release branch, so that's normal as far as I know