Change v0.0.120 release name

[TheBlueMatt]

"Un"blinded makes more sense, since the fuzzer was unblinded :)

[coderabbitai]

Walkthrough

The recent update has renamed the version from "Blinded Fuzzers" to "Unblinded Fuzzers," suggesting a shift towards more transparent testing processes. Additionally, the update includes a significant architectural change by removing the PeerManager restriction on UtxoLookup, which may increase flexibility in how unspent transaction outputs (UTXOs) are queried and managed.

Changes

Files Changed	Summary of Changes
Various	Renamed version from "Blinded Fuzzers" to "Unblinded Fuzzers".
.../UtxoLookup related files	Removed the PeerManager bound on UtxoLookup.

Poem

In the realm of code, a change does sweep,
"Unblinded Fuzzers" now the leap.
No more blinds on the UTXO's keep,
🐇 Hoppity hop, the blockchain's deep!

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

---

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit-tests for this file.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit tests for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository from git and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit tests.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• The JSON schema for the configuration file is available here.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between 5592378 and 79affa0.

Files selected for processing (1)

• CHANGELOG.md (1 hunks)

Additional comments: 9

CHANGELOG.md (9)

• 1-1: The file CHANGELOG.md has been updated with a comprehensive summary of changes from the diff.
• 3-3: The summary provided in the diff for CHANGELOG.md is clear and informative.
• 1-4: > Note: This review was outside the patches, and no patch overlapping with it was found. Original lines [5-5]

The changes in the CHANGELOG.md file are well-documented and cover a wide range of updates, including API updates, bug fixes, node compatibility, and serialization compatibility.

• 1-4: > Note: This review was outside the patches, and no patch overlapping with it was found. Original lines [7-7]

The AI-generated summary of changes is concise and matches the detailed diff provided for CHANGELOG.md.

• 1-4: > Note: This review was outside the patches, and no patch overlapping with it was found. Original lines [9-9]

The provided context for the entire file is crucial for understanding how the changes integrate within the file. The annotations with line numbers are helpful for pinpointing the exact segments of code that have been modified.

• 1-4: > Note: This review was outside the patches, and no patch overlapping with it was found. Original lines [11-11]

The changes in the CHANGELOG.md file are well-organized into categories such as API updates, bug fixes, node compatibility, and serialization compatibility, which provides a clear structure for the reader.

• 1-4: > Note: This review was outside the patches, and no patch overlapping with it was found. Original lines [13-13]

The updates to the CHANGELOG.md file reflect significant progress towards the 0.1 milestone, indicating a move towards a more stable release of Rust-Lightning and LDK.

• 1-4: > Note: This review was outside the patches, and no patch overlapping with it was found. Original lines [15-15]

The caution against using Rust-Lightning on mainnet at version 0.0.98 is an important security note that should be highlighted to users.

• 1-4: > Note: This review was outside the patches, and no patch overlapping with it was found. Original lines [17-17]

The final note in the CHANGELOG.md about the varying quality of language bindings in LDK is an important disclaimer for users looking to integrate LDK into their projects.