00:03:15 !seen p3rL 00:13:02 !seen p3rL 09:54:22 https://www.themoneromoon.com/p/the-monero-moon-issue-86 11:18:09 In monero cake wallet it just generates new monero address for you when you exchange from ltc to Xmr right ? 11:23:09 hopefully, haven't checked :) would be stupid not to right? 11:23:40 I loke how I can use the same wallet on both PC and android 11:27:00 dont know how it really compares to the default wallet feature wise 11:27:38 sure it's nice to have other coin support etc usability but its a legit fear that might mean the XMR wallet isnt really behaving optimally in that kind of generic wallet... 12:37:37 Is there a particularly efficient way of consolidating amounts in many diverse addresses? 12:38:10 consolidating amounts in many addresses? 12:38:17 to what? one address? 12:38:24 Or do I just send all to a new address in, say, feather? 12:38:40 Cindy: yes 12:38:41 are you talking about subaddresses or regular addresses 12:40:25 I wish I knew. They are coinbase txs. :) 12:40:52 so you're talking about consolidating all the coinbase outputs? 12:41:08 Yes 12:41:08 or just.. are you mining to many seperate addresses or something? 12:41:11 ah 12:41:21 yes, you can just send all the outputs to yourself 12:42:17 https://docs.featherwallet.org/guides/sweep-output 12:42:38 sweep all the outputs to yourself, which will merge them all into one 12:42:58 Aight. I remember I read something a long time ago that there was a particularly clever way if one ran ones own node. But I recall neither the motive nor anything else. 12:43:06 Cindy: Thanks! 12:43:14 honestly, you don't need to run your own node for this one 12:43:19 unless you have a LOT of outputs to use 12:43:34 restricted RPCs have a limit on how much outputs you can have in a transaction (to prevent DoSes) 12:43:55 Cindy: No they dont 12:44:01 oh? 12:44:07 i could have swore 12:44:25 sorry 12:44:36 The limit is 100kb one way or another. About 146 inputs 12:44:45 idk what a lot is 12:44:51 what ofrnxmr said 12:45:00 maybe 200-ish payouts 12:45:22 Feather wont create multiple txs when doing a clnsolidation, so youll have tk use another wallet for that (iirc) 12:45:29 so, more than 146 12:45:43 or just split it yourself 12:46:20 make one TX with 146 inputs, and another with the rest that is left 12:46:33 the problem is you'll end up with 2 outputs, rather than one output 12:46:47 unless you refer to the output that was created by the earlier TX 12:46:50 The main reason to use a local node is that finding decoys is slow, and if it takes too long thr wallet bails out 12:47:02 Aight. Guess it was more complicated than just clicking a button. I'll read up. Thanks for the hints. 12:47:27 Its not more complicated than clicking a button 12:47:39 Just sweep all to yourself 12:48:25 The sweep-output thingy in feather then? 12:48:38 Better to sweep to a new wallet or to a subacccount, so that youre not re-consolidating already consolidated funds 12:48:55 @tsjk:matrix.org: Use gui or wallet-cli 12:49:20 in GUI, it's pretty simple 12:49:36 copy your primary address, go to send, paste it as the dest, click the infinity button 12:49:39 and send 12:50:50 Okidoki. I'll try that! Guess I'll need to import the seed to the gui. But that's no problem. I'll do that and see. Thanks 12:51:44 ofrnxmr: does GUI let you switch accounts in the same wallet? 13:06:46 Cindy: yes 13:11:10 neat 13:12:09 It makes you think your wallet got drained until you realise you're in the wrong account :D 13:13:38 your wallet has nothing: O_O 13:13:43 you were in the wrong account: :) 13:14:02 your wallet actually has nothing and someone swept it all up: O_O 14:26:55 time for some upgrades! 14:27:05 am5 socket here i come 14:29:18 What about DDR5 RAM though, have you stocked up in advance? 14:32:49 It's not like I could've stocked up on it even if I wanted to. 14:33:31 sech1: i'm glad that i bought storage that i did not need 6 months ago 14:33:50 Thankfully 16 gigs is more than enough for me, and by the time I can afford to upgrade, AI may not have as much money to throw around... 14:33:51 they looked like good value at the time, looks like a genius move now 14:34:12 But storage - yeah. That I could've used. 14:34:58 the 2tb nvme drives that i bought 6 months back have damn near doubled in price 14:36:55 F 14:37:58 I haven't filled up even my 512 SSD + 1 TB HDD, but in hindsight should've bought another SSD. I can't leave the HDD plugged into my Raspberry all the time because I'd need it to be noiseless, and the SSD is getting full... 15:14:41 yeah ima just have to suck it up and pay cpu prices for some ram 15:36:46 is uh matrix doin something weird? 15:37:51 no 15:37:54 why? 15:39:06 i can't login on element 15:40:24 you tried another client? 15:48:23 tryin the web client. monero.social won't work when i put it as the homeserver 15:50:42 The irc-matrix birdge is also down 15:52:24 sgp save us 16:54:23 yeah monero.social must be down 17:09:14 yes, back end admin looking into this 🙏 18:48:43 Hi there. Good to know you guys all alive! 18:51:46 16:50:42 The irc-matrix birdge is also down 18:51:50 yeah, it goes via monero.social 19:22:09 Hey everyone! I'm new here and I tried joining the monero:monero.social Matrix channel (and others listed in https://www.getmonero.org/community/hangouts/), but for some reason neither Cinny nor Element can join it. Cinny fails with "MatrixError: [502] Failed to fetch alias" while Element just hangs. Is the Matrix server still working? Of course, I'm happy to use IRC, but the Matrix error looks weird 19:23:19 matrix monero.social is down 19:23:24 HTTP 502 mostly means it couldn't contact backend 19:23:31 yay 19:23:38 matrix-free day 19:23:41 woohoo 19:24:19 Oh. Will it come back online? 19:24:30 18:09:14 <@plowsof> yes, back end admin looking into this 🙏 19:24:48 Ah, great. Thank you! 19:25:29 also btw, why are there public monero nodes that only work in HTTP 19:25:34 (not HTTPS) 19:25:50 aren't people worried about DPIs? 19:26:21 or maybe setting up monerod to use HTTPS is hard 19:28:29 I wonder if this counts as "DPI" given that it's just reading plaintext. When I think "Deep", I think "figuring out whether this TLS connection is real or hiding a tunnel inside it". 19:29:15 DPI also includes reading into what's inside the packet, determine what kind of service it is for 19:29:25 and deserializing info from it 19:29:47 just look at wireshark, it's an example of a DPI 19:47:31 Cindy: there are issues, but if you are using it to sync + send txs via tor, you are mostly fine 19:47:57 though as always, a bug in how wallet handles this can make issues appear as the most recent one shows 19:48:18 and remember "fine" is relative 19:56:51 Cindy: Almost everything sent to and from a node is public anyway. The only privacy issue is its IP address origin. 19:57:56 Most node SSL certs would be self-signed. They can be swapped out by a man in the middle, theoretically. There is SSL cert pinning to defend against that AFAIK. 19:59:26 I run a public node and don't use an SSL cert. You can connect with the same node through my onion service. That sort of is like an SSL cert. 20:00:25 > That sort of is like an SSL cert. 20:00:25 unless you do ssl cert pinning, Tor is stronger than pure SSL with public certs 20:01:09 it'd make headlines but a rogue public/country CA could issue a cert for the node one, unless you pin to the pubkey/cert (which Tor onion address pins to pubkey) 20:05:44 Rucknium: yes i know 20:05:52 but the IP address thing is what i'm talking about 20:06:03 you can match subscribers up to the TXIDs they sent 20:08:53 IIRC RavFX switched his Monero nodes to use SSL only. 20:30:21 DataHoarder: is it okay to "encrypt" the spend and view key using a XOR cipher? 20:30:38 XORing the keys with hash function outputs 20:30:42 xor cipher means nothing 20:30:53 don't invent own crypto please 20:31:28 Crypto is one of the only space where the NIH syndrome is the worst thing ever 20:32:50 you can store spend/view key encrypted properly, and pubs in the open (it's the main address on legacy wallets) 20:33:01 encrypted properly requires space for the nonce 20:33:05 and other cipher stuff 20:33:05 yes 20:33:13 you can use pubkey as nonce 20:33:41 they can be verified. but straight hashing or password schemes you think of just ad more issues in the future 20:34:07 i figured not adding a MAC either 20:34:23 just verifying the decryption by multiplying the private key by the basepoint and comparing public keys 20:34:33 derive key using PBKDF2 20:34:51 i was thinking of argon2é 20:34:51 then encrypt with a nonce (which might as well be the pubkey) 20:34:53 argon2* 20:34:55 but sure 20:35:03 argon2 is a function 20:35:07 PBKDF2 is a method to use the function 20:35:24 argon2 here being the PRF part 20:35:33 i see 20:35:41 if you didn't have a nonce 20:35:54 someone can build a rainbow table 20:35:58 either for the bruteforce or encryption 20:36:20 nonce for the hash function? 20:36:24 i mean key derivation function 20:36:51 kdf 20:36:57 the key is unlikely to be used more than once for encryption tbh 20:37:04 so i don't need nonce in the encryption algorithm 20:37:12 someone will use password2 as password 20:37:43 yes, but i meant the derived key 20:38:01 which will have nonce applied 20:38:13 But yeah, if you can have the nonce on the kdf that should be relatively ok. You also want a scheme that has them do the full derivation to check, not fast checks where only partial outputs can be extra ted 20:38:24 Extracted* 20:38:41 For example if you used raw SHA3 you can skip some sponge extraction steps to do quick 64-bit checks 20:38:55 i want to save as much space as i can 20:41:51 Also think about: what if the pubkey has been lost :) 20:42:14 You want to save space at the cost of future usability or adding custom complexity 20:42:37 Tbh. Have the spend key be sealed inside a fold 20:42:59 doesn't an address have both public keys serialized in it? 20:43:51 * nioc watches as Cindy becomes a cryptographer 20:45:41 i wanted the gift wallet to take up 1/4 of an A4 paper, but after seeing how massive the QR code was, and how unrealistic it would be to expect most consumer printers to have the amount of DPI required to print it out without ruining the code 20:45:52 i had the QR code take up like 2/4 of the paper 20:46:04 below the whole info above 20:48:04 lemme upload something rq 20:49:06 https://0x0.st/P8si.png 20:49:17 this is the whole A4 paper lol 20:49:34 (also yes, placeholder QR code, but an actual one is much much larger) 20:50:53 21:42:59 doesn't an address have both public keys serialized in it? 20:50:55 yes 20:51:23 the QR code can be smaller 20:51:25 you can also have it within the layout 20:51:53 just think in bytes if you are encoding raw stuff 20:52:01 i'm encoding a whole URI 20:52:13 containing 1) address, keys, TXIDs 20:52:27 i mean address and keys already make the QR code massive, like version 18 or something 20:52:38 TXIDs would push it to version 25 20:52:52 split it on multiple, too 20:53:00 you can do multi qr encoding 20:53:05 this is with high error correction btw 20:53:08 oh really? 20:53:14 and as said, txids are not needed 20:53:35 you only need the global output index/amount which amount = 0 on all relevant recent hardforks 20:53:53 global output index is an uint64, which gets varint encoded to be much smaller 20:54:07 they are at like 147053899 atm 20:54:51 does the URI allow encoding global output index 20:54:53 with these values you can make RPC calls to get the specific transaction outputs (txid : local output id tuples) 20:55:01 the standard doesn't 20:55:02 I have no idea about what URL you are targeting 20:55:06 monero-wallet URI 20:55:19 https://github.com/monero-project/monero/wiki/URI-Formatting 20:55:36 it only lets you encode either the block height or list of TXIDs 20:55:40 https://github.com/monero-project/monero/wiki/URI-Formatting#wallet-definition-scheme 20:55:52 why are you encoding txid here 20:55:54 yes that 20:55:54 this is to generate the wallet restore height 20:55:58 you can pass a height instead 20:56:06 or leave empty to scan since monero inception 20:56:15 to make it much faster to scan 20:56:26 this is not to scan specific txids 20:56:28 yes, then you just pass an integer as height 20:56:36 txid will just lookup which height that tx was included as part of 20:57:04 did you misunderstand the meaning of that field? 20:57:23 i thought it would lookup each of the TXIDs and then scan the blocks they belong to 20:57:59 nope 20:58:23 wait 20:58:25 it does 20:58:27 "Absence of height" 20:58:32 it was me all along who didn't read 20:58:33 ha 20:58:34 you see 20:58:36 i knew it :D 20:58:40 tbh 20:58:46 it would be dumb to implement it if it didn't do that 20:59:00 just set height to the first tx 20:59:09 yeah this QR would be massive 20:59:30 dedicate an entire A4 for it :) 20:59:34 you also want to be able to support depositing? 20:59:44 if so, just setting the initial creation height works well 21:00:21 i mean, setting the height would make it waste more bandwidth searching from the creation of the gift wallet to the current block height 21:00:29 before it can send anything 21:00:37 that ain't fast 21:00:55 if you constraint to a single txid maybe 21:01:08 but realistically this would be a multipart qr 21:01:12 where you scan wallet details 21:01:27 then txid sets to scan 21:01:29 but ofc. not standard 21:01:58 at that point just encode this onto some NFC chip tbh 21:02:16 you can find 1K/4K ones cheap enough as stickers 21:02:31 then duplicate of the wallet restore (As fallback) without txids 21:02:41 phones can just tap/scan this 21:02:51 hmmm 21:02:58 and there are standards to resolve them as urls automatically 21:03:09 you can even write to them with phones too 21:03:23 but will it be as easy as printing 21:04:00 you can support multiple features Cindy 21:04:05 specially with txids being dynamic 21:04:14 you can always re-scan /write the nfc with more txids 21:04:21 sometimes there are issues with the exact restore height, I believe it is better if you set the restore height some small # of blocks b4 21:04:27 and leave the permanent one with just restore height 21:04:29 indeed nioc 21:04:41 I tend to set it to a week before :')