Skip to content

Adopt squid-evm-funding in Filecoin Pin #28

Description

@snissn

Goal

Adopt snissn/squid-evm-funding through a thin, interactive-only Filecoin Pin integration developed from upstream master, while keeping funded mainnet evidence as a separate release gate.

The active upstream draft is filecoin-project/filecoin-pin#637. The original in-repository implementation in filecoin-project#630 is closed as superseded.

Architecture Boundary

squid-evm-funding owns:

  • Squid token-catalog, quote, and status behavior;
  • exact FIL and USDFC shortfall route planning;
  • safe EVM approval and route execution;
  • route, spender, balance, nonce, and transaction-fee validation;
  • destination-balance verification and sensitive-value redaction.

Filecoin Pin owns:

  • authoritative FIL and USDFC wallet-shortfall calculations;
  • Filecoin Pay deposit behavior;
  • selected source-chain policy, source limits, CLI options, prompts, and RPC/environment resolution;
  • the atomic pending marker that blocks a blind retry after interrupted execution.

The integration is intentionally limited to interactive payments fund on Filecoin Mainnet with owner private-key authentication. payments setup --auto, Calibration, and devnet behavior remain unchanged.

Issue Graph And Gate Ownership

Issue or PR Role Status Authoritative gate
squid-evm-funding#10 reduced library API Merged Exact-head review and cross-platform CI passed; v0.1.0 is released. Upstream acceptance of the dependency form remains part of #31/filecoin-project#637 readiness.
#29 original thin-integration implementation Closed Historical implementation record; final scope was narrowed to interactive payments fund.
#30 deterministic validation and upstream draft Closed Current-head local validation passes and filecoin-project#637 remains the single upstream draft.
#31 funded mainnet evidence Open Representative execution proves arrival, deposit, and no duplicate acquisition before filecoin-project#637 becomes ready for review.
squid-evm-funding#10 -> #637 deterministic/CI validation -> #31 funded evidence -> ready-for-review decision

Existing Work Disposition

Documentation Minimality

  • Keep README/help changes short and task-oriented.
  • Define only provider-specific terms that developers need; do not add glossary entries for ordinary operational phrases.
  • Keep funded evidence and generated reports outside the repository.
  • Avoid route decision records or operator artifacts unless maintainers request them.

Performance Classification

The integration is possibly performance-relevant only for provider/RPC call behavior. Zero-shortfall paths make zero Squid/source-RPC calls and provider polling is bounded. No throughput benchmark is required.

Completion

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions