{"schema":"BUIDL","d":{"id":17737,"members":[],"pictures":["https://cdn.dorahacks.io/static/files/192a53ce18140c016a5e01f45f68a31a.jpg"],"roundProjects":[],"hackathonProjects":[{"id":19296,"hackathon":{"id":653,"tabSet":[{"id":1165,"name":"Submission Guide","slug":"submission","description":"# Tutorial Video\n\n![YouTube](https://youtu.be/yWhQPzxptg0)\n\n# **Getting Started [3-5 MIN]**\n\n**1.** **Submit your BUIDL via [DoraHacks.io](https://dorahacks.io/). You need an account with DoraHacks before you can submit.**\n\nUse the **Log in** button in the upper right corner of the page to access the sign-up options.\n\n

\n\nYou can create your account with either your **GitHub account, Google account, crypto wallet** or **email address**. We recommend connecting your account to GitHub to share your projects with a wider audience.\n\n*If asked for a verification code via email, the email may take a few minutes to arrive. The code expires 10 minutes after you click “**send code**”.\n\n**2.** **Before the submission deadline, make sure you have added your Github link to the project. You can submit the project first, and continue editing until the deadline.**\n\nClick “**Submit BUIDL**”.\n\n

\n\n\n> **→ Already have a BUIDL on DoraHacks?**\n> \n\n1. Click “**Use existing BUIDL**” and select your BUIDL project.\n2. Choose the track you want to enter. \n3. Answer the questions set by the organizer in the input field if applicable.\n\n

\n\n\n> **→ Submitting a new BUIDL?**\n> \n> Click **“Create new BUIDL”** and fill out the form with your project details.\n\n

\n\nBe sure to include **URLs (with http/https://)** for your demo, demo link, and social media.\n\n

\n\n

\n\nOnce you’ve completed the new BUIDL setup, select the relevant track, and click **“Submit for review”**.\n\n

\n\nAfter submitting successfully, you'll see this notification.\n\n

\n\n# **Manage BUIDL submission**\n\nAfter submitting your application, the \"Submit\" button will update to \"Manage Submission\". Click the button to manage your BUIDL's Track/Bounty submission.\n\n

\n\n# **Project Approval**\n\nAfter submission, your project needs to be approved by the Hackathon Organizer before it becomes publicly visible in the Hackathon [BUIDLs gallery](https://dorahacks.io/hackathon/653/buidl).\n\n

\n\n# **Getting Support**\n\nIf you have any questions for the hackathon organizers, feel free to contact them via their dedicated Telegram, Discord, or Slack communication channel. You can also click the \"**Message**\" button next to the organizer's logo to DM them on DoraHacks.\n\n# **Want to Update Your BUIDL?**\n\nHead to your Account Center by clicking **[Avatar] -> [Profile]**. Find your project and hit the **Edit** button on its detail page to make changes.\n\n

\n\n

"}],"skills":null,"applied":false,"isCurrentHackerRegistered":false,"buidlsCount":9,"applicationsCount":9,"organization":{"id":2779,"name":"ETHKyiv","logo":"https://cdn.dorahacks.io/static/files/192a0bfb1065bb71663e30b474c95703.png"},"description":"# Що взяти з собою\n\n- **Ноутбук:** Ви будете працювати над проєктом, тому без ноутбука ніяк.\n- **Зарядні пристрої:** Не забудьте зарядки для ноутбука та гаджетів.\n- **Гарний настрій та енергію:** Позитивний настрій — ключ до чудової атмосфери та продуктивності!\n\n# Що потрібно знати\n\n- Мова воркшопу — **англійська**. Базове знання англійської вам точно знадобиться, особливо для активної участі у воркшопі та взаємодії з іншими учасниками.\n- **Це хакатон, а не конференція**. Готуйтеся до коротких виступів і багато часу для роботи над вашими проєктами!\n\n# Розклад події\n\n- 08:30 — Реєстрація, легкий сніданок (чай, кава, круасани, печиво)\n\n- 09:00 — Відкриття + виступ секретного гостя (ми рекомендуємо прийти, щоб не шкодувати!)\n\n- 10:00 — Воркшоп від Atrium University: Uniswap V4 Hooks\n\n- 11:30 - 12:00 — Знайомство та формування команд (максимум 5 людей у команді)\n\n- 12:00 - 19:00 — Робота над проєктом\n\n- 13:00 — Обід\n\n- 19:00 — Вечеря\n\n- 20:00 — Оголошення переможців та нагородження\n\n# Призовий фонд\n\n- Призовий фонд складає 2000 доларів, який буде розподілений між найкращими проєктами. Ми не обмежуємо кількість переможців, оскільки хочемо відзначити всі якісні проєкти! Подача проєктів має бути завершена до 19:00, після чого судді оцінять проєкти.\n\n# Що потрібно знати для участі\n\n- Щоб успішно взяти участь у цьому хакатоні, важливо мати хоча б базові знання Solidity. Ми будемо працювати з Uniswap V4 Hooks – це складна, але дуже цікава тема, яка вимагає знань про Ethereum, Solidity та смарт-контракти. Якщо ви вже працювали з цими технологіями або маєте базове розуміння, це вам сильно допоможе! Але навіть якщо ні, не переймайтеся, базовим речам по роботі з Uniswap V4 ми вас навчимо.\n\n# Якщо ви не розробник\n\n- **Маркетологи:** Ви можете приєднатись до команди та допомогти створити круті тексти про проєкт або написати статтю про Uniswap V4 Hooks.\n\n- **Дизайнери:** Вас чекають! Гарних дизайнерів завжди не вистачає, особливо у web3. Якщо ви дизайнер, сміливо шукайте собі команду – вас «заберуть з руками і ногами»!\n\n- **Студенти та новачки:** Навіть якщо ви новачок, ваша підтримка, бажання вчитися та мотивація — це надзвичайно важливо! Не бійтеся ставити запитання та робити помилки. Ви тут, щоб розвиватися — і це вже великий крок уперед. Спробуйте знайти собі команду та бути корисним.\n\n# Додаткова інформація\n\n- Снеки та напої будуть доступні на локації протягом усього дня.\n\n- Якщо у вас ще немає команди, ви можете знайти її на локації або через наш Discord-канал: https://discord.gg/veN5qWPj.\n\n- Підписуйтесь на наші соцмережі, щоб залишатись в курсі всіх оновлень і подій!\n\n- Ми з нетерпінням чекаємо на вас і впевнені, що це буде день, повний інновацій, натхнення та співпраці!","onboardingCompleted":false,"registerFormUrl":null,"preRegisterTime":0,"publicContactHackerHandle":"ihorethkyiv","hackersCount":20,"winnerAnnounced":true,"teamCount":0,"title":"ETHKyiv Impulse: Uniswap V4 Hooks Edition","uname":"ethkyivimpulse","imageUrl":"https://cdn.dorahacks.io/static/files/192a0ccd88159cf5340d72648eb874eb.jpg","originUrl":null,"startTime":1729315800,"endTime":1729353600,"timezone":"-180","city":null,"visible":true,"approvalStatus":6,"state":0,"voteUrl":null,"voteMechanism":null,"bonusPrice":2000,"bonusMechanism":null,"followersCount":0,"ecosystem":"Ethereum","applyGuide":null,"weight":0,"participationForm":"IRL","field":"Blockchain,Ethereum,Uniswap","email":"ihor@ethkyiv.com","contacts":"Email,ihor@ethkyiv.com","externalContacts":null,"telegram":null,"discord":null,"whatsapp":null,"wechat":null,"prizeFundingEscrowed":0,"token":"USD","prizeSafeForm":0,"prizeSafeNetwork":null,"prizeSafeOwner":null,"prizeSafeWallet":null,"prizeSafePublishDate":null,"hasOnboarding":false,"isPublicTrackJudging":false,"isEndedTrackJudging":true,"question":null,"countryId":227,"cityId":1804382913,"venueName":"Sigma Software, Kyiv Office","venueAddress":"BC Astarta, Yaroslavska St, 58, Kyiv, 04071","category":1,"isEnableBounty":true,"isBountyRequired":false,"isEndedBountyJudging":false,"bountiesLimitForBuidl":10,"isPublicBountyJudging":false,"isMultiTracksAllowed":false,"tracksLimitForBuidl":0,"showIdeaTab":true,"showQuestionTab":true,"showTeamTab":false,"bonusDescription":[],"askHackers":[],"isEnabledQuestions":false,"isEnabledAskHackers":false,"isBuidlsPrivate":false,"trackJudgingMaxScore":100,"bountyJudgingMaxScore":100,"isExtended":false,"oldEndTime":null,"status":2},"status":4,"bounty":null,"track":null,"table":"0","trackObj":{"id":1684,"name":"All BUIDLs","judgingCriteria":"","weight":1},"bountyObjs":[]}],"chain":[],"chainList":[],"appliedGrant":false,"acceptRewards":false,"owner":78199,"ownerInfo":{"nickname":"tarasnurko","username":"U_0a39596d26ab8d","avatar":"https://cdn.dorahacks.io/static/files/18e000b7159dc4c9a768c4e4879bd5fc.png"},"visible":true,"deleted":false,"continuousSponsoring":false,"pageView":0,"sponsoredCount":0,"starCount":0,"sponsoredAmount":"0.00","sponsoredPersons":0,"followers":0,"voteCount":0,"projectMembers":[],"bnbRound":null,"doraGrantDaoTags":[],"techTrees":[0],"infrastructureTags":[65,66,122],"otherInfrastructures":["category:Automation"],"lastEditor":{"id":78199,"username":"U_0a39596d26ab8d","date":1732434988000},"upvoted":false,"followed":false,"upvoters":{"count":0,"list":[]},"kycStatus":0,"ideas":[],"name":"KeeperHook","techniqueField":"","source":"-","vision":"It's uniswap v4 based hook that allow users exchange their transaction work in return of lower swap fees and additional collected fee from appropriate liquidity position in current pool.","projectDescription":"# KeeperHook\n\nIt's uniswap v4 based hook that allow users exchange their transaction work in return of lower swap fees and additional collected fee from appropriate liquidity position in current pool.\n\n## Guide for protocol owner (team member)\n\nYou are one of protocol members. First you need to mint some liquidity position using UniSwap V4 [PositionManager](https://github.com/Uniswap/v4-periphery/blob/main/src/PositionManager.sol). It would be better for you if you would mint liquidity position on pool with high usage (highest swap count per amo9unt of time) as more frequently users make swaps, less time there would be between check upkeep calls (which is good for you). After you selected good pair and created liquidity position with good enough for you amound of liquidity you deposit this liquidity position to `KeeperHook` (also dont forget to call `KeeperHook.setKeepersData()` to set desired max gas and your contract that uses `AutomationCompatible` interface). Aaaaaand, THATS ALL🎉🎉🎉. Now every user that make swap in pool (where you minted liquidity position) would check and perform upkeep (if needed). Be carefull to implement `AutomationCompatible` interface because if you make that `checkUpkeep()` or `performUpkeep()` make damage to user (they always revert or use all gas) than this contract as you would be considered malicious and you would be subsequent to **SLASH** (all deposits would be taken from you and your contract would be out of systam that means your contract would not be checked for upkeeps).\n\n## Guide for user\n\nFind pool with hook `KeeperHook`, and make swaps. If you `performUpkeep()` you would get **0 fee** for swap and moreover you would get accumulated fees from liquidity position that was provided for contract you did `performUpkeep()` to.\n\n## Why?\n\nLet's imagine situation that you are small protocol with little money that try to build code in the shortest period of time. Your smart-contract includes simple `AutomationCompatible` interface...\n\n1. Why do you need AutomationCompatible interface? This interface is usually used when smart-contract need to update some data dependint on other state-changing stuff onchain ([read more from chainlink](https://docs.chain.link/chainlink-automation)). This can be used in various ocasions, for example:\n - automate liquidations of unhealthy users\n - update contract state that should be updated when other contract state (external from your system) is also updated \n - when function need to be called consistently with some interval\n - and it's small part of what Automation can do to improve protocol...\n\nSo... Why not just use Chainlink or create own script to call smart-contract consistently??? Of courese you can, but...:\n - Own code. Firstly you need to create script that would check state as you want, then you need to somwhere deploy this script, you need to make sure this script never fails, you use RPC calls that can be very limited, you need to rent some server to host this script and more and more time and material expences.\n - Chainlink. Chainlink solves problem described above but it still need to be managed and more important, YOU STILL NEED TO PAY FOR TRANSACTION!!! (bet we dont😊)\n\nInstead **KeeperHook** add ability to protocol owners to provide liquidity which is preserved and does not disappear anywhere. And that's a pros for user as user make transaction, checks whether you contract need upkeep and perform upkeep if it's needed. This gives advantages to both the user and protocol owner. WIN-WIN SITUATION.\n\n\n## Here is Hook Diagram\n\n![KeeperHookDiagram.png](https://cdn.dorahacks.io/static/files/192a55af339c340436f4a14490fb35af.png)","teamDescription":"No team, just me. And I am Taras.","githubPage":"https://github.com/tarasnurko/keeperhook","githubVerify":0,"demoLink":null,"demoVideo":"https://youtu.be/dEvhqL_CpvI","ownerTitle":null,"ownerIntroduction":null,"twitterVerified":false,"weibo":null,"nft":null,"scOwner":"","editTime":1732434988,"upvotes":"0.00","isRecruitingEnabled":false,"recruitingInfo":"","recruitingLink":null,"twitter":null,"facebook":null,"instagram":null,"socialTelegram":null,"socialDiscord":null,"socialLinks":["https://t.me/tosiknur","https://github.com/tarasnurko","https://www.linkedin.com/in/tarasnurko/"],"showedFunding":false,"agentStatus":null,"createdAt":"2024-10-19T22:50:28.167948+08:00","updatedAt":"2024-10-20T00:32:57.183714+08:00","milestoneEditor":null,"path":"/buidl/17737","techField":"","techFieldAry":[],"techTree":[0],"tags":[65,66,122],"otherTags":["category:Automation"],"origin":"-","intro":"# KeeperHook\n\nIt's uniswap v4 based hook that allow users exchange their transaction work in return of lower swap fees and additional collected fee from appropriate liquidity position in current pool.\n\n## Guide for protocol owner (team member)\n\nYou are one of protocol members. First you need to mint some liquidity position using UniSwap V4 [PositionManager](https://github.com/Uniswap/v4-periphery/blob/main/src/PositionManager.sol). It would be better for you if you would mint liquidity position on pool with high usage (highest swap count per amo9unt of time) as more frequently users make swaps, less time there would be between check upkeep calls (which is good for you). After you selected good pair and created liquidity position with good enough for you amound of liquidity you deposit this liquidity position to `KeeperHook` (also dont forget to call `KeeperHook.setKeepersData()` to set desired max gas and your contract that uses `AutomationCompatible` interface). Aaaaaand, THATS ALL🎉🎉🎉. Now every user that make swap in pool (where you minted liquidity position) would check and perform upkeep (if needed). Be carefull to implement `AutomationCompatible` interface because if you make that `checkUpkeep()` or `performUpkeep()` make damage to user (they always revert or use all gas) than this contract as you would be considered malicious and you would be subsequent to **SLASH** (all deposits would be taken from you and your contract would be out of systam that means your contract would not be checked for upkeeps).\n\n## Guide for user\n\nFind pool with hook `KeeperHook`, and make swaps. If you `performUpkeep()` you would get **0 fee** for swap and moreover you would get accumulated fees from liquidity position that was provided for contract you did `performUpkeep()` to.\n\n## Why?\n\nLet's imagine situation that you are small protocol with little money that try to build code in the shortest period of time. Your smart-contract includes simple `AutomationCompatible` interface...\n\n1. Why do you need AutomationCompatible interface? This interface is usually used when smart-contract need to update some data dependint on other state-changing stuff onchain ([read more from chainlink](https://docs.chain.link/chainlink-automation)). This can be used in various ocasions, for example:\n - automate liquidations of unhealthy users\n - update contract state that should be updated when other contract state (external from your system) is also updated \n - when function need to be called consistently with some interval\n - and it's small part of what Automation can do to improve protocol...\n\nSo... Why not just use Chainlink or create own script to call smart-contract consistently??? Of courese you can, but...:\n - Own code. Firstly you need to create script that would check state as you want, then you need to somwhere deploy this script, you need to make sure this script never fails, you use RPC calls that can be very limited, you need to rent some server to host this script and more and more time and material expences.\n - Chainlink. Chainlink solves problem described above but it still need to be managed and more important, YOU STILL NEED TO PAY FOR TRANSACTION!!! (bet we dont😊)\n\nInstead **KeeperHook** add ability to protocol owners to provide liquidity which is preserved and does not disappear anywhere. And that's a pros for user as user make transaction, checks whether you contract need upkeep and perform upkeep if it's needed. This gives advantages to both the user and protocol owner. WIN-WIN SITUATION.\n\n\n## Here is Hook Diagram\n\n![KeeperHookDiagram.png](https://cdn.dorahacks.io/static/files/192a55af339c340436f4a14490fb35af.png)","images":["https://cdn.dorahacks.io/static/files/192a53ce18140c016a5e01f45f68a31a.jpg"],"team":"No team, just me. And I am Taras.","github":"https://github.com/tarasnurko/keeperhook","demo":null,"video":"https://youtu.be/dEvhqL_CpvI","socialTwitter":null,"socialFacebook":null,"socialInstagram":null,"nftId":null,"haxonBuidls":[{"id":19296,"projectId":17737,"name":"KeeperHook","track":"All BUIDLs","bounties":[],"haxonId":653,"haxonName":"ETHKyiv Impulse: Uniswap V4 Hooks Edition","status":2,"haxonCreateAt":"2024/10/19 05:30:00 UTC"}],"kudoData":null,"bountyObjs":[],"tracks":[],"badges":["{\"schema\":\"BADGE\",\"d\":{\"index\":\"b15265\",\"badgeType\":\"buidl\",\"path\":\"/buidl/17737/achievement/b15265\",\"ownerId\":17737,\"iconName\":\"b0\",\"updatedDate\":\"2024/10/19\",\"title\":\"ETHKyiv Impulse: Uniswap V4 Hooks Edition\",\"detail\":\"Participation\",\"tag\":\"Hackathon\",\"imageUrl\":\"https://cdn.dorahacks.io/static/badge/b0_ETHKyiv~c32Impulse:~c32Uniswap~c32V4~c32Hooks~c32Edition.webp\",\"shareImageUrl\":\"https://cdn.dorahacks.io/static/badge/b0_ETHKyiv~c32Impulse:~c32Uniswap~c32V4~c32Hooks~c32Edition.jpg\",\"id\":15265,\"metaInfo\":{\"type\":\"HACKATHON_PARTICIPATION\",\"hackathonId\":653,\"title\":\"ETHKyiv Impulse: Uniswap V4 Hooks Edition\"},\"createdAt\":1729353223,\"updatedAt\":1729353223,\"type\":0,\"subjectId\":653,\"metadata\":{},\"buidl\":17737}}"]}}