There is a short version of this argument: we build privacy tools, and it would be strange if the people building them weren't private themselves. That is the whole thing. But strange things deserve explanation, and there is more to say about why this is the right default rather than a convenient excuse.
The Consistency Argument
When a team builds tools for financial privacy while broadcasting their identities, salaries, home addresses, and family details to every intelligence service and regulator that wants them, something is off. Not ethically — nobody owes the public their personal information. What is off is the signal it sends about the product.
If the team does not trust their own privacy to the system they are building, why should users? The consistency of pseudonymous development is not a security precaution. It is a demonstration. We use what we build. We extend to ourselves the same posture we are extending to users.
Precedent in the Space
This is not unusual. The creator of Bitcoin is a pseudonym. The original Zcash Sprout ceremony was conducted in part by people who have never published their legal names. Dozens of significant DeFi protocols were built by teams who were, to varying degrees, not publicly identified.
The pattern holds because the logic holds: open-source code is accountable regardless of whether the author's face is attached to it. The code either does what it claims to do or it does not. The math either checks out or it does not. The protocol either holds under adversarial conditions or it does not. None of these properties change based on whether you know the author's passport name.
Pseudonymous Is Not Anonymous
These words are often used interchangeably, but they are meaningfully different and the difference matters here.
- Anonymous means no identity at all — no history, no reputation, no accountability surface. A truly anonymous team could ship and disappear.
- Pseudonymous means operating under a consistent identity that is not legally tied to a birth name. Satoshi Nakamoto is pseudonymous. The identity has years of history, decisions, statements, and a reputation that can be damaged.
Sanect operates pseudonymously. Our decisions are public. Our code is open. Our on-chain activity is traceable. The GitHub commit history is there. The architecture documents are there. The governance proposals, when they come, will be there. What is not there is a LinkedIn profile and a home address.
Accountability does not require identity. It requires consistency and visibility. Both of those we have.
The Counterargument We Take Seriously
There are two strong objections to pseudonymous development. We want to be honest about them rather than pretend they do not exist.
The first is venture funding. Most institutional capital requires KYC of founders. You cannot raise from a16z or Paradigm pseudonymously. This is a real constraint that limits certain growth paths. We are aware of it.
The second is user trust. Some users, particularly institutional ones, want to know who they are working with. They want faces, credentials, LinkedIn histories, and the implicit accountability that comes from someone having a career at stake. This is a legitimate preference and we are not dismissing it.
Our Answer: The Protocol Is Trustless By Design
The answer to both objections is the same: you should not have to trust us. That is not a deflection. It is the actual design goal.
Trustless means the system works correctly regardless of what the team does. The smart contracts are open source — you can read every line, or have someone you trust read them. The consensus rules are public. The cryptographic primitives are auditable. The chain state is verifiable by anyone running a node.
When the protocol is trustless by design, the team's identity becomes less load-bearing. What matters is whether the code does what it says. Open source mitigates the team trust issue in a way that no amount of founder credentials can match — because credentials can be faked, but math cannot.
We will pursue a professional audit before any mainnet deployment with real value at stake. The auditors will know exactly who we are. The audit report will be public. That is the accountability mechanism that matters, and it does not require your knowing our names.