Skip to content

Open Grant Proposal: Dokrypt — Filecoin/FVM Development Toolkit #2048

@utabk

Description

@utabk

Open Grant Proposal: Dokrypt — Filecoin/FVM Development Toolkit

Name of Project: Dokrypt — Filecoin/FVM Development Toolkit

Proposal Category: Developer Tools & Libraries

Proposer: dokrypt-org

Do you agree to open source all work you do on behalf of this RFP?: Yes (Apache-2.0)


Project Description

Dokrypt is an open-source Web3 development toolkit (CLI) that simplifies dApp development with project scaffolding, local chain management, state snapshots, chain forking, and stress-test scenarios. Think of it as "Docker for Web3" — currently supporting EVM chains (Ethereum, Arbitrum, Polygon, Base, Optimism).

We propose adding first-class Filecoin/FVM support to Dokrypt, enabling developers to:

  1. Scaffold FVM projects with a built-in fvm-basic template including FEVM smart contracts, storage deal helpers, and pre-configured local Filecoin node setup
  2. Test storage deals locally with commands to create, verify, and retrieve mock storage deals against a local Lotus devnet
  3. Fork Filecoin mainnet/calibration for testing against real state
  4. Run FVM-specific stress-test scenarios (storage price spikes, deal expiry, sector faults)

This lowers the barrier to entry for Filecoin development significantly — new developers can go from zero to a working FVM project in under 60 seconds.

Value

What are the benefits to getting this right?

  • Dramatically reduces onboarding friction for FVM developers
  • Provides reproducible local testing for storage deals without needing real FIL
  • Brings battle-tested DX patterns from EVM tooling (Hardhat/Foundry-style) to the Filecoin ecosystem
  • Increases the number of developers building on FVM

What are the risks if we don't get it right?

  • FVM developer experience remains fragmented
  • Developers default to EVM-only chains due to easier tooling
  • Storage deal testing continues to require testnet FIL and slow feedback loops

What are the risks that will make executing on this project difficult?

  • Lotus devnet API compatibility may differ from mainnet
  • FVM is still evolving; we'll need to track breaking changes
  • Cross-platform support for Lotus node binaries

Deliverables

Milestone 1 — FVM Project Template & Local Node ($12,000, 3 weeks)

  • Built-in fvm-basic project template with:
    • FEVM smart contracts (Solidity targeting FVM)
    • Storage helper contracts
    • Pre-configured dokrypt.yaml for Filecoin local node
    • README with FVM-specific guides
  • dokrypt up support for starting a local Lotus devnet
  • dokrypt init --template fvm-basic scaffolding
  • Unit + integration tests
  • Documentation on docs.dokrypt.com

Milestone 2 — Storage Deal Testing Commands ($12,000, 3 weeks)

  • dokrypt storage create — Create mock storage deals on local devnet
  • dokrypt storage verify — Verify deal status and retrieval
  • dokrypt storage list — List active deals with status
  • dokrypt storage import — Import data for storage deals
  • Gas estimation for storage-related transactions
  • Pre-funded test accounts with local FIL
  • Unit + integration tests
  • Documentation

Milestone 3 — FVM Scenarios & Polish ($6,000, 2 weeks)

  • FVM stress-test scenarios:
    • storage-price-spike — Simulate storage cost increases
    • deal-expiry — Fast-forward time to expire deals
    • sector-fault — Simulate sector faults and penalties
  • Chain forking support for Filecoin mainnet and calibration testnet
  • End-to-end testing of full workflow
  • Tutorial: "Build Your First FVM dApp with Dokrypt"
  • npm + Docker release with FVM support

Total Budget

Milestone Duration Cost
M1: FVM Template & Local Node 3 weeks $12,000
M2: Storage Deal Commands 3 weeks $12,000
M3: FVM Scenarios & Polish 2 weeks $6,000
Total 8 weeks $30,000

Maintenance and Upgrade Plans

  • Dokrypt is actively maintained (latest release: v0.1.4)
  • FVM support will be maintained as part of the core CLI
  • We will track FVM/Lotus API changes and update accordingly
  • Community contributions welcome via GitHub

Team

Links

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions