Skip to content

data(providers): consolidate 263 verified contact and social fields from five conflicting PRs - #3250

Open
EazyHood wants to merge 12 commits into
Chain-Love:mainfrom
EazyHood:data/providers-consolidado
Open

EazyHood wants to merge 12 commits into
Chain-Love:mainfrom
EazyHood:data/providers-consolidado

Conversation

@EazyHood

@EazyHood EazyHood commented Aug 27, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Rebuilt against current main from five of my own PRs that have been sitting in conflict: #2635,
#2636, #2637, #2638 and #2993.

providers.csv has taken 70 commits since 11 August, so rebasing them one at a time only puts
them back in conflict a couple of days later - and merging any one of them re-conflicts the other
four, since all five edit the same file. Consolidating into one branch against today's main is the
only way out of that loop.

This applies the cells from those five that are still empty on main today and that no earlier open PR already proposes, and nothing else:

column cells
supportEmail 115
discord 52
telegram 27
docs 27
x 21
github 9
website 8
linkedin 4

263 cells across 195 provider rows today. When this was opened on 27 August it was 463 cells across
317 rows; Changes since it was opened below accounts for the difference.

No existing value is overwritten. The change only fills cells that are blank on main, and the
five PRs proposed no conflicting values between them - zero disagreements across the five.

Verified row by row after the edit: 727 rows before and after (re-checked on 26 Sep), every changed row keeps its slug,
and no changed cell had a prior value. validate_csv.py, csv_to_json.py and validate.py all
pass; the six csv_to_json warnings about camino, lightning and zilliqa are pre-existing and
appear identically without this change.

If this lands, #2635, #2636, #2637, #2638 and #2993 can be closed as superseded. I will close them
myself once it is merged.

Changes since it was opened

Of the 463 cells in the first version, 200 are no longer in the diff:

Separately, 42 rows whose values this PR does not change differed from main only in CSV quoting; they now keep main's exact text, and the rows this PR does edit keep main's quoting in their unchanged cells.

Type of change

  • Update data rows

Scope

  • Networks affected: global (references/providers/providers.csv)

  • Categories affected: none - provider metadata only

  • Additional notes: edits were made line by line rather than by reserializing the CSV, so quoting
    elsewhere in the file is untouched, and line endings are unchanged (the file stays LF throughout).
    The diff is 195 insertions and 195 deletions - one line per touched provider row.

Links

Validation checklist

  • I followed the Style Guide and Column Definitions. I'm aware of what is !provider syntax, and that entities in /networks sub-folders inherits records from /providers folder
  • I personally opened and verified every new link I'm adding. I can confirm, that all the links I'm adding are valid.
  • If I added new entries - I personally confirmed that the provider I'm adding (modifying) currently supports the adjusted network(s). I've also verified that value in every cell I'm changing is correct according to my best understanding
  • This PR is not a blind AI-generated submission

Optional

  • Rewards address (for data patching rewards): 0x06f44f4839fd5df4f4670036d028b29dec939363

@github-actions

Copy link
Copy Markdown

Summary

Status Count
🔍 Total 1360
🔗 Unique 1360
✅ Successful 1341
⏳ Timeouts 4
🔀 Redirected 200
👻 Excluded 0
❓ Unknown 0
🚫 Errors 15
⛔ Unsupported 0

Errors per input

Errors in ./references/providers/providers.csv

Timeouts per input

Timeouts in ./references/providers/providers.csv

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: REQUEST_CHANGES
Risk: MEDIUM
Summary: The CSV structure is stable and the PR only fills previously blank provider cells, but two newly added provider URLs are not usable. The current-cycle link-check run 33096311408 completed with workflow success while reporting URL failures in references/providers/providers.csv, and manual checks confirmed these two PR-introduced failures.

Findings:

  • MEDIUM references/providers/providers.csv:298 (ghostgraph): the new website value https://tryghost.xyz/graph returns HTTP 404. Please replace it with a working official GhostGraph/Ghost URL or leave the field blank if there is no stable public page.
  • MEDIUM references/providers/providers.csv:559 (solar-wallet): the new docs value https://docs.solarwallet.io/ returns HTTP 503. Please use a reachable official docs/support URL or leave the field blank until it is available.

Confidence: HIGH

@EazyHood

Copy link
Copy Markdown
Contributor Author

Both URLs are fixed in 1e165ee.

ghostgraph website: https://tryghost.xyz/graph still returns 404 (re-checked 29 Aug). Replaced with https://tryghost.xyz/, which returns 200 and is the studio's own site — its meta description reads "Ghost: Infrastructure and Data R&D Studio", so it is the official page for the product rather than a redirect target.

solar-wallet docs: https://docs.solarwallet.io/ still returns 503. Left blank, as the review offered, because there is no reachable official alternative today — solarwallet.io/faq and solarwallet.io/support both 404, and help.solarwallet.io does not resolve. The website value https://solarwallet.io/ is unaffected and returns 200.

