Skip to content

Finalize v1 platform stack spec pass #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
snissn merged 2 commits into from
Jun 2, 2026
Merged

Finalize v1 platform stack spec pass #2

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
696893a
Finalize v1 platform stack spec pass
snissn Jun 1, 2026
65dcdf4
Resolve v1 spec review comments
snissn Jun 2, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 10 additions & 11 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,7 +36,7 @@ This repository is currently a draft specification and planning workspace.

See [`spec.md`](./spec.md).

The design is not production-ready and does not yet prescribe a single implementation path. It is intended to clarify the model, identify viable payment and signer options, and guide early compatibility work against FOC.
The design is not production-ready, but it now selects a v1 implementation path to validate: platform EOA/KMS payer, FOC session-key coordinator, hosted coordination, and onchain request/object/usage/receipt state. Future payment and coordinator modes remain compatibility-gated by Phase 0 evidence.

## Related projects

Expand All @@ -49,15 +49,14 @@ Together, these projects cover different layers of the FOC developer experience.

## Initial development direction

The draft spec keeps several implementation options open, including:
The current v1 direction is:
Comment thread
snissn marked this conversation as resolved.

- platform EOA/KMS payer,
- smart-account payer,
- contract treasury payer,
- prepaid user balances,
- credit/quota accounting,
- trusted coordinator finalization,
- stronger receipt/proof models,
- Token Host-generated contracts and UI.

The next recommended step is a compatibility spike against Filecoin Calibration to determine which FOC payment, signer, and coordinator models are currently viable.
- FOC session keys for coordinator execution,
- platform-hosted allowlisted coordinator,
- onchain request, object, usage, and compact receipt state,
- quota/credit-style accounting before contract-custodied user deposits.

Smart-account payers, contract treasury payment, direct browser-to-FOC upload, BYO coordinators, stronger proof models, and Token Host-generated production scaffolding remain compatibility-gated future paths.

The next recommended step is to complete the Phase 0 Filecoin Calibration compatibility report in `spec.md`, including required transaction hashes, pass/fail answers, SDK gaps, and the final recommended v1 mode.
Loading