Monorepo for the Filecoin Pay ecosystem: subgraph, shared types/configs, UI library, and frontend apps.
- apps/
- packages/
- Node >= 22
- pnpm >= 9
Follow these steps to set up and run the applications:
Install all dependencies for the monorepo:
pnpm installSet up environment variables for the apps you want to run. You'll need the subgraph URLs for your Filecoin Payments Subgraph. If you need to deploy your own subgraph, see the subgraph deployment guide.
For Explorer app:
cd apps/explorer
cp .env.example .envEdit apps/explorer/.env and configure:
NEXT_PUBLIC_SUBGRAPH_URL_MAINNET=https://api.goldsky.com/api/public/project_xxx/subgraphs/filecoin-pay-mainnet/version/gn
NEXT_PUBLIC_SUBGRAPH_URL_CALIBRATION=https://api.goldsky.com/api/public/project_xxx/subgraphs/filecoin-pay-calibration/version/gnReplace the placeholder URL with your actual Filecoin Payments Subgraph endpoint.
NEXT_PUBLIC_SUBGRAPH_URL_MAINNET and NEXT_PUBLIC_SUBGRAPH_URL_CALIBRATION are required for the Explorer app to function.
For Metrics app:
cd apps/metrics
cp .env.example .envEdit apps/metrics/.env and configure:
VITE_GRAPHQL_ENDPOINT=https://api.thegraph.com/subgraphs/name/your-username/filecoin-paymentsReplace the placeholder URL with your actual Filecoin Payments Subgraph endpoint.
Note: VITE_GRAPHQL_ENDPOINT has a default fallback (http://localhost:8000/subgraphs/name/filecoin-payments) but should be configured for production use.
Return to root directory:
cd ../..- Explorer app depends on:
@filecoin-pay/typesand@filecoin-pay/ui - Metrics app depends on:
@filecoin-pay/types
Build all shared packages (recommended):
pnpm build --filter @filecoin-pay/types --filter @filecoin-pay/uiOr build only what you need:
# For Explorer only
pnpm build --filter @filecoin-pay/types --filter @filecoin-pay/ui
# For Metrics only
pnpm build --filter @filecoin-pay/typesThis step is required for both development and production environments.
Run all apps:
pnpm devRun Explorer only:
pnpm dev --filter @filecoin-pay/explorerRun Metrics only:
pnpm dev --filter @filecoin-pay/metrics1. Build the application(s):
# Build everything (recommended)
pnpm build
# Or build specific apps
pnpm build --filter @filecoin-pay/explorer
pnpm build --filter @filecoin-pay/metrics2. Start the production server(s):
# Start Explorer (runs on http://localhost:3000)
pnpm start --filter @filecoin-pay/explorer
# Start Metrics (runs on http://localhost:4173)
cd apps/metrics
pnpm preview
cd ../..- Build all:
pnpm build - Build specific app:
pnpm build --filter @filecoin-pay/explorerorpnpm build --filter @filecoin-pay/metrics - Lint:
pnpm lint - Format:
pnpm format - Type check:
pnpm type-check - Test:
pnpm test - Clean:
pnpm clean(removes build artifacts and node_modules)
apps/explorer/— The Explorer app: a statically-built Next.js frontend for browsing Filecoin Pay rails, accounts, and deal activity. This is the primary focus of the repo.apps/metrics/— A Vite-based metrics dashboard. Not a current focus.packages/subgraph/— A The Graph subgraph hosted on Goldsky that indexes Filecoin Pay contract events on mainnet and Filecoin calibration testnet. See the subgraph architecture guide for its data model and Explorer integration.packages/ui/,packages/types/,packages/configs/— Shared libraries consumed by the apps.
- Static site — The Explorer is statically built and deployed to Vercel. Vercel is used for convenience; there is no server-side logic that requires it.
- Subgraph — Hosted publicly on Goldsky with no proxy layer. It is intended to be consumed only by the deployed static frontend.
Static site and subgraph deployments are separate. See the release checklist for post-deploy verification and production promotion.
- Static site changes deploy automatically via the Vercel GitHub App on merge to
main. - Subgraph releases run through the Release Please workflow. Merging its Release PR creates the tag and GitHub Release, deploys both Goldsky networks, and opens a tracking issue.
Uptime monitoring for the static site and subgraph is managed via FilOzone/infra and visible at status.filoz.org.
Subgraph releases are automated with Release Please:
- Give every PR a Conventional Commit title, such as
feat:,fix:, orchore:. The PR title check enforces this because squash merges use the PR title as the commit onstaging. - When releasable subgraph changes reach
staging, Release Please opens or updates a Release PR targetingstaging. That PR bumps the subgraph version and updatespackages/subgraph/CHANGELOG.md. - Merge the Release PR to create the tag and GitHub Release, deploy calibration and mainnet to Goldsky, tag both as
staging, and open a release tracking issue. Do not create the release tag manually. - Use the tracking issue to confirm indexing and smoke-test the Explorer on staging.
- Merge the promotion PR (
staging → main). This applies theprodtag on Goldsky automatically, switching pay.filecoin.cloud to the new fully-indexed subgraph.
See release-please-config.json and .release-please-manifest.json for version tracking configuration.
- Use Node/pnpm versions from root
package.jsonengines. - Use Conventional Commits for PR titles (e.g.,
feat:,fix:,chore:). - Run
pnpm lint,pnpm format, andpnpm type-checkbefore committing. - See per-package READMEs for details.
- Contracts: https://github.com/FilOzone/filecoin-pay
- Explorer: https://github.com/FilOzone/filecoin-pay-explorer
Dual-licensed: MIT, Apache Software License v2 by way of the Permissive License Stack.