The commit touches two cells and nothing else: 720 rows, all 14 columns, verified by parsing the file rather than by line offset.

@github-actions

Copy link
Copy Markdown

Summary

Status Count
🔍 Total 1359
🔗 Unique 1359
✅ Successful 1348
⏳ Timeouts 1
🔀 Redirected 200
👻 Excluded 0
❓ Unknown 0
🚫 Errors 10
⛔ Unsupported 0

Errors per input

Errors in ./references/providers/providers.csv

Timeouts per input

Timeouts in ./references/providers/providers.csv

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: The two URL issues from the previous review are addressed: ghostgraph now uses https://tryghost.xyz/, and the unreachable Solar Wallet docs value is no longer introduced by this PR. The CSV still parses with stable 14-column rows, the change only fills previously blank provider cells, and required validation is passing. I am not approving this cycle because the current reviewer-owned link-check report is not clean: run 33264495749 completed with workflow success but reported 1348 successful links, 10 URL errors, and 1 timeout in references/providers/providers.csv.
Findings: None.
Confidence: HIGH

@EazyHood

Copy link
Copy Markdown
Contributor Author

Both URLs are fixed in 1e165ee.

ghostgraph website: https://tryghost.xyz/graph still returns 404 (re-checked 29 Aug). Replaced with https://tryghost.xyz/, which returns 200 and is the studio's own site — its meta description reads "Ghost: Infrastructure and Data R&D Studio", so it is the official page for the product rather than a redirect target.

solar-wallet docs: https://docs.solarwallet.io/ still returns 503. Left blank, as the review offered, because there is no reachable official alternative today — solarwallet.io/faq and solarwallet.io/support both 404, and help.solarwallet.io does not resolve. The website value https://solarwallet.io/ is unaffected and returns 200.

The commit touches two cells and nothing else: 720 rows, all 14 columns, verified by parsing the file rather than by line offset.

@EazyHood

Copy link
Copy Markdown
Contributor Author

On the link-check run that posted after my last comment: none of the 10 errors are introduced by this PR.

Eight of them are x.com URLs that do not appear in the diff at all — untouched rows — and six of those eight report "Connection failed" or "HTTP/2 protocol error", which is X blocking the checker rather than a dead link. The other three (developers.swing.xyz, swing.xyz, cloud.chainup.com) appear on both the removed and the added side of the diff: the row was modified for other cells, but those URLs were already there.

The two failures the review did attribute to this PR — tryghost.xyz/graph and docs.solarwallet.io — are no longer in the list.

@USS-Supervisor

Copy link
Copy Markdown
Member

@EazyHood this PR has been idle for more than 3 days, and the current blocker is unresolved requested changes. Please address the review feedback and update the PR when ready.

@EazyHood

EazyHood commented Sep 2, 2026

Copy link
Copy Markdown
Contributor Author

Merged current upstream main in 5e0b9481. The provider conflict was resolved cell by cell: current upstream values win where both sides changed, and the remaining verified fills from this PR were retained. Required validation is green and the branch is mergeable.

The old requested-changes review refers to URLs already fixed on the previous head. My fork permissions do not allow me to add the check-links label or request a new review. @eugene17kotov, please trigger the current-cycle link check/review when convenient.

@USS-Supervisor

Copy link
Copy Markdown
Member

Hi @eugene17kotov - following up on this stale PR. Required CI is passing and I do not see a current creator-side blocker, so it looks ready for reviewer action when you have a chance.

Rebuilt against current main from five of my own PRs that have been sitting
in conflict: Chain-Love#2635, Chain-Love#2636, Chain-Love#2637, Chain-Love#2638 and Chain-Love#2993. providers.csv has taken
70 commits since 11 August, so rebasing them one at a time just puts them
back in conflict a day later - and merging any one of them re-conflicts the
rest, since all five edit the same file.

This applies every cell from those five that is still empty on main today,
and nothing else:

  supportEmail  164    docs       39
  discord       108    github     10
  x              65    website     9
  telegram       60    linkedin    8

463 cells across 317 provider rows. No existing value is overwritten - the
script only fills cells that are blank on main, and the five PRs proposed no
conflicting values between them (zero disagreements across all 463).

Verified row by row after the edit: 720 rows before and after, every changed
row keeps its slug, and no changed cell had a prior value.

validate_csv.py, csv_to_json.py and validate.py all pass.

If this lands, Chain-Love#2635, Chain-Love#2636, Chain-Love#2637, Chain-Love#2638 and Chain-Love#2993 can be closed as
superseded.
- ghostgraph website: https://tryghost.xyz/graph returns 404. Replaced with
  https://tryghost.xyz/, the studio's own site (200), which is the official
  page for the product.
