Context
The TaskSubmission type and EventType::TaskSubmit already exist in the codebase but have no execution pipeline behind them. Currently only ordinary transfers flow through the Validator to Solver to TEE to DAG path. TaskSubmit is the intent-bound transaction type where PoCW scoring becomes meaningful since solver competition and causal work actually apply.
Builds on the flat-fee transfer mechanism from #8.
Scope
- HTTP endpoint for submitting tasks (
POST /api/v1/task)
- Solver execution of tasks through TEE with state changes and gas metering
- TaskSubmit events in the DAG with
executed_by and EventMetrics
- Formula-based burn for tasks (not flat fee) using
FluxConfig coefficients
- Fold observer and processor handle TaskSubmit events alongside transfers
- Pipeline starts with single-solver execution, but should be structured so that multi-solver fan-out (same task sent to N solvers, best output selected via
task_id grouping) can be added without reworking the core flow
Context
The
TaskSubmissiontype andEventType::TaskSubmitalready exist in the codebase but have no execution pipeline behind them. Currently only ordinary transfers flow through the Validator to Solver to TEE to DAG path. TaskSubmit is the intent-bound transaction type where PoCW scoring becomes meaningful since solver competition and causal work actually apply.Builds on the flat-fee transfer mechanism from #8.
Scope
POST /api/v1/task)executed_byandEventMetricsFluxConfigcoefficientstask_idgrouping) can be added without reworking the core flow