Engineering portfolio

Projects I built, launched, and operated.

Browse the work by technology and the operating problem it addressed. Each record separates my role, the result, and the public evidence available.

Project database

Find the closest proof.

12 of 12 case studies

Technology

Delivery impact

Search visibility · Portugal · 2026
Illustration of the global 42 peer-learning network used in the 42 Portugal visibility assessment

Search visibility research, question analysis, and source review

42 Portugal Search Visibility

I assessed how 42 Portugal appears in Portuguese search and AI answers: which candidate questions surface it, which sources models rely on, and where visibility drops.

42 is easy to find when people ask about free coding schools or campuses. It appears less often in questions about preparation, learning without teachers, and employer recognition.
AI product · Publishing · 2026
Agentic Brief visual showing reader identity and interests routed through an agent workflow into a personalized technical brief

Publisher and builder

Agentic Brief

I built an AI publishing product that combines the topics a reader chooses with the LinkedIn profile details they authorize, so each brief can follow their actual interests.

A signup that knows what each reader wants and verifies who is asking, instead of collecting anonymous email addresses.
AI agent · Virtuals Protocol · 2025
EVA's silver digital character with blue eyes against the project's cyan circuit artwork

Fractional CTO and Soul Generator co-founder

EVA Token Launch

I joined EVA Online as fractional CTO and co-founded Eva Soul Generator, helping connect its persistent identity system, authored character world, and $EVA launch on Virtuals Protocol.

$EVA launched on Base with public product documentation, an on-chain contract, and my team credit as Dadev.
Bitcoin · Marketplace · PSBT
Trio marketplace architecture showing seller and buyer wallets connected through listing and purchase PSBTs to Bitcoin settlement

Full-stack marketplace engineer

Trio Marketplace

I worked with the OrdinalsBot team on Trio’s full-stack marketplace transaction flow, turning listings and purchases into wallet-signable PSBTs that settle on Bitcoin.

A live Bitcoin marketplace where the seller’s terms, the buyer’s funds, signatures, broadcast, and confirmation remain visible parts of the transaction.
On-chain game · Bitcoin · 2024–25
Pizza Pets pixel-art wordmark for the Bitcoin on-chain game

Product engineering

Pizza Pets

I helped build a fully on-chain Bitcoin game where more than 58,000 pets can be fed, evolve through six stages, or die permanently without an off-chain game server.

More than 58,000 pets and one million on-chain interactions turned recursive inscriptions into a living Bitcoin product.
Bitcoin · Ordinals · 2024
Pizza Ninja #1 angel artwork with a yellow mask and halo on an orange background

Technical lead

Pizza Ninjas

I led the custom Bitcoin inscription pipeline for the original 1,500-piece collection, then helped build the recursive traits, animation, customization, and games that followed.

1,500 inscriptions shipped on Bitcoin. Pizza Ninja #1 later sold for $139,700 at Sotheby’s.
Permanent archive · Bitcoin · 2024
Project Spartacus I Am Assange archive wordmark

Inscription pipeline engineering

Project Spartacus

I worked on the Bitcoin inscription pipeline that mapped 76,911 Afghan War Diary records into a verifiable archive that could resume safely across many blocks.

A recoverable Bitcoin archive built for all 76,911 public records.
Ethereum · Emergency smart contract delivery · April 2022
NOT NASA number 1 hand-drawn bear character being lifted into a flying saucer on an orange background

Smart contract and mint engineer

Not NASA

Founder Domingo Mattle called with 24 hours left before mint. I delivered the ERC-721 contract, allowlist, sale controls, airdrops, metadata, and three-way payout path in time for launch.

A launch-critical contract delivered in 24 hours; 1,093 tokens minted and 88.23 ETH recorded in gross paid-mint receipts.
Ethereum · Smart contracts · February 2022
Yakuza Inc. number 1 red pixel-art character from the Ethereum collection

Lead smart contract and launch engineer

Yakuza Inc.

I built and launched the contract, allowlist, sale controls, metadata, and payout path behind a seven-figure, 3,223-token Ethereum sell-out.

A seven-figure, 3,223-token mint that sold out in under two hours; the final 596 public mints landed in 56 seconds.
Ethereum · Pre-launch contract audit · January 2022
Planetary Property Association Ethereum contracts reviewed before launch, linking Shuttle Passes, allowlists, the Surrealestates mint, and 10,000 NFTs

Pre-launch smart contract auditor

Planetary Property Association

I audited Planetary Property Association’s smart contracts before launch, reviewing the ERC-1155 Shuttle Pass and ERC-721 Surrealestates mint logic before the system went live.

Post-launch context: the Shuttle Pass contract received exactly 1,854.79 ETH during the 9–10 January 2022 mint; historical market reporting later recorded 1,945.226 ETH in secondary trading.
Education infrastructure · Portugal · 2020–21
David Dacruz with the 42 Lisboa founding team on the campus launch

Founding IT & Pedagogy team member and full-stack developer

42 Lisboa

After working on the student intranet with the 42 Network development team inside the Paris Bocal, I joined the founding 42 Lisboa team and helped turn Portugal’s first 42 campus into a working school.

From an unlaunched campus to two live intakes, more than 300 students, and an initial 20,000 online applicants.
Education platform · Paris Bocal · 2020
42 The Network logo

Full-stack developer · 42 Network

42 Network Student Intranet

Inside the 42 Paris Bocal, I worked with the 42 Network development team on the student intranet used to follow curriculum progress and skills.

Full-stack product work on a student platform embedded in the everyday 42 learning experience.

What teams can expect

I stay close to the consequential part of the work.

That usually means owning the difficult integration, planning for failure, and documenting the decisions another engineer will inherit.

01

I take responsibility for the risky part

I work on the piece that can sink the product, not only the piece that is easiest to present.

02

I plan for failure

Retries, limits, review paths, and operational controls belong in the design from the beginning.

03

I document the decisions

The next engineer should be able to understand what changed, why it changed, and how to keep it running.

Project questions

What to know before reading the case studies.

Clear answers about my role, public evidence, confidentiality, and earlier-stage work.

What does each case study include?

A case study explains the original problem, the part I owned, the important technical decisions, the result, and the strongest public evidence I can cite.

Did I build every project alone?

No. Most products were team efforts. Each case study separates my role from the wider team’s work and names collaborators or organisations when that context is public.

Can I discuss the private parts of these projects?

I can discuss public architecture, decisions, delivery constraints, and results. Client data, credentials, private repositories, and confidential operating details stay private.

Can I help with a project at an earlier stage?

Yes. I can begin with an unclear workflow, a difficult technical decision, or a first release. Send the current situation, constraints, and who will own the product.

Have a project that needs experienced hands?

Tell me what is hard about it.

Start a conversation