can someone review monero-project/monero #10086 ? it's a small change

<j​effro256:monero.social> Done. Seems reasonable, especially with FCMP++ upcoming

ty, please also review monero-project/monero #10106 - i updated checkpoints

and the corresponding monero-project/monero #10107

<o​frnxmr:monero.social> monero-project/monero #10083 this too plz

somebody asking if we can update the blockchain .raw on getmonero.org (nearly 5yr old...). I think nowadays importing the .raw is not faster than syncing from scratch. Do I remember well?

not #10149 selsta?

DataHoarder: i plan to include it

I checked the checklist, I guess not updated

will add it

ok so one more review for 10083 and we have everything

<o​frnxmr:xmr.mx> bF, we removed reference to blockchain.raw from the website. Chatgpt is annoying

<o​frnxmr:xmr.mx> importing the raw is probably only faster if you do the "dangerous unverified import". Id argue we should remove the raw file itself from the servers

<o​frnxmr:xmr.mx> If ppl want to share dbs, they should create a torrent or something

<b​asses:matrix.org> this is a terrible idea

<b​asses:matrix.org> the highest seed will be for the first version, people will always download the oldest one or take century to download the new one with little to no seeders

<o​frnxmr:xmr.mx> Its about as terrible as using a raw from 2019

mmm I wonder where they got the idea then. Possibly chatgpt yes.

<b​asses:matrix.org> update the raw

<o​frnxmr:xmr.mx> No.

<o​frnxmr:xmr.mx> bF, likely yeah

"wget downloads.getmonero.org/blockchain.raw" :D

docs.getmonero.org/interacting/monero-blockchain-import-reference still has the link too, but there is a disclaimer at the top

the AI will ignore the disclaimer

maybe we rename the file to blockchain-very-very-slow-to-import-dont-do-this.raw

<m​ichaelten:matrix.org> has there been any discussion how to modify Monero XMR protocol to stop or prevent or disincentivize botnets?

<o​frnxmr:xmr.mx> are you the same person from github

<o​frnxmr:xmr.mx> #monero:monero.social #monero

<m​ichaelten:matrix.org> Yesssir (or maaaaam)

<m​ichaelten:matrix.org> monero-project/monero #10145

<o​frnxmr:monero.social> There are plenty of mitigations being investigated, some old, some new, none in production. you can research most of them on the monero-research-lab github issues

<o​frnxmr:monero.social> nore: the mrl is for technical discussion

<m​ichaelten:matrix.org> Good to know . Thanks. I wonder if they don't realize that where I posted on github

<o​frnxmr:xmr.mx> dont post "whatsup guys" on mrl

<o​frnxmr:xmr.mx> mrl issues are for technical proposals, and monero issues are for issues with the software

<o​frnxmr:xmr.mx> Your github issue was a hollow, general question, that fits in [#monero:monero.social](https://matrix.to/#/%23monero:monero.social) . Its not technical, not an actionable proposal, and not a bug. Github isnt for casual discussions

<m​ichaelten:matrix.org> The answers could be technical

<m​ichaelten:matrix.org> Hollow is a subjective value judgment imo

<m​ichaelten:matrix.org> It could be actionable if there is a potential solution

<m​ichaelten:matrix.org> But yes .. not an actual bug that I am aware of. Correct

I'm not aware of any suggestions to mitigate disincentivize botnets apart from increasing the amount of RAM required to mine, in general if you can run it on your home computer some botnet will also be able to run it

<o​frnxmr:xmr.mx> monero-project/research-lab #98 stuff like this @selsta

couldn't they just solo mine or use p2pool in this case?

<o​frnxmr:xmr.mx> monero-project/research-lab #98#issuecomment-3201604983

.merge+ 10150 10149 10148 10147 10146 10125 #10109 #10086 10107 10106

Added

.merges

v0.18.4.3 has been tagged