Encrypt on the user's device
The zCred SDK encrypts credentials to the enclave's public key. Data leaves the device sealed, and no server, RPC node or operator can read it.
P-521 ECDH · AES-256-GCM
zCred lets institutions evaluate offchain records privately and gives smart contracts a signed eligibility decision, without handing sensitive identity documents to every app.
zCred separates where sensitive evidence is evaluated from where decisions are verified. Raw data never touches the chain, and contracts verify a signed cryptographic decision.
The zCred SDK encrypts credentials to the enclave's public key. Data leaves the device sealed, and no server, RPC node or operator can read it.
P-521 ECDH · AES-256-GCM
A Horizen Vela node decrypts and runs the policy inside a hardware-isolated AWS Nitro enclave. Memory is wiped as soon as the decision is made.
Rust → WASM · Wasmtime
The enclave signs a 171-byte attestation anchored to the Base Sepolia registry. Contracts verify it with a single view call. Onchain enclave-attestation verification is on the roadmap.
EIP-712 · Base Sepolia
Our core focus is Compliance Shield. All policies evaluate sensitive credentials inside the same hardware enclaves and settle signed verdicts to Base.
For RWA issuers, institutional pools, and compliant Web3 venues
Run KYC, sanctions screening, and investor accreditation without ever custodying personal identity documents. Your smart contracts receive one compact verdict. Your servers store zero PII.
What your contract sees
Result: 1 byte status · 32 byte nullifier · EIP-712 signature. Zero raw PII onchain.
For DeFi lending & undercollateralized credit
Evaluating offchain bank cashflows and treasury balances inside hardware enclaves to emit private credit tiers (AAA to BBB) for dynamic collateral ratios.
For autonomous agent payment & spending rails
Cryptographically verifying autonomous agent code provenance and enforcing onchain transaction thresholds directly from hardware enclaves.
Data minimization is built into the architecture, not left to policy. Compliance teams can see exactly what leaves the enclave.
Total footprint: 171 bytes per attestation
Your protocol never handles personal data. Check a user's zCred status directly from Solidity with ~2,520 gas and keep your compliance surface at zero.
import { IZcredRegistry } from "./IZcredRegistry.sol";
contract RwaPool {
IZcredRegistry constant ZCRED = IZcredRegistry(REGISTRY);
uint8 constant COMPLIANCE_SHIELD = 2;
uint8 constant ACCREDITED = 1;
function invest(bytes32 nullifier) external payable {
(bool valid, uint8 status, , ) =
ZCRED.getAttestation(COMPLIANCE_SHIELD, nullifier);
require(valid && status == ACCREDITED, "accreditation required");
// ... mint pool shares
}
}No. Data is decrypted strictly inside an isolated hardware enclave, evaluated against the policy bytecode, and immediately zeroized from memory upon execution. The only artifact that persists is an EIP-712 signed attestation containing a 1-byte status, nullifier, and expiry timestamp.
The institution operates as the Rule Owner: you define the qualification criteria, sanction lists, and approved evidence sources. zCred functions as confidential decision infrastructure that executes your policy in an isolated environment without custodying your users' records.
A standard smart contract view call costs ~2,520 gas (1 SLOAD). Full contract gating in an invest or mint transaction typically consumes under 26k gas. In contrast, verifying complex ZK circuits on-chain can cost 250k–500k+ gas and requires expensive off-chain proof generation for multi-source data.
zCred settles to Base today, with contracts live on Base Sepolia. The registry is a standard EVM contract deployable to any EVM L1 or L2 network, backed by Horizen Vela confidential coprocessing.
zCred is active on Base Sepolia testnet with 99 passing test suites. Independent third-party security audits and direct onchain hardware PCR0 measurement verification are scheduled ahead of mainnet. We are currently onboarding initial design partners for our scoped pilot program.
Scope one evidence source, one policy rule, and one contract gate. Benchmark review speed, zero-leak isolation, and onchain gas overhead for your protocol.