Loops HouseRahasya

NEAR HACKATHON
Team
1 member- ITOwner
itadori
Overview
rahasya (rahasya.chat) is a way to tap into private AI, paid for with almost any token: no account, email, card or subscription.
Problem: private or uncensored AI is usually still tied to you by a subscription tied to your card and identity, and "private" is a promise users cannot check. What I built:
(1) Private funding through NEAR Intents 1Click: deposit any of 200+ tokens on 35+ chains with no card or account, including straight from a shielded pool (the demo pays shielded ZEC from the Ironwood pool, so the payer stays private; the amount and the delivery on Base are public); it is swapped to USDC on the user's own Base address, which buys Venice inference credit over x402.
(2) Non-custodial wallets: one signature from the user's NEAR, EVM or Solana wallet derives a separate inference wallet in the browser; it signs every request (Sign-In-With-X), is billed per request, and is never stored.
(3) Truly private mode: prompts are end-to-end encrypted in the browser to models in TEE enclaves (DeepSeek V4.1 Flash 1017 in a NEAR AI enclave, per Venice's attestation); the browser checks a fresh nonce, the Intel TDX quote and the enclave-bound key before sending, and shows the proof. (4) Developers: OpenAI-compatible API keys with server-enforced spend limits, model allowlist and expiry (these spend from a separate server-held wallet that only ever holds non-withdrawable credit), and an open-source local proxy (npx rahasya) that signs with the user's own wallet, so requests, including end-to-end encrypted TEE requests from scripts, never pass through our server. NEAR's role: Intents is the cross-chain settlement that turns those tokens into credit, NEAR wallets work as the login, and the default private model runs in a NEAR AI TEE enclave (as reported by Venice's attestation; the Intel TDX proof is verified in the browser, the enclave software measurement is not yet pinned).
Tracks: privacy (main) and security.