Fileverse track #2
Description
Fileverse Track ($1,000)
What's real: AES-256-GCM encryption is genuine. SHA-256 CIDs (bafk prefix) are content-addressed. The get_history and compile_report MCP tools work end-to-end with the storage service.
Criticism (serious): The Fileverse storage (index.ts) is a local filesystem service — it writes JSON files to .fileverse-data/ using fs.writeFileSync. It does not call the Fileverse SDK or any Fileverse API. It mimics IPFS-style CIDs but data stays on the local machine. This is a self-built encrypted file store, not Fileverse.
A judge from Fileverse will look for import { FileverseClient } from '@fileverse/...' or an API call to api.fileverse.io — neither exists.
What would make this pass: Replace the local file store in index.ts with actual @fileverse/sdk calls to write to Fileverse's IPFS-backed storage.