$GPS pushing higher every candle, chat’s already measuring it against the stars but that’s not the line that actually stopped me scrolling this week, that one came from Project @Dusk_Foundation own documentation, buried a few pages deep: “integration not yet live.”
went back through the CCIP announcement expecting more to have shipped than what’s actually there. the headline story is that dusk and npex are adopting CCIP, DataLink and Data Streams to move regulated assets cross-chain. reads like it’s already running.
Checked dusk’s own docs though, and the status next to CCIP is still marked not yet live.
what is verifiably live, as of aug 10, is the duskevm testnet solidity and hardhat support, $DUSK bridged over as the native gas token, contracts you can deploy and check on the explorer right now.
so the “expanded reach” story isn’t cross-chain asset movement yet. it’s developers getting a familiar evm environment before that composability exists. small distinction but it stuck with me the layer CCIP would eventually plug into is what actually shipped, not CCIP itself.
not sure if that’s deliberate sequencing or just how these timelines tend to run ahead of the code. genuinely curious how much real deployment activity is happening on duskevm testnet right now vs how much attention the CCIP headline is pulling anyone watching the contract count there?
#dusk
went back through the CCIP announcement expecting more to have shipped than what’s actually there. the headline story is that dusk and npex are adopting CCIP, DataLink and Data Streams to move regulated assets cross-chain. reads like it’s already running.
Checked dusk’s own docs though, and the status next to CCIP is still marked not yet live.
what is verifiably live, as of aug 10, is the duskevm testnet solidity and hardhat support, $DUSK bridged over as the native gas token, contracts you can deploy and check on the explorer right now.
so the “expanded reach” story isn’t cross-chain asset movement yet. it’s developers getting a familiar evm environment before that composability exists. small distinction but it stuck with me the layer CCIP would eventually plug into is what actually shipped, not CCIP itself.
not sure if that’s deliberate sequencing or just how these timelines tend to run ahead of the code. genuinely curious how much real deployment activity is happening on duskevm testnet right now vs how much attention the CCIP headline is pulling anyone watching the contract count there?
#dusk