Mirrored from filpgf.io — ProPGF Batch 3 (Karma program 1479, application 6a284b5beaebee9ea5a5c4cf, status: pending). Contact details redacted; canonical application lives on filpgf.io. 1.1 Project Name SynapS3 1.2 Project Github https://github.com/strahe/SynapS3 1.3 Project Website https://synaps3.strahe.com/en/ 1.4 Team Lead/Point of Contact Lee, Lead Maintainer. Preferred contact: Telegram @octal5 1.5 Category [ "Core Infrastructure" ] 1.6 Open Source Status Fully Open Source 2.1 Project Summary SynapS3 makes Filecoin FOC usable through the S3 API. Most object storage users already understand AWS S3. They use S3 clients, SDKs, backup tools, data pipelines, media workflows, and S3-compatible applications. SynapS3 gives these users a direct path to Filecoin storage without requiring them to learn Filecoin-specific APIs, payment flows, or provider workflows. Users write objects through normal S3 APIs. SynapS3 persists the data locally, records metadata, and uploads it to Filecoin FOC in the background. Operators get a dashboard, wallet operations, task retries, health checks, metrics, and Docker deployment. The result is a practical bridge from existing Web2 object storage workflows to paid Filecoin storage. 2.2 Who does this work support? [ "Application Users", "Application Builders", "Storage Providers", "Onramps", "Network Infrastructure" ] 2.3 Total Funding Requested (USD) 80000 2.4 Milestones & Budget [ { "title": "S3-Compatible FOC Gateway", "description": "Deliverables:\n- S3-compatible bucket and object APIs\n- Object versioning\n- Multipart upload\n- Copy and delete flows\n- Path-style S3 access\n- AWS CLI, rclone, and MinIO Client support", "dueDate": "2026-07-31", "fundingRequested": "20000", "completionCriteria": "- Users can connect common S3 clients to SynapS3.\n- Users can create buckets, upload objects, read objects, delete objects, and use multipart upload.\n- S3 behavior and limitations are documented." }, { "title": "Filecoin FOC Upload Pipeline", "description": "Deliverables:\n- Synapse SDK integration\n- Cache-first write path\n- Background Filecoin upload workers\n- Task leases, retries, and recovery\n- Cache eviction after Filecoin storage is available\n- Read path from local cache or remote Filecoin copy", "dueDate": "2026-08-31", "fundingRequested": "30000", "completionCriteria": "- S3 writes are accepted safely before background Filecoin upload starts.\n- Objects can move from S3 upload to Filecoin FOC storage.\n- Failed or stalled tasks can be inspected and retried." }, { "title": "Operator Dashboard and Runtime Tools", "description": "Deliverables:\n- Admin dashboard\n- Admin API\n- Wallet funding, deposit, and withdrawal operations\n- Task queue views\n- Provider and data set health views\n- Health endpoint and Prometheus metrics\n- Docker deployment documentation", "dueDate": "2026-09-30", "fundingRequested": "15000", "completionCriteria": "- Operators can inspect wallet, tasks, objects, cache, providers, and health.\n- SynapS3 can be deployed as a self-hosted gateway.\n- Troubleshooting and recovery paths are documented." }, { "title": "Public Readiness and Validation", "description": "Deliverables:\n- Publish release builds and Docker images\n- Validate core S3-to-FOC workflows on Calibration\n- Improve deployment and troubleshooting documentation\n- Improve operator diagnostics for upload and task failures", "dueDate": "2026-10-31", "fundingRequested": "15000", "completionCriteria": "- A public release build is available.\n- Docker deployment is documented and tested.\n- Core S3 upload, read, multipart upload, and background FOC upload flows are validated on Calibration.\n- Operators can inspect failed upload tasks and retry them." } ] 3.1 Impact pathway S3 is the default interface for many object storage users. Filecoin FOC needs simple paths for those users to try, adopt, and operate Filecoin-backed storage. SynapS3 turns Filecoin FOC into an S3-compatible endpoint. This lowers adoption cost for existing applications and operators because they can keep their current storage interface while SynapS3 handles the Filecoin side. Each successful S3-to-FOC workflow creates a practical path toward paid Filecoin storage usage. 3.2 Verification metrics - Protocol Compliance & Client Compatibility SynapS3 will publish and pass a documented S3 workflow validation suite using AWS CLI, rclone, and MinIO Client against its public compatibility matrix. Covered workflows include bucket creation/listing, object upload/read/head/delete, multipart upload, object versioning, delete markers, copy flows, and documented limitations such as path-style access and unsupported bucket deletion. Verification artifacts will include commands, expected results, compatibility notes, and release-linked documentation. - End-to-End FOC Workload Validation SynapS3 will run a continuous 7-day automated workload on the Calibration testnet. The target workload is at least 2 TB of test data transferred through SynapS3; the minimum completion threshold is 500 GB if Calibration provider, network, or testnet limits constrain throughput. The test will verify cache-first writes, background FOC uploads, task leases, retries, remote read fallback, and cache eviction. Success requires zero checksum mismatches, zero unrecovered stuck tasks after final reconciliation, and documented handling of any provider, RPC, wallet, or network failures. - Production Readiness & Observability SynapS3 will deliver a Prometheus metrics endpoint and a Grafana dashboard template for operator diagnostics. The dashboard will cover task queue depth and latency, worker health, cache utilization, wallet and USDFC readiness, upload success/failure rates, exhausted retries, and FOC/provider health signals. Success requires operators to identify blocked uploads, low balance, cache pressure, failed tasks, and retryable upload issues through documented dashboard, CLI, and Admin API checks. - Public Release & Reproducibility SynapS3 will publish tagged release artifacts, Docker images, deployment documentation, and validation notes. Reviewers and operators should be able to deploy SynapS3, create S3 credentials, run common S3 clients, observe Filecoin upload progress, inspect failed tasks, and reproduce the core validation workflows from public documentation. 3.3 References N/A 4.1 Monthly Operating Burn [ "< $10K (basic solo operation or part-time team)" ] 4.2 What % of total team monthly burn depends on this grant? 100 4.3 If this grant is not awarded, what happens? SynapS3 will remain open source. Public releases, validation, documentation, and user support will continue more slowly. 4.4 Core Team SynapS3 is an independent project led by Lee. Lee brings over 10 years of software development experience, including 7 years in the IPFS/Filecoin community and more than 5 years working at storage provider companies. The work covers implementation, Filecoin FOC integration, testing, documentation, releases, and community support. 4.5 Has your team received a ProPGF grant or funding from PLFIF before? [ "Yes" ] 5.1 Key risks & dependencies Core delivery risk is low. The main gateway, S3 compatibility layer, FOC upload pipeline, dashboard, Docker deployment, and documentation are already implemented. Remaining risks are limited to external dependencies such as FOC/Synapse SDK changes, provider behavior, and network availability during validation. Anything else you want to share that we didn't ask? The main SynapS3 workflow is already implemented and ready for deployment and testing. Documentation is available here: https://synaps3.strahe.com/en/ Contributing to Core Infrastructure? SynapS3 lets Web2 object storage users use Filecoin Onchain Cloud like AWS S3. It provides an S3-compatible endpoint for Filecoin FOC, so existing S3 tools, applications, backup systems, data pipelines, and operators can use Filecoin storage without changing their storage interface. Objective 1 Direct Objective 2 Indirect Objective 3 Indirect