How I Became the World's Foremost Bitcoin Script Engineer

It Started With Forth

In 2008, fresh out of university, I joined a tiny five-person company called Electronic Innovations. My first real job. They threw me into the deep end with Forth — a stack-based programming language that most developers have never heard of.

Forth is weird. There's no syntax highlighting. No IDE holding your hand. You push values onto a stack, manipulate them with words, and build up from primitives. It's minimalist, powerful, and unforgiving.

I didn't just learn Forth. I fell in love with it.

Over the next 15 years, I used Forth repeatedly in control systems — industrial automation, embedded devices, anywhere you needed tight control over hardware with minimal overhead. Stack-based thinking became second nature.

The Bitcoin Discovery

In 2017, I was digging into how Bitcoin actually works. Not the price. Not the hype. The protocol.

Then I saw Bitcoin Script.

It was Forth. Not exactly — but the DNA was unmistakable. Stack-based. Postfix notation. Opcodes that felt like old friends.

I had a realisation: I'd been training for this for 15 years without knowing it.

While everyone else was treating Bitcoin as digital gold or a speculation vehicle, I saw something different. A programmable ledger. A system where you could encode logic directly into transactions. Smart contracts — real ones, not the bloated, gas-guzzling kind.

Going Deep

I made a decision: I would understand this protocol completely.

Not surface-level. Not "I read the whitepaper." I'm talking opcode-by-opcode, script-by-script, edge-case-by-edge-case understanding.

I became a protocol expert. I started contributing to the ecosystem. The Bitcoin Association noticed and asked me to write the curriculum for the BitcoinSV Academy — the official educational program for developers learning to build on Bitcoin.

I wrote the courses that now teach thousands of developers how Bitcoin Script actually works.

Building Elas

In 2020, I founded Elas Digital.

The mission was simple: help companies build on Bitcoin the right way.

I'd seen too many projects fail. Teams would come in with ambitious ideas, throw together some code, and ship something that was inefficient, insecure, or just fundamentally misunderstood how the protocol worked.

I wanted to be the person who stops that from happening.

For several years, Elas had a team. We worked on major projects, built infrastructure, consulted with enterprises. We had successful years.

Today, it's just me. The market shifted. Funding dried up. But the expertise didn't go anywhere.

What I Actually Do

When you work with me, you get someone who:

• →Analyses your requirements — What are you actually trying to build? What problem are you solving?
• →Advises on what belongs on-chain — Not everything should be. I'll tell you what should and shouldn't touch the ledger.
• →Minimises your costs — Transaction fees, data storage, computational overhead. I optimise ruthlessly.
• →Keeps your ledger private — Using public infrastructure doesn't mean exposing everything. Encryption, hash functions, zero-knowledge proofs — I know when and how to apply them.
• →Designs smart contracts at the opcode level — Not copying templates. Building from first principles.

The Method

Here's what 15 years of stack-based programming taught me:

Start with the constraints. Bitcoin Script is intentionally limited. No loops. No recursion. Limited opcodes. Most people see this as a weakness. I see it as a design philosophy.

Think in data flows. Every script is a transformation. Inputs come in, get processed, outputs emerge. If you can't draw the data flow, you don't understand the contract.

Build from primitives. Complex behaviour emerges from simple pieces composed correctly. Don't reach for abstractions until you've mastered the basics.

Test at the edges. The happy path is easy. What happens when someone sends malformed data? What happens at block boundaries? What happens in a reorg?

Minimise trust assumptions. Every time you trust something off-chain, you've weakened your contract. Push as much verification on-chain as possible.