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). wa.me +1 (501) 444‑2116

oh hot dog!

hello, i have a small problem with making any transactions. i asked in #monero, i'll copy my messages here hoping it's OK.

<elucidator> trying to send some xmr using cli wallet + local full monerod (i tried with gui and feather + remote nodes, still same problems)

using sweep_all => <elucidator> both monerod and cli shows errors. monerod gives "Bad key image!" and wallet says "transaction <XXXXXXXXX> was rejected by daemon Reason: invalid input"

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

about the wallet age => <elucidator> it's not so recent, i also confirmed all the data scanning from 0 height 2-3 times.

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

<elucidator> trying to transfer arbitrary amounts gives "Error: internal error: Known ring does not include the spent output:"

<elucidator> i tried remote nodes for couple of times even starting from scratch, creating the wallet from seeds etc.

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.

how many available inputs do you have in this wallet? "balance detail" command in cli

one of your inputs, as you might've guessed, has bad key image and thus cannot be spent

why it happened is another question

paste.uguu.se/?936ddc7015ec55d1#64e…ELUvPgSeQCvfQUWZZwRbse86UdXHWy94pn9 it goes like this

so 14 in total

yeah

you can try to sweep_single them one by one

run "incoming_transfers available verbose" to get key images (last column)

and use these key images in sweep_single command

but maybe wait for moneromooo first

incoming_transfers available verbose => i was looking for this in all docs, thanks so much

he might want to run some tests on this wallet

last column has the numbers without <> surrounding right ?

well that definitely looks fucked up :D

all 14 of them

don't paste key images please :D

fucked up how? All 0's?

kinda ^

so i'll probably will share for the sake of science :)

key image is 32 hex characters, they should be random

nope, no random, also ALL of them are the same

huh

then you can spend only one of them

choose the one with largest amount

whoever sent you funds did it on purpose or used broken wallet

if you get two inputs from two transactions with the same key image, you can only spend one of them

if that's a possible attack shouldn't it be mitigated?

just do sweep_single on key image with largest amount

yeah but can i select the amount with sweep_single ?

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

you can select key image with sweep_single

since ALL of the key_images are the same, how do i do that :)

incoming_transfers will show you amounts and images

not sure, try all the different hex strings from the line with the largest amount

aight sweet :)

maybe it's not the last column but some other column

I haven't used it in a while

"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

sometimes it shows only the maximum one

sech1: no you are right about it being the last column

there are headers, it really is the last column

Output format: Amount, Spent(\"T\"|\"F\"), \"frozen\"|\"locked\"|\"unlocked\", RingCT, Global Index, Transaction Hash, Address Index, [Public Key, Key Image]

so key image is the last column

the other hex values are tx id and pubkey which are not the same except two tx ids

then you can't even do sweep_single

yeah

you need to wait for moneromooo

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.

If I got that right, all the key images are identity ?

That sounds like a bug somehow. AFAIK the sender isn't able to predict what the receiver's key images will be.

Did all these outputs come from hte same sender as far as you know ?

moneromooo: i don't know unfortunately

are they somehow missigned ?

Hello everyone, Im having some problems with integrating rpc to my application, anyone willing to help out?

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

Guest26: like it says in the channel info " Don’t ask to ask, just ask:) " :)

Im trying to connect to rpc to send or verify transaction

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

this is my rpc section of config file

rpc-bind-ip=0.0.0.0

rpc-bind-port=18081

confirm-external-bind=1

rpc-restricted-bind-ip=0.0.0.0

rpc-restricted-bind-port=18089

rpc-login=user:test

but when I try to send a transaction with the application I get this response

local.ERROR: Request have return error: Method not found;

Request: {"jsonrpc":"2.0","method":"make_integrated_address","params":{"payment_id":null},"id":1};

and this is when I curl the server

curl -u user:test --digest 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'

{

  "error": {

    "code": -32601,

    "message": "Method not found"

  },

  "id": "0",

  "jsonrpc": "2.0"

}

Any other info I need to provide?

Make sure you connect to the wallet, and not another process.

18081 is typically a daemon port.

Node.

deamon is on 18089

tcp        0      0 0.0.0.0:18080           0.0.0.0:*               LISTEN      63465/monerod

