Hey guys! Did not see any outright "Stay away" warning for guys like me in the repo docs. So..

Any plans on moving (partially) to Rust? Can we make contributions with parts in Rust (including updating the build system ofc)

There is a community supported daemon implementation written in Rust: cuprate.org

As for core: a proposed network upgrade (FCMP++) will add Rust for new cryptography. It has not been decided yet which, if any, other parts of the codebase should oxidize.

Oh damn!! Missed that in the FCMP flood of changes. Thanks!

And can it be recommended to run the curate.org daemon for your own full node? I know Bitcoing core also has a Rust implementation but they have a strong warning to not use it beyond experimentation as they don't want even the tiniest deviations from the consensus rule.

<boog900> we haven't released wallet/RPC support yet

<boog900> also it is in alpha so no you should depend on it yet for anything of value

.merge+ 10786 10788 10772 10773 10775 10776 10768 10769

Added

.merges

10768 10769 10788

<jpk68:matrix.org> selsta: I agree with ofrn that the copyright date should just be 2025

if you touched the file in 2026 it can be 2025 - 2026

<jpk68:matrix.org> Alright, fixed

<tobtoht> I really wish we would just remove the copyright year from the headers. It is needless maintenance.

<tobtoht> monero-project/monero #9666

<tobtoht> (Not relevant for this PR)

<jpk68:matrix.org> Bitcoin Core just does, for example, Copyright (c) 2009-present The Bitcoin Core developers

<ofrnxmr:xmr.mx> monero-project/monero #9666#issuecomment-2659406539

<jpk68:matrix.org> Just to play devil's advocate, it could be possible to remove the full license text as well. Imagine we were licensed under GPLv3 and had to include the full thing in every file, lol

<ofrnxmr:xmr.mx> id be in favor of not adding the license text to your current pr

<jpk68:matrix.org> I guess that was suggested in the comment you linked to anyways

<jpk68:matrix.org> I can submit one changing all of the files /s

<ofrnxmr:xmr.mx> github.com/google/leveldb/blob/main/db/db_test.cc#L1

<tobtoht> "All rights reserved" is archaic.

<ofrnxmr:xmr.mx> alternative it to just have the year of file creation, like leveldb > <@tobtoht> I really wish we would just remove the copyright year from the headers. It is needless maintenance.

<tobtoht> I'm fine with that too.

<jpk68:matrix.org> In any case, such a shift from convention would be better suited for a different patch, IMO

<jpk68:matrix.org> I think 2025-2026 is good for now

<tobtoht> I used SPDX for Feather, like the Linux kernel:

<tobtoht> // SPDX-License-Identifier: BSD-3-Clause

<tobtoht> // SPDX-FileCopyrightText: The Monero Project

<jpk68:matrix.org> That would be a bit more difficult in files where attribution is given to CryptoNote, Boolberry, etc.

<jpk68:matrix.org> Sorry, I meant to phrase that as a question

<tobtoht> You could just another line or SPDX tag.

<tobtoht> Meh, SPDX is too verbose. I think I prefer a variation from monero-project/monero #9666#issuecomment-2659650854 with or without creation year.

<tobtoht> Thing is, if you keep the creation year you'll get people trying to update it.

<jpk68:matrix.org> My two cents is that I agree with iamamyth in the first one being the best

<jpk68:matrix.org> Though it would be nice to have 2014-present or something as the year

<jpk68:matrix.org> Example with multiple people (tor_address.cpp): paste.debian.net/hidden/def4e083

<tobtoht> Are we still fresh and juicy? monero-project/monero 84ca73e

<tobtoht> Anyways

<tobtoht> @jpk68:matrix.org: That's fine with me tbh

<tobtoht> My preference is: no year > <creation>-present > <creation> (but I'm fine with whatever we can agree to)

<tobtoht> As long as it doesn't involve updating the headers on every edit or every year.

.merge+ 10781 10785

Added

tobtoht regarding 10781 if you want to wait until jberman adds more info it's also fine since rbrunner also wanted to review it

I'll give jberman a chance to respond and rbrunner a chance to review ^^