08:54:47 Title: About supply auditability 08:54:47 Link: https://getmonero.org/2020/01/17/auditability.html 10:58:11 is getmonero.org down for anyone else? i just get the message "error code: 1010" 10:58:28 ah, apex domain is borked but www. is ok 11:38:53 Asymptotically: The website just got updated. Could be a temporary issue related to that 11:39:43 ErCiccione[m]: yep looks like it, working fine for just getmonero.org now :) 14:27:03 hello 14:32:29 hi raivavae83 15:16:25 hi 15:17:24 mapuche, hello 15:28:25 Hi 19:08:26 hello 19:08:50 hello 19:08:50 wazzuppp. 19:08:50 biicoonneeeeeee 19:08:54 lol. 22:35:32 is there a way to prune xmr address to fit into 80 bytes? maybe remove checksums? 22:38:02 afaik it's 95 bytes but I'm working on an alias scheme. so far would need 2 btc transactions to fit xmr address into op_return or could put address onto ipfs 22:40:33 oh maybe it's less bytes in base58 nvm 22:45:17 stargatesg5: you can fit it in 64 bytes. 32 for the public spend key, and 32 for the public view key 22:45:42 see https://xmr.llcoins.net/addresstests.html for a little explanation 22:46:23 yeah, I facepalmed when I realized I don't need to use the entire utf8 space >< 22:48:54 I'm getting 70 bytes with basic address. Looks like I'll have to read the link :) 22:53:32 69 bytes for address, 1 byte (network) prunable, 32 bytes spendkey keep, 32 bytes viewkey keep, 4 bytes checksum prunable. I guess have to figure out how to do checksum myself or now that it fits into op_return 80 bytes don't really need to. neat 22:53:57 I wonder why I get 70 bytes with this node code: const bs58 = require('bs58'); 22:56:13 hmmm i would have thought that you'd get 69 bytes 22:56:34 can you compare against the output on the website above? 23:03:16 yeah it's weird, extra byte and different hex... not good lol 23:03:18 https://repl.it/repls/ReflectingOvalMarkuplanguage 23:03:35 is base58 encoding same as bitcoin? 23:04:32 nope. the monero base58 encoding happens in blocks 23:04:58 oh. interesting. same characters though? 23:05:48 as long as I can recover the real xmr address again from byte data, no big deal 23:05:59 view-source on that page and have a look at base58.js :D 23:06:04 and yes i think that the alphabet is the same 23:07:18 don't use the bitcoin one, bad things might happen 23:07:48 ok, i'll check out the base58 library just to be safe 23:09:17 oh you meant js file on xmr site. i wonder if I can use that directly 23:14:21 I don't really understand licensing in software and If i'm allowed to copy/paste that js file if I cite where it's from 23:21:02 if software has no license at all, you can't do anything (all rights reserved). the license is what gives you permission to do things 23:21:03 nvm found a library, gonna skip the source and should be good then. thanks again. https://www.npmjs.com/package/@xmr-core/xmr-b58 23:21:24 ah haha. never knew that 23:21:27 was just about to link that. i think it's the same, that they both come from mymonero 23:22:54 thanks again, might've helped me avoid a gotcha moment there, didn't see anything wrong with 10 addresses I tried with bitcoin encoding but you never know. 23:23:50 working on name system on bitcoin, very early stages, just fake satoshi alias at the moment on testnet to show https://ildarmgt.github.io/BitcoinNameSystem/#/id/satoshi 23:24:55 xmr addresses compatibility would be nice way to give aliases that don't reveal your spending patterns publicly 23:27:51 you can do stealth addresses with btc too 23:27:57 yeah bip47 23:28:00 already know those fit 23:29:32 ah i was thinking of something else called sx (i think) 23:30:27 https://en.bitcoin.it/w/index.php?title=Sx/Stealth&oldid=43757 23:30:31 ah interesting. I know samourai has the paynym thing that uses bip47 payment codes. the padding of 0's at end helps fit them for now. I'll look into sx 23:30:42 it's dead, so don't look into it too hard :( 23:31:49 it looks very similar with a secret and notification requirement of 47, but it's a bit complex hence only 1 wallet support atm