02:15:28 <WinslowEric[m]> <Elijah[m]> "Stagenet is just mainnet code..." <- There isn't any difference?
02:16:32 <hocuspocusoutoff> Youre free to pay money for stage net xmr if you want but I'm pretty sure they flow like water
02:16:55 <WinslowEric[m]> lol
02:19:05 <WinslowEric[m]> Ehh sorry for being off-topic, but I'm actually from Translation Workgroup. Does "Change" here means "alter" or "small money"?
02:19:08 * WinslowEric[m] uploaded an image: (134KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.org/jDdFvvMvshxVPqktqiGrrvAq/image.png >
02:24:59 <plowsof[m]> "Claimed change does not go to a paid address" 🤔 i don't understand the original sentence 
02:26:30 <plowsof[m]> but it is 'small money' 
02:26:55 <WinslowEric[m]> Understood, thanks!
02:32:36 <hocuspocusoutoff> Iirc one of the ways monero obscures your tx is by sending an amount greater than what you tell it, and then routing the change back to yourself. So if you want to send 1 xmr, your wallet sends 5 xmr total, 1 to the real recipient and 4 back to you
02:32:45 <hocuspocusoutoff> So the 4 is "change"
03:57:44 <merope> That's not obfuscation, and all cryptos do that. A tx input must be spent as a whole, by design; so when you have a 5 xmr input and you need to send 1 xmr to someone, you must also send the "remaining" 4 xmr somewhere else (i.e. a separate output that goes back to you, aka change)
04:01:20 <merope> Think of each tx output as a euro/dollar bill, but instad of standard denominations (1, 5, 10, etc.) they can have any value
04:01:30 <hocuspocusoutoff> TIL
04:25:56 <pagwin[m]> > That's not obfuscation, and all cryptos do that. A tx input must be spent as a whole, by design; so when you have a 5 xmr input and you need to send 1 xmr to someone, you must also send the "remaining" 4 xmr somewhere else (i.e. a separate output that goes back to you, aka change)
04:25:56 <pagwin[m]> I may be missing something but why is change necessary, shouldn't cryptocurrency be subdividable to whatever degree the spec allows in which case you'd just send the amount and be done with it?
05:23:22 <pysticmunk[m]> > <@pagwin:matrix.org> > That's not obfuscation, and all cryptos do that. A tx input must be spent as a whole, by design; so when you have a 5 xmr input and you need to send 1 xmr to someone, you must also send the "remaining" 4 xmr somewhere else (i.e. a separate output that goes back to you, aka change)
05:23:23 <pysticmunk[m]> > I may be missing something but why is change necessary, shouldn't cryptocurrency be subdividable to whatever degree the spec allows in which case you'd just send the amount and be done with it?
05:23:23 <pysticmunk[m]> Indivisibility of outputs is an organizational design. Think of fiat bills, one or more outputs are spent completely to execute a transaction and change is received.
09:45:18 -xmr-pr- mj-xmr opened pull request #8207: CMake: Add missing headers via monero_find_all_headers macro
09:45:18 -xmr-pr- > https://github.com/monero-project/monero/pull/8207
10:53:34 <binaryFate> Heads up that the melo.tools nodes are migrating to a new URL at community.rino.io, anyone needing a remote mainnet/stagenet/testnet node can see more info here: https://community.rino.io/nodes.html
14:00:18 -xmr-pr- ThomasAn73 opened issue #8208: SSD Bottleneck and wear with monolithic file.
14:00:18 -xmr-pr- > https://github.com/monero-project/monero/issues/8208
14:48:32 <w[m]> "Adding a new block to the chain means the entire 40Gb file has to be re-written even though the last seven years of blockchain data has not changed."
14:48:32 <w[m]> From the above pr.
14:48:33 <w[m]> Is this correct?. Doesn't sound right 
14:49:39 <w[m]> There cant be anyway that i'm rewriting 40gb every2 mins. .. my device isnt that fast. 
15:18:52 <moneromooo> It is indeed obviously not true.
16:17:06 <binarybaron[m]> <binaryFate> "Heads up that the melo.tools..." <- Thanks for the info! Do you have an estimate on when the old domain is gonna stop working? The atomic swap cli (comit) currently defaults to the old domain for the remote node
16:28:51 <spirobel[m]> <Elijah[m]> "Just wait 3 minutes when you can..." <- I waited really long and the onNewBlock callback never gets called. 
16:29:14 <spirobel[m]> maybe I did something wrong I dont know.
16:43:55 <spirobel[m]> I also put a breakpoint here: https://github.com/monero-ecosystem/monero-javascript/blob/f167d6890d0764ee7dbeb9deacc6ad1825e77961/src/main/js/wallet/MoneroWalletFull.js#L1759 but it never gets hit....maybe there is some issue with the daemon or there is another reason for this haha...I think I just need to work on another part and then come back....but its not easy to back off haha
17:32:19 <w[m]> <binarybaron[m]> "Thanks for the info! Do you have..." <- Comit has no maintainer ATM iirc
17:51:19 <binarybaron[m]> I and a few other volunteers submit pull requests and review them. Thomas Eizinger (part of the comit team) also reviews PRs and usually merges them within a few days. It's not completely unmaintained, but the situation could be better.
19:03:12 <spirobel[m]> <spirobel[m]> "maybe I did something wrong I..." <- or maybe my assumptions were wrong. I just double checked: It seems like the wallet is connected to the daemon and it is synced. I dont know why but I assumed that even after a short period of time it would not be synced and these listeners would start to fire. Also I expected this onNewBlock listener to fire when a new block gets added to the chain like it is stated in the docs. But
19:03:12 <spirobel[m]> maybe this is just not how it works. It could also be the case that because I do background syncing with walletFull.startSyncing(1000); that these sync and new block related listeners dont fire and they only fire when walletFull.sync(listener) is called. All of this is just speculation. Just wanted to put it out there to heal my mind haha 😅😆 If there is someone else who implemented a wallet with monero-javascript or has any advice
19:03:12 <spirobel[m]> on this I would be glad. How do you handle syncing? I currently do walletFull.startSyncing(1000) to start the background syncing and attach the listener with walletFull.addListener(listener). I dont know if this is the right approach and if there are any other approaches. If you have any ideas let me know 🥰
19:31:39 <reeemuru[m]> spirobel: im still learning how to integrate monero-javascript. haven't displayed sync progress yet. just testing on new wallets. will check it out and let you know
19:48:39 <spirobel[m]> I have one more guess: https://github.com/monero-ecosystem/monero-javascript/blob/f167d6890d0764ee7dbeb9deacc6ad1825e77961/src/main/js/wallet/MoneroWalletFull.js#L1745 maybe to listen to the sync process we need to pass the listener to sync(listener) there. but it isnt passed for the background sync as seen in this function. In the function we can see it adds the listners than queues a sync task to the wasm module and then removes the
19:48:39 <spirobel[m]> listener again https://github.com/monero-ecosystem/monero-javascript/blob/f167d6890d0764ee7dbeb9deacc6ad1825e77961/src/main/js/wallet/MoneroWalletFull.js#L680  I wonder if it is necessary to remove and attach listeners before and after the sync process or if this is just because it was decided to be like this for the wallet.sync() API. I hoped/assumed I can just attach a listener with wallet.addListener(listener) and be done with it.
19:48:39 <spirobel[m]> (without a need to attach, or remove listeners and be able to depend on them firing when expected) but it seems like that isnt the case and it is not that easy to get this right. 🥺
20:03:44 * spirobel[m] uploaded an image: (121KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.org/SzOXbSQuMmfuYuZBVYWZDYqA/image.png >
20:04:19 * spirobel[m] uploaded an image: (292KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.org/LxvHrQhoNTPRhIJUlTjhSWsK/image.png >
20:06:54 <spirobel[m]> just did some more tests. the listeners dont fire because either there were no new blocks (created the wallet yesterday...would be surprising) or because they only fire when related to the wallet. Maybe the confusing also comes from that onNewBlock does not refer to the chain but to the wallet. (not really coherent and just speculation lol) 
20:07:14 <spirobel[m]> s/confusing/confusion/
22:52:20 <woodser[m]> it should fire for any new block added
22:52:27 <woodser[m]> you can mine yourself to ensure the network has blocks added
22:52:32 <woodser[m]> you can also print the height to check if it's increasing