1. Kernel implementation
A. Skate APP Template
B. Kernel Counter App Implementation
Take note of the
increaseCounter() and _handleSkateIntent() implementations.The signature format for methods should follow this structure:- Method Name: The first part of the signature must be the method name.
-
Parameter Types
The subsequent parts represent the input parameter types, separated by commas.
These types must be supported by Solidity. -
Cross-Chain Type Handling
For non-EVM chains, type transpilation occurs at the MessageBox level.
For example, Solana doesn’t supportuint256— emit it asuint128oruint64, then cast touint256at the Kernel layer. -
Format Rule
All parts of the signature must be comma-separated with no spaces.
Example:
increaseCounter,uint256,uint256
2. Periphery Implementation (EVM example)
Take note of the
increaseCounter() and _handleSkateIntent() implementations.The signature format for methods should follow similar standard to kernelNotes and best practices
-
All deployed periphery should be registered on Kernel App using bytes32 format, see
setChainToPeripheryContracton Kernel Skate App template. - All shared logic should be maintain at Kernel level, periphery should only act as proxy for assets handler.
- Ensure to used a consistent omnichain assets format across your app, i.e. in case of rebalancing between periphery