Kaelis

Privacy-first token operations protocol and sybil resistant infrastructure by Passport . Built on iExec Nox.

[Wisdom Tek @agwuchikwendu]

This is exactly the direction I explored with Kaelis.

I took confidential tokens a step further into a practical distribution layer: encrypted allocations for

→ Payroll
→ Vesting
→ Grants and
→ Airdrops.

with selective disclosure and Human Passport for Sybil resistance.

[Wisdom Tek @agwuchikwendu]

The important shift: confidentiality isn't just about encrypting the workload.

It's about proving what is actually running before trusting it with the secrets.

That's where hardware-backed attestation becomes powerful.

[Kaelis @KaelisdApp]

@moulderofweb3 @HumnPassport @iEx_ec Thank you sir🫠

[Kaelis @KaelisdApp]

The future of token distributions isn't public spreadsheets on-chain.

It's confidential, Sybil-resistant, and verifiable.

That's why we built Kaelis with @HumnPassport and @iEx_ec .

For private payroll, vesting, grants, and airdrops without sacrificing trust.

[TechVVV @TechVVV]

Just scrolling through the WTF Hackathon submissions and this one from @agwuchikwendu caught my eye ♨️

Kaelis does confidential airdrops, vesting, payroll and grants on iExec Nox: amounts stay encrypted, only the right people can decrypt them, and Human Passport @HumnPassport keeps the Sybil attacks out.

These are the kind of practical Privacy builds the space actually needs. More of these please 🤝

$RLC #CryptoSecurity

[Human Passport @HumnPassport]

👀

Passport can catalyze so many cool use cases; we seriously don't get enough of these

[Kaelis @KaelisdApp]

@iEx_ec Onchain finance just got leveled up, encrypt everything.

[iExec RLC @iEx_ec]

https://t.co/eJeGWECbLk is refreshed.

Confidential on-chain finance. Selective disclosure. Verifiable execution.

The clearest statement of what we build 👇

[Kaelis @KaelisdApp]

Web3 made transparency the default.

Kaelis asks a different question: what if sensitive allocations could stay private while everything remained verifiable?

@HumnPassport + @iex makes that possible. 🔐

[Wisdom Tek @agwuchikwendu]

Nobody tells you that Web3 privacy is about control.

@KaelisdApp combines @HumnPassport + @iEx_ec to make token distributions confidential by default.

Verify who can claim, encrypt what they receive, and keep every transaction verifiable.

Privacy, without sacrificing trust.

[Kaelis @KaelisdApp]

GM KAELIS

[Kaelis @KaelisdApp]

@iEx_ec This is deFI in 2026, nice Tek fr

[Kaelis @KaelisdApp]

Fourth era: Prove you're one person, claim your tokens without revealing the amount claimed💨

[Human Passport @HumnPassport]

first airdrop era: show up, get tokens

second era: farm harder, get more

third era: prove you're one person, get your fair share

[iExec RLC @iEx_ec]

In February, we said onchain finance needs confidentiality.

Six months later, that's no longer a contrarian take. It's the direction the whole industry is moving.

Here's the recap of how we got here 👇

[Kaelis @KaelisdApp]

Privacy doesn't mean confidential bots.

iExec Nox + Humanpassport = Confidential sybil resistant Airdrops.

Good Tek here

[iExec RLC @iEx_ec]

Privacy!

That's the homework.

[iExec RLC @iEx_ec]

Compatible, trustless, and permissionless. But what else does onchain confidentiality need to deliver?

That’s what @0xNatc explained during our recent live session with @COTInetwork, hosted by @amateo 👇

[Kaelis @KaelisdApp]

Kaelis is confidential infrastructure for Web3 token distributions.

@HumnPassport verifies who can claim.

@iEx_ec protects what they receive.

Payroll, vesting, grants, and airdrops become private, Sybil-resistant, and fully verifiable on sepolia.

https://t.co/2Qhqh2zLds

[Kaelis @KaelisdApp]

Privacy is necessary because public blockchains permanently exposed financial activity, while privacy let's people and organizations protect sensitive information like salaries, airdrops, grants while still proving every transaction is legitimately recorded onchain.

[iExec RLC @iEx_ec]

Why should anyone care about privacy?

Explain in one sentence 👇

[iExec RLC @iEx_ec]

How do you prove, right now, that a Nox component is running the expected code inside a genuine Intel TDX Trust Domain?

Not at boot. Right now.

That's runtime attestation. Our very own Aghiles just wrote a deep dive on how Nox surfaces it through the Attestation UI 👇

[Kaelis @KaelisdApp]

The future is confidential🔏

[Kaelis @KaelisdApp]

Building on @iEx_ec

Stay Tuned🔏