Tracking Issue for `cuprated 0.0.2 Molybdenite` release

[hinto-janai]

About tracking issues

Tracking issues are used to record the overall progress of implementation.
They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions.
A tracking issue is however not meant for large scale discussion, questions, or bug reports about a feature.
Instead, open a dedicated issue for the specific matter.

What

This is a tracking issue for the cuprated 0.0.2 Molybdenite release.

Steps

• Changelog
  • Relevant changes added to misc/changelogs/cuprated/$VERSION.md: cuprated: v0.0.2 version + changelog #413
• Fast sync
  • Update hashes, see misc/FAST_SYNC_HASHES.md: cuprated: fast_sync_hashes.bin -> 3384832 #427
• User Book
  • Update necessary documentation: books: user-book for cuprated 0.0.2 #402
  • Book title reflects cuprated's version
• cuprated
  • Killswitch timestamp updated: cuprated: update killswitch timestamp for v0.0.2 #403
• Repository
  • Decide specific commit: 95aca1d
  • Create draft release
  • Create version tag
  • Build CI binaries: https://github.com/Cuprate/cuprate/actions/runs/14360523317/job/40260566103
• cuprated testing
  • Full-sync from scratch
    • x64 Linux
    • ARM64 macOS
    • ARM64 Linux
• Release
  • Add binaries to release
  • Publish Cuprate/user-book: https://github.com/Cuprate/user-book/actions/runs/14366006078
  • Release: https://github.com/Cuprate/cuprate/releases/tag/cuprated-0.0.2
• Release announcements
  • Reddit: https://www.reddit.com/r/Monero/comments/1jvfrgl/cuprate_v002_released/
  • Matrix

Related

• https://github.com/Cuprate/cuprate/milestone/2