tcp        0      0 0.0.0.0:18081           0.0.0.0:*               LISTEN      63465/monerod

tcp        0      0 0.0.0.0:18089           0.0.0.0:*               LISTEN      63465/monerod

elucidator: did you look at the wallet log on log level 2 when receiving these outputs ? Might be a clue.

shall i rescan the wallet with verbosity up ?

should I check monero-wallet-rpc log or monerod log?

Also, unlikely to be that, but... try rebuilding wallet2 with cmake -D MONERO_WALLET_CRYPTO_LIBRARY=cn

elucidator: yes, --log-level 2

Guest26: 18081 is clearly the node in your paste.

Unless you renamed the wallet for funsies.

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

x86_64 btw ?

yes 18081 is the node and this is the out put of the following command

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

E !r. THROW EXCEPTION: tools::error::no_connection_to_daemon

E Initial refresh failed: no connection to daemon

E Failed to query mining status: No connection to daemon

i ran the cli wallet on armv8 but i also tried the gui wallet and feather on several platforms, including osx and windows

Guest26 why do you try to bind monero-wallet-rpc to 18081, it's already taken by monerod

fix your command line for monero-wallet-rpc

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.

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"

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

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

Guest26 bind to another port number

moneromooo or the view key will not be enough to see key images?

Actually I need to create addresses and view balances as well

changed the bind port nothing happened same error

E !r. THROW EXCEPTION: tools::error::no_connection_to_daemon

and before anyone asks firewalls are disabled

maybe your daemon is not listening on external IP

or the actual IP you should use is different

The spend key is needed to calc key images.

sech1: yeah i will share any info necessary, i don't mind

Is it a hot/cold wallet setup, or a normal one ?

Identity or similar might be used as a placeholder when the key image is not yet known.

nope a normal wallet

enter seeds, scan the blockchain, find the tx's etc.

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 ?

Can you share the txid for one of those txes ?

sure thing, let me PM you if that's OK

Just to see if the tx pubkey looks obviously weird.

this is not so sensitive for me

yes I can telnet from the same server and from anyone on the network

this is the output when I curl

[10:44:30 PM] <Guest26> curl -u user:test --digest 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'

[10:44:30 PM] <Guest26> {

 "error": {

    "code": -32601,

    "message": "Method not found"

  },

  "id": "0",

  "jsonrpc": "2.0"

}

You are ignoring what you've been told twice.

You are asking the node for a wallet RPC. Don't. Ask hte wallet.

And bind the wallet to a port that's not already in use.

care to elaborate? should I change the monerod conf file to another port?

No. monerod seems good.

just ask the wallet on whatever port it's on.

if, if you ran the wallet with --bind-rpc-port 8765, make the get_balance request on 8755.

moneromooo: isnt already on the same port I mean its 18081 in this case

I can even browse to ip:18081/json_rpc from lan

18081 is not the wallet

you're browsing your Monero node

These are two different servers. They do not respond to the same set of RPC.

Your monero-wallet-rpc --rpc-bind-port THISNUMBER

ofrnxmr[m] E !r. THROW EXCEPTION: tools::error::no_connection_to_daemon

That one is odd. Your --daemon-address looks ok.

But given the above, I assume some kind of non obvious bad user assumption.

Try with 18089. Though the restricted port ought to be fine...

ie, --daemon-address 10.10.1.105:18089

mooo

elucidator: CHECK_AND_ASSERT_MES(!(sig.I == rct::identity()), false, "Bad key image!");

I saw this on my node a couple days ago that is listed in Feather, so I assume that was your wallet?

selsta: it may be, not sure

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.

Changelly is related to minergate, scammers. IIRC changelly was doing selecting scamming.

Anyway, ask in #monero-community for details.

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)

UkoeHB: I built in on macOS and it worked

but no idea why it fails on Ubuntu maybe someone with more C++ experience knows

performance_tests should *not* need to link

ok

UkoeHB: try linking mx25519 as a private library. You are linking it publicly here: github.com/UkoeHB/monero/blob/serap…lib/src/seraphis/CMakeLists.txt#L96

nvm, looks like when linking a static library, even private linking doesn't remove the need to link to the final executable: stackoverflow.com/questions/3618162…ternal-library-without-exporting-it