Senior Blockchain Engineer

Aries Blockchain

About the Project

Aries Blockchain was a no-code platform that let users design, build and deploy blockchain applications without writing a single line of code. The goal was to make the full range of crypto primitives accessible to non-developers — from token issuance and crypto exchanges/swaps to on-chain auctions and other DeFi building blocks — through a visual, modular builder that generated and deployed the underlying contracts automatically. Each module in the builder mapped to a reusable smart contract template on EVM chains, so a user could assemble a working dApp by composing pre-built components rather than hand-writing Solidity. The platform targeted entrepreneurs, businesses and teams that wanted to ship Web3 products quickly without an in-house blockchain engineering team.

• Cryptocurrency
• Blockchain

Responsibilities

I owned the entire smart contract layer that powered the platform's no-code builder. I designed, wrote and maintained all of the Solidity contracts behind the available modules — token standards, exchange/swap logic, auction mechanisms and supporting infrastructure — making each one generic and parameterizable enough to be safely generated and configured from the visual builder. I wrote the full test suites and was responsible for testing and verification before contracts shipped, covering edge cases, failure modes and gas behavior. I also worked with the integration side to expose the contracts through the builder via TypeScript/JavaScript and Web3.js, so user-facing configuration mapped cleanly onto on-chain deployments.

KittieFight

About the Project

KittieFight was an Ethereum dApp that turned CryptoKitties NFTs into a play-to-earn battle game. Players sent their CryptoKitties to a smart contract, which translated each cat's on-chain "cattributes" into combat stats and pitted two kitties against each other in a fight. Spectators backed their favourite cat with ETH into a shared honeypot, and the winning side split the pot together with the project's KTY utility token. The game wrapped this around a full token economy — a KTY ERC-20 token, scheduling and escrow logic for fights, a Dutch-auction mechanism, and yield/redemption flows — all settled on-chain. The aim was to add a new gameplay and economic layer on top of the existing CryptoKitties collectibles and bring blockchain gaming to a wider audience.

• Cryptocurrency
• Blockchain

Responsibilities

I joined the team after the initial contracts had been started and took ownership of the Solidity smart contract codebase. My core responsibility was writing and extending the contracts behind the game — the fight/escrow logic, the honeypot and payout distribution, the KTY token and the auction mechanism — and making them work together correctly on-chain. A large part of my work was auditing the existing code, finding bugs and edge cases in the game and economic logic, and fixing them so that funds and outcomes were handled safely. I wrote and ran tests against the contracts to reproduce issues and verify fixes before deployment, and iterated closely with the rest of the team as the game's mechanics evolved.

Global Crypto Alliance

About the Project

Global Crypto Alliance (GCA) was a blockchain organization building decentralized services around its own utility token, CALL. CALL was the first ERC777 token ever deployed on Ethereum (June 2018) — a then-new standard that improved on ERC-20 by adding hooks that let contracts react automatically when they receive tokens, removing the separate approve/transferFrom step. On top of CALL, the team explored real-world use cases for the standard. The main one team worked on was a smart-lock prototype: a physical lock tied to an Ethereum address that toggled between locked and unlocked states based on ERC777 token transfers sent to it, using the standard's receive hooks to trigger the state change on-chain. The goal was to show that an ERC777 token could drive real, tokenized access control without manual approvals.

• Cryptocurrency
• Blockchain

Responsibilities

I co-developed the CALL token with one other engineer — writing and deploying the ERC777 contract that became the first ERC777 token live on Ethereum, working directly against a brand-new and still-evolving standard with very little prior art to rely on. I then built the smart-lock prototype on top of it: the lock was bound to an Ethereum address, and I implemented the logic so that receiving ERC777 tokens at that address moved the lock between locked and unlocked states via the standard's tokensReceived hook. I worked through the practical and security characteristics of ERC777 hooks first-hand. The project wound down when the limitations and risks around the ERC777 standard — particularly its reentrancy-prone receive hooks — made it unattractive to keep building on.

Injective Protocol

About the Project

