Skip to content

Allowlist BigONE domains#1824

Open
elioncode wants to merge 1 commit into
phantom:masterfrom
elioncode:codex/allowlist-bigone-domains
Open

Allowlist BigONE domains#1824
elioncode wants to merge 1 commit into
phantom:masterfrom
elioncode:codex/allowlist-bigone-domains

Conversation

@elioncode

@elioncode elioncode commented Jun 16, 2026

Copy link
Copy Markdown

Summary

Allowlist BigONE root domains and wildcard subdomains:

  • bigone.com
  • *.bigone.com
  • big.one
  • *.big.one

Why

BigONE users are still being redirected by the Phantom extension to the phishing warning page for bigone.com. The warning shown by Phantom says bigone.com is blocked and that the website is considered malicious and unsafe to use.

There is an older PR for this false-positive appeal (#1707), but it only adds wildcard entries. This PR also includes the root domains because the observed warning is triggered on bigone.com itself.

Notes for reviewers

I checked the current public blocklist.yaml and did not find bigone.com or big.one there. If this repository is not the active source for the current production verdict, please advise the correct appeal path or data source so the false-positive block can be removed.

Validation

  • git diff --check
  • yarn install --frozen-lockfile && node ./ci.js
  • yarn run build and confirmed all four BigONE entries appear in generated blocklist.json whitelist data

Summary by CodeRabbit

  • Chores
    • Updated domain whitelist configuration to support bigone.com and big.one, including all subdomains, while maintaining existing whitelisted services.

@coderabbitai

coderabbitai Bot commented Jun 16, 2026

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: df41930c-e88b-404f-be91-1cbf9a49bae0

📥 Commits

Reviewing files that changed from the base of the PR and between 5030186 and 32a1d28.

📒 Files selected for processing (1)
  • whitelist.yaml

📝 Walkthrough

Walkthrough

whitelist.yaml adds four new domain entries — bigone.com, *.bigone.com, big.one, and *.big.one — while retaining the existing nftplus.io entry.

Changes

Domain Whitelist Update

Layer / File(s) Summary
Add bigone.com and big.one entries
whitelist.yaml
The single nftplus.io entry is replaced with nftplus.io plus explicit and wildcard entries for bigone.com (bigone.com, *.bigone.com) and big.one (big.one, *.big.one).
🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'Allowlist BigONE domains' directly and clearly summarizes the main change—adding BigONE domains to the allowlist/whitelist.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

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

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant