Clarification of license, versioned trade shards and observation-time provenance

#3
by T0mmyZEd0g - opened

Hello Slink Dev,

I am independently assessing the historical PumpFun corpus for private, offline research. I matched the SHA256 of all 18 trades/trades-00000.parquet through trades-00017.parquet files against your published file hashes.

Could you please clarify:

  1. The dataset card metadata says MIT, while the README Licensing & Provenance paragraph says CC BY 4.0. Which license governs the exact trade files in the 18-shard release, and do any third-party provider terms apply? Is there a canonical license file or rights statement for that revision?
  2. Are the 18 trade Parquet shards direct published source outputs, and can you identify the exact immutable revision containing the complete final set?
  3. Do raw collector logs or columns exist with received_at, observed_at, ingested_at, or another verifiable first-availability timestamp distinct from on-chain event_time? If not, please confirm that the event timestamp does not imply contemporaneous observation.
  4. Your KNOWN_ISSUES describes a full WebSocket outage on July 3, 2026. Is that gap permanently missing, or was any portion backfilled? Are outage, reorganization, deduplication policies and collector coverage logs available?

A textual response is sufficient; no private keys, credentials, endpoints or non-public datasets are requested.

Thank you.

Thanks for reaching out. to clear up any confusion, here are the answers regarding your queries

Governing License: The entire dataset release including all 18 Parquet trade shards (trades-00000.parquet through trades-00017.parquet)—is strictly governed under CC BY 4.0.
Attribution Requirement: Mandatory attribution (to SlinkDev)  is required for any downstream use or publication.
Third-Party Terms: There are no third-party provider terms or third-party rights associated with this data as it was captured and processed directly by me. 

Parquet Shards: The 18 Parquet shards represent the complete, canonical trade corpus derived from my direct capture pipeline.
Release Revision: The 18-shard set matching the published SHA256 checksums is the complete and final set for this release revision.

Schema & Logs: No separate collector logs or first-availability timestamps (received_at, observed_at, ingested_at) exist beyond the columns explicitly defined in the schema and README.
Observation Latency: The timestamps reflect the on-chain event times and should not be interpreted as guaranteed contemporaneous capture latency metrics.

July 3, 2026 Outage: The WebSocket gap documented on July 3, 2026, is permanently missing and has not been backfilled.
Coverage Logs: No external collector logs, drop metrics, or coverage reports exist beyond what is outlined in the KNOWN_ISSUES section.

Thanks

Sign up or log in to comment