20.7 Off-chain-computation trigger class

[determined-001]

Labels: type:feature area:workers needs-design type:security
Milestone: Phase 4 - Workers W2: external operators
Effort: High
Depends on: 20.6

Description

Third trigger class from §C.1: run when an external result lands - an oracle
resolves and settlement must execute, a model finishes an analysis and a position
must change.

This class is where verifiability gets hard, because the condition is not on
chain. The design must state what an off-chain condition means for 19.1's
verdicts: an unverifiable trigger is not a miss, and must not be scored as one.

Reflector Subscriptions already offers price-threshold triggers with webhook
notification (§C.8) and overlaps this use case. Position deliberately rather than
by accident.

Acceptance criteria

• Off-chain conditions are attested: the result carries a signature from a
  declared source, and the source is part of the manifest
• The attestation is submitted with, or referenced by, the invocation so the
  chain records why the worker fired
• Verification produces unverifiable rather than missed where the condition
  cannot be reconstructed from chain data
• unverifiable windows are excluded from reputation scores, not counted as
  successes
• Positioning against Reflector Subscriptions documented in the design note
• Security review covers a malicious or compromised computation source

Implementation notes

1. Decide the attestation model before writing code; needs-design clears on the
   design note.
2. Silently scoring unverifiable windows as successes turns the reputation score
   into a number operators can inflate by choosing unverifiable triggers.
3. Reuse packages/abi-registry/src/attestation.ts if its signature model fits
   rather than introducing a second attestation concept.

Affected files

• packages/worker-core/src/triggers/computationTrigger.ts
• packages/worker-core/src/triggers/attestation.ts
• packages/worker-core/src/verification/verdict.ts
• docs/design/worker-offchain-triggers.md

[Princeadim]

@Princeadim has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi maintener I would like to work on this issue please assign it to me

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Princeadim to this issue.

[royalTreasure]

@royalTreasure has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi, I would like to work on this issue. I will open a design note covering the attestation model, the positioning against Reflector Subscriptions, and the security review for a malicious or compromised computation source before writing any implementation code since needs-design clears on the design note and the attestation model decision propagates into every downstream component. I will implement the computation trigger in computationTrigger.ts requiring the result to carry a signature from a declared source that is part of the manifest, submit or reference the attestation with the invocation so the chain records why the worker fired, and add the unverifiable verdict to verdict.ts so windows where the condition cannot be reconstructed from chain data are excluded from reputation scores rather than silently counted as successes or misses. I will reuse packages/abi-registry/src/attestation.ts if its signature model fits rather than introducing a second attestation concept, and verify the security properties against the malicious computation source scenario documented in the design note before submitting. Can I be assigned?

ℹ️ Repo Maintainers: To accept this application, review their application or assign @royalTreasure to this issue.

[drips-wave]

Congratulations, @royalTreasure! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

🧑‍💻 @royalTreasure: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