Independent, shipping since 2024

Ayaan

.

I write the contract, the cryptography, and the interface, then put the whole thing on mainnet. Any EVM chain. Two apps live right now, no backend behind either of them.

See my work → Open Brushpass ↗

About

Builds things
that actually ship.

I am an independent Web3 developer and crypto content creator. I do not work at a chain and nobody hands me a spec. I pick a problem, write the contract, write the client, deploy to mainnet, and put the link out. The contracts are plain EVM, so they go wherever the work is. The two below happen to run on BOT Chain.

My interest sits in three places: cryptography that runs in the browser, on-chain data as the only source of truth, and self-custody. Both of my live apps encrypt before anything touches the chain, so the contract stores bytes it cannot read and I cannot read either.

I also document what my code does not protect. Brushpass hides message content, not the social graph, and its security review is written by me rather than a third party. That is on page one of the PDF. Overselling is easy and it breaks trust once.

Reachable on X and GitHub. I answer.

Work

Two contracts,
both on mainnet.

Every address below is live on BOT Chain and readable in the explorer right now.

Live on mainnet 0xB30a27654D2f297BE8090a5bD7C748349C0e5b46 BOT Chain · 677

Brushpass

End-to-end encrypted messaging between wallets.

Send a message to another wallet address. Your browser encrypts it before the transaction leaves, the contract stores the ciphertext, and only you and the recipient can open it. There is no server, no database, and no account to create.

You sign one fixed statement to derive an X25519 identity key. That key is rebuilt from the signature every session, so nothing is stored anywhere. Your public key is published on chain as a self-message, which means no registry contract is needed and nobody can publish a key on your behalf.

Key exchangeX25519 ECDH
CipherAES-256-GCM
KDFHKDF-SHA256
Overhead164 bytes
Bundle457 KB
Solidity 0.8.24HardhatReact 18 Vite 5Tailwind CSS 3ethers v6 @noble/curves@noble/hashesWeb Crypto API EIP-6963MetaMask deep linkVercel
Open the app ↗ Read the contract ↗ Security review ↗

The review is written by me, not an independent auditor, and the PDF says so on page one.

Live on mainnet 0xe1eedfF10174C4Cfa7a038c555EA8120d2E91158 BOT Chain · 677

BlockNotes

Notes that live in your wallet, not on someone else's server.

Write a note and it becomes a real transaction. Every note belongs to the wallet that wrote it, and only that wallet can edit or delete inside its own list. No account, no password, no backend to shut down and take your notes with it.

Your wallet signs a fixed message once. The client hashes that signature into a 256-bit AES key and encrypts each note with a fresh random IV before it reaches the chain. The contract stores a blob it cannot read.

ContractNotesVault
CipherAES-256-GCM
Key sourceSHA-256 of sig
Note cap4096 bytes
Ownershipper wallet
Solidity 0.8.24HardhatCustom errors React 18Vite 5Tailwind CSS 3 ethers v6WalletConnect v2Web Crypto API PostCSSVercel
Open the app ↗ Read the contract ↗ Security review ↗

Swap-and-pop deletion keeps gas flat as a list grows. Note order is not stable by design.

Skills

Everything here
is in the shipped code.

By the numbers

Small totals,
all of them real.

0
dApps live
on mainnet
0
lines of Solidity
deployed
0bit
AES-GCM on
every payload
0
contract and crypto
tests passing
0KB
Brushpass production
bundle
0B
on-chain cap
per entry

Contact

Say something.

Work, a bug in one of the contracts, or an idea worth deploying. All three reach me.

Emailayaanonyoutube@gmail.com X@AyaanOnCrypto GitHubgithub.com/ayaanoncrypto