data(providers): fill 43 verified contact and social fields on 28 providers - #3136
Open
EazyHood wants to merge 2 commits into
Open
data(providers): fill 43 verified contact and social fields on 28 providers#3136EazyHood wants to merge 2 commits into
EazyHood wants to merge 2 commits into
Conversation
Summary
|
Summary
|
USS-Supervisor
previously approved these changes
Aug 22, 2026
USS-Supervisor
left a comment
Member
There was a problem hiding this comment.
Verdict: APPROVE
Risk: MEDIUM
Summary: The broad provider metadata fill only updates previously blank provider contact/social/docs cells, does not add or remove rows, preserves the 14-column provider CSV shape, and the platform/contact formatting pass found no full-URL leakage in social fields or malformed contact values.
Findings: None.
Confidence: MEDIUM
Required validation passed on current head 42c245d, static CSV checks were clean, and the current-cycle link-check run 32548092553 reported 180 total links, 180 successful, and 0 errors/timeouts/unsupported URLs.
…viders Second batch of the same lane. All 37 providers back listings on bounty-eligible networks (Algorand, Filecoin, Somnia), directly or through listings/all-networks. Every value was read from the provider's own website, its official documentation, or a GitHub repository linked from that website, and then re-checked by a second pass whose job was to disprove it. Five candidates failed that second pass and are not here: one Telegram group the provider's own anti-phishing page disowns, one whose designated link resolves to an empty destination, one belonging to an individual rather than the organisation, one dead address on a domain the provider does not own, and one that existed only inside a schema block. Only previously empty cells were filled. Cell-by-cell comparison against upstream/main: 55 changed cells, 55 declared, zero emptied, zero overwritten, row count and slug set unchanged. Every value was composed into a URL the way .github/workflows/link-check-analysis.yaml composes it and requested: 31 of 31 resolve, and all 11 Discord invites are live and non-expiring. Fields: supportEmail 24, discord 11, telegram 8, github 5, x 4, docs 3. Format follows AGENTS.md: website and docs hold full URLs, while x, github, discord and telegram hold only the value after the domain. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
EazyHood
force-pushed
the
data/provider-contacts-lote2
branch
from
August 23, 2026 11:08
42c245d to
613914b
Compare
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
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.
Fills contact and social fields that were empty on 28 provider rows: support email, docs, X, GitHub, Discord and Telegram. The final diff adds 43 non-null cells and does not overwrite or remove any value from current main.
Field breakdown:
Every value was read from the provider's own site, contact page, documentation, or official channel—not from an aggregator or third-party list. Where a provider does not publish a channel, the cell is deliberately left empty rather than guessed.
Collision and rebase audit:
Validation:
Rewards address
0x06f44f4839fd5df4f4670036d028b29dec939363