- solar-wallet docs: https://docs.solarwallet.io/ returns 503. Left blank, as
  the review offered, because no reachable official docs URL exists today:
  solarwallet.io/faq and /support are both 404 and help.solarwallet.io does
  not resolve.

Both re-verified on 29 Aug. No other cell touched: 720 rows, all 14 columns.
@EazyHood
EazyHood force-pushed the data/providers-consolidado branch from 5e0b948 to df60efb Compare September 10, 2026 16:59
@EazyHood

Copy link
Copy Markdown
Contributor Author

@eugene17kotov — a small mechanical request rather than a review one, if you have a moment.

Thirteen of my open PRs are waiting on something I cannot trigger from a fork: the check-links label. @USS-Supervisor says so in its own words on several of them — on this PR, "I am not approving this cycle because the current reviewer-owned link-check report is not clean", and on #3326 and #3577, "I could not verify a current-cycle link-check success before cleanup". On #3152 and #3153 it goes further and writes "I did not find a data-integrity issue in this change", and still does not approve, for the same missing report.

So these are not waiting on anyone's judgement. They are waiting on a run that only a label can start, and without the approval they never reach your queue at all.

Blocked on a current-cycle link-check — #2453, #3152, #3153, #3250, #3326, #3577

Previously approved, dismissed when a commit landed, and not re-reviewed since — #2457, #3135, #3136, #3137, #3251, #3323, #3325

All thirteen are rebased on current main, conflict-free and green on required validation. I rebased the last four myself yesterday to clear merge conflicts, which is what dismissed their approvals; that was the cost of making them mergeable at all, and they have been stable since.

Five others — #2454, #2456, #2995, #3252, #3324 — already carry @USS-Supervisor's approval and are simply in the normal queue. I am not asking for anything on those.

If applying the label to a batch is awkward, tell me which order you would rather have them in and I will close the rest and re-open them a few at a time. I would rather fit your process than add thirteen rows to it.

