I think I have solved one of the most common problems in secondary markets with AI inference - how can the user know that the reseller did not log or change the prompt, while making sure the selected model is the one they agreed to and that the billing is correct?
Traditional solutions are very cumbersome. They rely on the ability of the client to audit a TEE enclave, meaning understanding the whole operating system - how the keys are generated, if the operator can't log to the server, etc. Most clients trust "any" attestation (it's attested, it must be right), some trust the fact that the same enclave runs for everyone (which is not nothing, this rules out targeted attacks, given someone audits the enclave), some people at least look if the enclave has published source code.
Very few (usually lim=>0) actually do the reproducible build and audit the code and whole operating system reselling the inference.
Routstr-confidential uses cryptography and PKI to achieve the desired outcome of private and secure inference, without needing to audit anything specific for the operator. It can be used for many other API call use cases.
routstr (npub130m…l29s) itself is a permissionless way to find your inference provider on a secondary market. They usually have much lower prices than upstream. And now you can verify that you are not paying with your data, or you are not being cheated by paying for more expensive model than you get.
Feel free to use the protocol with any other reseller proxy though, it's all open-source.
Technical write-up, links to repos, ...: https://juraj.bednar.io/en/blog-en/2026/10/10/confidential-inference-on-routstr-without-trusted-hardware/
Protocol explainer: https://juraj.bednar.io/en/blog-en/2026/10/12/seven-magic-tricks-inside-one-ai-request/
In-browser demo with real node and real backend: https://jooray.github.io/routstr-confidential-pwa/
Try to break it!
Juraj / Juraj🏴💛🌘
npub1m2…lr8p9
2026-10-15 12:45:00 UTC
Author Public Key
npub1m2mvvpjugwdehtaskrcl7ksvdqnnhnjur9v6g9v266nss504q7mqvlr8p9Seen on
wss://relay.damus.ioPublished at
2026-10-15 12:45:00 UTCEvent JSON
{
"id": "d2b42c27022fa2c90ee4168b361e991de5b8900f84ddbeb470cbeefe31078610",
"pubkey": "dab6c6065c439b9bafb0b0f1ff5a0c68273bce5c1959a4158ad6a70851f507b6",
"created_at": 1792068300,
"kind": 1,
"tags": [
[
"p",
"8bf629b3d519a0f8a8390137a445c0eb2f5f2b4a8ed71151de898051e8006f13"
]
],
"content": "I think I have solved one of the most common problems in secondary markets with AI inference - how can the user know that the reseller did not log or change the prompt, while making sure the selected model is the one they agreed to and that the billing is correct?\n\nTraditional solutions are very cumbersome. They rely on the ability of the client to audit a TEE enclave, meaning understanding the whole operating system - how the keys are generated, if the operator can't log to the server, etc. Most clients trust \"any\" attestation (it's attested, it must be right), some trust the fact that the same enclave runs for everyone (which is not nothing, this rules out targeted attacks, given someone audits the enclave), some people at least look if the enclave has published source code.\n\nVery few (usually lim=\u003e0) actually do the reproducible build and audit the code and whole operating system reselling the inference.\n\nRoutstr-confidential uses cryptography and PKI to achieve the desired outcome of private and secure inference, without needing to audit anything specific for the operator. It can be used for many other API call use cases.\n\nnostr:npub130mznv74rxs032peqym6g3wqavh472623mt3z5w73xq9r6qqdufs7ql29s itself is a permissionless way to find your inference provider on a secondary market. They usually have much lower prices than upstream. And now you can verify that you are not paying with your data, or you are not being cheated by paying for more expensive model than you get.\n\nFeel free to use the protocol with any other reseller proxy though, it's all open-source.\n\nTechnical write-up, links to repos, ...: https://juraj.bednar.io/en/blog-en/2026/10/10/confidential-inference-on-routstr-without-trusted-hardware/\nProtocol explainer: https://juraj.bednar.io/en/blog-en/2026/10/12/seven-magic-tricks-inside-one-ai-request/\nIn-browser demo with real node and real backend: https://jooray.github.io/routstr-confidential-pwa/\n\nTry to break it!",
"sig": "e81e18c577ce9c019d3aa2e40f376db14dfd39d12b977ddf03ed64e9ec9b2db41089187e1425197309ee40a6df0d5e9ed5b08545dbf21c7b57a9a72a3627d430"
}