Project troubleshooting Q&A
summary
Live Q&A covers hackathon rules, submission checklist and concrete fixes: judges score on 5 judging criteria (UI/UX, technical depth, originality, practicality, wow), submissions must change chain state and include a public repo plus a 3‑minute video by June 9. Practical tips: use mock functions for unit tests, run integration with npx functions hardhat simulate, split VRF work into batched callbacks to avoid gas caps, and prefer Functions over external adapters for off‑chain compute and API calls; ask followups on Stack Overflow tagged chainlink.
AI-written summary · about
chapters (19)
- 0:00Welcome
- 3:11Hackathon Q&A overview
- 6:20Judging criteria
- 12:01Team changes & submissions
- 14:45Registration & deadlines
- 15:06Hardhat tests with Chainlink Functions
- 16:52VRf gas limit issues
- 20:47Chainlink on Optimism
- 24:22Automation restrictions
- 29:58Functions vs API calls
- 32:34Manual triggers prevention
- 35:44What is a hackathon?
- 38:10Office hours feedback
- 38:31Saddest aspects of Web3
- 42:27Flow blockchain track
- 43:30Submission tips
- 46:18Public access
- 48:02Exciting project types
- 51:35Final reminders
