The problem Flowing ThirdEye solves

ThirdEye tactically addresses the security needs of diverse user segments:

• Security novices: We cater to users new to security who seek assurance for their on-chain activities. Our intuitive and user-friendly platform guides them in safeguarding their transactions.

• Audited projects on alert: For projects with audited contracts, ThirdEye remains vigilant, providing a safety net and readiness for war-room situations, ensuring rapid response to potential threats.

• Cautious projects: We assist projects that prioritize comprehensive monitoring by intelligently detecting Indicators of Compromise, helping them maintain a secure environment for their users.

• OpSec experts: ThirdEye appeals to security wizards by offering advanced features and alerts, empowering them to stay informed about potential events that could jeopardize their wallet security or current investments/allowances.

• User-sided Journeys: We're although huge fans of user-sided security and definitely thinking of panning into gamified experiences for users to boost the mainstream adoption of the security of their smart contracts and accounts.

• We have a strong belief that security isn't a luxury or niche, but an actual necessity and at ThirdEye, we're trying to solve that first hand.

And for the nerds, ThirdEye allows you to do automation and monitoring using YAML :) (for now)

Challenges we ran into

We did certainly run into a lot of issues, technical and operational, a few of them:

• Our project is modular and has a structure where we can plug in and integrate various blockchain, keeping that in mind while we were integrating FLOW was a bit difficult, but we cracked it.

• Gaining real-time data for a monitoring project like us is tough and we had to work our way around indexer data and make sure that it's relevant for our platform -- and secure enough.

• Balancing our limited budget and resource constraints necessitated strategic prioritization of feature development to create a lean, yet robust platform.

• Crafting unique features like automated contract locking involved intricate smart contract interactions and implementing intelligent automation protocols.

• Developing more and more IoCs (indicators of compromise) that give the user or project various top-notch options to choose from.

• Designing a custom interface for seamless integration between Web2 and Web3 tools was necessary to cater to apps with mixed infrastructures.

• The project itself is fairly complicated. Getting it running and keeping it running is tough considering how new it is. This required a lot of effort to get things up and running because we joined the hackathon late.