Public key log
Contract ainek-log-dastan.testnet on testnet.
The code behind the key
The log above records keys and launcher configurations. The release that serves the model is in an action log the enclave keeps and attests; an entry says something about it only when its verifier writes release marks. The check below verifies, each time you ask, the hardware evidence of the replica that attests to this browser, then reads its action log and follows the release to public sources: NEAR AI's compose repository on GitHub and the signed build of the proxy image. Its last line says where the log above stands on that replica's action log: whether verifiers you trust have marked it as it stands. It runs in this browser and asks GitHub and Sigstore from your address, so it starts only when you ask. Each replica has a log of its own.
Who you trust
Site defaultThe chat sends a message only when verifiers on this list have logged the model key. You decide who counts. Your choice stays in this browser and applies from the next message.
- site default
This preview uses the newest key in the log. The chat runs the same check on the key the model attests. It also uses the deployment of that newest entry. The chat checks the deployment that attests to it, which may be another one behind the same key, so the chat can refuse where this says it would send.
On the hosted demo, the page that applies your choice comes from our server. To take us out of it, run the client from the repository.
Wallet
Connecting (top right) asks the wallet for a function-call key limited to commit_proof on this contract, so the chat can commit salted proof hashes without asking the wallet each time. The wallet decides the limit and may allow every method of this contract; once connected, the list below shows what the keys of this account allow. A function-call key cannot attach a deposit or call another contract.
No wallet connected.