hi, just a noob lol

a afungible[m]1 if you can’t pay the fee, then you can’t make a tx

<UkoeHB> "You’d be better off writing a..." <- What’s ch2 ?

I assume chapter 2.

moneromooo: I should wait to be fully waken up in the morning before writing 😂

Too much worried to miss the pace lol

Few days ago Someone told me that ge_p2 was of 120 bytes each X Y Z of 40 bytes just for sake of calculation but today I debugged the code and found that when ge_double_scarlarmult_base_vartime() return a point after calculating aG+bH eah of coordinate of the new point returned is not of 32 bytes as stated in ztmw for point addition their is

formula for each coordinate but at last mod is applied on them at every step of point addition and this mod makes that coordinate of 32 bytes as mod q is of 32 bytes but here when calculating function returns point it actually returns each coordinate as 40 bytes and than ge_tobytes() who is responsible for compressing point to present it in key

form instead of point form than ge_tobytes() passes it to fe_tobytes()  which actually is applying mod on the point that has been calculated and also returns comprehensive point. My question is why x,y is not produced as per formula in ztm2.

As formula states when new point's x,y is calculated it goes through mod and than that mod applied point goes to calculated with itself in point doubling

For point doubling P's x,y are used to produced P2 by adding point P+P using the formula of twisted curve where in production of P2 the points produced by applying mod at every step

<UkoeHB> "a afungible if you can’t pay the..." <- Yes, I'm aware. My point was even if I top up the wallet with sufficient amount to cover for fees, I cannot transfer out all of my balance. It's the same case again.

Isn't this a problem?

Are there changes for the upcoming v15,16 fork that pools need to be aware of?

Pools only need to update monerod to v0.18

P2Pool miners also need to update to p2pool v2.2.1

did anything on the blocktemplate change?

view tags were added, but they are not a part of the hashing blob for miners, and if pools use get_block_template RPC, they just need to update monerod

Cool. Thanks

afungible[m]: I see, yes that would be an edge case the current wallet code doesn’t handle. My seraphis lib has an input selection algo that can solve that case

Even with sweep_all and set ignore-fractional-outputs 0 ?

<UkoeHB> "afungible: I see, yes that would..." <- Thanks for acknowledging this.

well I didn't test it, you should try moneromooo's test case

test settings*

moneromooo: sweep_all alone, did not work. I will try 'set ignore-fractional-outputs 0', later today & report back.

moneromooo: any idea here? since they run their own node it should be possible to get logs monero-project/monero #8478#issuecomment-1203625277

selsta: looks like "remove wallet cache, let it resync, try again".

Alternatively, set reorg-max-depth to a lot.

they did say they resynced already

a couple comments later

OK. Then... lemme check whether there are interesting logs currently...

Hmm. 2 million blocks reorg, that's very wrong...

Ah, 46k in the logs, looks more plausible.

No interesting logs. If they can run with a log patch, I can make one now I guess.

I'll comment.

moneromooo: these are the only two output distribution changes i remember monero-project/monero #8404 monero-project/monero #8433

The first one looks totally fine. The second one should be fine, unless bug if the daemon I think.

Which means it's also fine, really.

ok let's wait for logs

Worthwhile to keep an eye on I guess -> twitter.com/stephenlacy/status/1554697077430505473

Hello, Ive been trying to prune my blockchain on ubuntu. It was synchronized yesterday and before going to sleep I ran the ./monero-blockchain-prune instance. It ran all night and this morning it still wasnt done? I started it again this morning and I do not have an confirmation on if it is over or not... (full message at libera.ems.host/_matrix/media/r0/do…1845ed79996507fb065075f537eba09cd4e)

doesnt make sense.. I read everywhere that the pruned blockchain should be something like 25-30 gigs?

ls -l /home/ubuntu/.bitmonero/lmdb-pruned/data.mdb

50220294144 (size) /home/ubuntu/.bitmonero/lmdb-pruned/data.mdb

theoneandonly011: "started it again", what do you mean by that? did you kill it?

it would be easier to just resync from scratch with --prune-blockchain instead of using the prune tool

Yes it was stuck after 12+ hours..

selsta: I get that but I would like to setup a pruned blockchain on my vps without having to have 100 gigs of storage.

are you sure it was stuck or just not finished yet? prune tool takes a long tine

yes, like I said sync from scratch with --prune-blockchain, you won't need more than 45gb of space

From what I heard, doing what you say will leave your blockchain to 80+ gigs. Just not take more new space

No it will prune from scratch

what you are saying only applies to pruning existing blockchains, not syncing from scratch

Ok got it, so the solution is to delete all my blockchain data and start over with ./monerod --prune-blockchain?

correct

and use v0.18 for fast sync

Thank you. I will try that instead

so we have a version number problem

we usually keep the version number on master branch at v0.18.0.0 - but the ledger app has blocked v0.18.0.0 since ledger support only got added in v0.18.1.0, that would mean everyone who uses the master branch can't use a ledger

setting the master version to v0.18.9.9 would work for example but seems a bit odd

<selsta> "it would be easier to just..." <- It works, thank you

52248924160 is the current pruned chain size

<selsta> "setting the master version to v0..." <- v0.18.99.99 to make it a bit more clear it's not a real version number? I think either way there isn't a perfect solution to this, technically v0.18.0.0 is wrong too. I think v0.18.9.9 would be fine also

Could always set the master branch to 0.18.1.0

Also thinking we could give stronger indication in the logs that it's on the master branch when it logs the version number

ofrnxmr[m]: but the master v0.18.1.0 is different than the release v0.18.1.0 - it would be confusing

ofrnxmr[m]: oh shit that makes sense then, thank you

selsta: this is same behavior we currently have with v0.18.0.0 master vs v0.18.0.0 release, no?

Perhaps ledger should change it to v0.18.0.1 and we set master to v0.18.0.1

Monero gui wallet has localization? I can’t find it in the source

what are you searching for exactly?

Different language support

smh

Thanks didn’t see that

if you are trying to add / change translations then you have to do it through translate.getmonero.org

I see. So roughly 1000 phrases