No More Exchanging ABIs Through Slack: CI/CD for On‑Chain Code

Smart-contract engineering still feels like 1990s web dev: ABI JSONs pasted over Slack, no canonical URL per branch, and teams guessing which build lives on which chain. This talk outlines what full CI/CD for on‑chain code must provide: per‑commit ABI URLs, preview networks, provenance‑linked deployments, and an MCP layer that LLMs can query, restoring dev velocity and good practices.

I’m Guil Sperb Machado, founder of AxLabs), Technical Committee member at Neo X), and a developer‑experience advocate in Web3 since 2017. I've initially released neow3j) SDK and compiler and helped to ship production dApps such as DAOs) and grant platforms, spending far too many hours chasing ABI files in chat threads and piecing together which contract version was actually live. That pain sparked GitMyABI) and my drive to share a practical blueprint for smart‑contract CI/CD, so every team can ship on‑chain code with the same ease and confidence they expect in Web2.