cross-chain
Cross-chain bridge and multi-chain development expertise. Supports LayerZero, Chainlink CCIP, Wormhole, and Axelar for omnichain messaging, token bridging, and cross-chain state verification.
Best use case
cross-chain is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Cross-chain bridge and multi-chain development expertise. Supports LayerZero, Chainlink CCIP, Wormhole, and Axelar for omnichain messaging, token bridging, and cross-chain state verification.
Teams using cross-chain should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/cross-chain/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How cross-chain Compares
| Feature / Agent | cross-chain | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Cross-chain bridge and multi-chain development expertise. Supports LayerZero, Chainlink CCIP, Wormhole, and Axelar for omnichain messaging, token bridging, and cross-chain state verification.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Cross-Chain Development Skill
Expert cross-chain bridge development and multi-chain integration.
## Capabilities
- **LayerZero**: Omnichain messaging and OFT tokens
- **Chainlink CCIP**: Cross-chain interoperability protocol
- **Bridge Verification**: Implement verification logic
- **Finality Handling**: Handle chain finality differences
- **Wormhole/Axelar**: Alternative bridge protocols
- **Canonical Bridges**: Token bridge implementations
- **State Verification**: Cross-chain state proofs
## LayerZero Integration
### OFT Token (Omnichain Fungible Token)
```solidity
// SPDX-License-Identifier: MIT
pragma solidity ^0.8.20;
import { OFT } from "@layerzerolabs/lz-evm-oapp-v2/contracts/oft/OFT.sol";
contract MyOFT is OFT {
constructor(
string memory _name,
string memory _symbol,
address _lzEndpoint,
address _delegate
) OFT(_name, _symbol, _lzEndpoint, _delegate) {
_mint(msg.sender, 1000000 * 10 ** decimals());
}
}
```
### OApp (Omnichain Application)
```solidity
import { OApp } from "@layerzerolabs/lz-evm-oapp-v2/contracts/oapp/OApp.sol";
import { Origin } from "@layerzerolabs/lz-evm-oapp-v2/contracts/oapp/interfaces/IOAppReceiver.sol";
contract CrossChainCounter is OApp {
uint256 public count;
constructor(address _endpoint, address _owner) OApp(_endpoint, _owner) {}
function increment(
uint32 _dstEid,
bytes calldata _options
) external payable {
bytes memory payload = abi.encode(count + 1);
_lzSend(
_dstEid,
payload,
_options,
MessagingFee(msg.value, 0),
payable(msg.sender)
);
count++;
}
function _lzReceive(
Origin calldata _origin,
bytes32 _guid,
bytes calldata _message,
address _executor,
bytes calldata _extraData
) internal override {
uint256 newCount = abi.decode(_message, (uint256));
count = newCount;
}
}
```
### LayerZero Configuration
```typescript
// hardhat.config.ts LayerZero setup
import { EndpointId } from "@layerzerolabs/lz-definitions";
const config = {
networks: {
ethereum: {
url: process.env.ETHEREUM_RPC,
accounts: [process.env.PRIVATE_KEY],
},
arbitrum: {
url: process.env.ARBITRUM_RPC,
accounts: [process.env.PRIVATE_KEY],
},
},
layerZero: {
ethereum: {
eid: EndpointId.ETHEREUM_V2_MAINNET,
endpoint: "0x1a44076050125825900e736c501f859c50fE728c",
},
arbitrum: {
eid: EndpointId.ARBITRUM_V2_MAINNET,
endpoint: "0x1a44076050125825900e736c501f859c50fE728c",
},
},
};
```
## Chainlink CCIP
### Token Transfer
```solidity
import {IRouterClient} from "@chainlink/contracts-ccip/src/v0.8/ccip/interfaces/IRouterClient.sol";
import {Client} from "@chainlink/contracts-ccip/src/v0.8/ccip/libraries/Client.sol";
import {IERC20} from "@openzeppelin/contracts/token/ERC20/IERC20.sol";
contract CCIPTokenTransfer {
IRouterClient public router;
address public linkToken;
constructor(address _router, address _link) {
router = IRouterClient(_router);
linkToken = _link;
}
function transferTokens(
uint64 destinationChainSelector,
address receiver,
address token,
uint256 amount
) external returns (bytes32 messageId) {
Client.EVMTokenAmount[] memory tokenAmounts = new Client.EVMTokenAmount[](1);
tokenAmounts[0] = Client.EVMTokenAmount({
token: token,
amount: amount
});
Client.EVM2AnyMessage memory message = Client.EVM2AnyMessage({
receiver: abi.encode(receiver),
data: "",
tokenAmounts: tokenAmounts,
extraArgs: "",
feeToken: linkToken
});
uint256 fee = router.getFee(destinationChainSelector, message);
IERC20(linkToken).approve(address(router), fee);
IERC20(token).approve(address(router), amount);
messageId = router.ccipSend(destinationChainSelector, message);
}
}
```
### Cross-Chain Message
```solidity
import {CCIPReceiver} from "@chainlink/contracts-ccip/src/v0.8/ccip/applications/CCIPReceiver.sol";
import {Client} from "@chainlink/contracts-ccip/src/v0.8/ccip/libraries/Client.sol";
contract CCIPReceiver is CCIPReceiver {
event MessageReceived(bytes32 messageId, bytes data);
constructor(address router) CCIPReceiver(router) {}
function _ccipReceive(
Client.Any2EVMMessage memory message
) internal override {
emit MessageReceived(message.messageId, message.data);
// Process message
(string memory text) = abi.decode(message.data, (string));
// Handle the message...
}
}
```
## Wormhole Integration
### Token Bridge
```solidity
interface IWormholeTokenBridge {
function transferTokens(
address token,
uint256 amount,
uint16 recipientChain,
bytes32 recipient,
uint256 arbiterFee,
uint32 nonce
) external payable returns (uint64 sequence);
function completeTransfer(bytes memory encodedVm) external;
}
contract WormholeBridge {
IWormholeTokenBridge public bridge;
function bridgeTokens(
address token,
uint256 amount,
uint16 targetChain,
address recipient
) external payable {
IERC20(token).transferFrom(msg.sender, address(this), amount);
IERC20(token).approve(address(bridge), amount);
bytes32 recipientBytes = bytes32(uint256(uint160(recipient)));
bridge.transferTokens{value: msg.value}(
token,
amount,
targetChain,
recipientBytes,
0,
uint32(block.timestamp)
);
}
}
```
## Bridge Security Patterns
### Rate Limiting
```solidity
contract RateLimitedBridge {
uint256 public constant RATE_LIMIT = 1000000 * 1e18;
uint256 public constant RATE_PERIOD = 1 hours;
uint256 public currentPeriodStart;
uint256 public currentPeriodTransferred;
modifier rateLimited(uint256 amount) {
if (block.timestamp >= currentPeriodStart + RATE_PERIOD) {
currentPeriodStart = block.timestamp;
currentPeriodTransferred = 0;
}
require(
currentPeriodTransferred + amount <= RATE_LIMIT,
"Rate limit exceeded"
);
currentPeriodTransferred += amount;
_;
}
}
```
### Circuit Breaker
```solidity
contract CircuitBreakerBridge {
bool public paused;
address public guardian;
uint256 public pauseThreshold;
modifier notPaused() {
require(!paused, "Bridge paused");
_;
}
function pause() external {
require(msg.sender == guardian, "Only guardian");
paused = true;
}
function unpause() external {
require(msg.sender == guardian, "Only guardian");
paused = false;
}
function emergencyWithdraw(
address token,
address to,
uint256 amount
) external {
require(msg.sender == guardian, "Only guardian");
require(paused, "Must be paused");
IERC20(token).transfer(to, amount);
}
}
```
### Message Verification
```solidity
contract VerifiedBridge {
mapping(bytes32 => bool) public processedMessages;
mapping(uint256 => uint256) public chainConfirmations;
function processMessage(
bytes32 messageHash,
bytes[] calldata signatures,
uint256 sourceChain
) external {
require(!processedMessages[messageHash], "Already processed");
require(
verifySignatures(messageHash, signatures),
"Invalid signatures"
);
processedMessages[messageHash] = true;
// Process the message...
}
function verifySignatures(
bytes32 messageHash,
bytes[] calldata signatures
) internal view returns (bool) {
// Verify threshold signatures from validators
uint256 validSigs = 0;
for (uint i = 0; i < signatures.length; i++) {
address signer = recoverSigner(messageHash, signatures[i]);
if (isValidator(signer)) {
validSigs++;
}
}
return validSigs >= threshold;
}
}
```
## Finality Handling
```typescript
// TypeScript finality handling
const CHAIN_FINALITY = {
ethereum: { blocks: 32, time: 384 }, // 384 seconds for finality
arbitrum: { blocks: 1, time: 0 }, // Inherits ETH security
optimism: { blocks: 1, time: 0 }, // Inherits ETH security
polygon: { blocks: 256, time: 512 }, // ~8.5 minutes
bsc: { blocks: 15, time: 45 }, // ~45 seconds
avalanche: { blocks: 1, time: 2 }, // 2 seconds
};
async function waitForFinality(chainId: number, txHash: string) {
const finality = CHAIN_FINALITY[chainId];
const receipt = await provider.getTransactionReceipt(txHash);
while (true) {
const currentBlock = await provider.getBlockNumber();
if (currentBlock - receipt.blockNumber >= finality.blocks) {
return receipt;
}
await sleep(1000);
}
}
```
## Process Integration
| Process | Purpose |
|---------|---------|
| `cross-chain-bridge.js` | Bridge development |
| `blockchain-node-setup.js` | Multi-chain infra |
| `multi-signature-wallet.js` | Cross-chain multisig |
## Best Practices
1. Implement rate limiting on bridges
2. Use circuit breakers for emergencies
3. Handle finality differences per chain
4. Verify message authenticity thoroughly
5. Monitor bridge TVL and anomalies
6. Plan for chain reorganizations
## See Also
- `skills/solidity-dev/SKILL.md` - Contract development
- `agents/bridge-architect/AGENT.md` - Bridge expert
- [LayerZero Docs](https://docs.layerzero.network/)
- [CCIP Docs](https://docs.chain.link/ccip)Related Skills
middleware-chain-designer
Design middleware and interceptor chains for SDK extensibility
supply-chain-visibility-integrator
End-to-end supply chain visibility integration skill connecting systems and data sources
supply-chain-simulation-engine
Supply chain discrete-event simulation for scenario testing and optimization
supply-chain-risk-assessor
Comprehensive supply chain risk identification and assessment skill with heat mapping
supply-chain-digital-twin
Digital twin representation of supply chain for real-time monitoring and simulation
critical-chain-scheduler
Critical Chain Project Management (CCPM) skill with buffer management and resource leveling
supply-chain-visibility-platform
End-to-end supply chain visibility skill providing real-time tracking and control tower capabilities
cross-dock-orchestrator
Flow-through logistics process coordination skill to minimize storage time and accelerate product movement
keychain-credential-manager
Manage credentials in OS keychains across Windows, macOS, and Linux
cross-platform-test-matrix
Generate CI test matrix for Windows, macOS, and Linux combinations
chain-forensics
On-chain analysis and transaction forensics for blockchain security investigations. Provides capabilities for tracing fund flows, identifying suspicious patterns, MEV analysis, and generating forensic reports for incident response.
cross-platform-path-handler
Generate cross-platform path handling utilities for Windows, macOS, and Linux compatibility in CLI applications.