Requirements: - Onchain execution of strategy should be presented during the final demo - Custom Limit Orders should not be posted to official Limit Order API - Consistent commit history should be in the GitHub project. No low or single-commit entries allowed! Stretch goals (not hard requirements): - UI
- Application should use 1inch API as much as possible - Consistent commit history should be in the GitHub project. No low or single-commit entries allowed!
Requirements: - Preserve hashlock and timelock functionality for the non-EVM implementation - Swap functionality should be bidirectional (swaps should be possible to and from Ethereum) - Onchain (mainnet/L2 or testnet) execution of token transfers should be presented during the final demo (EVM testnets will require the deployment of Limit Order Protocol contracts) Stretch goals (not hard requirements): - UI - Enable partial fills
Requirements: - Preserve hashlock and timelock functionality for the non-EVM implementation - Swap functionality should be bidirectional (swaps should be possible to and from Ethereum) - Onchain (mainnet/L2 or testnet) execution of token transfers should be presented during the final demo (EVM testnets will require the deployment of Limit Order Protocol contracts) Stretch goals (not hard requirements): - UI - Enable partial fills
Requirements: - Preserve hashlock and timelock functionality for the non-EVM implementation - Swap functionality should be bidirectional (swaps should be possible to and from Ethereum) - Onchain (mainnet/L2 or testnet) execution of token transfers should be presented during the final demo (EVM testnets will require the deployment of Limit Order Protocol contracts) Stretch goals (not hard requirements): - UI - Enable partial fills
Requirements: - Preserve hashlock and timelock functionality for the non-EVM implementation - Swap functionality should be bidirectional (swaps should be possible to and from Ethereum) - Onchain (mainnet/L2 or testnet) execution of token transfers should be presented during the final demo (EVM testnets will require the deployment of Limit Order Protocol contracts) Stretch goals (not hard requirements): - UI - Enable partial fills
Requirements: - Preserve hashlock and timelock functionality for the non-EVM implementation - Swap functionality should be bidirectional (swaps should be possible to and from Ethereum) - Onchain (mainnet/L2 or testnet) execution of token transfers should be presented during the final demo (EVM testnets will require the deployment of Limit Order Protocol contracts) Stretch goals (not hard requirements): - UI - Enable partial fills
Requirements: - Preserve hashlock and timelock functionality for the non-EVM implementation - Swap functionality should be bidirectional (swaps should be possible to and from Ethereum) - Onchain (mainnet/L2 or testnet) execution of token transfers should be presented during the final demo (EVM testnets will require the deployment of Limit Order Protocol contracts) Stretch goals (not hard requirements): - UI - Enable partial fills
Requirements: - Preserve hashlock and timelock functionality for the non-EVM implementation - Swap functionality should be bidirectional (swaps should be possible to and from Ethereum) - Onchain (mainnet/L2 or testnet) execution of token transfers should be presented during the final demo (EVM testnets will require the deployment of Limit Order Protocol contracts) Stretch goals (not hard requirements): - UI - Enable partial fills
Requirements: - Preserve hashlock and timelock functionality for the non-EVM implementation - Swap functionality should be bidirectional (swaps should be possible to and from Ethereum) - Onchain (mainnet/L2 or testnet) execution of token transfers should be presented during the final demo (EVM testnets will require the deployment of Limit Order Protocol contracts) Stretch goals (not hard requirements): - UI - Enable partial fills
Requirements: - Preserve hashlock and timelock functionality for the implementation - Swap functionality should be bidirectional (swaps should be possible to and from Ethereum) - Onchain (mainnet/L2 or testnet) execution of token transfers should be presented during the final demo (EVM testnets will require the deployment of Limit Order Protocol contracts) Stretch goals (not hard requirements): - UI - Enable partial fills
Requirements: - Preserve hashlock and timelock functionality for the non-EVM implementation - Swap functionality should be bidirectional (swaps should be possible to and from Ethereum) - Onchain (mainnet/L2 or testnet) execution of token transfers should be presented during the final demo (EVM testnets will require the deployment of Limit Order Protocol contracts) Stretch goals (not hard requirements): - UI - Enable partial fills
Requirements: - Preserve hashlock and timelock functionality for the non-EVM implementation - Swap functionality should be bidirectional (swaps should be possible to and from Ethereum) - Onchain (mainnet/L2 or testnet) execution of token transfers should be presented during the final demo (EVM testnets will require the deployment of Limit Order Protocol contracts) Stretch goals (not hard requirements): - UI - Enable partial fills
Requirements: - Preserve hashlock and timelock functionality for the non-EVM implementation - Swap functionality should be bidirectional (swaps should be possible to and from Ethereum) - Onchain (mainnet/L2 or testnet) execution of token transfers should be presented during the final demo (EVM testnets will require the deployment of Limit Order Protocol contracts) Stretch goals (not hard requirements): - UI - Enable partial fills
Requirements: - Preserve hashlock and timelock functionality for the non-EVM implementation - Swap functionality should be bidirectional (swaps should be possible to and from Ethereum) - Onchain (mainnet/L2 or testnet) execution of token transfers should be presented during the final demo (EVM testnets will require the deployment of Limit Order Protocol contracts) Stretch goals (not hard requirements): - UI - Enable partial fills
Requirements: - Preserve hashlock and timelock functionality for the non-EVM implementation - Swap functionality should be bidirectional (swaps should be possible to and from Ethereum) - Onchain (mainnet/L2 or testnet) execution of token transfers should be presented during the final demo (EVM testnets will require the deployment of Limit Order Protocol contracts) Stretch goals (not hard requirements): - UI - Enable partial fills
Requirements: - Preserve hashlock and timelock functionality for the non-EVM implementation - Swap functionality should be bidirectional (swaps should be possible to and from Ethereum) - Onchain (mainnet/L2 or testnet) execution of token transfers should be presented during the final demo (EVM testnets will require the deployment of Limit Order Protocol contracts) Stretch goals (not hard requirements): - UI - Enable partial fills
Requirements: - Preserve hashlock and timelock functionality for the non-EVM implementation - Swap functionality should be bidirectional (swaps should be possible to and from Ethereum) - Onchain (mainnet/L2 or testnet) execution of token transfers should be presented during the final demo (EVM testnets will require the deployment of Limit Order Protocol contracts) Stretch goals (not hard requirements): - UI - Enable partial fills
- Get picked for the bonus by the judges. - Nothing specific is required in the entry to be eligible for this prize.
To qualify for a prize, submissions must: 1. Deploy on Etherlink using Solidity (EVM-compatible) smart contracts. 2. Demonstrate how your project integrates or extends 1inch Fusion+ on Etherlink. 3. Include a clear README with instructions on: β’ How to run or test the code β’ What components were built or modified β’ Which 1inch protocol features were used or extended 4. Be submitted before the ETHGlobal Unite deadline and presented during judging. 5. Be original work created during the hackathon. Bonus points for: β’ Technical depth and practical utility β’ Working UI or CLI to demonstrate integration β’ Clear potential for future development or 1inch partnership
Must integrate both Stellar blockchain and 1inch API/protocols in a meaningful way. Project should demonstrate functional use of each platform's core capabilities.
Your solver must listen for quote requests (mocked or real), produce valid 1inch Fusion meta-orders using NEAR's Chain Signatures, include comprehensive documentation with setup instructions, and demonstrate end-to-end functionality. Bonus points for modular architecture that extends to other protocols.
Your solver must listen for quote requests (mocked or real), produce valid 1inch Fusion meta-orders using NEAR's Chain Signatures, include comprehensive documentation with setup instructions, and demonstrate end-to-end functionality. Bonus points for modular architecture that extends to other protocols.