-
Notifications
You must be signed in to change notification settings - Fork 16
feat(telemetry): realtime attested execution pools for AC and Prism #46
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.
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
echobt
merged 7 commits into
BaseIntelligence:main
from
alpha1122x:feat/realtime-execution-telemetry
Jul 27, 2026
Merged
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
c00d030
test(agent-challenge): add contracts for attested progress telemetry
echobt cd90e88
test(agent-challenge): add contracts for live execution pool
echobt a21e7ba
feat(agent-challenge): add attested progress and live pool telemetry
echobt e3fb72c
test(prism): add contracts for execution telemetry
echobt bbe5420
feat(prism): add execution events session and live pool
echobt 616e45c
test(master): add contracts for eval telemetry proxy and pools
echobt 016bff7
feat(master): allowlist eval telemetry and aggregate live pools
echobt File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🔒 Security & Privacy | 🟠 Major | 🏗️ Heavy lift
🧩 Analysis chain
🌐 Web query:
Phala Cloud CVM encrypted_env env_keys must be listed in app-compose allowed_envs💡 Result:
In Phala Cloud, when using a CVM (Confidential Virtual Machine) with on-chain Key Management Service (KMS), the list of environment variable keys provided in
env_keys(during an environment update) must correspond to theallowed_envswhitelist defined in the application'sapp-compose.jsonconfiguration [1][2]. Theapp-compose.jsonis a canonicalized JSON manifest that defines your application's settings, including theallowed_envsfield—a whitelist of environment variable names that your workload is permitted to read [1]. Becauseallowed_envsis a component of theapp-compose.jsonfile, any modification to this list (adding or removing an environment variable key) changes the manifest's contents, thereby generating a newcompose_hash[1][2]. This process necessitates a specific two-phase update flow: 1. Phase 1: You submit the newencrypted_envand the updatedenv_keyslist [3]. If these keys differ from the previously registered whitelist or if the on-chain configuration requires verification, the API will return acompose_hash[3][4]. 2. On-chain Registration: You must use thiscompose_hashto call theaddComposeHashfunction on the blockchain to register the new configuration [1][2]. 3. Phase 2: Once registered, you retry the environment update request, providing both thecompose_hashand the resultingtransaction_hashas proof of on-chain registration [5][3]. If you update the encrypted values of environment variables without changing the keys themselves, theallowed_envs(and thus thecompose_hash) remain unchanged, and the update can typically proceed without the two-phase on-chain registration flow [2].Citations:
🏁 Script executed:
Repository: BaseIntelligence/base
Length of output: 203
🏁 Script executed:
Repository: BaseIntelligence/base
Length of output: 347
🏁 Script executed:
Repository: BaseIntelligence/base
Length of output: 50377
🏁 Script executed:
Repository: BaseIntelligence/base
Length of output: 27029
🏁 Script executed:
Repository: BaseIntelligence/base
Length of output: 36969
Align Phala
env_keyswith the measuredallowed_envsbefore sending deploy secrets.EVAL_PROGRESS_BASE_URL,EVAL_RUN_ID,EVAL_SUBMISSION_ID, andRUNNER_HOTKEY_MNEMONICare encrypted asenv_keys, but the default measured compose andEVAL_ALLOWED_ENVSuseMEASURED_ALLOWED_ENVS, which drops those names. Phala CVMenv_keysmust match the composeallowed_envs; otherwise the runtime binding can fail or these telemetry/signing inputs won’t be injected to the CVM. Bind the progress inputs to a measured/compose-bound configuration instead of keeping an operator-shipped URL outsidecompose_hash.🤖 Prompt for AI Agents