Solidity

Transferring Tokens with Canton Daml: State and Authorization Compared with Solidity

Transferring Tokens with Canton Daml: State and Authorization Compared with Solidity

When Alice sends all 100 token units to Bob, Bob becomes the person who can spend them next. The Solidity example updates balances by address; the Daml example for Canton consumes Alice’s holding contract and creates Bob’s. They express the same transfer outcome with different units of state and different authorization checks.

Read More
Chainlink CCIP EVM Contracts: Architecture from Source Code

Chainlink CCIP EVM Contracts: Architecture from Source Code

EVM chains are isolated by design. A contract on Arbitrum has no native way to call a contract on Base, and sending USDC from Ethereum Mainnet to Polygon is not a built-in operation. Cross-chain bridges filled that gap for years, but the category has seen repeated security incidents that highlight how wide the attack surface is.

Read More
Circle CCTP V2 EVM Contracts: A Source-Code Walkthrough

Circle CCTP V2 EVM Contracts: A Source-Code Walkthrough

Bridge designs for moving USDC between chains come down to two families. Lock-and-mint parks the original token in a contract on the source chain and issues a wrapped version on the destination. Burn-and-mint destroys the token on the source chain outright and issues the same amount fresh on the destination. Circle’s CCTP (Cross-Chain Transfer Protocol) is the second kind.

Read More
Categories
Tags