ABOUT SYNCProof

The convergence story.

SyncProof is a small, founder-led systems consultancy. Its current work grows out of a personal history of connecting infrastructure, software, communities, and identities. For 25 years, the technology has changed. The work has stayed the same: connecting systems that were never designed to work together — and making them reliable when it matters.
Scroll to trace the convergence →

25 years of connecting systems.

From open-source telecom protocols to mission-critical communications, hosted infrastructure, and decentralized identity — the same engineering problem keeps returning: make disparate systems work together reliably.
2026

SyncProof

Today SYNCPROOF is a layer-1 blockchain services and development company focused on virtual agent economies and digital identity. My role is Lead Systems Designer (Agentic & Identity), carrying the same thread into new infrastructure.
Lessons learned: Systems should be open where possible, explicit about constraints, and verified before they are trusted.
2023

Verus DeFi and Fair-Price Execution

I worked on Verus DeFi integrations involving MEV-free fair-price execution and parallel-execution testing. The focus was testing whether decentralized execution could preserve fair pricing while processing activity in parallel, without giving an unseen intermediary an advantage.
Lessons learned: fair execution has to be designed into the system and demonstrated under realistic conditions; it cannot be bolted on after the market is live.
2021

Open Food Chain

Supply-chain integration using blockchains and web services to provide sustainable, transparent truth for the public good.
Lessons learned: Interoperability becomes meaningful when technical systems make real-world provenance easier to understand and trust.
2019

Komodo and Atomic Swaps

Komodo Platform work combined open-source blockchain engineering with product and adoption strategy: scaling solutions, decentralised exchange, interoperable smart contracts, decentralised governance, social-venture funding, incentives, and participation rewards. The role moved between coding and testing with engineers and roadmap-setting with marketing and community teams.
Lessons learned: Blockchain adoption is as much an inclusion, product, and community-design problem as it is an engineering problem.
2018

Komodo Pioneers and Blockchain Security

As a systems engineer for the Komodo blockchain security service, I supported Komodo Pioneers Organization notary nodes across the EU and Southern Hemisphere. The global 64-node network coordinated multisignature transactions and anchored the security of more than 50 blockchain projects to the Bitcoin network, with a 99.99% uptime target.
Lessons learned: Decentralised security is an operational discipline: global redundancy, careful coordination, and reliability at protocol scale.
2010s

Hosted PBX + load testing

Hosted telecom and carrier-grade load testing taught me to push systems until their failure modes became visible — before customers found them in production.
Lessons learned: Test the limits, expose failure modes, and build the gates before you need them.
2009

Omnium Research Group

Omnium is a group of artists, designers, programmers, writers, and academics from different countries exploring online collaborative communities. Formed in 1998, the Research Group developed online environments for art and design schools, then expanded into e-learning, social, and business software. I was the sysadmin in 2009, supporting this work from the College of Fine Arts at UNSW.
Lessons learned: Online collaborative creativity connected infrastructure to design, UX, social participation, and ethical community practice before those ideas became standard web language.
2008

Alertee

I co-founded Alertee with Richard Matthews of Leda Security Products. Alertee turned automated alerts from security and fire alarms, SCADA machinery, and BACnet equipment into a human response through conference calls. Its prepaid, pay-per-use model and telecom billing integration made a new class of response service practical for industry partners.
Lessons learned: Reliable infrastructure is valuable when it closes the loop between machine signals, human action, and sustainable commercial models.
2008–2016

Sydney to Hobart

For eight years I deployed and ran communications for the media tent at the Sydney to Hobart yacht race, where failure meant losing contact with people at sea.
Lessons learned: Reliability is a design constraint from the beginning, not a feature added at the end.
2001

The Network?

A hospital IT conversation captured a larger shift: from asking whether a network existed to accepting that the network would become the infrastructure everything depended on.
Lessons learned: Infrastructure becomes invisible just before everyone depends on it.
2000

openCSTA

I wrote one of the first open-source CSTA implementations in Java, helping bridge proprietary PBX systems and IP networks. It was cited in Asterisk: The Future of Telephony.
Lessons learned: Protocols matter when independent systems can actually speak to one another.

The three trust vectors.

Depth

25 years of protocol-level engineering.

Pressure

Real-time communications when failure mattered.

Resilience

Load testing, failure analysis, and explicit gates.

The timeline is the short version.

For the full openCSTA story — source code, scans from the Asterisk book, and early network diagrams — visit the technical lineage archive.
Explore the lineageStart a conversation