EazyHood and others added 5 commits September 21, 2026 09:23
These rows carry the same values as main and only differed in CSV quoting, which put them in the diff and in the link check.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
swing.xyz serves an invalid certificate and developers.swing.xyz does not resolve; www.mosaia.io serves an invalid certificate; learnweb3.io returns 503 Service Suspended; github.com/strangelove-ventures is gone (the org is now amygdala-labs, fixed in Chain-Love#3325). Touching those rows puts their dead links in the link check, so this PR leaves them as they are in main. The bybit x value pointed at the EU entity rather than the global exchange, so it is dropped too.

The rows this PR does edit now keep main's quoting in their unchanged cells, so the diff shows only the cells it fills.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Chain-Love#3326 fills the same Temple Wallet x and discord cells and clears its dead docs link; editing the row here too would only put docs.templewallet.com, which times out, back into this PR's link check.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@EazyHood EazyHood changed the title data(providers): consolidate 463 verified contact and social fields from five conflicting PRs data(providers): consolidate 386 verified contact and social fields from five conflicting PRs Sep 24, 2026
@EazyHood

Copy link
Copy Markdown
Contributor Author

Updated in d096af8 and 62c2f3c: five rows whose existing links fail today are left as they are on main — swing, mosaia, learnweb3, strangelove-ventures and temple-wallet — and bybit's x is dropped because it pointed at the EU entity rather than the global exchange. The 42 rows that differed from main only in CSV quoting are out of the diff. That leaves 386 cells across 271 rows; the description now has a section accounting for the difference from the original 463.

@EazyHood

Copy link
Copy Markdown
Contributor Author

@USS-Supervisor the findings from your 27 Aug review are addressed: ghostgraph's website is now https://tryghost.xyz/ (200 today) instead of the /graph page, and this PR no longer changes the solar-wallet row. Ready for a re-review.

main changed the sardine, vestige and xrpscan rows (Chain-Love#2817, Chain-Love#3922, Chain-Love#2818).
This branch does not touch those rows, so they are taken from main as they are.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown

Summary

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

Errors per input

Errors in ./references/providers/providers.csv

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: REQUEST_CHANGES
Risk: HIGH
Summary: The prior GhostGraph and Solar Wallet findings are fixed, the 386 current changes preserve provider-field formatting, and required validation passed. Fresh link-check run 36206694353 reported one HTTP 304 on the unchanged Trust Wallet website; a direct recheck returned 200, so that is not treated as a PR defect. The blocking issue is extensive exact overlap with other active contributions.
Findings:

  • HIGH — references/providers/providers.csv: 166 of the 386 submitted cells exactly duplicate values in 24 still-open PRs. The largest repeated sets include 43 occurrences in #3914, 41 in #2977, 31 in #3326, 30 in #2890, 17 in #3324, and 11 each in #3323 and #3325; additional matches remain in #2859, #2864, #2880, #2884, #3333, #3554-#3556, #3685, #3720, #3721, #3913, #3964-#3966, #3982, and #3983. Please coordinate a single surviving contribution for each exact cell and remove the duplicates before re-review. The census excluded same-row/different-field edits and values already present on current main.
    Confidence: HIGH

76 cells are proposed with the same value by PRs opened before this one (Chain-Love#2977, Chain-Love#2890, Chain-Love#2880,
Chain-Love#2859, Chain-Love#2884, Chain-Love#2864). 46 are also in my own smaller batches Chain-Love#3323-Chain-Love#3326 and stay there only.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
EazyHood added a commit to EazyHood/chain-love that referenced this pull request Sep 26, 2026
17 of them are in Chain-Love#2977 (16 Aug), one in Chain-Love#2859 and one in Chain-Love#2880 (13 Aug), all opened before
this PR with exactly the same values. The 31 cells shared with Chain-Love#3250 stay here: Chain-Love#3250 drops
them instead.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@EazyHood EazyHood changed the title data(providers): consolidate 386 verified contact and social fields from five conflicting PRs data(providers): consolidate 264 verified contact and social fields from five conflicting PRs Sep 26, 2026
@EazyHood

Copy link
Copy Markdown
Contributor Author

@USS-Supervisor updated in ae45d8b, from 386 to 264 cells. Of the 166 duplicated cells in your census:

Re-running the same census on the new head finds no cell here that an earlier open PR, or another PR of mine, also proposes. The title and description are updated.

@github-actions

Copy link
Copy Markdown

Summary

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

Errors per input

Errors in ./references/providers/providers.csv

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: REQUEST_CHANGES
Risk: HIGH
Summary: The exact-overlap blocker is resolved for this earlier contribution, required validation passed, and the fresh link check's sole 304 is on unchanged trust.website. Current first-party evidence still exposes three provider-metadata issues that green CI cannot detect.
Findings:

  • HIGH — references/providers/providers.csv:546, secondfi.x=secondfiapp: SecondFi's current official site and knowledge base state that it is ceasing operations and will not resume normal operations. Remove this enrichment and coordinate a provider → offer → listing retirement audit instead.
  • MEDIUM — references/providers/providers.csv:359, laevitas.docs=https://app.laevitas.ch/: this is the authenticated analytics dashboard, not documentation. Laevitas publishes its API documentation at https://docs.laevitas.ch/; use that current docs URL or leave the field blank.
  • MEDIUM — references/providers/providers.csv:332, infstones.discord=5Sgu93crrA: the current InfStones homepage publishes discord.gg/infstones, which resolves to a different current guild (InfStones Global). Replace the older invite with infstones or provide current first-party evidence for retaining it.
    Confidence: HIGH

From USS-Supervisor's re-review:
- secondfi.x: removed. SecondFi's own site states it will not resume
  normal operations, so the enrichment is dropped.
- laevitas.docs: app.laevitas.ch (the authenticated dashboard) -> docs.laevitas.ch,
  the actual API documentation ("Getting Started | Laevitas V1.0 API").
- infstones.discord: 5Sgu93crrA -> infstones, the vanity published on the
  current InfStones homepage (guild "InfStones Global").

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@EazyHood EazyHood changed the title data(providers): consolidate 264 verified contact and social fields from five conflicting PRs data(providers): consolidate 263 verified contact and social fields from five conflicting PRs Sep 26, 2026
@EazyHood

Copy link
Copy Markdown
Contributor Author

@USS-Supervisor addressed in 1688d37:

  • secondfi.x removed - SecondFi's own site states it will not resume normal operations, so the enrichment is dropped.
  • laevitas.docs changed from the app.laevitas.ch dashboard to docs.laevitas.ch, the API documentation ("Getting Started | Laevitas V1.0 API").
  • infstones.discord changed from 5Sgu93crrA to infstones, the vanity invite published on the current InfStones homepage (guild "InfStones Global").

The PR is now 263 cells across 195 provider rows; the title and description say so.

@EazyHood

Copy link
Copy Markdown
Contributor Author

@USS-Supervisor a gentle reminder: the three findings from your 26 Sep review (secondfi x, laevitas docs, infstones discord) have been addressed in 1688d37 since 26 Sep, as described in my comment above, and the required validation is green. Could you take another look when you have a chance?

@github-actions

Copy link
Copy Markdown

Summary

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

Errors per input

Errors in ./references/providers/providers.csv

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: APPROVE
Risk: LOW
Summary: The three prior provider-metadata blockers are resolved on the exact current head. InfStones now uses the Discord invite published by its homepage, Laevitas now points to its API documentation, and the discontinued SecondFi X enrichment is removed. Required validation passed, and fresh reviewer-owned link-check run 36335114628 completed successfully; its sole reported 304 is the unchanged Trust Wallet website and a direct request returned 200.
Findings: None.
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