02:52:14 I'll help 10 people to earn $30k within 72 hours but you will pay me 10% of your profit when you receive it. Note only interested people should apply, drop a message let's get started by asking (HOW). https://wa.me/ +1 (501) 444‑2116 02:52:24 oh hot dog! 08:05:32 hello, i have a small problem with making any transactions. i asked in #monero, i'll copy my messages here hoping it's OK. 08:05:51 trying to send some xmr using cli wallet + local full monerod (i tried with gui and feather + remote nodes, still same problems) 08:06:18 using sweep_all => both monerod and cli shows errors. monerod gives "Bad key image!" and wallet says "transaction was rejected by daemon Reason: invalid input" 08:06:31 i'm using the latest v0.18.1.0 version, i synced it with this version, didn't upgrade or use any previous database file etc. 08:07:01 about the wallet age => it's not so recent, i also confirmed all the data scanning from 0 height 2-3 times. 08:07:15 i built up the wallet from scratch a couple of times by now. like i said in some instances from the 0 height in spite of waiting time. results is the same. 08:07:36 trying to transfer arbitrary amounts gives "Error: internal error: Known ring does not include the spent output:" 08:08:04 i tried remote nodes for couple of times even starting from scratch, creating the wallet from seeds etc. 08:09:22 sorry for the spammy spam, people who knows me from -pools may know, i get notifications if you ping, i'll try to reply ASAP for any testing. 08:10:13 how many available inputs do you have in this wallet? "balance detail" command in cli 08:12:57 one of your inputs, as you might've guessed, has bad key image and thus cannot be spent 08:13:03 why it happened is another question 08:13:18 https://paste.uguu.se/?936ddc7015ec55d1#64eKQVJXDELUvPgSeQCvfQUWZZwRbse86UdXHWy94pn9 it goes like this 08:13:48 so 14 in total 08:13:53 yeah 08:13:54 you can try to sweep_single them one by one 08:14:19 run "incoming_transfers available verbose" to get key images (last column) 08:14:26 and use these key images in sweep_single command 08:14:40 but maybe wait for moneromooo first 08:14:47 incoming_transfers available verbose => i was looking for this in all docs, thanks so much 08:14:49 he might want to run some tests on this wallet 08:15:36 last column has the numbers without <> surrounding right ? 08:15:47 well that definitely looks fucked up :D 08:16:13 all 14 of them 08:16:25 don't paste key images please :D 08:16:50 fucked up how? All 0's? 08:16:57 kinda ^ 08:17:22 so i'll probably will share for the sake of science :) 08:17:47 key image is 32 hex characters, they should be random 08:18:02 nope, no random, also ALL of them are the same 08:18:07 huh 08:18:15 then you can spend only one of them 08:18:19 choose the one with largest amount 08:18:39 whoever sent you funds did it on purpose or used broken wallet 08:19:03 if you get two inputs from two transactions with the same key image, you can only spend one of them 08:19:23 if that's a possible attack shouldn't it be mitigated? 08:19:29 just do sweep_single on key image with largest amount 08:20:03 yeah but can i select the amount with sweep_single ? 08:20:21 badjabber that's an old attack and it's been mitigated, if it is what I think it is. Wallet should show available balance = the max value of all these inputs, not the sum of their values 08:20:40 you can select key image with sweep_single 08:20:56 since ALL of the key_images are the same, how do i do that :) 08:20:59 incoming_transfers will show you amounts and images 08:21:18 not sure, try all the different hex strings from the line with the largest amount 08:21:20 aight sweet :) 08:21:41 maybe it's not the last column but some other column 08:21:46 I haven't used it in a while 08:21:49 "Wallet should show available balance = the max value of all these inputs" => it kinda does that when i try with gui wallet to send "MAX" i.e. all the balance 08:22:13 sometimes it shows only the maximum one 08:22:33 sech1: no you are right about it being the last column 08:22:44 there are headers, it really is the last column 08:23:16 Output format: Amount, Spent(\"T\"|\"F\"), \"frozen\"|\"locked\"|\"unlocked\", RingCT, Global Index, Transaction Hash, Address Index, [Public Key, Key Image] 08:23:22 so key image is the last column 08:23:45 the other hex values are tx id and pubkey which are not the same except two tx ids 08:24:16 then you can't even do sweep_single 08:24:20 yeah 08:24:44 you need to wait for moneromooo 08:26:11 i'll reply when someone can add some extra feedback, thanks for the ideas again. you mentioned/pinged him, he'll probably notice this bunch of messages. 11:53:21 If I got that right, all the key images are identity ? 11:53:44 That sounds like a bug somehow. AFAIK the sender isn't able to predict what the receiver's key images will be. 11:54:06 Did all these outputs come from hte same sender as far as you know ? 11:55:31 moneromooo: i don't know unfortunately 11:55:49 are they somehow missigned ? 11:59:51 Hello everyone, Im having some problems with integrating rpc to my application, anyone willing to help out? 12:01:14 moneromooo: also all of the key images being some kind of identity is correct, they are all the same and LOTS of zeros all over 12:01:43 Guest26: like it says in the channel info " Don’t ask to ask, just ask:) " :) 12:06:08 Im trying to connect to rpc to send or verify transaction 12:06:09 I have monero node synced up on a separate server but in the same network as the webserver, in laravel environment file I have pointed to monero rpc port 12:06:09 this is my rpc section of config file 12:06:10 rpc-bind-ip=0.0.0.0 12:06:10 rpc-bind-port=18081 12:06:11 confirm-external-bind=1 12:06:11 rpc-restricted-bind-ip=0.0.0.0 12:06:12 rpc-restricted-bind-port=18089 12:06:12 rpc-login=user:test 12:06:13 but when I try to send a transaction with the application I get this response 12:06:13 local.ERROR: Request have return error: Method not found; 12:06:14 Request: {"jsonrpc":"2.0","method":"make_integrated_address","params":{"payment_id":null},"id":1}; 12:06:55 and this is when I curl the server 12:06:55 curl -u user:test --digest http://localip:18081/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"get_balance","params":{"account_index":0,"address_indices":[0,1]}}' -H 'Content-Type: application/json' 12:06:56 { 12:06:56   "error": { 12:06:57     "code": -32601, 12:06:57     "message": "Method not found" 12:06:58   }, 12:06:58   "id": "0", 12:06:59   "jsonrpc": "2.0" 12:06:59 } 12:11:40 Any other info I need to provide? 12:13:43 Make sure you connect to the wallet, and not another process. 12:13:57 18081 is typically a daemon port. 12:14:00 Node. 12:14:13 deamon is on 18089 12:14:18 tcp        0      0 0.0.0.0:18080           0.0.0.0:*               LISTEN      63465/monerod 12:14:19 tcp        0      0 0.0.0.0:18081           0.0.0.0:*               LISTEN      63465/monerod 12:14:19 tcp        0      0 0.0.0.0:18089           0.0.0.0:*               LISTEN      63465/monerod 12:16:27 elucidator: did you look at the wallet log on log level 2 when receiving these outputs ? Might be a clue. 12:16:59 shall i rescan the wallet with verbosity up ? 12:17:12 should I check monero-wallet-rpc log or monerod log? 12:17:49 Also, unlikely to be that, but... try rebuilding wallet2 with cmake -D MONERO_WALLET_CRYPTO_LIBRARY=cn 12:18:04 elucidator: yes, --log-level 2 12:18:21 Guest26: 18081 is clearly the node in your paste. 12:18:37 Unless you renamed the wallet for funsies. 12:19:52 moneromooo: i think i see where you are getting, kinda.. i'll compile it when i have the chance.. i'll be out of town for some days, i'll definitely let you know when i return at most 12:20:41 x86_64 btw ? 12:21:03 yes 18081 is the node and this is the out put of the following command 12:21:03 monero-wallet-rpc --daemon-address 10.10.1.105:18081  --rpc-bind-port 18081 --wallet-file test wallet password=reducted  --rpc-login user:test --log-file logs/monero-wallet-rpc.log --max-log-files 2 --trusted-daemon 12:21:04 E !r. THROW EXCEPTION: tools::error::no_connection_to_daemon 12:21:04 E Initial refresh failed: no connection to daemon 12:21:05 E Failed to query mining status: No connection to daemon 12:21:37 i ran the cli wallet on armv8 but i also tried the gui wallet and feather on several platforms, including osx and windows 12:22:57 Guest26 why do you try to bind monero-wallet-rpc to 18081, it's already taken by monerod 12:23:08 fix your command line for monero-wallet-rpc 12:24:55 MONERO_WALLET_CRYPTO_LIBRARY only matters on x86_64 AFAIK, so if you had that issue on armv8 among others, then it's not the reason. 12:25:55 because when I delete bind port from command I get this output "Failed to parse arguments: the option '--rpc-bind-port' is required but missing" 12:25:56 And also node is on a separate servers and im trying to connect rpc from my webserver to node server to send transaction and stuff 12:26:33 elucidator hmm, maybe you can share the view key if you don't care much about that wallet transactions? This way mooo can reproduce it faster 12:26:41 Guest26 bind to another port number 12:27:19 moneromooo or the view key will not be enough to see key images? 12:27:56 Actually I need to create addresses and view balances as well 12:28:11 changed the bind port nothing happened same error 12:28:23 E !r. THROW EXCEPTION: tools::error::no_connection_to_daemon 12:28:40 and before anyone asks firewalls are disabled 12:29:08 maybe your daemon is not listening on external IP 12:29:44 or the actual IP you should use is different 12:30:31 The spend key is needed to calc key images. 12:30:37 sech1: yeah i will share any info necessary, i don't mind 12:30:49 Is it a hot/cold wallet setup, or a normal one ? 12:31:24 Identity or similar might be used as a placeholder when the key image is not yet known. 12:31:53 nope a normal wallet 12:32:09 enter seeds, scan the blockchain, find the tx's etc. 12:32:21 Guest26: if you telnet or nc to 10.10.1.105:18081 from that same machine you're running the wallet on, does the connection succeed ? 12:32:40 Can you share the txid for one of those txes ? 12:33:14 sure thing, let me PM you if that's OK 12:33:17 Just to see if the tx pubkey looks obviously weird. 12:33:28 this is not so sensitive for me 12:36:48 yes I can telnet from the same server and from anyone on the network 12:37:03 this is the output when I curl 12:37:03 [10:44:30 PM] curl -u user:test --digest http://localip:18081/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"get_balance","params":{"account_index":0,"address_indices":[0,1]}}' -H 'Content-Type: application/json' 12:37:04 [10:44:30 PM] { 12:37:38  "error": { 12:37:39     "code": -32601, 12:37:39     "message": "Method not found" 12:37:40   }, 12:37:40   "id": "0", 12:37:41   "jsonrpc": "2.0" 12:37:41 } 12:38:33 You are ignoring what you've been told twice. 12:38:45 You are asking the node for a wallet RPC. Don't. Ask hte wallet. 12:39:10 And bind the wallet to a port that's not already in use. 12:40:28 care to elaborate? should I change the monerod conf file to another port? 12:41:30 No. monerod seems good. 12:41:46 just ask the wallet on whatever port it's on. 12:42:12 if, if you ran the wallet with --bind-rpc-port 8765, make the get_balance request on 8755. 12:43:58 moneromooo: isnt already on the same port I mean its 18081 in this case 12:45:04 I can even browse to ip:18081/json_rpc from lan 12:45:17 18081 is not the wallet 12:45:23 you're browsing your Monero node 12:46:06 These are two different servers. They do not respond to the same set of RPC. 12:49:39 Your monero-wallet-rpc --rpc-bind-port THISNUMBER 12:51:27 ofrnxmr[m] E !r. THROW EXCEPTION: tools::error::no_connection_to_daemon 12:56:11 That one is odd. Your --daemon-address looks ok. 12:56:49 But given the above, I assume some kind of non obvious bad user assumption. 12:57:36 Try with 18089. Though the restricted port ought to be fine... 12:57:58 ie, --daemon-address 10.10.1.105:18089 13:37:40 mooo 15:54:51 elucidator: CHECK_AND_ASSERT_MES(!(sig.I == rct::identity()), false, "Bad key image!"); 15:55:26 I saw this on my node a couple days ago that is listed in Feather, so I assume that was your wallet? 17:02:30 selsta: it may be, not sure 17:19:56 So, this morn I downloaded the monero gui. Created an wallet and sent transaction via changelly? Didn't see anything about syncing till afterwards. Either way it cleared on there side. However,I'm now synced and still nada. Any idea if support exist to hurry process with hash? when I set up I chose simple. However, the amount of time it will take to sync locally is unacceptable so I'm using remote node. It's going on 5 hrs. 17:36:04 Changelly is related to minergate, scammers. IIRC changelly was doing selecting scamming. 17:36:29 Anyway, ask in #monero-community for details. 18:49:51 selsta: any idea why this build would fail? performance_tests should need to link against the mx25519 library, since I fully wrapped it in seraphis_lib (which performance_tests is linking against) 18:49:53 https://github.com/UkoeHB/monero/actions/runs/2935565515 18:52:48 UkoeHB: I built in on macOS and it worked 18:53:11 but no idea why it fails on Ubuntu maybe someone with more C++ experience knows 18:53:51 performance_tests should *not* need to link 18:53:52 ok 19:09:27 UkoeHB: try linking mx25519 as a private library. You are linking it publicly here: https://github.com/UkoeHB/monero/blob/seraphis_lib/src/seraphis/CMakeLists.txt#L96 19:19:07 nvm, looks like when linking a static library, even private linking doesn't remove the need to link to the final executable: https://stackoverflow.com/questions/36181626/cmake-linking-to-static-internal-library-without-exporting-it