spirobel:... (full message at libera.ems.host/_matrix/media/r0/do…403e94ba9ebe43fcdbc5230a7f2bda95333)

github.com/monero-project/monero/bl…292/contrib/epee/include/net/smtp.h why is this in here?

No particular reason beyond it being in the original source.

> <@hoverhalver:monero.social> spirobel:... (full message at libera.ems.host/_matrix/media/r0/do…392a7d7f5e2b2aa5ed082b86b65bb04b373)

<lockhead[m]> "github.com/monero-..." <- damn email is everywhere...should rather focus on getting rid of emails instead :D

> <@hoverhalver:monero.social> spirobel:... (full message at libera.ems.host/_matrix/media/r0/do…9724ad28f7d18f416fb50a82fe83970eb5b)

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?

Toggle the bool in the mlog_init startup call IIRC.

<spirobel[m]> "damn email is everywhere......" <- it's not even used anywhere that's why I'm confused lmao

If it is not used anywhere, neither intended to be, then a PR to remove it would probably be welcome.

At least it would help to see if it is needed somewhere ?

<spirobel[m]> "> <@hoverhalver:monero.social..." <- 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.

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.

But their licence seems kind of funny haha medium.com/metamask/evolving-our-li…wave-of-metamask-users-81b0b494c09a dont know how to feel about that...but you gotta make money somehow i guess

spirobel[m]: oh yikes. i do remember hearing about that. not to difficult to build something from scratch i guess

reeemuru[m]: i just looked at the apireference of webln that is used in joule. webln.dev/#/api/request-provider it seems clean in comparison to wallet rpc or etherum api.

how long did it take you to build joule?

I didn't build it. Just helped out. I think it took Will a few weeks to put together the meat of the project

reeemuru[m]: cool. seems like a manageable timeframe.

I don't get the basic idea / approach of the 'blocks_ids' input parameter of the /getblocks.bin daemon RPC call.

Do I as the caller tell the daemon "I know already about these blocks, no need to return them to me (again)"?

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

Really no idea why the genesis block should be in there at all :)

"github.com/monero-project/monero/bl…col/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

did it help ?

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?

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?

Because there can be multiple blocks at a given height.

By the way, I try to take a shot at this here: monero-project/monero #7571

This list allows the daemon to find where the local chain and the wallet chain connect.

You mean how far the cached "assumptions" of the wallet about the chain are correct?

when is the next meeting

in MRL, there was a discussion that there's a good chance Monero transactions are being spammed

so it would be very important to get on the [ BP+ / ringsize ^ / base fee ^ ] upgrade

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?

It is not boost. It uses the src/serialization code.

er, actually...

It uses the key value format in contrib/epee/include.

Though some of the payload (txes, blocks) use the src/serialization code.

Out of curiosity, did you already code some of it and try it on mainnet ?

Someone messed up and included more than one identical field in a key/value packet ^_^

Working off stagenet, but yea, I'm able to decode a Handshake message (mostly working off this code: github.com/sanderfoobar/py-levin)

zwischenzug_: why do you need it ?

zwischenzug_, "github.com/cirocosta/go-monero/blob…aster/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

Just for fun :)

"github.com/m2049r/xmrwallet/blob/ma…a/com/m2049r/levin/data/Bucket.java", hmm, how much ram would it allocate for that DoS packet ?

that’s how i crawl the net (clearnet & tor)

could profile it’s memory usage

its*

(bad code tbh, just did enough to work)

Howdy! I can't tell if I'm stupid, or it --rpc-access-control-origins doesn't work. I submitted an issue: monero-project/monero #7951 cause the option didn't seem to do anything, but my monerod didn't give me an eror or warning or anything

vtnerd: I think that's yours ? Or woodser, I forget.