Ecosystem story / Dave Isbitski at Chainlink

Aptos

Speed, Move, and building with CCIP

I like Aptos for its focus on speed, but the developer story is just as interesting to me. Move brings a different way of thinking about assets and ownership. I created a developer presentation on using Chainlink CCIP with Aptos and demonstrated it live, turning that new territory into something developers could explore.

My role   Presenter & demo builderFormat   Live developer presentation

01 / My presentation & live demos

Building on Aptos with Chainlink CCIP

I built the presentation and demos for this session to help developers get started with CCIP on Aptos. Delivering it live meant taking the integration beyond an announcement and showing it in action.

Building on Aptos With Chainlink CCIP. Recording and artwork hosted by Chainlink. Watch on YouTube

Chainlink added CCIP support for Aptos on September 9, 2025, continuing its expansion beyond EVM networks. My contribution was developer education: creating the material, building the demos, and presenting the integration live.

02 / My perspective

Performance gets my attention. The developer model keeps it.

I like speed, but I also want to understand what makes a platform different for the person building on it. With Aptos, that means looking at both how transactions execute and how Move changes the way we represent assets.

As with Solana, I care about responsive applications. If we want people to use onchain services as naturally as the software they already rely on, the experience needs to feel fast. That makes Aptos's performance-focused architecture interesting to me.

One part of that architecture is Block-STM, a parallel execution engine. It executes transactions speculatively, detects dependencies, and resolves conflicts while preserving the result of a predetermined transaction order. That is an execution design, not a promise that every application or cross-chain transfer will complete at the same speed.

For me, the opportunity is to connect that engineering to a developer's first useful experience. A live demonstration gives people a concrete starting point for understanding a platform and deciding what to build next.

03 / Learning a different model

Move puts assets at the center

Aptos uses Move, a smart-contract language with a resource-oriented approach. For a developer arriving from Solidity and the EVM, this is more than switching networks: there is a different programming model to learn.

Move's resource rules make the distinction concrete. Values cannot simply be copied or discarded unless their types explicitly permit those operations through the copy and drop abilities. Modules also control access to their data. That gives developers language-level tools for expressing ownership and protecting assets.

I find that compelling because it brings the design of the asset into the design of the program. It also creates a teaching opportunity: help developers understand the model, then connect it to a practical integration. Those safeguards are valuable, but they do not remove the need for sound application logic, testing, and security review.

An engineering lineage worth understanding

Aptos has roots in Meta's Diem blockchain work. The Aptos Labs team history connects its founding engineers to Diem and to technologies including Move and Block-STM. What interests me is how that research informs a public blockchain and the tools developers use today.

This is why I enjoy working across ecosystems. The goal is not to give the same talk with a different chain name. It is to understand what changes for the developer, build with it, and make that learning useful to someone else.

More of my ecosystem work

The presentation authorship, demo-building work, and personal perspective described here are my firsthand account. The linked recording documents the public session; official documentation and research provide the technical background.