Sanect is a portmanteau. Sanctuary and Connect, collapsed into five letters. That is the whole explanation of the name — but it is not the whole story of what the name does.
Most projects choose a name and then figure out what to build. We did it the other way. The tension between these two words was identified first, as a design problem. The name came from that tension, not the other way around.
Sanctuary: What We Mean By It
A sanctuary is a protected space. It is defined by what cannot enter it — outside observation, unwanted interference, the gaze of those who have not been invited. When applied to a blockchain, sanctuary means that the contents of a transaction are visible only to the parties involved. Not to validators. Not to block explorers. Not to governments, corporations, or competitors watching on-chain.
This is not a new idea. Zcash, Monero, Tornado Cash, Railgun — privacy in blockchain has a long and technically serious history. What changes with Sanect is the default. Most privacy protocols treat privacy as a mode you enter deliberately: a special address type, a separate pool, an opt-in mechanism. Sanect is being built so that privacy is the baseline, not the exception.
Connect: What We Mean By That
Connect means the opposite of isolation. A blockchain that no one can use with the tools they already have is a sanctuary that nobody enters. EVM compatibility is not a technical convenience — it is a statement about who we are building for.
When Sanect runs EVM-compatible smart contracts accessible via MetaMask, that is a Connect decision. When we chose Cosmos SDK with its IBC interoperability layer, that is a Connect decision. When we decided that our privacy tools should work without installing a new wallet, a new browser extension, or learning a new address format, that is a Connect decision.
Connect means: meet users where they are. Build bridges, not islands.
Why the Tension Is Intentional
Here is the difficult part. Sanctuary and Connect are in genuine conflict with each other. Making something more private often makes it harder to connect with. Making something more interoperable often means exposing more about what is happening inside it.
Most privacy projects resolve this tension by picking a side. Monero chose sanctuary so completely that it cannot be listed on most exchanges. Ethereum chose connect so completely that every transaction is a public broadcast. Neither is wrong — they are honest about their priorities.
Sanect's position is that the tension should not be resolved. It should be held. Every architectural decision we make is evaluated against both constraints simultaneously: does this preserve sanctuary? Does this preserve connect? If the answer to either is no, we look for a different approach.
How the Name Shapes Architecture
This is not philosophy for its own sake. The name has produced specific technical choices:
- MetaMask-native (Connect). Users add Sanect to MetaMask the same way they add any EVM chain. No new wallet required. This was non-negotiable from day one.
- Shielded transfers (Sanctuary). The privacy pool uses UltraHonk zk-SNARKs via Noir circuits — no per-circuit trusted setup, no surveillance window — to allow transfers where only the sender and recipient can see the amount and destination.
- Dual transfer paths. Public transfers work exactly like Ethereum. Shielded transfers route through the privacy pool. Both paths move the same token. Users choose based on what they need, not what the protocol forces.
- EVM chain ID 7628. Just a Sanect chain. Your DeFi tooling, your hardware wallets, your block explorers — they all treat this like any other EVM chain.
Why Not "Shield" or "Privacy" or "Anon"
These are features, not philosophies. A feature can be toggled. A feature can be deprecated. A feature can be present in the marketing copy and absent in the code.
A philosophy embedded in the name is harder to walk away from. When we say Sanect, we are saying the duality is permanent. There is no version of this project where we decide Connect is too hard and become a sealed sanctuary. There is no version where we decide Sanctuary is too complicated and become just another public EVM chain.
The name is the constraint. That is why it matters.