KnifeOfPi: I just tested the branch with `./monero-wallet-cli --log-level 0 --restore-deterministic-wallet --daemon-address node.xmr.to:18081`

and my logs are correct, so they are doing something wrong at some point (sends wrong logs maybe)

can you ask them to use a different file hoster?

he’s sent the file like 3 different ways

every time 73kb

Maybe his disk is shot ^_^

That wouldn't explain the seemingly nice extra logs though. Shrug.

Or RAM.

The log timestamp seems to be earlier than the binary timestamp, assuming it's not a locale display thing.

timestamp seem to match, the wallet got created at minute 56 and the logs also begin at 56

the binary timestamp are the same as mine

nvm, I misread 8/6.

did you see this wallet2.cpp:2501 logging line before?

I don't remember.

KnifeOfPi: can the person move out his coins?

i will ask

no he can not move out his coins.

his wallet shows only 0.084 XMR balance.

Which makes sense if you count the digits 84.,201,250,000

The std::to_string probably butchers the number (there's a broken patch on github to deal with that).

So the code to insert . sees , as another character.

KnifeOfPi: and what is his balance supposed to be?

src/wallet/wallet2.cpp:2625Received money: 0.084201250000,

it should be 128 XMR I believe

none of the transactions he sent ever actually showed up on the chain

but they were still deducted from his balance

I think someone is pulling your leg with fake txids.

I guess you could ask to run with windows' equivalent of all the LC_* unset.

this guy seems very non technical

Enough to add new logs :)

well something is weird here, the logs even say that he is running the correct commit according to the version number

moneromooo: would the logs show up if --log-level 0 is missing?

Only the first line showing log levels.

e.g. the logs say 2020-08-07 22:13:03.603 16984 ERROR wallet.wallet2 src/wallet/wallet2.cpp:1889

1889 is a line we added

but the logs don’t match what it is supposed to say

selsta: what platform are you running on ?

Mac, I was going by the logs the KnifeOfPi sent

that*

when I run the branch it looks correct on my mac, it says the `process_new_transaction: money received in` line

iDunk: if we can get the locale settings that person runs with, could you try running with those to see if you get weird things ?

he is from pakistan

(on windows)

(or anyone else who runs windows)

Sure (but I still think someone in Pakistan is trying to get something for nothing).

Hmm. The code printing txids doesn't use std::to_string, it indexes direcrtly into a hex char string, so unlikely to be a locale thing.

is that enough info (from pakistan) for windows ?

They've got at least two languages there IIRC, pashtun and.. arabic I think ?

Wikipedia gives a few more.

US English numbers and currency formats i.imgur.com/7kgRZHK.png i.imgur.com/Hq3b5Qi.png

Pashto (Pakistan) numbers and currency formats i.imgur.com/8VQpPBh.png i.imgur.com/qeaFP4N.png

^ default settings.

The , matches what we see. So, are txid mangled ? :)

the line numbers seem totally wrong in the logs

even for known things like the "Received money with tx" line

L473 looks like an editing fail.

Heh, odd one indeed.

Could be two threads logging at once maybe.

Though I don't see a partial remainder of such a line.

iDunk: btw does the binary produce expected logs on your system?

I might as well run it...

(Not to mention that block heights in the last four lines are ~10 days into the future)

lol what the hell

why would he go through effort of faking logs

Social atomic swaps :)

I don’t understand what’s going on lol

but the weird logs + changing file size is suspicious

though not sure what he is trying to achieve

could it be caused by a localization issue...?

Here's what line numbers belong to what category and what they log paste.debian.net/hidden/b7971390

iDunk: that’s what it looks like on my system too

this was with my bin?

With mine.

KnifeOfPi: one thing he can try is to restore a non broken wallet and then post the logs

if the resulting logs are also broken then I would guess some localization issue

Or an attempted scam.

also possible :D

XMC->XMR swap :D

Block heights in the future make sense now.

still don’t fully get it

tried to scam?

Someone is trying to pass his XMC for XMR.

you think the logs are faked?

Yes.

the whole story was suspicious anyway lol

I linked the 128 XMR txid to Monero Classic.

yea I saw it

soo they used XMC to create the screenshot?

and then merged the logs

Probably.

doctored logs would explain why they went from 100KB -> 70KB lol

iDunk: log line numbers match XMC github.com/monero-classic/monero/bl…master/src/wallet/wallet2.cpp#L2501

Mystery solved :)

w a t

XMC???

its fucking monero classic

is there any way it could have been done by mistake?

KnifeOfPi: no

No, the logs were doctored. You only need to take a look at other lines in the wallet2.cpp selsta linked.

fucking hell man

"FUCKXMR" wallet name made me look at other forks' explorers :)

i had expected he would just be mad

because we had him use cli and he was acting like a very non technical user

this idiot wasted many hours of our time

I think he was trying to get a "refund". That's why I keep calling it a swap.

yeah, that's what I expected

he seemed suspicious from the beginning because he complained of 128xmr being 1 year of his income

so how the hell did he buy it in the first place

hey, iDunk, did he just use straight up XMC logs, or did he try to splice in some stuff from the proper wallet log?

he mixed them

Wow

So someone who knows how monero works well

i almost want to make a post on /r/monero to expose this guy

he wasted so many hours of time of everybody on the cake wallet team, and you guys as well

> ok i wont be able to do it again please... i have tried thousand times and then my seed works

he would usually take 30 minutes to one hour to respond with stuff

guess because he was faking shit

welcome to my world

endogenic: this happened to u before?

running a high traffic wallet and having to support lots of different user cases? being asked to do things for people on occasionally bad info who didnt want to contribute back? lol welcome to cryptocurrency

risk

finance

Yeah

moneromooo: I can't sync monerod from scratch. Using recent master build. I's beind stuck with calculating tx weight. 2020-08-08 17:23:16.881 E get_pruned_transaction_weight does not support older range proof types

Is it interesting bug or something trivial to avoid?

If you're going to release soon then this bug will pop up later. it's likely unexpected regression.

I thought I'd fixed that. Let me check github...

What height block is it breaking on ?

2020-08-08 17:32:03.354 I transaction is too heavy: 18446744073709551615 bytes, maximum weight: 149400

2020-08-08 17:32:03.354 E Transaction verification failed: <bf98829d8644e7a395a8972543ee7313290ecf801330ab88453fbda9f7b957ec>

Thas' from block 1685619

I can locally dig into it if it's important and not trivial problem.

I'd like to know where it's coming from (call stack).

Ok. I'll try to debug it personally since it require this level of details.

I think paste.debian.net/hidden/f12b5837 will fix it.

I was asking for prunable from when BPs started, but should do so only when they become mandatory.

Alternatively, making get_pruned_transaction_weight support Borromean proofs would be better.

Why this error didn't pop up earlier during your own testing?

I doubt I made a full sync.

Are there no any relevant regression tests in monero codebase?

Not for this.

More tests are welcome if you feel like adding some. Though tests syncing through actual live data... not sure.

Patch works: it's syncing. Hope my report was useful.

Thanks for fast response.

It was. Thanks.

UkoeHB_: Thanks, I may have conflated two different proofs