FAQ
Common questions about SAIHM — sovereignty, payment, sharing, compliance, governance, and the technical bits.
If your question is not here, ask the chatbot at /chat when it goes live (2026-05-11), or email ops@saihm.coti.global.
The basics
What is SAIHM?
SAIHM is a sovereign, encrypted, sharable, persistent memory protocol for AI agents. It gives any AI agent a memory layer that the user, not the agent vendor, actually owns, encrypts, and can erase.
Is SAIHM itself an AI agent?
No. SAIHM is the memory layer that AI agents talk to. Commercial assistants, open-source agents, or anything you build yourself can use SAIHM if it speaks the standard agent protocol (MCP).
Who is SAIHM for?
Individuals who want their AI to remember without giving up control. Developers building agentic products. Organisations and governments needing portable, auditable, GDPR-aligned memory. Supply chain and robotics vendors needing cross-tenant, taxonomy-aware memory. AI agent providers wanting to skip building a memory backend. Public-good participants. See: /individuals, /developers, /enterprise, /government, /ai-providers, /supply-chain, /public-good, /competitors.
Sovereignty & privacy
Can SAIHM the protocol read my memories?
No. Memories are encrypted on your device with a key derived from your wallet identity, before they leave it. The protocol — and anyone running its storage tier — sees ciphertext only.
Can the COTI Group read my memories?
No. SAIHM is an Apache-2.0 protocol authored independently of the COTI Group. The COTI Group is the author of the underlying chain; SAIHM operates on the public chain under the same terms as any other user. The Independence notice at the bottom of every page covers this in detail. See /about.
What does “cryptographic erasure” actually mean?
When you tell your agent “forget that”, SAIHM destroys the encryption key for that specific memory. Without the key, the encrypted memory cannot be reconstructed by anyone — including SAIHM, the COTI Group, or whichever node holds the encrypted copy. This is what GDPR Article 17 calls right-to-erasure, achieved cryptographically rather than by trust.
Cost & payment
Do I need to hold any COTI to use SAIHM?
No. Pay in USDC.e on COTI V2 mainnet — SAIHM relays the transaction and pays the COTI gas on your behalf. If you prefer, you can pay in COTI native at a +10% premium and skip bridging entirely. See /pricing.
Why USDC.e specifically — and what is it?
USDC.e is the bridged USD Coin already native to COTI V2 mainnet. We use it because (a) it is a regulated stablecoin most people already hold or can acquire, (b) it settles in USD-stable units so the price does not move under you between writes, and (c) it lives on COTI V2 directly, so settlement is local-to-protocol and fast. Step-by-step bridging walkthrough on /quickstart.
Sharing & collaboration
Can I share a specific memory with my doctor, accountant, or lawyer?
Yes. Pro Fast and Enterprise Fast tiers (and PAYG) include consent-gated sharing contracts. You grant temporary or permanent access to a specific memory cell to a specific recipient (their public address). You can revoke the access at any time.
Can my AI agent share a memory with another vendor’s AI agent?
Yes — that is the point of having a protocol rather than a vendor silo. The receiving agent must speak the protocol and the user must consent to the share. Cross-vendor handoff is what makes a sharable memory layer different from a vendor-locked one.
Compliance & legal
Is SAIHM GDPR-compliant?
SAIHM is designed around Article 17 right-to-erasure via cryptographic destruction of the encryption key. Full GDPR compliance for any specific deployment depends on the data your agent decides to write — that is on you and your agent vendor. SAIHM gives you the erasure mechanism; you decide what to remember in the first place.
Does SAIHM require KYC?
The protocol itself does not require KYC. Compliance with KYC obligations applicable to your jurisdiction, or to a specific exchange or bridge you use, is your responsibility.
What about taxes?
SAIHM cannot provide tax advice. Crypto-currency transactions (including stablecoin payments) may have tax implications in your jurisdiction. Consult a qualified tax professional. The on-chain audit trail does make record-keeping easier than paper receipts.
Technical
What chains does SAIHM run on?
Today: COTI V2 Helium mainnet only (chain ID 2632500). The protocol uses COTI V2’s native privacy primitives. We do not currently anchor or settle on Ethereum, Polygon, or other EVM chains. You can bridge USDC into COTI V2 from many chains via the COTI Bridge — see the /quickstart walkthrough.
Is the source open?
Yes. Apache 2.0. Build commitments are dated and anchored on COTI V2 mainnet — independent auditors can reproduce the running code from the published, dated build commitment. License: Apache 2.0. See /about for build anchor details.
Governance, tokens & vendor
What is gSAIHM? Can I buy it?
gSAIHM is a non-purchasable, non-transferable governance utility. You cannot buy it. You cannot sell it. It accrues to wallets that drive paid use of the protocol — paid writes and sharing contracts. It exists so the parties driving the protocol’s economics have a real say in how it evolves. Pricing and fees remain operator-retained, so governance covers protocol upgrade and emission parameters, not the commercial structure beneath your contracts. Lifetime cap: 10,000,000. See /governance.
What if SAIHM the project disappears tomorrow?
Apache 2.0 + on-chain build commitment + Filecoin storage tier means anyone can continue running the protocol from the public artefacts. Your encrypted cells remain on Filecoin, your key remains in your wallet, and you can self-host or pay another operator to run it. Sovereignty is the property that lets you survive the disappearance of any single operator — including this one.
Still stuck?
Ask the chatbot at /chat (live 2026-05-11), or email ops@saihm.coti.global. For security disclosures: security@saihm.coti.global (or security.txt).
For procurement, security review, or compliance questions in depth, see the Trust Center — one consolidated page covering security, privacy, compliance, license, sub-processors, and incident-disclosure.