Repository navigation
Conversation
This was referenced Oct 14, 2026
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.
NEAR’s configured GLM-5.3-Flash model supports native encrypted function schemas, arguments and tool-result history. Add an experimental codec and bounded synthetic qualification CLI that verifies the attested model’s signature over the declared request hash and complete response before releasing tools to Pi. The server’s trusted-gateway request-hash override is documented as a separate integrity trust dependency: a matching signed hash alone cannot prove the input body actually received by the model. Consolidate authenticated function-name fragments for Pi’s parser and provide the required compatibility settings.
Live evidence (2026-10-14): two consecutive native echo calls passed; a separate echo/result/final-answer round trip passed. Six POSTs total; catalog-priced signed token usage estimates $0.00022808 against the authorized $0.25 cap. Gateway TCB is OutOfDate (four Intel advisories), model TCB is UpToDate. Strict admission fails; protocol-only evidence used the existing reported-TCB policy with quote/key/GPU/compose/registry/TLS checks retained. Source-to-deployment closure is not established. Normal providers/configuration are unchanged and private-work enablement is not claimed.
Validation: 15 codec/actual-Pi tests plus six existing signature tests pass; seven new offline deployment-evidence tests pass; 172 local documentation links/fragments pass; syntax, import and whitespace checks pass. All six saved live model-signature proofs were reverified after final metadata/SDK hardening. Local tests reused the existing compiled Pi/ACI outputs; this is not a fresh installed-release or full integration-gate pass. The earlier full-gate failures remain separately recorded in #74. No new heavy build was run on the laptop.
The CLI encrypts known sensitive fields, refuses unsupported API surfaces, never retries POSTs, and holds a locked persistent budget ledger. Raw evidence/credentials are not published. Remaining work: source/deployment closure, request-hash authority and privileged gateway credential custody, independent review and applicable integration qualification before ordinary-provider migration.
Relates to #73, #56 and #48; research amiller/awesome-private-inference#23 and DevProof amiller/devproof-audits-guide#5. Based independently on hosted main 7c1d9fa, not stacked on unreviewed #74.
Read-only deployment checks now retain exact attestation responses and verify the manager quote, canonical action digest, fresh nonce and matching model measurements. A genuine quote passed and a modified quote was refused. The last recorded deployment file matches its reported public commit/hash. Current manager source uses canonical sorted-key JSON, so formatting changes do not necessarily break digest verification; exact bytes support legacy variants and review. These results authenticate history rather than active state: compose actions can be logged before success. The new capture has different model outer-compose bytes from earlier native-tool observations, which are kept separate. Gateway forwarding and TOKEN/PROXY_TOKEN configuration are source-traced; deployed token custody and source/image closure remain open in #77. No additional inference POSTs or policy changes.