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.