In C++, you can override default "new/delete/new[]/delete[]" operators which std::allocator uses

<l​m:matrix.baermail.fr> Is it known that on Windows the size of the DB reported by "get_info" is always 0 ?

<l​m:matrix.baermail.fr> monero-project/monero #9513

Just to make sure, this node isn't in restricted mode, right ?

If it is not, then AFAIK it is not known.

<l​m:matrix.baermail.fr> to make it restricted you must pass the --restricted-rpc arg, right ?

<l​m:matrix.baermail.fr> The issue appears without any args.

<j​effro256:monero.social> Pushed a PR that may or may not help

<j​effro256:monero.social> monero-project/monero #9514

I'm working on an application that I wish to integrate Monero to. But I'm struggling to understand how one can go about it. As far as I understand there are two ways: 1) Assume that the user has installed the monero daemon and make requests to that daeomon from the application, and 2) re-implement the Monero wallet in my own application. Is this correct or is there something I'm missing?

<s​yntheticbird:monero.social> It highly depends what are your needs. Wallet and Nodes are two distinct things. I'm more inclined to believe you want to integrate monero transaction processing/wallet

<j​effro256:monero.social> Yeah what are you actually trying to do?

I only need the wallet functionality, e.g. view balance, send coins to someone, create/destroy wallets, etc.

<s​yntheticbird:monero.social> Then you have two options:

<s​yntheticbird:monero.social> 1. Make a fully fledged wallet in your application that implements tx scanning and all the logic behind. It will need to communicate to a monero daemon (aka monerod node aka monerod). This is hard.

<s​yntheticbird:monero.social> 2. Make use of monero-wallet-rpc. Which is basically a wallet daemon which you can communicate with through JSON-RPC.

If I go with 2), is it better security-wise to ship the monero-wallet-rpc alongside my app, or tell the user to install it themselves? (assume that the user is capable of installing it themselves)

1 is not hard if you just use wallet2.

(which does all that tx scanning logic already)

Also if I'm not mistaken, I will have to implement the atomic swaps myself, as the RPC has no such calls

<s​yntheticbird:monero.social> moneromooo is right but just to be sure. what are you trying to do ***exactly*** ?

<j​effro256:monero.social> If you want atomic swap code for Monero, look at the Farcaster project or COMIT project

I got inspired by Mozilla Hubs and wanted to create a similar application where users can receive/send XMR

But in C++ (as opposed to Hubs, which runs on a browser, I think)

j​effro256: invited you to an h1 issue, not sure how valid it is

<s​yntheticbird:monero.social> zamn. how many vulns are still hiding

<s​yntheticbird:monero.social> btw how can we see on github pulls that resolved vulnerabilities?

<j​effro256:monero.social> selsta: seems like a duplicate of an issue already in their other report, no?

i'm not really sure what they are reporting

<j​effro256:monero.social> Maybe 0xfffc could make an flair for resolved vuln

<s​yntheticbird:monero.social> That would be very cool

<j​effro256:monero.social> Obviously, depending on the nature of the vulnerability, some fixes aren't going to be publicly flagged before merge and release

<s​yntheticbird:monero.social> Seems fair enough.