Your tech partner for borderless finance.

What do you build?

Four things: smart contract development, blockchain migration, confidential systems, and security review.

Most engagements start with the architecture and the system design, before any contract is written.

What have you shipped?

Sixteen mainnet deployments across three protocols.

16 Mainnet deployments. Live systems handling real transactions.

3 Protocols shipped on. Aptos, Movement and EVM.

Cross-chain deployments over LayerZero. A Solidity to Move port delivered with a UI playground so the partner could test it themselves. Strategy vaults and orchestration contracts for a Move yield platform that Movement later acquired.

This is protocol work led by our founder between 2023 and 2026, first through Code & Ledger in Belgium and now under Bits & Blocks in Qatar.

Which chains?

Aptos, Movement and EVM networks, with Stellar in proposal.

We write Move, Solidity and Rust. On mainnet we have shipped against Base, Aptos, Movement, Pyth and Circle's USDC, with Hypernative monitoring the deployments and Stripe handling the payments that stay off-chain.

If you are on a chain we have not listed, migration between chains is one of the four services.

Who are you?

Bits and Blocks LLC, QFC No. 3865, Doha Tower, West Bay.

Incorporated in the Qatar Financial Centre in August 2025, licensed to design and build software and to run non-financial FinTech APIs.

Founded and led by Ala Eddine Battikh, co-author of AIP-76, the digital-asset composability standard in the Aptos Improvement Proposals repository. The team is small and senior.

Why not a normal dev shop?

We take on the architecture, not only the implementation.

A lot of the work happens before there is code: what the system should do, where the money sits, and what each contract is allowed to touch. Partners usually come to us with those still open.

Security review is included rather than quoted separately, and we do turn down work we think is a bad idea.

Tell me about CipherPhi

On-chain philanthropy on Stellar, designed for the Swiss Zakat Foundation. It is in proposal and not yet built.

As designed, a donor can verify from the Stellar ledger that their zakat category was distributed to a recipient whose eligibility was signed before the funds moved.

Allocation across the eight categories runs in the policy contract. The custody contract releases funds only against a signed eligibility attestation, verified on-chain, and it has no upgrade path over donor money.

Funds and rules live on Stellar. Identity and human judgment stay off the ledger, and no personal data is designed to reach the chain.

How do you handle security?

Code review and vulnerability analysis are part of every build engagement.

The review is done by someone who did not write the code, and what we deploy goes out with Hypernative monitoring on it.

We raise design problems during the design phase, rather than at an audit once the system is built.

How do we start?

A call, then a written scope.

Tell us what you are building and what has to be true about it once it is live. We come back with an architecture and a price. Both are yours whether or not you continue with us.

What does it cost?

Scoped per engagement.

Two things move the number: how much of the design already exists, and how much money the contracts have to hold. We will tell you which of the two is driving your quote.

Are you actually an AI?

No. This is a keyword match over a list of written answers.

Nothing you type here leaves your browser, and every line was written by the people who did the work. It covers about a dozen questions and says so when yours is not one of them.

We do build with models when a partner's problem calls for one.