docs: add Profanity/Split-Key safety narrative to README - #4
Merged
manifoldor merged 1 commit intoAug 26, 2026
Merged
Conversation
Explain why Vaddro exists relative to archived Profanity (CVE-2022-40769) and the 2022 Wintermute incident, and record that the coffee address is a 13-leading-zero-nibble proof of work. Co-authored-by: manifoldor <manifoldor@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The current README explains Split-Key and CUDA well, but never mentions Profanity, CVE-2022-40769, or the 2022 Wintermute incident, so people searching for a safe EVM vanity tool cannot connect this repo to that story. This docs-only change adds a short factual homepage section in English and Chinese (after the tagline, above “Why Vaddro”), records that the coffee address is a 13-leading-zero-nibble proof of work, and adds a one-line historical pointer in the existing security-model policy. Performance tables, CUDA engine details, scripts, and version numbers are unchanged.