Injective Protocol is a decentralized exchange built around a fully on-chain order book rather than an AMM — the first fully decentralized order-book derivatives exchange, supporting perpetual swaps, futures and spot trading with instant finality and no gas fees on trades. Founded in 2018 out of a Binance hackathon, it was originally built as an Ethereum-based protocol, using a custom scaling layer and smart contracts to bring exchange and derivatives logic on-chain. Over time the team decided the DEX needed its own dedicated infrastructure, and the protocol was rebuilt as a sovereign Cosmos SDK chain (Tendermint consensus), where order-book management, matching, settlement and the derivatives engine live as native chain modules. The goal was to match the speed and UX of a centralized exchange while keeping everything transparent, on-chain and community-governed

• Cryptocurrency
• Blockchain

Responsibilities

I was one of the first on the project and wrote the protocol's original smart contracts — the on-chain exchange and derivatives logic that ran the DEX in its Ethereum-based phase. When the team decided the DEX should run on its own Cosmos chain rather than on EVM smart contracts, I helped with the migration from the Solidity contract layer to native chain code, re-implementing the exchange logic as Cosmos SDK modules. A core part of my work was the perpetuals engine: together with one other engineer and the CEO, I built and tested the full on-chain flow for the perpetual protocol — position handling, margin, funding and settlement — making sure it behaved correctly end-to-end. I owned a large share of the contract and protocol-level testing throughout.

Nexera

About the Project

Nexera (formerly AllianceBlock) is a Web3 infrastructure provider focused on compliant tokenization of real-world and digital assets, powered by the NXRA token. Its product suite spans Fundrs — a decentralized capital-raising and launchpad platform (private sales, presales, milestone-based financing) — and the tokenization platform now known as Evergon: a no-code, white-label system, plus API/SDK, that lets institutions issue, fractionalize, vest, distribute and manage tokenized assets with built-in compliance, without writing any code. The whole stack is built on the ERC-7208 standard, which can wrap any asset, fractionalize it, and manage its full lifecycle across chains. The goal is to give financial institutions, crypto companies and asset issuers a compliant, interoperable bridge between TradFi and on-chain markets — letting them launch a complete tokenization business in minutes.

• Cryptocurrency
• Blockchain

Responsibilities

I spent ~4 years here as a lead blockchain engineer, responsible for a large part of the smart contract work across the ecosystem. I built Fundrs, the capital-raising/launchpad platform, and then designed the architecture for and built the entire tokenization platform (Evergon) — effectively the whole on-chain backend is mine. I architected it around the Diamond Standard (EIP-2535), using modular facets to keep the system upgradeable and composable enough to back a configurable, white-label product. On top of that I built the issuance, wrapping and fractionalization protocols and the compliance/lifecycle logic that the no-code platform configures and deploys for clients. I co-authored the ERC-7208 standard the platform is built on and wrote its reference implementation (the Wrapper and Fractionalizer). I owned the contract architecture, implementation and testing throughout.

Chainsafe Systems-Augur

About the Project

Augur is one of the original decentralized prediction-market and oracle protocols (Ethereum, 2015–16), now being revived under the Lituus Foundation, which stewards the original Augur treasury and funds independent teams to rebuild it. The current focus, Augur Lituus, generalizes Augur's oracle into standalone infrastructure: a permissionless, manipulation-resistant resolution layer that any application — prediction markets, DeFi protocols, DAOs, games, insurance, cross-chain systems — can use by paying a fee to resolve a well-specified question. Its security rests on an algorithmic fork mechanism and an open escalation game where honest reporting is economically enforced, designed so that attacking the oracle costs more than it could extract, making truth-telling the dominant strategy. The aim is a modular, cross-chain oracle-as-a-service that runs on any EVM chain.

• Cryptocurrency
• Blockchain

Responsibilities

I work as a smart contract engineer at ChainSafe Systems, one of the teams building the Augur Lituus oracle, contributing at the protocol-architecture level. My work covers the core Solidity/EVM design of the generalized oracle — the storage layout, the forking and escalation mechanics behind the oracle's security model, gas optimization of the critical paths, and the accounting around fees and rewards. A constant design constraint is keeping the critical operations within block gas limits as the protocol's history grows. I collaborate closely with the Augur founder, the ChainSafe project lead and the partner team on an evolving specification, and I'm responsible for turning that design into correct, efficient and well-tested contracts.