- Your submission must be deployed on the NEAR testnet. - Your submission may incorporate any ECDSA-based blockchain(s) of your choice. - Your submission must NOT be a simple fork of an existing example with minimal changes. - Your submission should include a basic readme file explaining the scope of the project - Your submission should demonstrate a creative chain signatures API use case. For example: 1) Account aggregation: aggregate accounts and transactions across several chains while only signing with NEAR. 2) Pay in $NEAR, validate price by oracle in a NEAR contract, and have this contract MPC sign and transfer an asset, fungible or non-fungible, on another chain. 3) Protect accounts on other chains with a NEAR smart contract that can only call an MPC to sign when certain conditions are met. You will be judged by: - Creativity and originality of the idea. - Quality and completeness of the product. - BONUS: Feedback on the chain signatures technology and developer experience to help improve it before mainnet launch (we will read every word!)
- You have a working product and are moving closer towards product market fit. Bonus points if you have users already! - Near, Aurora, or any Near adjacent project must be meaningfully integrated during the hackathon. Testnet or mainnet, your demo should be clickable and working, please no Figma mockups. - UX/UI: Fully functional browser based or mobile dApp. Submissions will be judged by these criteria: - Founder-market fit (the team has some professional background on the market they're entering e.g. a space tech startup needs to have at least one rocket scientist as a contributor or advisor ) - Technical excellence - Business model
Building a cross-chain product? Meet Chain Signatures: the latest programmable MPC technology that enables cross-ch...
03:40 PM GMT — Friday, Mar 15, 2024 in Workshop Room 2
ETHGlobal London