verigrant

Demo

About

The problem it solves ### 🛠️ Problems VeriGrant Solves * **No Standard Way to Represent Online Identity** When applying for grants, jobs, or partnerships, there's no simple, verifiable way to showcase your digital personality or values. * **Grant Applications Lack Personality Insights** DAOs and funding bodies often rely on proposals and wallets alone—VeriGrant adds an **AI-analyzed personality snapshot** to help assess alignment and intent. * **Job Applications in Web3 Miss Cultural Fit Checks** Employers in Web3 may struggle to judge if someone fits the culture or mission—VeriGrant provides a quick background check based on Twitter behavior. * **No Verifiable Reputation Layer** By minting a persona NFT, users create a **trustable, tamper-proof proof of personality**, which can be shown during applications or collaborations. * **Time-Consuming Social Media Review** Instead of manually scrolling through tweets, reviewers get an **automated summary** with ethical and alignment scores—saving time and improving clarity. * **Lack of Wallet-Linked Proof of Persona** VeriGrant ties the analysis to a wallet address, making it useful for on-chain identity and trust in a decentralized world.

How it's made

Challenges we ran into ### 🛠️ Problems Faced & How You Overcame Them 1. **Understanding Chainlink Automation** * **Problem:** Initially unclear how to connect your backend to smart contracts using Chainlink Automation. * **Solution:** Studied how Automation (formerly Keepers) works and rewired your flow to use Chainlink as a middleman between the server and contract. 2. **Chainlink VRF Integration Issues** * **Problem:** NFT minting with Chainlink VRF worked earlier, but later broke or became unreliable. * **Solution:** Re-tested and debugged your implementation; explored fallback options and considered simplifying the contract logic. 3. **High Costs & Friction with Chainlink Functions** * **Problem:** Functions required LINK payment; even Automation needed 0.05 ETH, which added friction. * **Solution:** Sought community help and looked for workarounds using **Automation only**, avoiding costly Functions. 4. **Complex/Nested Smart Contract Logic** * **Problem:** Some contracts became too complex or returned outputs that broke frontend behavior. * **Solution:** Refactored code and considered simplifying contracts to return more manageable data. 5. **Contract Compatibility with Automation** * **Problem:** Your smart contracts weren’t initially designed to support Chainlink’s `checkUpkeep`/`performUpkeep` pattern. * **Solution:** Modified and redeployed contracts to be **Automation-compatible**, keeping future extensibility in mind. 6. **Debugging NFT Minting & State Flow** * **Problem:** State wasn’t updating properly during NFT minting, and contract functions weren’t always returning expected values. * **Solution:** Tweaked both the backend and contract flow; broke down the minting logic into smaller, testable parts. 7. **Limited Testnet Persistence** * **Problem:** Learned that Sepolia testnet contracts aren’t forever, despite smart contracts being "permanent." * **Solution:** Factored this into your design and testing routine; understood the difference between testnet limitations and smart contract immutability. 8. **Time Management During the Hackathon** * **Problem:** Burnout days (e.g., "slept all day") and time crunch nearing the deadline. * **Solution:** Took breaks when needed, evaluated progress, and pushed forward with clear daily goals. 9. **Community Support & Stuck Moments** * **Problem:** Got stuck on Chainlink integration and funding aspects. * **Solution:** Reached out to devs on Twitter/X (@pappas9999, @solangegueiros), tagged Chainlink and ElizaOS, and used #buildinpublic for visibility and help.