Skip to content

data(filecoin): add Forest Explorer USDFC faucet - #3152

Open
EazyHood wants to merge 1 commit into
Chain-Love:mainfrom
EazyHood:data/filecoin-forest-usdfc-faucet
Open

data(filecoin): add Forest Explorer USDFC faucet#3152
EazyHood wants to merge 1 commit into
Chain-Love:mainfrom
EazyHood:data/filecoin-forest-usdfc-faucet

Conversation

@EazyHood

Copy link
Copy Markdown
Contributor

Summary

  • add the canonical Forest Explorer USDFC faucet offer from ChainSafe
  • list it for Filecoin Calibration through an !offer: reference
  • reuse the existing ChainSafe provider and calibnet chain assets
  • keep the contribution to two new rows and 13 non-null cells

Official evidence

The faucet URL is live behind a Cloudflare browser challenge (HTTP 403 to automated HEAD requests), and both official Filecoin sources above link to it.

Collision audit

Validation

  • official json-tools validate_csv.py: All checks passed
  • official csv_to_json.py generation: passed
  • official validate.py schema validation for all generated network JSON: passed
  • offer/listing widths: 13/14 columns
  • git diff --check: passed

Rewards address

0x06f44f4839fd5df4f4670036d028b29dec939363

@github-actions

Copy link
Copy Markdown

Summary

Status Count
🔍 Total 2
🔗 Unique 2
✅ Successful 2
⏳ Timeouts 0
🔀 Redirected 0
👻 Excluded 0
❓ Unknown 0
🚫 Errors 0
⛔ Unsupported 0

Full Github Actions output

@USS-Supervisor USS-Supervisor left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Verdict: COMMENT
Risk: LOW
Summary: I did not find a data-integrity issue in this change. The new Forest Explorer USDFC faucet offer and Filecoin Calibration listing keep the CSV widths stable, use unique slugs, resolve the !offer:forest-usdfc-faucet reference, and match the cited Filecoin/ChainSafe evidence.
Findings: None. Approval is blocked in this review cycle because the only successful link-check run for the current head started at 2026-08-23 13:01 UTC, before this 14:53 UTC review cycle; under the current approval rule I cannot approve without a current-cycle link-check=success.
Confidence: HIGH

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.

2 participants