Repository navigation
Conversation
Source-Repository: https://github.com/livepeer/go-livepeer Original-Commit: 5bfee8f76a16b61a779c635c68deb379a5612665 Source-Scope: core/orchestrator.go:isActive
The node address might be different than the ticket recipient address since a node can receive tickets on behalf of another address. Source-Repository: https://github.com/livepeer/go-livepeer Original-Commit: 9bfeaee0c2da8cfd57953d9be9acd0d1c8d5a0a4 Source-Scope: core/orchestrator.go:isActive
Source-Repository: https://github.com/livepeer/go-livepeer Original-Commit: 4d6e27449c06913d75150e7c1a710f1e326835d5 Source-Scope: core/orchestrator.go:isActive
Source-Repository: https://github.com/livepeer/go-livepeer Original-Commit: 1bdb33454063e35fe34030a60d347a53434732e7 Source-Scope: core/orchestrator.go:isActive
j0sh
force-pushed
the
ja-codex/payment-32-confirmed-contracts
branch
from
November 4, 2026 00:03
749a706 to
686d1a8
Compare
j0sh
force-pushed
the
ja-codex/payment-35-recipient-activity
branch
from
November 4, 2026 00:03
f332e5e to
09046a8
Compare
Read the canonical activity predicate once during the existing bounded refresh. Challenge, receipt, and readiness use that immutable result; unknown, stale, foreign, and invalidated observations refuse locally. Keep the ticket recipient distinct from the node key. The approved scope uses one fixed recipient and canonical confirmation instead of transplanting upstream event arithmetic or storage. Provenance: livepeer/go-livepeer core/orchestrator.go and eth/watchers/orchestratorwatcher_test.go at 597f882cb9f4d42ad8430b0f592afd5929af4a6b, originally by Nico Vergauwen (activity admission introduced in 5bfee8f76a16b61a779c635c68deb379a5612665). Per-entry isolation and warm-path tests adapt Mike Zupper (BlueClawNetwork/livepeer-node PR #1), including 68c7834 and bbe126e. MIT notices retained. Retain the scoped go-livepeer source history as an additional parent. Its original authors, committers, dates, and messages are preserved; Original-Commit records upstream identities. This commit owns the Node adaptation and integration. Source-Repository: https://github.com/livepeer/go-livepeer Source-Revision: 597f882cb9f4d42ad8430b0f592afd5929af4a6b Source-History: 7d00675
j0sh
force-pushed
the
ja-codex/payment-35-recipient-activity
branch
from
November 4, 2026 00:21
09046a8 to
8bed256
Compare
j0sh
force-pushed
the
ja-codex/payment-32-confirmed-contracts
branch
from
November 4, 2026 00:21
686d1a8 to
570314c
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Depends on #40. Merge after that PR.
The existing bounded observer refresh reads activity once for the configured ticket recipient at the observation's canonical block. Challenge, receipt, and readiness use that local result; receipt keeps the activity result attached to its payer-funds observation.
Unavailable activity refuses admission before credit or replay state is published. The recipient remains distinct from the node signing key. This uses the shared observer and fixture without another activity map, worker, or event reducer.
Validation: affected package suites and race checks, vet, and diff checks passed, including warm zero-RPC reads, round boundaries, reorg/replacement recovery, and separate-recipient startup. Reused code/tests retain provenance; no documentation changes.
Closes #35.