Add wolfxy.com to whitelist

[react-universe]

Adds wolfxy.com to whitelist.yaml.

Summary by CodeRabbit

• Bug Fixes

  • Fixed a malformed whitelist entry so existing domain entries are correctly recognized and processed.

• New Features

  • Added wolfxy.com to the whitelist, expanding allowed domains.

Notes: These changes normalize whitelist formatting and increase the domain list by one, improving reliability of domain checks without other functional changes.

[coderabbitai]

📝 Walkthrough

Walkthrough

Fixes YAML formatting for an existing nftplus.io entry in whitelist.yaml and adds a new wolfxy.com domain entry to the whitelist; no other files or exported entities changed.

Changes

Cohort / File(s)	Summary
Whitelist Configuration whitelist.yaml	Corrected malformed line for nftplus.io (from - - url: nftplus.io to - url: nftplus.io) and added a new - url: wolfxy.com entry.

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately and concisely describes the main change: adding wolfxy.com to the whitelist. It directly reflects the primary purpose of the pull request.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[react-universe]

REQUEST to Remove wolfxy.com from the blocklist

About the site
wolfxy.com is the official website of Wolfxy, a Web3-based platform focused on blockchain-powered transactions and digital asset utilities. The platform provides legitimate blockchain interactions and wallet-based features for its users.

The project operates transparently and does not engage in phishing, malware distribution, or deceptive practices. All smart contract interactions are user-initiated and visible on-chain.

Project credibility

• Official production domain: https://wolfxy.com/
• Public blockchain interactions (fully verifiable on-chain)
• No history of phishing reports or scam activity
• Standard wallet integrations (e.g., Solana-compatible wallets)
• No malicious scripts, hidden redirects, or exploit attempts

The issue

When users visit wolfxy.com, Phantom displays a warning stating:

“This dApp could be malicious”

This warning appears to be a false positive triggered by heuristic or transaction simulation limitations. The application performs legitimate blockchain transactions, and in some cases wallet simulation may not fully interpret dynamic transaction flows — which can incorrectly trigger protective warnings.

The domain does not appear in the public blocklist repository and does not engage in any unsafe behavior.

Clarification

• Transactions can be pre-simulated via RPC before requesting user signatures.
• No automatic signing requests occur without user interaction.
• No malicious contract calls are executed.
• The site does not request seed phrases or private keys.

Request

We respectfully request a manual review of wolfxy.com and removal from the malicious/unsafe classification. This appears to be a false positive and is negatively impacting legitimate users.

If additional verification steps, code review details, or transaction simulation logs are required, we are happy to provide them.

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@whitelist.yaml`:
- Line 34: The PR adds wolfxy.com to whitelist.yaml but whitelist/fuzzylist are
not enabled (per README) and build.js lacks whitelist-vs-blocklist conflict
handling, so the warning won't be cleared; update the active detection source
and conflict resolution: enable whitelist/fuzzylist usage as described in README
or change the detector to consult whitelist.yaml/fuzzylist during runtime, and
modify build.js to implement logic that checks whitelist entries (exact and
fuzzy) before applying blocklist rules so whitelisted domains like wolfxy.com
are exempt from blocking.

---

ℹ️ Review info

Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 0b33b888-876a-4ff0-8712-cc0cf9503f10

📥 Commits

Reviewing files that changed from the base of the PR and between 69e9719 and 8099e8d.

📒 Files selected for processing (1)

• whitelist.yaml

[coderabbitai]

⚠️ Potential issue | 🟠 Major

Whitelist-only addition likely won’t clear the reported warning.

Line 34 adds wolfxy.com to whitelist.yaml, but based on README.md (Line 19-35) whitelist/fuzzylist are not currently active, and build.js (Line 1-25) has no whitelist-over-blocklist conflict handling. This PR likely won’t satisfy the stated objective unless the active detection source is also updated.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@whitelist.yaml` at line 34, The PR adds wolfxy.com to whitelist.yaml but
whitelist/fuzzylist are not enabled (per README) and build.js lacks
whitelist-vs-blocklist conflict handling, so the warning won't be cleared;
update the active detection source and conflict resolution: enable
whitelist/fuzzylist usage as described in README or change the detector to
consult whitelist.yaml/fuzzylist during runtime, and modify build.js to
implement logic that checks whitelist entries (exact and fuzzy) before applying
blocklist rules so whitelisted domains like wolfxy.com are exempt from blocking.