VeilPay
End-to-end encrypted payroll infrastructure. Employers assign salaries, employees decrypt only their own — no amount ever touches the chain in plaintext.
Input the amount — it's encrypted off-chain inside an Intel TDX enclave. What hits the chain is just a 32-byte handle, never the number.
Each employee decrypts only their own salary — gasless, ACL-gated. Nobody else can read the figure.
On claim, the owed balance resets to an encrypted zero. Public infra stays transparent; only the numbers stay private.
Salaries stored as euint256 in a TEE. Plaintext never reaches the chain.
Employees decrypt only their own figure — gasless, ACL-gated by iExec Nox.
Public infra stays transparent. Privacy without breaking DeFi composability.
Works with any wallet: MetaMask / Rabby / Coinbase (browser extension on desktop), or scan with WalletConnect on mobile (MetaMask mobile, Rainbow, Rabby, Safe). Use the Sepolia test network.
Assign an encrypted salary. The amount is encrypted off-chain in a TEE — never stored in plaintext.
Decrypt your own salary (gasless, ACL-gated) and claim it. Nobody else can read your figure.
Deploy VeilPay for your team. Confidential by design, composable by default.
VeilPay is confidential payroll infrastructure built on iExec Nox. It lets companies run on-chain payroll without exposing any salary in plaintext — solving a privacy gap that blocks real adoption of on-chain compensation.
On a normal smart contract, every salary is public forever. Anyone with an explorer can see exactly what each employee earns. That leaks compensation bands to competitors, exposes individuals to targeting, and is a non-starter for real companies. Transparency is good for the ledger — not for people's pay.
Each salary is encrypted off-chain inside an Intel TDX enclave using the Nox SDK. What lands on-chain is only a 32-byte handle — a pointer to encrypted state, never the number. The contract stores an euint256; the plaintext never exists on-chain.
| Aspect | Plain contract | VeilPay (Nox) |
|---|---|---|
| Salary visible on explorer | Yes | No (handle only) |
| Employee reads own pay | Yes | Yes (gasless, ACL) |
| Third party reads pay | Yes | No |
| Contract / events transparent | Yes | Yes |
| Composable with DeFi | Yes | Yes |
Privacy and composability are usually framed as a trade-off. VeilPay shows they aren't: the public infrastructure (contract, events, ERC-20 rails) stays fully transparent and composable — only the numbers are private. That's the exact shape the WTF challenge asked for: take something public-by-design and add privacy with Nox, without breaking composability.
01 Employer assigns an encrypted salary → 02 Employee decrypts only their own (gasless, ACL-gated) → 03 Claim resets the owed balance to an encrypted zero. Try it live in the dApp below, or read the source on GitHub.