Senior-only protocol engineering · Lahore, working across time zones
CodesenSys builds smart contracts, full-stack apps, and AI agents with senior engineers only. You get one accountable team.
01 · Work
We write Solidity, Rust, Go, TypeScript and Python, so we work from contracts and hooks up through rollups, cross-chain messaging, AI agents and the product on top.
A Uniswap v4 hook that sets the pool fee from an exponentially weighted moving average of price volatility. Deployed on Sepolia and verified on Etherscan; a controlled swap battery checks that fees adapt as intended.
Solidity · Foundry · fuzz tests
A Uniswap v4 hook that only lets eligible holders swap a tokenized asset, backed by an open-source Solidity library: a ComplianceRegistry, an IdentityBridge and the hook callbacks that consult them.
Solidity · Foundry · fuzz + invariant tests
A working OP Stack chain, published on GitHub, that shows an enterprise team what running its own rollup involves: configuration, deployment and the parts to operate.
OP Stack · Docker · runbooks
A LangGraph agent that takes an Ethereum address, gathers its on-chain activity and writes a structured intelligence report.
Python · LangChain · LangGraph
Moves an Aave v3 position in one transaction: swap the debt asset or the collateral without closing the loan. Built with Foundry and tested on Sepolia.
Solidity · Foundry · Sepolia
02 · Capabilities
We take protocol work end to end: design, contracts, tests, deployment and the interface people use.
AMM hooks, lending integrations, vaults and fee logic in Solidity, built with Foundry and Solady. We test with fuzzing and invariants before anything is deployed, and the tests stay in the repo.
Related work: EWMA volatility dynamic fee hook · Aave v3 loan swapper
Your own L2 or L3 on OP Stack, Arbitrum Orbit or ZK Stack, deployed self-hosted or through a rollup-as-a-service provider. We set up bridging, explorers and the operating runbook.
Related work: OP Stack demo network
Token and message flows over LayerZero v2, Chainlink CCIP, Wormhole, Axelar and IBC. We document what each path trusts and what happens when one side fails.
Scoped per project. Tell us what you are building.
Agents in LangChain and LangGraph that read on-chain data, with evaluation sets that show whether the output is right before it reaches a user.
Related work: On-chain intelligence agent
The app around the protocol: Next.js and React front ends, NestJS APIs, PostgreSQL with Prisma, and wallets with ERC-4337 smart accounts and passkeys.
Related work: Aave v3 loan swapper
03 · Tokenization and RWA
Real-world asset tokens need the same six parts whatever the asset. What changes is how each part is configured.
A special-purpose vehicle holds the property, and each token is a share in that vehicle, issued under a permissioned standard such as ERC-3643 so only eligible investors can hold it.
Fund units become permissioned tokens. Eligibility rules follow the offering: a Reg D 506(c) fund admits accredited investors only, so its transfer rules cannot open it to retail.
Tokens are backed by vaulted reserves, with proof of reserve published on-chain through an oracle. Redemption follows the custodian's terms and cut-off times.
A credit is retired in its registry, and the token reflects that retirement. Burning the token on its own does not retire anything.
SPV, fund or trust that owns the asset.
Identity and accreditation claims on-chain.
Minting against the cap table.
Checks every transfer must pass.
Compliant pools, such as our v4 hook.
Holder registers and event exports.
We build the technology. Your counsel decides the legal structure and jurisdiction.
Related work: Compliant RWA hook and rwa-compliance library
04 · Stack coverage
The chains and protocols we work with. Shipped means public code, delivered means client work, and scoped means we would plan it with you first.
Interop and app-chains
Base layers
Rollups
App-chains on L2s
DeFi protocols
Messages are verified by the DVNs each app chooses and delivered by executors. We configure the security stack per route and test the failure cases.
Toolchain: Solidity
Token and message transfers between supported chains, with rate limits set per lane. We integrate senders and receivers and handle failed deliveries.
Toolchain: Solidity
Messages are attested by Wormhole's Guardian network; Native Token Transfers move tokens without wrapped copies.
Toolchain: Solidity · Rust
General Message Passing for contract calls across chains, and the Interchain Token Service for tokens.
Toolchain: Solidity
App-specific chains written in Go on CometBFT consensus, talking to each other over IBC.
Toolchain: Go
The settlement layer for most EVM rollups. We have shipped and verified contracts on its Sepolia testnet, built and tested with Foundry.
Toolchain: Solidity · Foundry · Solady
Programs written in Rust with Anchor. Proof of History orders transactions; Tower BFT is the consensus mechanism.
Toolchain: Rust · Anchor
EVM-compatible, so Solidity contracts and Foundry tooling carry over with chain-specific configuration.
Toolchain: Solidity
An EVM chain with low fees and its own validator set, checkpointed to Ethereum. Solidity contracts deploy with few changes.
Toolchain: Solidity
Solidity contracts on the TRON Virtual Machine, which differs from the EVM in its fee model (energy and bandwidth) and address format.
Toolchain: Solidity (TVM)
Sovereign chains, formerly called Subnets, each with its own validator set and EVM configuration.
Toolchain: Solidity
Chains built with the Polkadot SDK in Rust, using XCM for cross-consensus messages and coretime for blockspace.
Toolchain: Rust
Validators on the eUTXO model, written in Aiken or Plutus. We start with a discovery phase.
Toolchain: Aiken · Plutus
The framework behind Base and many other L2s. We have built and published a working OP Stack demo network.
Toolchain: Solidity · Go
An OP Stack rollup; Solidity contracts deploy with Base-specific gas and bridge settings.
Toolchain: Solidity
An EVM L2; contracts deploy with Foundry and chain-specific gas settings.
Toolchain: Solidity
A zkEVM rollup that runs EVM bytecode. Contracts still need the same testing and audit as on Ethereum.
Toolchain: Solidity
An EVM chain for games. Players can be shielded from gas when the game sponsors it; gas still exists.
Toolchain: Solidity
A validity rollup with contracts written in Cairo. We start with a discovery phase.
Toolchain: Cairo
Custom chains on Arbitrum Nitro. Stylus adds Rust contracts; BoLD dispute resolution is still in beta for Orbit chains.
Toolchain: Solidity · Rust (Stylus)
ZKsync's framework for launching ZK chains, which it previously called hyperchains.
Toolchain: Solidity
An Ethereum L2 that runs the Solana VM, so programs are written in Rust with Anchor.
Toolchain: Rust · Anchor
RollApps built with the Cosmos SDK that settle on the Dymension hub.
Toolchain: Go
Hooks that add custom logic to v4 pools, such as dynamic fees and holder eligibility checks.
Toolchain: Solidity · Foundry
Contracts that work with Aave v3 positions, such as swapping a loan's debt or collateral in one transaction.
Toolchain: Solidity · Foundry
We deploy rollups self-hosted or through rollup-as-a-service providers.
Toolchain
The same toolchain runs through every layer above: Solidity and Foundry for contracts, Rust and Go for chains, TypeScript and Python for the product and the agents.
05 · Industries
Four sectors where a shared, verifiable ledger solves a real coordination problem.
Tokenized funds and assets with transfer rules enforced on-chain.
A shared ledger for parties who need the same record but not the same database.
Consent and access logs on-chain; the records themselves stay off-chain.
Device registries and reward contracts for physical infrastructure networks.
06 · Engage
Prices are published so you can tell in a minute whether we fit.
Fixed price quoted at $45/hr
A defined protocol, contract suite or app, delivered against an agreed spec with tests. One price, agreed before work starts.
Fits: startups with a clear first release.
$4,000 / month
100 committed hours a month from a senior engineer inside your team, in your repo and your standups, with priority response.
Fits: teams with a roadmap and not enough hands.
$45 / hour
Design reviews, pre-audit code review, prototypes and rollup or bridge architecture, billed by the hour.
Fits: enterprises deciding before they build.
30 minutes with the engineer who would build it.
What we build, what we do not, and the price.
Working code in your repo every week.
Tests, docs and deploy scripts your team can run.
07 · About
CodesenSys is a senior-only engineering team in Lahore, working across time zones. Since 2017 our work has moved from CMS builds to full-stack TypeScript, EVM and Solana protocols, and now AI agents. The engineers who scope your project are the ones who build it.
08 · FAQ
Short, true answers to what buyers ask before the first call.
We do pre-audit review and test hardening. For contracts holding real value, we recommend an independent audit firm as well, and we prepare the code for it.
A senior engineer you meet on the first call. We do not hand work to juniors or subcontractors.
Yes. We sign your NDA before the first technical call and follow your access, review and secrets policies. Client work is never published without your written approval.
We do not hold your production private keys. Deployments go through your multisig or deployment pipeline, and we keep only the access each task needs, removed at handover.
Yes. Scoped means we have not shipped there publicly yet, so we start with a short paid discovery to confirm the toolchain and estimate honestly.
No. We build the technology to the structure your counsel sets, and we work alongside them.
We estimate the hours at $45 an hour and agree one fixed price in the written scope, before any work starts.
Every engagement runs under a written scope agreed before work starts. We invoice in US dollars, with payment terms set out in that scope.
Yes. On the dedicated model, our engineer works in your repository, your tickets and your standups, under your review process.
Every project keeps its design notes, runbooks and tests in your repository, so the work never lives in one person's head and another engineer can pick it up.
We are in Lahore (UTC+5) and overlap with Gulf and European working hours, with scheduled calls for US teams.
You do, once the invoice for that work is paid.
09 · Contact
Send a few lines about the project and we will reply with next steps.
