Security and limits

What protects you

• Read-only connections. Keys that can trade or withdraw are rejected. The assets stay at your exchange.
• Your key stays with you. A passkey lives in your device's secure hardware. A password key is encrypted on your device. Linvesther never sees either.
• Bounded traffic. Sign-in, connecting an account, actions that cost gas and public reads each have a per-client limit, the number of worker processes is capped, and a real proof runs one at a time.
• Nothing leaks in an error. Failures return a short code, never the text of what went wrong, and errors from an exchange are stripped of the address that carried your token or signature.
• Percentages only. No balance, position or trade is ever published.
• Exact consent. A claim is signed as a whole. Nothing can be added or changed after signing.
• No operator override. The registry contracts have no upgrade mechanism, and any party can submit a transaction, because your signature is what authorizes it.

Known limits

• Data comes from a collector. Linvesther reads your exchange with a read-only key. If the exchange or the collector supplied wrong data, a correct calculation gives a wrong result.
• Only what you connect. The record covers connected accounts, from the moment of connection. It cannot know about accounts you never linked.
• Sampled valuation. Values use prices sampled at a fixed cadence. The method is versioned and never changed silently.
• Disclosure is permanent. Once a statement is public, copies may exist elsewhere.
• No recovery. If you lose every way of signing in, the identity cannot be restored by anyone.
• Test network. The registry runs on Base Sepolia, a test network. It carries no economic finality.

Where things are heading

1. Zero-knowledge proofs for the combined record and for each claim, attached on-chain.
2. Stronger origin: authenticated sessions with exchanges and signed statements from institutions.
3. More exchanges and brokers, and more metrics with their own published methods.
4. A production deployment on Base after independent review.

Reporting a problem

Found something wrong? Open an issue on the project's GitHub repository. Please do not post secrets or account data.