Skip to content

data(filecoin): refresh Ramo storage metadata - #3129

Open
edras-create wants to merge 1 commit into
Chain-Love:mainfrom
edras-create:update-ramo-storage-metadata
Open

data(filecoin): refresh Ramo storage metadata#3129
edras-create wants to merge 1 commit into
Chain-Love:mainfrom
edras-create:update-ramo-storage-metadata

Conversation

@edras-create

Copy link
Copy Markdown
Contributor

Summary

Refresh Ramo's canonical provider and Filecoin storage metadata from its current official product pages. The patch replaces the legacy web3mine-era provider description and records Ramo's current access path, machine-readable pricing, uncapped zero-egress policy, petabyte-scale workload focus, production footprint, durability, and sustained throughput.

Type of change

  • Add data rows
  • Update data rows
  • Remove data rows
  • Schema change
  • Documentation/metadata only

Scope

  • Networks affected: Filecoin
  • Categories affected: providers / storages
  • Additional notes: updates five existing non-empty cells; no new provider or offer is introduced.

Links

Validation checklist

  • I followed the Style Guide and Column Definitions.
  • I personally opened and verified every updated link.
  • I verified every changed value against current official Ramo sources.
  • The modified CSV files parse successfully, remain sorted by slug, and their JSON fields are valid.
  • A fresh open-PR search found no existing Ramo contribution.
  • This PR is not a blind AI-generated submission.

AI assistance was used for discovery, collision checking, CSV preparation, and validation. Every submitted value and source was individually verified.

Optional

  • Rewards address (Ethereum): 0x60079059d9E623fC87b69124Ccb6E4671124a834
  • Twitter (X) post link: Not provided

@edras-create
edras-create marked this pull request as ready for review August 21, 2026 19:26
@github-actions

Copy link
Copy Markdown

Summary

Status Count
🔍 Total 7
🔗 Unique 6
✅ Successful 7
⏳ 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: APPROVE
Risk: LOW
Summary: The Ramo provider and storage-offer refresh is narrow, source-backed, and keeps the existing provider/offer wiring intact.
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.

3 participants