00:00:40 <vtnerd__> its leaking to other zmq clients that this particular node is the origin (or at the very least a manual re-broadcast)
00:01:04 <vtnerd__> might as well just publish during the "stem" phase anyway then
00:01:36 <vtnerd__> ugh, I'll just comment in PR. this behavior was as-designed by me, but I see why people don't like it
00:05:29 <vtnerd__> ah nevemrind, read the PR wrong, yeah this is an annoying bug I'll definitely have to review this pr
01:56:10 <JakeHawkinse[m]> selsta: selsta https://github.com/monero-project/monero/issues/8440
01:56:19 <JakeHawkinse[m]> urgent pls！！！
01:58:23 <ofrnxmr[m]> Did you send those funds to yourself?
01:58:34 <JakeHawkinse[m]> no
01:59:41 <ofrnxmr[m]> So you dont own the recipient wallet, correct? (Cant troubleshoot on the receiving end?)
01:59:41 <ofrnxmr[m]> What node did you send it from?
01:59:42 <JakeHawkinse[m]> I jsut wana to recharge to binance
01:59:57 <ofrnxmr[m]> You sent to Binance from where? 
02:00:20 <JakeHawkinse[m]> xmrwallet.com
02:00:29 <plowsof> you transferred funds from a third party to another third party , one of which is linked to phishing / scams (xmrwallet)
02:00:44 <ofrnxmr[m]> I was about to say, xmrwallet.com isnt that a scam?
02:01:15 <JakeHawkinse[m]> xrmwallet.com isn't a scam one
02:02:56 <ofrnxmr[m]> https://www.reddit.com/r/Monero/comments/jh15e3/psa_xmrwalletcom_is_a_scam_who_steals_your_funds/
02:04:33 <JakeHawkinse[m]>  I had read this article. But my situation is different with it
02:04:42 <ofrnxmr[m]> Piece of advice.
02:04:42 <ofrnxmr[m]> Running a node and using a full wallet isnt hard
02:04:42 <ofrnxmr[m]> Sorry to say, but sounds like you got scammed 
02:04:55 * JakeHawkinse[m] uploaded an image: (64KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.org/FRkygDqGOTyZKQBgrHvKHAyY/image.png >
02:06:58 <ofrnxmr[m]> .. next time dont use some scammy web wallet. .
02:08:57 <ofrnxmr[m]> You say you tried other nodes
02:08:57 <ofrnxmr[m]> Did you try to restore your seed into a non-scam wallet ? (Monero gui, feather wallet, Cake wallet, monerujo)
02:10:12 <ofrnxmr[m]> Also, you had a different txid before you edit your issue.
02:10:12 <ofrnxmr[m]> Where is the original one from? 
02:10:43 <JakeHawkinse[m]> I had a another successful trx. The state  "output match" is true
02:10:47 * JakeHawkinse[m] uploaded an image: (92KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.org/WYquriMukkRHxcSrDvgMyalh/4.PNG >
02:11:42 <ofrnxmr[m]> Id stop using that wallet 🥲
04:42:13 <selsta> vtnerd__: this one would be kinda important https://github.com/monero-project/monero/pull/8379
04:42:25 <selsta> at least i don't know who else should review this
12:36:43 <sethforprivacy> I've updated the checklist up to the extent of my knowledge of our readiness: https://github.com/monero-project/meta/issues/690
12:37:08 <sethforprivacy> Thanks for the immense amount of work that has gone into this, everyone! Almost there 🙂 If anyone knows of something on the list being completed that I'm not aware of, please ping me or leave a comment on that issue.
12:42:24 <WillMorrison[m]> Are there docs for the zeromq server?
12:43:19 <sech1> https://github.com/monero-project/monero/blob/master/docs/ZMQ.md
12:48:35 <sethforprivacy> One quick question, seems like release naming changed quite a bite -- I assume `monero-arm-linux-android-*` is the new version of `monero-linux-armv8-*`?
12:49:16 <sech1> no, it's 32-bit arm
12:49:19 <selsta> we rename them before uploading to the website
12:49:31 <selsta> https://gui.xmr.pm/files/cli/v0.18.0.0/
12:49:43 <sethforprivacy> ahh
12:49:49 <sethforprivacy> Hadn't ever noticed that before. Thanks
13:00:28 <r4v3r23[m]> are these the binaries that are gonna be uploaded?
13:02:50 <sethforprivacy> Is the libunbound version min really `1.4.16`? All of my Ubuntu-based Docker builds are broken in v0.18.0.0 with libunbound errors:
13:02:50 <sethforprivacy> https://paste.sethforprivacy.com/?a79e4410854deb3f#47qEn6i8SMUv9JrjoSeM5afVa9NrXovxiGTCWjMvBytd
13:03:16 <sethforprivacy> Base image for these builds is Ubuntu 20.04, so libunbound-dev is `1.9.4`.
13:03:31 <selsta> show your dockerfile
13:04:04 <sech1> r4v3r23[m] yes, if no emergency fixes will be needed
13:05:08 <sethforprivacy> selsta: https://github.com/sethforprivacy/simple-monero-wallet-rpc-docker/blob/release-v0.18.0.0/Dockerfile
13:05:47 <sethforprivacy> My main image is Alpine-based and builds properly, but now need libunbound installed in the final image for the binary to run properly.
13:05:54 <sethforprivacy> I'm troubleshooting that separately.
13:08:31 <selsta> can you do make depends inside the dockerfile?
13:08:47 <selsta> otherwise you have to compile static unbound yourself, not from package manager, see https://github.com/monero-project/monero/issues/8439#issuecomment-1186548894
13:11:50 <sethforprivacy> I can test it, this image is somewhat out of date (it doesn't match all of the changes I've made for my monerod one yet)
13:12:28 <sethforprivacy> My Alpine build is working outside of needing the new lib, but will work on modernizing the broken one and just hotfix the Alpine one for now: https://github.com/sethforprivacy/simple-monerod-docker/blob/release-v0.18.0.0/Dockerfile
13:13:49 <sethforprivacy> Is `make depends` run as a prior command before the actual make command for building the binaries, or does it replace that?
13:14:08 <selsta> it replaces that
13:14:24 <selsta> make depends target=x86_64-linux-gnu
13:14:55 <sethforprivacy> Ah, yes, see the official Dockerfile does that
13:14:56 <sethforprivacy> I'll play around with it, thanks selsta!
13:36:36 <sethforprivacy> can I do `make depends` and keep building only the daemon with `-C build/release daemon`?
13:37:04 <r4v3r23[m]> how can i point the monero build to my local unbound?
13:39:21 <selsta> there is the `UNBOUND_ROOT` env variable, and you can set cmake `-D UNBOUND_INCLUDE_DIR=` and `-D UNBOUND_LIBRARIES=`
13:40:15 <sethforprivacy> selsta: Is this for *not* using `make depends`?
13:40:27 <sethforprivacy> And working around the libunbound issue?
13:40:37 <selsta> i was replying to r4v3r23[m]
13:40:54 <selsta> you can theoretically just build the daemon
13:41:01 <sethforprivacy> Oh, sorry, have them muted.
13:41:30 <sethforprivacy> `make depends` seems the more ideal solution overall anyways so I'm working on migrating to that for both my images.
13:41:31 <selsta> i don't see you just building the daemon in the dockerfile
13:41:34 <sethforprivacy> Will test and report back 🙂
13:42:00 <sethforprivacy> selsta: Not the one I linked before, this one I do though: https://github.com/sethforprivacy/simple-monerod-docker/blob/release-v0.18.0.0/Dockerfile#L111
13:43:07 <selsta> sethforprivacy: https://github.com/monero-project/monero/blob/master/Makefile#L50-L51
13:43:43 <selsta> copy these two steps in your dockerfile and then just build the daemon, should work similar to how you do it currently
13:44:23 <sethforprivacy> Ah, interesting, will try that out
13:44:38 <selsta> you have to replace target with x86_64-linux-gnu
13:44:53 <sethforprivacy> Yeah, I'm doing it dynamically as this is a multi-arch image
13:44:57 <sethforprivacy> Will set it via a var
13:45:13 <selsta> that's a problem then
13:46:02 <selsta> it's probably better for you to just compile unbound manually
13:46:07 <sethforprivacy> AFAICT it should work OK doing it like this:... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/5295d70d764c132ccb4f7942983892a1dd7beff8)
13:46:16 <sethforprivacy> Where MAKE_TARGET will replace target in the lines you linked
13:46:38 <sethforprivacy> selsta: Maybe 😕
13:46:46 <selsta> you have to test it out, i don't know if make depends works on arm
13:46:59 <sethforprivacy> Ahh
13:48:19 <sethforprivacy> This image works fine without building it at all, just requires bloating the final image with unbound-dev
13:48:48 <sethforprivacy> Probably not really worth the headache to figure out all of the compilation just to remove that at this point. Will focus on fixing the Ubuntu build alone then.
13:49:28 <r4v3r23[m]> <selsta> "there is the `UNBOUND_ROOT..." <- in `FindUnbound.cmake` yeah?
13:49:42 <r4v3r23[m]> unbound_root isnt working for me
13:52:10 <hyc> make depend assumes x86-64 build host, but will work for all the targets
13:55:19 <selsta> r4v3r23[m]: can you set the two cmake options?
14:28:08 <edisonamosyox[m]> hi selsta， the issue #8440 of github，how i can check the trx was successful or not？
14:28:10 <edisonamosyox[m]> https://github.com/monero-project/monero/issues/8440
14:30:59 <edisonamosyox[m]> I need be know which platform the problem happed，now I totoally confused
14:32:19 <selsta> what does it say in xmrwallet.com as receiver address?
14:35:29 <edisonamosyox[m]> selsta: communicated with customer service of xmrwallet.com，but no response
14:36:10 <selsta> but what does it say inside the wallet? there has to be a receiver?
14:36:37 <edisonamosyox[m]> I had test another trascation： i could use my own sender account and viewkey check the trx was successful，why？
14:44:40 <edisonamosyox[m]> selsta: to my knowledge, the characterstic of xmr is  each txid hide the address both of sender and receiver, right ?  I need the support from core team urgently!!!
15:14:30 <selsta> edisonamosyox[m]: from the outside yes but the wallet should still say the receiving address assuming it's the wallet you sent the transaction from and you didn't delete the wallet cache
15:14:58 <selsta> that's why I'm asking what does it say as receiver inside xmrwallet.com ?
16:41:05 <HungHaVan[m]> Hi everyone, can anyone help me how to use open_wallet and close_wallet method of wallet-rpc properly?
16:41:15 <HungHaVan[m]> thanks
16:49:47 <hyc> HungHaVan[m]: ask in #monero
16:50:47 <MexicanTakeout96> I found a bug in the monero-wallet-cli software, check_reserve_proof returns bad signture error when reserve proof signature has a message attached.
16:51:13 <MexicanTakeout96> This is on Monero 'Fluorine Fermi' (v0.18.0.0-b6a029f22)
16:55:52 <MexicanTakeout96> get_reserve_proof doesnt accept more than 1 word message. Weird
16:56:36 <MexicanTakeout96> I tried `get_reserve_proof 2 "this is a message"` and got a usage error
16:57:25 <selsta> could you open a github issue with description?
17:03:44 <MexicanTakeout96> I am making one rn
17:07:47 <selsta> MexicanTakeout96: did it work with v0.17?
17:21:52 <MexicanTakeout96> same error in v0.17.3.2-release :((
17:29:55 <alexey[m]1> Hi! I have a problem with the monero daemon, I am unable to synchronize the blockchain. Yesterday my server had a power outage, after that daemon crashes on start. I suspect that blockchain file got corrupted. Is there any way to fix? I have a limited internet plan, so I would like to avoid deleting it and... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/95654dfd5376657a96041e5445219e65de7ecdf9)
17:31:36 <selsta> ./monerod --db-salvage
17:31:44 <selsta> but most of the time it doesn't work, it only helps in some cases
17:39:13 <alexey[m]1> <selsta> "./monerod --db-salvage" <- No luck. I have no other option but to download the whole blockchain again?
17:43:00 <selsta> alexey[m]1: if you do --prune-blockchain --sync-pruned-blocks it will use less bandwidth
17:43:11 <selsta> but yes, assuming you don't have a backup
17:51:53 <jeffro256[m]> alexey if you expect more power outages in the future or other I/O interuptions, I recommend using db-sync-mode=safest
18:15:59 <hyc> it's just --db-sync-mode=safe
18:23:17 <MexicanTakeout96> selsta: any luck on my issue? :((
18:23:49 <selsta> I didn't look yet, I'm busy with release notes
18:24:16 <selsta> can you try the GUI?
18:24:34 <HungHaVan[m]> Can I have multiple users using their wallets to connect or use the same monero wallet rpc ?
18:24:59 <MexicanTakeout96> kk I will try with rpc server too
18:28:04 <MexicanTakeout96> hyc: I had to resync'd 3 times on my machine because of outages like alexey.
18:28:56 <MexicanTakeout96> db-sync-mode=safe is very slow, so I switched back to fast mode
18:29:19 <nikg83[m]> <hyc> "it's just --db-sync-mode=safe" <- I am using this, does this cause a lot more io then normal mode ?
18:29:55 <jeffro256[m]> > it's just --db-sync-mode=safe
18:29:55 <jeffro256[m]> yeah you're right. The modes are safe, fast, and fastest
18:31:19 <jeffro256[m]> > Can I have multiple users using their wallets to connect or use the same monero wallet rpc ?
18:31:19 <jeffro256[m]> Are you asking about multiple monero clients connect to one remote monero-wallet-rpc instance ?
18:32:54 <MexicanTakeout96> HungHaVan[m]: no, one wallet can only be opened one at a time for a single instance of wallet-rpc.
18:33:47 <alexey[m]1> Does "--db-sync-mode=safe" produce more writes to disk? I have a blockchain on SSD, iirc lots of small writes to flash memory can wear it down pretty fast.
18:38:31 <ofrnxmr[m]> alexey[m]1: Yes. Are you using windows?
18:38:37 <hyc> alexey[m]1: yes
18:39:20 <alexey[m]1> ofrnxmr[m]: Linux 5.15.0-33-generic
18:40:02 <ofrnxmr[m]> Was asking because, my understanding is that windows is more likely to corrupt the database 
18:45:43 <kico> sirs was trying to compile release-v0.18 and get this error ... libssl? https://pastebin.com/1ri0pqnh
18:46:35 <hyc> wow, pastebin has gone full invasive with ads and shit
18:46:45 <kico> F
18:47:03 <selsta> kico: you need newer openssl
18:47:09 <kico> aight
18:47:13 <kico> tks for confirming sir
18:47:57 <selsta> 1.1.1 or newer I think
18:48:14 <selsta> you will also need newer boost as a consequence
18:48:35 <kico> I see
18:48:43 <kico> thanks selsta :)
19:29:59 <vtnerd__> selsta: you asked me once and I began looking at it, but I had to go back and familiarize myself with some of that
19:30:07 <vtnerd__> will do it now because it looks high priority
19:36:59 <selsta> thanks, i just don't know who else is supposed to review this
20:17:23 <jeffro256[m]> > thanks, i just don't know who else is supposed to review this
20:17:23 <jeffro256[m]> which PR?
20:17:46 <selsta> 8379
21:28:47 <MexicanTakeout96> selsta: https://i.imgur.com/epIinY6.png
21:30:49 <MexicanTakeout96> check_reserve_proof requires the exact message to verify the proof. False advertising on this guide https://www.getmonero.org/resources/developer-guides/wallet-rpc.html#check_reserve_proof
21:37:53 <plowsof> MexicanTakeout96complain in #monero-site:monero.social or make a PR on github if you feel " Should be the same message used in get_reserve_proof" is false advertising.  
21:47:53 <MexicanTakeout96> plowsof: That part I understand completely. The part that is false is that message here is not (optional), also this string message acts more like a pass phrase when revealing the proof and not like "message" passed between parties.
21:48:43 <ofrnxmr[m]> "If a message was added to 'get_reserve_proof' (optional), this message is required when using 'check_reserve_proof'"
21:53:44 <MexicanTakeout96> That is completely different from "message - string; (Optional) Should be the same message used in get_reserve_proof."
22:09:31 <MexicanTakeout96> Sorry I misread your text. I think yours would work better replacing this ^ text