-
DataHoarder
-
DataHoarder
Along with a generated InProof ready for usage on Monero CLI/GUI
irc.gammaspectra.live/790051e6fc352e8a/image.png
-
DataHoarder
tracked entities are these,
blocks.p2pool.observer/proofs of note, Monero General Fund, Monero Bounties, MAGIC Grants
-
br-m
<bigmenpixel:matrix.org> I think I should do this after the task is fully completed (yes, I made it but the pull request hasn't been merged yet). Also, after we are given the key, I should update the pr > <@plowsof:matrix.org> @bigmenpixel:matrix.org: can you provide an update/payout request please for the remaining 3.5 xmr
repo.getmonero.org/monero-project/c…als/-/merge_requests/381#note_33204
-
br-m
<bigmenpixel:matrix.org> @bigmenpixel:matrix.org: @plowsof:matrix.org:
-
br-m
<plowsof:matrix.org> thanks for the update @bigmenpixel:matrix.org , left some comments reg the dependency updates
-
br-m
<ofrnxmr> @sgp_:monero.social can ya look onto the 101 connections that skylight is making at startup?
-
plowsof
and my $1 in monero lost forever
-
br-m
-
plowsof
i didnt write the seed down, and restarted monero-lws without an account loaded, left an issue
-
br-m
<ofrnxmr:xmr.mx> You cant view the seed from skylight settings?
-
plowsof
yes, its a new seed
-
plowsof
:P
-
plowsof
wait, ignore me, i have multiple versions of the app with other test wallets , bad plowsof
-
br-m
<plowsof:matrix.org> ive deleted my slander messages 🧑💻
-
DataHoarder
vibes of
iacr.org/news/item/27138 > 14:31:15 <@plowsof> and my $1 in monero lost forever
-
br-m
<sgp_> Tor?
-
br-m
<sgp_> Arti is needed for the wallet to work, even if your LWS isn't an onion address
-
br-m
<ofrnxmr:xmr.mx> @sgp_: Mni
-
br-m
<ofrnxmr:xmr.mx> pre-setup
-
br-m
<sgp_> It's still probably Tor. I told Artur (the dev) to speed up the initial Tor connection time as much as possible to reduce waiting, and opening the circuits as soon as it's open is a good way to reduce waiting later. If we waited until after you clicked connect, there would be a noticeable lag to first connect to tor, then connect to the endpoint
-
br-m
<sgp_> This way it's connecting to tor on the background while you're busy typing in the server and finding/writing your wallet seed
-
br-m
<sgp_> Does it happen before you click past the welcome screen (literally, a fresh install, open, and you haven't clicked anything at all) or when you get to the connection setup screen?
-
br-m
<ofrnxmr:xmr.mx> @sgp_: I have tor running locally, why does it need to be running at all, especially if im using i2p?
-
br-m
<ofrnxmr:xmr.mx> Should turn on if i check the "use tor" box, shouldnt be on if i specify my own port / dont click use tor
-
br-m
<ofrnxmr:xmr.mx> @sgp_: Will check
-
br-m
<sgp_> There's currently no way to completely disable tor in the app. Even if you set the proxy port to your for instance, it'll still attempt to use internal tor for the API connections
-
br-m
-
br-m
<ofrnxmr:xmr.mx> As soon as app is opened, fresh install
-
br-m
<ofrnxmr:xmr.mx> @sgp_: I find that annoying 🙃
-
br-m
<ofrnxmr:xmr.mx> Shouldnt need to create a new tor instance is one if already active. Cool for people why are achieving privacy w/o knowing anything about tor, but its a battery drain (and a time waste) for someone like me who already has tor running 24/7
-
br-m
<sgp_> The primary goal was to make tor work without a user knowing anything about it. We can add a tor setup option later
-
br-m
<ofrnxmr:xmr.mx> How do i make lws work with subaddresses>
-
br-m
<ofrnxmr:xmr.mx> I added max-subaddresses=50 to lws, but it says ive exceeded subaddresses
-
br-m
<ofrnxmr:xmr.mx> Also, are you seeing lmdb errors in lws console?
-
br-m
<ofrnxmr:xmr.mx> 2025-11-23 03:07:14.009 E lmdb error (storage.cpp:1090): MDB_NOTFOUND: No matching key/data pair found
-
br-m
<ofrnxmr:xmr.mx> I get this after reatoring wallet in lws
-
br-m
<ofrnxmr:xmr.mx> Also, the restore height doesnt seem to be transmit properly. I have to manually edit the restore height on the server after restoring
-
br-m
<sgp_> I can't help too much on the LWS side, but I wouldn't be surprised if there are other errors there. I don't think I've seen that error before
-
br-m
<sgp_> @ofrnxmr:xmr.mx: Restoring generally for lws is still a huge WIP
-
br-m
<sgp_> Not on the app side, but on the LWS side
-
br-m
<ofrnxmr:xmr.mx> @sgp_: Happens when i reatore from 25 word seed + restore height
-
br-m
<ofrnxmr:xmr.mx> That errror doesnt break anything. Sync works and (after modifying restore height manually) balance shows up
-
br-m
<sgp_> A lot of this is super fresh, so if you want to use subaddresses with Skylight, maybe wait a few weeks if you don't want to fully test everything haha
-
br-m
-
br-m
<sgp_> I think there are still a few subaddress related bugs on the wallet side as well. We are using a weird workaround since there isn't a simple server status endpoint to know if the server supports subaddresses and how many
-
br-m
<sgp_> I have limited confidence that subaddresses and notifications actually work 100% correctly in this first release
-
br-m
<ofrnxmr:xmr.mx> Looks like the mdb error is fixed on develop or that pr
-
br-m
<ofrnxmr:xmr.mx> no luck onnsubaddresses. Still get max subaddr| exceeded err on subaddr branch
-
plowsof
I had to set max sub adds to 20000 monero-lws side
-
br-m
<ofrnxmr:xmr.mx> 🥲 didnt work for me
-
br-m
<ofrnxmr:xmr.mx> Maybe only works with a newly generated wallet?
-
br-m
<ofrnxmr:xmr.mx> After fully synced, my balance disappears 🥲🏳️⚧️
-
br-m
<vtnerd> Edge wallet has seen this error, it's still being tracked down unfortunately > <@ofrnxmr:xmr.mx> 2025-11-23 03:07:14.009 E lmdb error (storage.cpp:1090): MDB_NOTFOUND: No matching key/data pair found
-
br-m
<vtnerd> Lwsf uses 50,200 lookahead by default so you'll need to 10000+ subaddresses to get rid of it. Lookahead is still being actively developed as it's trickier with lws > <@ofrnxmr:xmr.mx> I added max-subaddresses=50 to lws, but it says ive exceeded subaddresses
-
br-m
<ofrnxmr> @vtnerd: Its gone on the subaddress branch
-
br-m
<vtnerd> You mean `feature/subaddr_lookahead` ?
-
br-m
<vtnerd> Oh I just checked and this is a different error than what edge was seeing. This error may need to be modified as it's expected to fail sometimes - it occurred because a subaddress wasn't found in the db
-
br-m
<ofrnxmr:xmr.mx> @vtnerd: The subaddress pr, not sure which branch exactly
-
DataHoarder
is monero bounties down?
-
plowsof
seems to be, thanks will ask the pigeons
-
br-m
<plowsof:matrix.org> working now , thanks!
-
br-m
<sashimi420:matrix.org> am also very expensive, not like you could have afforded me in the first place, hence why worked for free for all these years > <@diego:cypherstack.com> Very expensive. And I have to pay them. :P
-
br-m
<sashimi420:matrix.org> funny you still out here ebegging for $20 for "pinging you" despite being an early adopter, how come you cant pay these guys out of own pocket? 😹
-
br-m
<ofrnxmr> Who's beggin?
-
» plowsof bans sashimi420 because he has no control over his own life
-
DataHoarder
-
DataHoarder
-
plowsof
⭐
-
br-m
<sashimi420:matrix.org> diego tried to extort $20 for pinging, super cringe
-
br-m
<sashimi420:matrix.org> he never did any tip himself back then while received tip from myself and through the ccs from others
-
br-m
<sashimi420:matrix.org> anyways, clearly out of touch since he dont even know that monerologs even is a thing
-
br-m
<sashimi420:matrix.org> the meme posted on nov 8 as a hello in the meeting was first posted in diego's ccs but someone deleted it after only 20mins
-
br-m
<sashimi420:matrix.org> he a dumbass and have no clue about anything, always was
-
DataHoarder
for some reason for f122e633da0a0e4fac3b0f1c2a33c5d515e3d91e474710c16db1239d21fe67af when running against a pruned node and verifying Proofs on Monero GUI I get "Error: Failed to calculate transaction hash"
-
plowsof
is this a "pruned nodes have a random portion of the chain and you got unlucky?"
-
DataHoarder
I assume this is due to get_transactions rpc returning zero hash for the ""pruned"" part of V1 ring signatures
-
DataHoarder
no, all v2 txs work
-
br-m
<ofrnxmr> @sashimi420:matrix.org: You offered to send the $
-
DataHoarder
see $ curl
127.0.0.1:18081/get_transactions -d '{"txs_hashes":["f122e633da0a0e4fac3b0f1c2a33c5d515e3d91e474710c16db1239d21fe67af"], "decode_as_json": true, "prune": true}' -H 'Content-Type: application/json'
-
DataHoarder
"prunable_hash": "0000000000000000000000000000000000000000000000000000000000000000",
-
DataHoarder
-
» plowsof bans sashimi420 for fraud, spam, evasion, spam, saying mean things to me
-
DataHoarder
where in V2 it properly includes the prunable hash
-
DataHoarder
that said
-
DataHoarder
V1 don't have prunable part
-
DataHoarder
hash = full hash, so this code should take the txid as granted when it receives pruned
-
DataHoarder
"tx_hash": "f122e633da0a0e4fac3b0f1c2a33c5d515e3d91e474710c16db1239d21fe67af"
-
br-m
<sashimi.:matrix.org> @ofrnxmr: after he tried to extort, i didnt offer shit, i already sent him enough
-
br-m
<ofrnxmr> @plowsof:matrix.org need to ban diego for extortion
-
br-m
<datahoarder> Where is the "I'm out of here see you all" message
-
br-m
<datahoarder> lasted a whole day or so before coming back
-
br-m
<ofrnxmr> @datahoarder: More like 14minutes
-
plowsof
lol
-
br-m
<ofrnxmr> > Diego Salazar drop addy for the $20 for pinging you lmao, stack wallet working rn, not sure how long but it working for now
-
br-m
<ofrnxmr> > and no, it wont be $40 for pinging you twice, u can fuck off with that lol
-
br-m
-
DataHoarder
fails on wallet2::check_tx_proof -> const crypto::hash txid = cryptonote::get_transaction_hash(tx);
-
DataHoarder
or tx_hash = cryptonote::get_transaction_hash(tx);
-
DataHoarder
it explicitly calls ok = get_pruned_tx(res.txs.front(), tx, tx_hash);
-
DataHoarder
so this will always fail on V1 transactions that return pruned data when explicitly asking for pruned data
-
DataHoarder
it has an extra check too, // only v2 txes can calculate their txid after pruned
-
DataHoarder
// for v1, we trust the dameon
-
DataHoarder
except it then calculates it again just after
-
DataHoarder
so V1 tx proofs are unverifiable on Monero GUI / Monero CLI
-
br-m
<ofrnxmr> Related to kayabas feat req? > <DataHoarder> so this will always fail on V1 transactions that return pruned data when explicitly asking for pruned data
-
DataHoarder
this calls get_transactions so no I don't think it's relevant to the other API
-
DataHoarder
the API here returns fine, it's check_tx_proof that fails
-
DataHoarder
as node can 100% be pruned, in such case for V1 txs it must trust the RPC returns the tx for that txid, but not recalculate txid
-
br-m
-
DataHoarder
ah, right, I only remembered the get_blocks.bin part
-
DataHoarder
well, that'd do it, or as the comment says, trust tx_hash (which we have already) for explicitly V1 old txs, which cannot be made anymore
-
DataHoarder
-
DataHoarder
> Given the security implications of a federation protocol vulnerability, we’ve shared details under embargo over the last 4 weeks with all known active server implementations
-
DataHoarder
Need to upgrade to room version 12 :D but it was published July-August
-
DataHoarder
-
DataHoarder
> This allows a malicious participating homeserver to potentially corrupt a room's state by sending a crafted sequence of Matrix events and API responses.
-
DataHoarder
> These issues only affect servers which are federating with untrusted or potentially malicious servers, such as participating in the public Matrix network.
-
DataHoarder
hopefully we don't get state reset across Matrix rooms
-
DataHoarder
pigeons: ^ maybe worth taking a look, for example, this room is version 6
-
br-m
<ofrnxmr:xmr.mx> all rooms are way behind
-
br-m
<diego:cypherstack.com> Er... They do know the $20 things was a joke, right?
-
br-m
<ofrnxmr:xmr.mx> They still asked for your addy
-
br-m
<ofrnxmr:xmr.mx> Which you didnt share
-
br-m
<ofrnxmr:xmr.mx> Yet came back 24hrs later to shitpost
-
br-m
<diego:cypherstack.com> @sashimi420:matrix.org: It's really unfortunate that I'm a dumbass, since FCMPs is depending on me and my team.
-
br-m
<ofrnxmr:xmr.mx> joke or no joke (it was obviously a joke), he still offered to send
-
br-m
<sashimi420:matrix.org> @diego:cypherstack.com: lmao fucking duh, obvi ik you said it as a joke, i wasnt joking about you posting the address, not i wasnt joking about you saying you a dumbass, but i was joking today being all like theatrical and shits to just catch you up to speed on what has been happening around lately, which you still out of touch on all of that
-
» plowsof warns sashimi420 for continuing the private conversation in public and bans again
-
br-m
<ofrnxmr:xmr.mx> so.. post the addr, diego
-
br-m
<diego:cypherstack.com> @sashimi420:matrix.org: I don't need your money regardless, so I won't be sending the address.
-
DataHoarder
just get a room, I can bridge it to IRC so we can continue looking into the public Private Messages
-
br-m
<ofrnxmr:xmr.mx> Its principle. You have to post it now
-
br-m
<ajs_:matrix.org> @vtnerd:monero.social: I am also getting same error message in log with max subaddresses set to 200
-
br-m
<diego:cypherstack.com> Your opinion about me being a dumbass is also noted and forwarded to the appropriate department
-
br-m
<sashimi420:matrix.org> @diego:cypherstack.com: come on, are you too scared to take "dirty money" and be associated with shits you have nothing to with? just post the addy lol
-
br-m
<ofrnxmr:xmr.mx> @ajs_:matrix.org: Set to >10000
-
br-m
<vtnerd> @ajs_ yes 200 is too low for lwsf default settings. afaik skylight doesn’t expose the settings to change lookahead
-
br-m
<ajs_:matrix.org> I am testing lws with XMRpos backend app
-
br-m
<ofrnxmr:xmr.mx> Set it to >10000
-
br-m
<ofrnxmr:xmr.mx> Error went away for me but had to re-create the wallet (i just deleted my db to do that)
-
br-m
<plowsof:matrix.org> 30 day ban for kitty, (aka anyone who says "smh" and "shits" and spams public rooms with drivel like theyre having a private conversation with their bud)
-
DataHoarder
exponentially increase bans each time they disregard the moderation action and make another alt to continue the same conversation straight away
-
br-m
<ofrnxmr:xmr.mx> Will be back in time for christmas?
-
br-m
<plowsof:matrix.org> the only person who adheres to their ban is Juliu lol
-
br-m
<ofrnxmr:xmr.mx> nope
-
br-m
<ofrnxmr:xmr.mx> Juliu has tried to return multipke tines per day, but is immediately k-lined
-
DataHoarder
^ they keep rejoining every few days, Libera.Chat were the one to force it
-
br-m