01:06:27 Got a new one: `2022-08-15 17:25:06.221 E wrong variant type: N10cryptonote12txout_to_keyE, expected txout_to_tagged_key in transaction id=` 01:06:47 you can ignore it, some node is sending you transaction without view tags 01:09:20 Custom node? Shouldn't they be on the other side of the fork? 01:09:47 Can have different reasons why this happens. 01:10:49 I'll ignore that one. Just haven't seen that one before. 01:12:15 I have seen it on almost all nodes since fork. 01:14:04 Yeah. You are probably watching the logs a lot closer than I do 🙂 01:14:43 it gets printed on log level 0 so it looks a bit scary 01:16:59 Traffic is still rather high still. `Sent 14951513330 bytes (13.92 GB) in 798151 packets in 2.8 days` 01:17:57 Nodes are way up on monero.fail ^.. weird 01:18:23 For months I was seeing 10-12k. At >16k eight now 01:19:15 (Perhaps why uploaded data is up) 02:27:03 hyc: sech1: https://github.com/monero-project/monero/issues/8504#issuecomment-1216071452 02:36:21 I thought we already said we're not supporting 10.12 02:38:20 but also, I thought we already tested on intel 10.12 too... 02:39:17 but that's self compiled, not the binary 02:41:56 ask him for the output of "ulimit -a| 02:42:05 "ulimit -a" 02:42:29 I'm getting the feeling this is a system environment issue and not a code issue 02:48:06 I just don't understand why it would work with v0.17 and fail with v0.18 when self compiled. 02:52:46 yeah, makes no sense 02:57:12 ulimit looks ok 03:06:04 if he builds ae8e98b681766f31d49ac562dd6974906156e07b 03:06:16 in external/randomx does randomx-test work in there? 03:08:54 I asked them to build master~20 which is before ae8e98b681766f31d49ac562dd6974906156e07b, same issue 03:10:02 ah. so it's not even a recent code change that's involved then 03:21:22 so maybe some feature that the 10.12 sdk enables is causing the problem? 03:23:38 I can ask them to compile with 10.11 sdk 03:23:51 or whatever we used previously 03:24:34 it was 10.11 11:17:31 "yes so it may be a legit..." <- Probably not related but, I'm getting:... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/41e9672f07d5c8d49f36275fd62fbacb9d91f3bc) 11:28:58 Looks like the compiler thinks `ndata' is `mn_data`, so likely false. 11:29:16 s/'/`/ 11:37:49 Looks like a case where malloc size if adjusted for whatever variable size data is written into the array. 1 is usually used for compatibility for compilres that balk on 0. 11:38:30 I do not see the alloc offhand to make sure this is the case, but it seems very likely. 13:23:54 Can anyone on here help me figure out why I can’t find my XMR coins that were sent to my external Monero wallet in an address that was generated by Monero? I’m a total novice at this so I’m sure I did something but I’ve been trying since yesterday to figure out and cant 13:26:13 Or does anyone know if Monero wallet has a customer support phone? 13:29:45 wrong channel, ask in #monero. As for "customer support", it depends on which wallet. Cake wallet probably has something. 13:31:54 I'm trying to build monero-project after updating MacOS to 12.0 and updating protobuf and unbound, but I'm getting these build errors. it appears the build is targetting a higher version than what's being linked to?... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/e463f916525890cea389007efda9a6546d62dbf0) 13:49:03 Vague guess from old memory: I would try setting in cmake: `set(CMAKE_OSX_DEPLOYMENT_TARGET 115)`. 13:51:46 And vary the version number in that to match the SDK that the linker finds. 14:55:51 Where is #monero to be found? I’m a novice 14:56:38 "Vague guess from old memory: I..." <- in monero-project? no luck 14:56:44 It might still be missing from the matrix bot. That'd explain all the non dev questons here... 14:57:26 So, if you can't ask there: make sure refresh-from-block-height is below the height your tx got mined. Then rescan the chain. 14:58:16 liliana914: #monero:monero.social 14:58:30 "wrong channel, ask in #monero..." <- Where do I find that channel? And it was an external Monero wallet I downloaded 14:59:15 Is is "freewallet" ? :) 14:59:29 no it’s Monero wallet 14:59:40 Doens't help. Thre are several monero wallets. 14:59:45 i guess it’s a free wallet you down load 14:59:55 how do I find out? 15:00:35 If it's "freewallet", it's a scam and you may never see your coins again. Monejuro, cake, feather are ok. monero-wallet-{cli,gui} are the most trustworthy (says me...). 15:00:53 it’s the cli wallet 15:01:05 or gui 15:01:20 yes! That’s what I have 15:02:12 Then check the refresh-from-block-height setting, set it low, even to 0. Rescan. 15:02:42 Anyone looked at the matrix bot ? IIRC it was buggy with monero at some point. 15:03:39 so, I transferred Monero from kraken to external wallet that is from Monero-wallet-gui 15:03:54 hiw to do that? 15:05:27 monero-wallet-gui > settings > info > Wallet restore height 15:07:22 It is at 0 now 15:07:44 good. it should re-sync 15:07:45 it appears monero-project wants to build with mac's 11.3 sdk, but external dependencies, libunbound and protobuf, are built using current 12.4 sdk 15:08:40 Does it need to start a node? Don’t know what that is 15:09:02 Oh, make sure you have a 0.18.x.y version. Earlier will stop as of a couple days ago. 15:09:08 "in monero-project? no luck" <- Yeah. Maybe try these: https://stackoverflow.com/questions/43216273/object-file-was-built-for-newer-osx-version-than-being-linked 15:09:30 I do have latest version cause I just did it 3 days ago 15:09:31 Ah, if you're using some random stranger's node to do the work for you, they may feed you bullshit, or just have old software, etc. 15:10:27 Local node? 15:11:38 May I have one of you guys call me? I don’t know if that’s proper ediqette, but I’ve been trying since yesterday to figure this out 15:11:45 Local is good. Downloads and *verifies* the chain. Selecting pruning. It'll need ~ 50 GB. 15:12:39 Etiquette 15:13:33 i can give my number? I just want to get my money 15:13:50 I recommend you do not give your number to anyone. 15:14:05 Ok. 15:14:30 ummm. There has to be an easier way 15:15:10 this a a brand new MacBook Pro 2021 15:15:12 Just make sure your refresh height is 0 (to make sure) and you're conncted to a recent daemon (local is best) that's finished syncing. 15:16:32 It says it’s synchronizing 15:17:25 it could take few hours to finish synchronizing then after that your funds should appear 15:18:23 Do I need to reset blockchain location? 15:18:59 Probably not, unless it's somewhere you have not enoguh space (~150 GB for full, ~50 GB if pruned). 15:19:02 i wouldnt think so, if you see the number keeps going up then it means it's doing its thing already 15:19:23 right, make sure you have enough storage space 15:19:36 a message came up that that was 0GB and it needs 105 GB 15:19:51 how do I fix that? 15:20:14 oh so in that case then yeah, gotta move to new folder 15:20:22 it’s a new computer so there should be plenty of storage space 15:20:49 so reset blockchain? 15:22:07 i dont know much about macs but do you have a way to see the drives and how full they are and such? 15:23:30 im sure I do but not sure how to check on mac 15:23:54 also btw, this channel is more for dev works, would gladly help on an other channel, on matrix there's different channels like "monero", "monero-dev", "monero-community" and such, is there a way for you to join an other of those channels? 15:24:20 It must be un settings 15:24:58 another error message saying file system is read only 15:25:38 therenis only 0 GB available on device. Blockchain requires 105gb 15:25:44 how dome fix that 15:25:46 (invited you over the monero community channel, if you seeing the invite, please accept it so could move over there :)) 15:26:43 Accepted 15:26:49 Thank you spacekitty420[m4 :) 15:27:12 chat there? 15:27:12 :3 15:27:33 if you seeing the messages over there yeah 15:28:41 Just one word before you go: having monero makes you more of a target than usual for assholes, so be *very* wary of giving your number or other identifying info to randoms. 15:29:16 And especially not access to secret keys. 15:29:29 Even if they seem helpful. Scammers will appear to be. 15:29:41 Yes, the world sucks... 15:29:54 I'm getting this out of a wallet-rpc python test: `json.decoder.JSONDecodeError: Invalid control character at: line 5 column 65 (char 117)` What is a good way to debug this? 15:30:08 moneromooo: This is very important liliana914: 15:30:24 Do you use a binary RPC and try to parse as text ? 15:31:19 I'm encoding to z85 so that should be okay I think. 15:31:40 Oh, you're adding a new RPC IIRC. Then make sure you don't send, eg, crypto::hash, but std::string, with epee::string_tools::pod_to_hex, that kind of thing. 15:33:42 Indeed. Ah, okay. I think the error comes from the return from the newly added fn and I'm adding a std::string to res. 15:47:39 I'm thinking that if I have any of `. - : + = ^ ! / * ? & < > ( ) [ ] { } @ % $ #` in a string I'm trying push through json, it will break? Possibly the `/`? This is part of z85 so I guess I need to use hex encoding instead? 15:51:18 These look ok. / is fine. 15:51:42 " would be problematic. Possibly \ too. 15:54:20 OK, that's not the problem then. That's all I have besides letters and numbers. 17:35:14 "Yeah. Maybe try these: https://..." <- thanks for your help jozsef. I discovered that after updating macos, it didn't update the system's sdk for some reason. deleting and reinstalling mac's command line tools force updated the sdk 17:39:39 vtnerd: I think existing multisigs are unusable without this PR https://github.com/monero-project/monero/pull/8329 could you review it? 17:42:00 Are wallet2::{en,de}crypt used/tested somewhere? 17:47:20 I do encrypt/decrypt and I correctly get back the original plaintext + 2 garbage bytes. 17:53:02 It's used to exchange various data. Like cold signig data IIRC. 17:53:29 Extra bytes would likely be transparent there. 17:56:01 I don't see it anywhere outside of wallet/wallet2.cpp. Can you point me to it? 17:58:14 git grep crypt\( src/wallet ? 17:58:36 Or did I misunderstand your question ? 18:11:12 No, you didn't. I've done similar: `grep -Iir 'encrypt(' | grep wallet`, both getting some non-wallet2 hits but I don't see these the wallet2's used anywhere. I think I'm using them right: via json rpc. I get this json outputs: from python tests:... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/2786bcba1889e3facaac98ff9ccf67c6f5070d55) 18:16:07 encrypt_with_view_secret_key() is used often which uses encrypt() internally 18:24:00 True. Might/should there be a difference if encryption is done with the spend key instead? 18:24:49 I mean in the implementation required for wallet2::encrypt/decrypt, not where encrypt_with_view_secret_key() is currently used. 18:24:59 Not to trailing bytes. 18:25:37 Yeah. Maybe I'm getting garbage from json somewhere... 18:27:04 I meant, whether using view or spend key will not change whether you get trailing bytes. 18:27:46 In any case, an extra unit test is good ^_^ 18:28:07 Yeah, I think I will just add one. 18:28:10 Or two. 19:16:22 i have this xmr transaction that won't appear in my wallet (ive tried several). Where do i begin to figure out what's wrong with it? It has over 9000 confirmations 19:17:10 would it make sense for this line to be `EXECUTE_PROCESS(COMMAND brew --prefix openssl⊙1` since 1.1 is generally used, including by libunbound? 19:17:23 https://github.com/monero-project/monero/blob/b6a029f222abada36c7bc6c65899a4ac969d7dee/CMakeLists.txt#L582 19:17:43 https://xmrchain.net/tx/0b114eb120b50b2e167837e43c3db450029d2fd62bf81d328a9e3203dea691d6 19:17:54 does libunbound not work with openssl3? 19:18:10 burnstrees[m]: which wallet are you using? 19:18:22 the installation instructions specify 1.1: https://unbound.docs.nlnetlabs.nl/en/latest/getting-started/installation.html 19:18:57 do you run into any issues currently? 19:19:13 I can try installing everything with 3 and see 19:19:25 * 9000 confirmations., * ofc ive verified the wallet address already and it is correct. what else can i do? 19:19:42 it works specifying 1.1, but then, that's the only I had installed 19:20:17 I assumed brew --prefix openssl should show 1.1 when only that is installed 19:21:06 it shows /usr/local/opt/openssl@3 for me, maybe my links got messed up 19:21:31 actually brew install openssl installs 3, so maybe not 19:22:40 burnstrees[m]: first step is saying which wallet you are using. and then joining the correct channel. 19:26:21 woodser[m]: maybe check for 1.1 first and then for 3? 19:27:33 in cmakelists? 19:28:01 will try to google if there is a good way to make cmake compatible with homebrew openssl, without calling brew --prefix 19:28:13 yes in cmakelists 19:28:39 do you know the syntax to check? 19:29:13 it works if I manually check for `brew --prefix openssl⊙1`, so I expect it should work if it checks 1.1 before 3 19:30:24 * the build works, modifying to check for `brew --prefix openssl⊙1` 19:30:34 s/// 19:30:35 yes that should work as a workaround if no better solution is found 19:52:50 i'm using the monero-wallet-gui. i didn't see a support channel so i figured this would be the right place? could you point me in the right direction? 19:55:18 #monero-gui 19:55:42 or rather #monero-gui:monero.social for matrix users 19:56:34 thanks. which irc network are you guys on? 19:58:54 * guys on? i checked efnet but it was empty 20:00:41 you can join via matrix, just search for monero-gui. this is on libera 20:49:28 a lot of people complain about "vanished coins", this is just wallets not synced right? 20:58:36 there are no vanished coins 20:59:07 yes, they possibly are connected to a node that isn't updated 20:59:41 it is recommended that they set a custom remote node instead of using simple mode, which connects to a random node 21:00:04 Yeah, the support requests ive seen were either... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/192d0bfd86a5f7e596c8b227bf97b29fbffcf86b) 21:01:28 Selsta, using your node fixed burntrees missing tx 21:01:28 After they updated their gui, it left the old monerod process running (stuck at block block 2688888) 21:02:33 manually stopping and starting the local daemon should work 22:11:45 should limit_up include rpc traffic?