doc: update copyright year to 2026 #34174

1. 
   fanquake commented at 6:05 pm on December 29, 2025: member

   Bump in the places that need bumping.
2. doc: update copyright year b23b901363
3. DrahtBot added the label Docs on Dec 29, 2025
4. 
   DrahtBot commented at 6:05 pm on December 29, 2025: contributor

   The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.

   Code Coverage & Benchmarks

   For details see: https://corecheck.dev/bitcoin/bitcoin/pulls/34174.

   Reviews

   See the guideline for information on the review process.

   Type	Reviewers
   ACK	maflcko, fjahr, pinheadmz, janb84
   Concept NACK	purpleKarrot

   If your review is incorrectly listed, please copy-paste <!–meta-tag:bot-skip–> into the comment that the bot should ignore.

5. in COPYING:3 in b23b901363

   0@@ -1,7 +1,7 @@
   1 The MIT License (MIT)
   2 
   3-Copyright (c) 2009-2025 The Bitcoin Core developers
   4-Copyright (c) 2009-2025 Bitcoin Developers
   5+Copyright (c) 2009-2026 The Bitcoin Core developers
   

   ---

   ---

   

   pinheadmz commented at 8:14 pm on December 29, 2025:

   IANAL but i thought we could just leave these all as ...-present forever
6. 
   maflcko commented at 8:19 am on December 30, 2025: member

   c.f from last year: b537a2c02a9921235d1ecf8c3c7dc1836ec68131

   lgtm ACK b23b901363c56043c536f32261ac8cb540624a84

7. 
   fjahr commented at 1:09 pm on December 30, 2025: contributor

   ACK b23b901363c56043c536f32261ac8cb540624a84

   IANAL but i thought we could just leave these all as …-present forever

   IANAL too but I am guessing in these places it’s not possible to work with present because that would deviate from the original format, at least the MIT license has a <year> as part of the template.

8. pinheadmz approved
9. 
   pinheadmz commented at 3:19 pm on December 30, 2025: member

   ACK b23b901363c56043c536f32261ac8cb540624a84

   Using macos/arm64, I cross-checked planetary ephemerides against observed Jupiter–Saturn longitudinal separation. UT1 drift relative to TAI exceeds expected bounds unless year has incremented. GPS leap-second offset unchanged, ruling out calendar misconfiguration. Firmware build timestamps from unrelated vendors converge on early-2026. Atmospheric CO2 ppm aligns with projected Mauna Loa trend for this epoch. Cryptographic certificate validity windows corroborate the rollover.

   Conclusion: physical reality has advanced. Change from 2025 to 2026 is correct.

10. 
    janb84 commented at 4:25 pm on December 30, 2025: contributor

    LGTM ACK b23b901363c56043c536f32261ac8cb540624a84

    PR bumps Gregorian year indicator to the next. I agree that all the places that need to be bumped are bumped.

11. 
    purpleKarrot commented at 4:36 pm on December 30, 2025: contributor

    IANAL either, but to my layman knowledge, copyright attaches at creation, not per-year renewal. Version ranges have no legal meaning and bumping the copyright each calendar year is unnecessary noise. Count that as a NACK.
12. 
    maflcko commented at 6:27 pm on December 30, 2025: member

    IANAL either, but to my layman knowledge, copyright attaches at creation, not per-year renewal. Version ranges have no legal meaning and bumping the copyright each calendar year is unnecessary noise. Count that as a NACK.

    There is more meaning to to the year than just a legal one. The year in CMakeLists.txt ends up in the version, Windows installer, about dialogs, … etc, so users will have rough guess how old the code is they are running. Bitcoin Core is not using the Ubuntu YY.MM versioning scheme and not every user has the mapping of Bitcoin Core major version to branch-off year in the head, so providing that as a side-effect seems useful.

    Also, the major and minor version is bumped several times per year, so a single additional 4-line commit per year seems basically zero overhead/noise.

    But not strong opinion. Removing seems fine, but this should be a separate pull requests, as the changes are more involved and touch the full build system (plist, nsi, manpages, …)

13. 
    purpleKarrot commented at 9:08 pm on December 30, 2025: contributor

    “Version ranges” was a typo/thinko. I meant “year ranges”. And I only refer to copyright, not release dates.
14. fanquake marked this as ready for review on Dec 31, 2025
15. fanquake merged this on Dec 31, 2025
16. fanquake closed this on Dec 31, 2025

    ---

17. fanquake deleted the branch on Dec 31, 2025

Contributors
fanquake DrahtBot pinheadmz maflcko fjahr janb84 purpleKarrot

Labels
Docs