Lead Blockchain Developer

Description:

BlueLift builds software for businesses that operate under licence — banks, asset issuers, and institutions under regulatory supervision. We’re building tokenization infrastructure for real-world assets, and we need someone to own the smart contract layer entirely.

This isn’t a role where blockchain is a feature bolted onto a product. The contracts are the foundation. They’ll be read by external auditors, examined by regulators, and relied upon to enforce ownership records representing real assets. If a transfer restriction fails, someone holds a token they should never have received.

You’d be the first blockchain engineer here, and for a period the only one. What you build in the first six months becomes the thing everyone else works within.

What you’ll own

→ Permissioned token contracts implementing ERC-3643 (T-REX) — identity registries, claim topics, trusted issuers, compliance modules

→ Transfer restriction logic — eligibility whitelists, jurisdiction limits, holding caps, lock-ups — enforced at the contract level, not by application policy

→ On-chain registries and evidence anchoring, including the judgement calls about what belongs on-chain versus off

→ Deployment tooling — repeatable, parameterised deployments across multiple client configurations; node infrastructure; monitoring

→ Chain and standard selection — evaluating EVM chains on cost, finality, and institutional acceptance, and defending the choice

→ Audit preparation — writing code an external audit firm can assess without archaeology, then working through their findings

What we need

→ 4+ years writing Solidity in production, with contracts deployed to mainnet that have handled real value. Testnet work and tutorial projects don’t count here

→ Deep EVM understanding: gas mechanics, storage layout, proxy and upgrade patterns, and their trade-offs

→ Fluency with common attack vectors — reentrancy, access control failures, oracle manipulation, front-running — and the design habits that prevent them

→ Hardhat or Foundry, with testing discipline you’d stake money on. Coverage isn’t the metric; adversarial thinking is

→ The ability to read a token standard specification and implement it correctly, including the parts that are ambiguous