Files
smom-dbis-138/contracts/flash/interfaces/ICrossChainFlashBridge.sol
defiQUG 76aa419320 feat: bridges, PMM, flash workflow, token-aggregation, and deployment docs
- CCIP/trustless bridge contracts, GRU tokens, DEX/PMM tests, reserve vault.
- Token-aggregation service routes, planner, chain config, relay env templates.
- Config snapshots and multi-chain deployment markdown updates.
- gitignore services/btc-intake/dist/ (tsc output); do not track dist.

Run forge build && forge test before deploy (large solc graph).

Made-with: Cursor
2026-04-07 23:40:52 -07:00

21 lines
915 B
Solidity

// SPDX-License-Identifier: MIT
pragma solidity ^0.8.20;
/**
* @title ICrossChainFlashBridge
* @notice Minimal surface for “pull `token` from msg.sender then initiate CCIP / bridge”.
* @dev Wire to `UniversalCCIPFlashBridgeAdapter` (→ `UniversalCCIPBridge.bridge`), a dedicated adapter, or a mock in tests.
* Implementations MUST pull from `msg.sender` (e.g. `transferFrom`) up to `amount` after allowance.
* For `UniversalCCIPFlashBridgeAdapter`, optional `extraData` encodes
* `(bytes32 assetType, bool usePMM, bool useVault, bytes complianceProof, bytes vaultInstructions)`; empty uses zeros/false.
*/
interface ICrossChainFlashBridge {
function bridgeTokensFrom(
address token,
uint256 amount,
uint64 destinationChainSelector,
address recipientOnDestination,
bytes calldata extraData
) external payable returns (bytes32 messageId);
}