teckel: Account & Identity
Every teckel product — the App, the AI toolkits, the Ethereum RPC service, IPFS storage — runs on one foundation: your account is a public Ethereum address. Understanding this takes two minutes, and it explains how everything else works.
Your account is a public Ethereum address
When you set up teckel, the App generates (or imports) a public Ethereum address. That address is your account ID — the unique identifier that ties your usage, your API key, and your teckel credit (tc) balance together. You can create as many as you like; each is a separate, self-sovereign account.
Your account holds no personal identity
teckel never logs your IP address, and opening an account needs no name, email, phone number or KYC documentation — your Ethereum address is the only identifier it holds, and it reveals nothing about who you are. Practices using Benedict add their practice details separately, because CQC paperwork has to carry them.
This isn't a privacy setting you switch on. It's how teckel is built: there's no personal identity attached to your account to leak, subpoena, or sell, because the account layer never collects it.
Patient data is different again, and the guarantee is stronger. Benedict is built so that patient identifiers never have to reach teckel at all: every field on every form is tagged, the personal-identifying ones can be left blank, and a blank one never blocks a submission. Your practice can complete a full compliance record without recording a single patient identifier — and that is enforced in the system, not promised in a policy.
How authentication works
Two credentials, both generated by the teckel App:
- Your account address — public; your identity.
- Your API key — secret; your authentication.
Call any teckel service — an MCP server, the RESTful API, an Ethereum RPC endpoint — and you authenticate with your API key as a Bearer token. The service recognizes your account, checks your tc balance, and runs your request. No login forms, no OAuth, no third-party identity providers.
How your tc balance is tracked
Your teckel credit (tc) balance is associated with your account address. Top up in the App via standard in-app purchase (Apple / Google billing, in GBP). The billing path is simply GBP → tc → services — no cryptocurrency to buy, no exchange to navigate, no on-chain transactions.
What it is — and what it isn’t
- An account identifier (like a username, but self-sovereign)
- An authentication primitive (paired with your API key)
- A ledger key (your tc balance lives here)
- NOT a crypto wallet you fund with ETH
- NOT a payment rail — no on-chain transactions ever occur
- NOT an investment or trading product
Built on this foundation
Every teckel tool authenticates the same way. Once you understand your account address and API key, you can use any of them — the AI toolkits, the Ethereum RPC service, IPFS storage, and teckel talk.
