## Meeting logs ``` boog900: 1) greetings ``` ``` syntheticbird: Hello ``` ``` shortwavesurfer2009: 🌊 ``` ``` rucknium: Hi ``` ``` boog900: 2) updates ``` ``` boog900: I have been getting the tree code ready to PR. Also been benching against before the tree and monerod ``` ``` syntheticbird: me: RPC pt.3 on rate limiting is now ready. Released Cuprate's first technical blog on RPC and monero HTTP stack. Hopefully there will be more. ``` ``` boog900: I managed to get syncing to around the same speed as before the tree ``` ``` boog900: 3) Project: What is next for Cuprate? ``` ``` boog900: I will make the first PR today it will contain just the pedersen hashing code and the tree database ``` ``` syntheticbird: you want to merge fcmp++ for 0.2.0 ? ``` ``` syntheticbird: tree code i mean ``` ``` boog900: Then the next will be the blockchain database changes. The third and final PR will be the tree task manager in cuprated ``` ``` boog900: > <@syntheticbird:monero.social> you want to merge fcmp++ for 0.2.0 ? I think we might as well merge it now ``` ``` boog900: Better than maintaining multiple different branches ``` ``` syntheticbird: sure ``` ``` syntheticbird: but do you wanna like lock 0.2.0 release on the three PR being merged ? ``` ``` boog900: Nah ``` ``` syntheticbird: ok ``` ``` syntheticbird: I would be tempted to say "will review soon" as usual, but usually everytime I say it I don't review it anytime soon. So I just won't say it in the hope that this will make review it soon ``` ``` boog900: The first PR will be easy I think, if you just trust the crypto code is correct :) ``` ``` boog900: I tried to make the code as clear as possible but you will still need to know what it is even trying to do ``` ``` syntheticbird: duly noted ``` ``` boog900: The second will be the hardest probably the database changes has been annoying ``` ``` syntheticbird: database has always be annoying so at least there is no surprise ``` ``` boog900: Anything else to discuss today? ``` ``` syntheticbird: yes ``` ``` syntheticbird: I want to add a new easter egg to Cuprate. But I want to call public for communicating their ideas ``` ``` syntheticbird: cuprate website ``` ``` syntheticbird: fine w/ it? ``` ``` boog900: I mean that won't make it an easter egg right? ``` ``` syntheticbird: no they'll share it to me privately ``` ``` syntheticbird: so it wont be a secret for me, the person that won and whoever is reviewing the PR ``` ``` boog900: You can do it personally if you want to. ``` ``` syntheticbird: ok ``` ``` boog900: Anything anything else to discuss today? ``` ``` rucknium: Is there an expected timeline for when it would be safe to use cuprate as a reliable public RPC node for wallet syncing and tx construction/broadcast? ``` ``` syntheticbird: i saw shortwavesurfer writing ``` ``` shortwavesurfer2009: I submitted a few small PRs. Building instructions for NixOS, a default.nix one command build and submitted a package request to nixpkgs repo ``` ``` syntheticbird: whenever RPC pt.3 and pt.4 are merged + tx relay bug found and fixed. ``` ``` boog900: > <@rucknium:monero.social> Is there an expected timeline for when it would be safe to use cuprate as a reliable public RPC node for wallet syncing and tx construction/broadcast? Next release will be a lot more secure than the current one ``` ``` syntheticbird: thanks shortwavesurfer for it. ``` ``` boog900: However until 1.0 I would still not recommend relying on for anything of significant value ``` ``` boog900: > <@shortwavesurfer2009:monero.social> I submitted a few small PRs. > Building instructions for NixOS, a default.nix one command build and submitted a package request to nixpkgs repo Thanks ``` ``` boog900: * However until 1.0 I would still not recommend relying on Cuprate for anything of significant value ``` ``` rucknium: OK. I run a public node that's in the Feather Wallet list of nodes. Thinking about that one. ``` ``` syntheticbird: yeah I'm more than confident for public node adoption but it should be labelled as experimental ``` ``` rucknium: Are there stricter timeouts than monerod in the p2p code by the way? ``` ``` syntheticbird: Yes ``` ``` syntheticbird: see latest blog post I talked a bit about the default timeouts in Cuprate and cited the ones in monerod ``` ``` rucknium: I may want to relax them for my/our network scanner code. ``` ``` boog900: > <@rucknium:monero.social> OK. I run a public node that's in the Feather Wallet list of nodes. Thinking about that one. If you run you could monitor both to make sure they agree on consensus ``` ``` syntheticbird: Some are configurable. You'll have to check RPC Hardening pt.2 changes to be sure ``` ``` boog900: * If you run both you could monitor both to make sure they agree on consensus ``` ``` syntheticbird: based idea ``` ``` rucknium: Bitcoin Cash has an umbrella software that monitors different node implementations and tries to resolve any chain discrepancies, AFAIK. Chaingraph it's called, I think. ``` ``` syntheticbird: https://github.com/bitauth/chaingraph ``` ``` syntheticbird: \>typescript ``` ``` boog900: Yeah I think something like that for monero would be good ``` ``` syntheticbird: great idea, bad language. but still great idea ``` ``` syntheticbird: I've the impression a lot of idea will be free to come to life once FCMP++ reaches mainnet ``` ``` rucknium: Not sure if it's rude to ask this, but here goes. Did this really come from bird's grey matter? https://cuprate.org/blog/turns-out-it-is-hard-to-secure-a-web-server/ ``` ``` syntheticbird: just because I act like an idiot you thought i was an idiot? ``` ``` syntheticbird: understandable opinion lol ``` ``` rucknium: No. The writing style is very different. ``` ``` boog900: > <@syntheticbird:monero.social> I've the impression a lot of idea will be free to come to life once FCMP++ reaches mainnet Yeah a lot of dev time being spent on that ATM :) ``` ``` syntheticbird: very different? compared to who/what? ``` ``` syntheticbird: I wrote everything myself and use an LLM for spelling mistakes or weird proses if that is your question ``` ``` rucknium: Yes that's my question. Thanks. ``` ``` rucknium: Very good post. ``` ``` syntheticbird: thanks ``` ``` shortwavesurfer2009: Will the RPC hardening and timeouts negatively affect wallets syncing over Tor? I always sync over a tor hidden service and offer it for others to use as well. ``` ``` syntheticbird: maybe the basic stream timeouts will be a problem if you hit a very bad circuit. but I doubt the rest will cause any issue. ``` ``` boog900: Anything else for today? ``` ``` syntheticbird: be just sure to exclude localhost or your daemon ip in case you are using multiple wallets ``` ``` syntheticbird: because Cuprate will not make a difference in terms of rate limiting since they don't see which connection is which circuits ``` ``` syntheticbird: everything will come from the IP of your tor daemon. ``` ``` syntheticbird: or otherwise just increase the rate limiting budget and income to an unreasonable amount, also an option ``` ``` syntheticbird: nothing else to discuss for me ``` ``` boog900: I think we can here ``` ``` boog900: Thanks everyone ``` ``` syntheticbird: thanks ``` ``` boog900: !meeting ```