AI

It was quite challenging to make an AI system to execute the DAO's decision in a way that was both robust and aligning with the DAO's decision. We achieved this by making a system of AI agents, designed in a modular manner. Upon the DAO's approval of a new proposal, Agent Blue drafts the initial contract. This draft is then evaluated by Agent Purple to ensure it aligns with the DAO's proposal terms and by Agent Red to check the contract for any potential security issues. Agent Green refines the contract, incorporating feedback from Agents Purple and Red. This modular approach allowed the AI system to execute the DAO's decision in a robust and secure manner.

Cross Chain Signature

Our team tried to integrate NEAR's Chain Signatures to our product and have seen examples of NEAR's Chain Signatures, but we felt there was a lack of SDK that could comfortably be used by developers familiar with EVM. Therefore, we decided to develop a simple SDK compatible with Viem for the purpose of easy use of NEAR's chain signatures. Initially, the major hurdle was dealing with the payload in the "sign" function for "multichainContract.requestSignature". We had to navigate through trial and error to learn that instead of using a Uint8Array format, a number array was required and that reversing it was necessary to generate the correct signature. Additionally, we encountered slight differences between the "big_r" and "big_s" values compared to the "r" and "s" values. Crucially, the absence of a provided "v" value necessitated receiving two signatures with "yParity" values of 0 and 1, and then verifying which was the correct signature through "verifyMessage", "verifyTypedData", and "recoverTransactionAddress" before sending it.

Frontend

On the frontend side, deploying and testing across multiple blockchains introduced its own set of challenges, including issues with Sepolia's default RPC and difficulties arising from blockchain disruptions.