Skip to content
This repository was archived by the owner on May 15, 2024. It is now read-only.

Milestones

List view

  • An S3 Compliant head that supports baseline S3 integration functionality(GET, POST, HEAD). Definition of Done: An ISV has downloaded the S3 connector, and run it to create a test bucket using their own s3 credentials. SEE Dogfooding: https://www.notion.so/pl-strflt/Dogfooding-In-Motion-c5f8f5a4fc2541dcbe1b0310b016c51d

    Overdue by 2 year(s)
    Due by August 31, 2023
    3/3 issues closed
  • Files stored by motion API on Filecoin Storage provider are retrievable via motion API calls. Non Functional Requirements: -We will leverage Lassie and sub out lookups to the IPNI. -32GiB max upload size for files, and no resumption, but will include the ability to stream data and resume interruptions. Not Included: -Will not include the ability to retrieve from multiple deals simultaneously. User Story for Milestone: As an ISV, I want to use the Motion API to retrieve my files, so that I can test the entire roundtrip of blob storage with my software API integration.

    Overdue by 2 year(s)
    Due by September 29, 2023
    5/5 issues closed
  • The Motion API can be used by an ISV to write a Filecoin deal to a storage provider and can confirm the status of the storage blob. Files will be verifiably stored on Filecoin mainnet with a storage provider from the selected pool of storage providers. Support for a single configurable Wallet address in the a local docker file. Non Functional Requirements: -1 store request per second -1 retrieval request per second. -1s TTFbyte -S3 integration Not Included: -Will not include limitless streaming -Will not include resumption of failed uploads. -ISV will perform their own encryption User Story for Milestone: As an ISV, I want to be able to store blobs of data on Filecoin to a Storage Provider with the Singularity deal making engine, so that I can make storage deals on Filecoin which I may later access.

    Overdue by 2 year(s)
    Due by August 31, 2023
    20/20 issues closed
  • An API which achieves the following functionality: Docker HTTP server which runs the Motion API locally /POST API User can store a blob locally utilizing the base schema to /v0/blob /GET API User can retrieve the blob, can get range, '/GET' API User can check the status of blob storage via /v0/blob/{id}/status User Story for Milestone: As an ISV, I want a local docker image I can use to deploy the motion API, so that I can start testing and building integrations into my codebase, and storing data into motion.

    Overdue by 2 year(s)
    Due by July 28, 2023
    6/6 issues closed