> For the complete documentation index, see [llms.txt](https://data-programs.gitbook.io/singularity/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://data-programs.gitbook.io/singularity/overview/v1-or-v2.md). # V1 or V2 [Singularity V1](https://github.com/tech-greedy/singularity) began as an initiative focused on onboarding a substantial volume of public datasets to Filecoin. Its success and efficacy transformed it into the most sought-after data onboarding tool within the Filecoin ecosystem. As we transition into the new era, Singularity V2 emerges. While it retains the foundational strengths of V1, V2 is an entirely reimagined implementation, boasting both feature parity with V1 and the addition of groundbreaking capabilities. ## A Brief Comparison
FeatureSingularity V1Singularity V2
Languagenodejs + golanggolang
Installationnpm installgo install
Local FS data source✅✅
Remote data sourcePublic S3 bucket40+ integrations
Upload / Push new file❌✅
Inline Preparation❌✅
Maintain Dataset hierarchy✅✅
CAR download❌✅
File download❌✅
Deal making scheduler✅✅
Deal making self service✅✅
Zero external dependency❌✅
Wallet management❌✅
Remote signer❌✅
Web API❌✅
--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://data-programs.gitbook.io/singularity/overview/v1-or-v2.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.