Incomplete Documentation: One of the biggest hurdles was navigating the Aptos CLI, as its documentation was not as comprehensive or user-friendly as we hoped. This made understanding the nuances of the Aptos environment challenging. We overcame this by diving deep into the available resources, experimenting through trial and error, and engaging with the community to fill in the gaps.

Lack of Established Tools: Unlike the EVM ecosystem, which has mature frameworks like Hardhat and Forge, Aptos lacked a similar comprehensive toolset. This meant that we had to build many custom scripts and workflows to achieve the functionality we needed, which added to the development time.

Learning the Move Language: Being our first time working with the Move programming language, there was a steep learning curve. The language's unique ownership model and resource-oriented programming required a shift in mindset, but through dedicated learning and hands-on practice, we were able to grasp its concepts and effectively implement them.

First-Time LayerZero Integration: Integrating LayerZero to facilitate cross-chain communication was another new experience for us. Understanding its architecture and ensuring secure and efficient interactions between EVM and Aptos took time, but with persistence and thorough testing, we successfully integrated it into the project.