About ShieldCard

Built for Teams That Cannot
Afford Leaks

Corporate spend on a public chain is public. Competitors can see your vendor relationships, budget allocations, and approval patterns. ShieldCard makes spend policy enforceable without making it visible.

We built ShieldCard on Fhenix CoFHE because the problem requires stateful computation over encrypted data — not just hiding values, but enforcing policy rules on values that must remain sealed across the entire lifecycle of a request.

From Proof of Concept to Production

1

Private Approval Engine

First encrypted spend approval on Arbitrum Sepolia. Employees submit amounts sealed with Fhenix CoFHE; the contract evaluates policy without seeing the value.

2

Policy Engine

Four policy packs, three-tier FHE routing (auto-approve / review / deny), and rolling encrypted department budgets.

3

Treasury Control Plane

Departments, vendor compliance registry, risk routing, recurring spend controls, and a multi-approver settlement vault.

4

Complete Treasury Product

Scoped auditor access with per-request disclosure grants, hash-chained tamper-evident receipts, wallet-free public verification, and one-click self-deployment.

Why Fhenix CoFHE

CoFHE lets contracts compute over ciphertext. FHE.add, FHE.lte, FHE.and, and FHE.select run on encrypted operands. No value is decrypted until the threshold MPC network produces a signed result. Correctness is secured by fraud proofs and EigenLayer economic staking.

Built by Vinay

Vinay is a builder embedded in the Indian Web3 ecosystem, co-founder of Vega Protocol, and host of the Buy High Sell Low podcast. ShieldCard was built during the Fhenix Privacy-by-Design Buildathon.