09:19:48 <Halver[m]> spirobel:... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/a9337403e94ba9ebe43fcdbc5230a7f2bda95333)
10:34:47 <lockhead[m]> https://github.com/monero-project/monero/blob/dcba757dd283a3396120f0df90fe746e3ec02292/contrib/epee/include/net/smtp.h why is this in here?
10:39:46 <moneromooo> No particular reason beyond it being in the original source.
11:41:44 <spirobel[m]> > <@hoverhalver:monero.social> spirobel:... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/cc840392a7d7f5e2b2aa5ed082b86b65bb04b373)
11:43:36 <spirobel[m]> <lockhead[m]> "https://github.com/monero-..." <- damn email is everywhere...should rather focus on getting rid of emails instead :D
11:50:45 <spirobel[m]> > <@hoverhalver:monero.social> spirobel:... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/bd3ec9724ad28f7d18f416fb50a82fe83970eb5b)
12:41:28 <rbrunner> Is there an easy trick to get the CLI wallet to log to console as well as to file, like the daemon does, or would that need a small code modification?
12:41:59 <moneromooo> Toggle the bool in the mlog_init startup call IIRC.
14:01:52 <lockhead[m]> <spirobel[m]> "damn email is everywhere......" <- it's not even used anywhere that's why I'm confused lmao
14:06:18 <Halver[m]> If it is not used anywhere, neither intended to be, then a PR to remove it would probably be welcome.
14:06:18 <Halver[m]> At least it would help to see if it is needed somewhere ?
14:17:17 <reeemuru[m]> <spirobel[m]> "> <@hoverhalver:monero.social..." <- https://github.com/joule-labs/joule-extension is lightning wallet browser extension I used to work on. It could be forked to integrate with monero-wallet-rpc.
14:29:43 <spirobel[m]> wow cool.  I dont know much about lightning. I will look into it. I also thought about reading more of the metamask source code and the web3.js stuff. super interesting. 
14:38:08 <spirobel[m]> But their licence seems kind of funny haha https://medium.com/metamask/evolving-our-license-for-the-next-wave-of-metamask-users-81b0b494c09a dont know how to feel about that...but you gotta make money somehow i guess
14:41:11 <reeemuru[m]> spirobel[m]: oh yikes. i do remember hearing about that. not to difficult to build something from scratch i guess
14:43:07 <spirobel[m]> reeemuru[m]: i just looked at the apireference of webln that is used in joule. https://webln.dev/#/api/request-provider it seems clean in comparison to wallet rpc or etherum api.
14:43:48 <spirobel[m]> how long did it take you to build joule? 
14:46:01 <reeemuru[m]> I didn't build it. Just helped out. I think it took Will a few weeks to put together the meat of the project
14:50:45 <spirobel[m]> reeemuru[m]: cool. seems like a manageable timeframe.
16:15:35 <rbrunner> I don't get the basic idea / approach of the 'blocks_ids' input parameter of the /getblocks.bin daemon RPC call.
16:16:05 <rbrunner> Do I as the caller tell the daemon "I know already about these blocks, no need to return them to me (again)"?
16:16:26 <rbrunner> If yes, what is this: first 10 blocks id goes sequential, next goes in pow(2,n) offset, like 2, 4, 8, 16, 32, 64 and so on, and the last one is always genesis block
16:17:08 <rbrunner> Really no idea why the genesis block should be in there at all :)
16:20:16 <wfaressuissia> "https://github.com/monero-project/monero/blob/master/src/cryptonote_protocol/cryptonote_protocol_defs.h#L278" it's copy-paste from here; that rpc call is a combination of NOTIFY_REQUEST_CHAIN + NOTIFY_REQUEST_GET_OBJECTS from p2p: client puts sparsely selected hashes of known blockchain and daemon finds fork point and picks K next blocks and returns them
16:24:02 <wfaressuissia> did it help ?
16:24:29 <rbrunner> Thanks. Unfortunately this only deepens the riddle for me: What is a fork point? And what does this protect against, after all? Why is it useful?
16:26:25 <rbrunner> Or, in other words, why does 'wallet2' not simply tell: "Dear daemon, give the me new blocks starting from height x". All because of the possibility of reorgs? Even large ones?
16:28:26 <moneromooo> Because there can be multiple blocks at a given height.
16:28:35 <rbrunner> By the way, I try to take a shot at this here: https://github.com/monero-project/monero/issues/7571
16:28:51 <moneromooo> This list allows the daemon to find where the local chain and the wallet chain connect.
16:29:59 <rbrunner> You mean how far the cached "assumptions" of the wallet about the chain are correct?
18:22:59 <sgp_[m]> when is the next meeting
18:23:10 <sgp_[m]> in MRL, there was a discussion that there's a good chance Monero transactions are being spammed
18:23:11 <sgp_[m]> so it would be very important to get on the [ BP+ / ringsize ^ / base fee ^ ] upgrade
18:50:43 <zwischenzug> Hello, I'm trying to implement the Levin protocol in golang.  Looks like message payloads are serialized with a special Boost binary format.  Anyone know if there's an official "Boost binary serialization" spec anywhere?
18:51:26 <moneromooo> It is not boost. It uses the src/serialization code.
18:52:08 <moneromooo> er, actually...
18:52:30 <moneromooo> It uses the key value format in contrib/epee/include.
18:52:50 <moneromooo> Though some of the payload (txes, blocks) use the src/serialization code.
18:53:34 <moneromooo> Out of curiosity, did you already code some of it and try it on mainnet ?
18:54:06 <moneromooo> Someone messed up and included more than one identical field in a key/value packet ^_^
19:00:19 <zwischenzug> Working off stagenet, but yea, I'm able to decode a Handshake message (mostly working off this code: https://github.com/sanderfoobar/py-levin)
19:29:16 <wfaressuissia> zwischenzug_: why do you need it ?
19:32:47 <wfaressuissia> zwischenzug_, "https://github.com/cirocosta/go-monero/blob/master/pkg/levin/portable_storage.go" I don't know how it will treat DoS packet, but it looks like a try to implement levin in go
19:37:15 <zwischenzug_> Just for fun :)
19:46:02 <wfaressuissia> "https://github.com/m2049r/xmrwallet/blob/master/app/src/main/java/com/m2049r/levin/data/Bucket.java", hmm, how much ram would it allocate for that DoS packet ?
20:06:17 <utxobr[m]> that’s how i crawl the net (clearnet & tor)
20:06:27 <utxobr[m]> could profile it’s memory usage
20:06:37 <utxobr[m]> its*
20:07:32 <utxobr[m]> (bad code tbh, just did enough to work)
23:09:54 <jerfo> Howdy! I can't tell if I'm stupid, or it --rpc-access-control-origins doesn't work. I submitted an issue: https://github.com/monero-project/monero/issues/7951 cause the option didn't seem to do anything, but my monerod didn't give me an eror or warning or anything 
23:51:18 <moneromooo> vtnerd: I think that's yours ? Or woodser, I forget.