{"schema":"HACKATHON","d":{"id":514,"tabSet":[{"id":903,"name":"Submission Guide","slug":"submission-guide","description":"# **Getting Started [3-5 MIN]**\n\n**1.** **Submit your BUIDL via [DoraHacks.io](https://dorahacks.io/).** To begin, you’ll need a DoraHacks account. Click the **Login** button in the top-right corner to sign up.\n\n

\n\nYou can create an account with **GitHub, a crypto wallet**, or your **email address**. We recommend using **GitHub** to reach a wider audience with your project\n\n*Note: You may be asked to verify your email. The code can take a few minutes to arrive, but don’t worry—it will be valid for 10 minutes after you click “**send code**.”\n\n**2.** Make sure to add your GitHub link to your project before the submission deadline. You can submit first and make edits until the hackathon submission deadline.\n\nClick “**Submit BUIDL**” to open the Hackathon submission form.\n\n

\n\n> **→ Already have a BUIDL on DoraHacks?**\n> \n\nClick “Use Existing BUIDL” and select your project. Choose the track you'd like to join, answer the organizer’s questions, and then click “Submit for review.”\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

\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 submission, you’ll see a notification confirming your project has been submitted.\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/514/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# Need to Update Your BUIDL?\n\nTo make changes to your project, click [Avatar] -> [Profile] to access your Account Center. Then, click the \"**Edit**\" button on the top right of your BUIDL to update your BUIDL information.\n\n

\n\n

"},{"id":904,"name":"Developer Toolkit","slug":"developer-toolkit","description":"# Developer Resources\n\n- **Website:** [Reactive Network](https://reactive.network/)\n- **Docs:** [Reactive Documentation](https://dev.reactive.network/)\n- **Education:** [Educational course on Reactive Network](https://dev.reactive.network/education/introduction)\n- **Testnet Information:** [Kopli Testnet](https://dev.reactive.network/kopli-testnet)\n- **Start Building:** [**Boilerplate Repo**](https://github.com/Reactive-Network/hackathon)\n- [**YouTube**](http://www.youtube.com/@0xReactive)\n\n# Developer Office Hours\n\n- Wednesday 19.09, 10:00 - 18:00 UTC+3\n- Friday 21.09, 10:00 - 18:00 UTC+3\n- Monday 24.09, 10:00 - 18:00 UTC+3\n- Wednesday 26.09, 10:00 - 18:00 UTC+3\n- Friday 28.09, 10:00 - 18:00 UTC+3\n\nIf you have any additional questions about the event or need technical support, feel free to reach out to us on our official Reactive Network [Telegram](https://t.me/reactivedevs) and [Discord](https://discord.gg/D5ch9ajgfP)."},{"id":905,"name":"Track Descriptions","slug":"track-descriptions","description":"# 1. Open Track\n**Prizes:**\n- 1st place: 5000 USDT\n- 2nd place: 2000 USDT\n- 3rd place: 1000 USDT\n\nThis track is designed for the most ambitious and competitive participants. We are looking for significantly new ideas on how Reactive Smart Contracts (RSCs) can be utilized. Applications may include RSCs, Ethereum smart contracts, and possibly backend and frontend components. The focus will be on creativity, business meaningfulness (e.g., saving money, generating revenue, or improving user experience). We encourage improvements to existing dApps or DeFi workflows, though completely new dApps are also welcome.\n\nA successful application MUST:\n- Contain the Reactive Smart Contracts and Destination smart contracts, the deploy script, and the instructions for it.\n- If the application uses its own Origin contracts, the repository MUST also include these contracts, along with their deploy scripts and instructions.\n- It MUST contain the address of the Reactive Smart Contracts deployed by the team.\n- It MUST contain the addresses of the Origins and Destination smart contracts.\n- It MUST contain a detailed explanation of the problem Reactive Smart Contracts solve in that use case and why it is more difficult or even impossible to achieve without them.\n- It MUST contain the step-by-step text description of how this setup works after being deployed.\n- The team MUST run this workflow. The application MUST include the transaction hashes for every step of the workflow, for Origin transactions, Reactive transactions, and Destination transactions.\n- The application MUST contain a presentation video not longer than 5 minutes. The video might contain slides, narration, app or code demonstration, depending on what the team finds more persuasive. The judges will watch the video, as well as read the code and the docs.\n\nThe applications will be evaluated based on the following criteria:\n- Whether Reactive Smart Contracts in this use case solve an important problem that could not be solved or could be solved less optimally without them.\n- How well the use case is explained and justified.\n- Code quality, security, readability.\n\n# 2. Pangolin Track\n**Prizes:**\n- 1st place: 2000 USDT\n- 2nd place: 1000 USDT\n- 3rd place: 500 USDT\n\nThis track is sponsored by our partners Pangolin exchange. We ask the participants to use Reactive Smart Contracts to add new functionality to a DEX. The teams can build on top of the Pangolin smart contracts or emulate a DEX using their own smart contracts. The focus will be on creativity and business meaningfulness (e.g., saving money, generating revenue, or improving user experience).\n\nA successful application MUST:\n- Contain the Reactive Smart Contracts and Destination smart contracts, the deploy script, and the instructions for it.\n- If the application uses its own Origin contracts, the repository MUST also include these contracts, along with their deploy scripts and instructions.\n- It MUST be integrated with a DEX.\n- It MUST contain the address of the Reactive Smart Contracts deployed by the team.\n- It MUST contain the addresses of the Origins and Destination smart contracts.\n- It MUST contain a detailed explanation of the problem Reactive Smart Contracts solve in that use case and why it is more difficult or even impossible to achieve without them.\n- It MUST contain the step-by-step text description of how this setup works after being deployed.\n- The team MUST run this workflow. The application MUST include the transaction hashes for every step of the workflow, for Origin transactions, Reactive transactions, and Destination transactions.\n- The application MUST contain a presentation video not longer than 5 minutes. The video might contain slides, narration, app or code demonstration, depending on what the team finds more persuasive. The judges will watch the video, as well as read the code and the docs.\n\nThe applications will be evaluated based on the following criteria:\n- Whether Reactive Smart Contracts in this use case solve an important problem that could not be solved or could be solved less optimally without them.\n- How well the use case is explained and justified.\n- Code quality, security, readability.\n\n# 3. Template Deployer Track\n**Prizes:**\n- 1st place: 2000 USDT\n- 2nd place: 1000 USDT\n- 3rd place: 500 USDT\n\nParticipants in this track will develop templates for simple RSCs that address specific use cases for end users or developers, along with a Web3 app to deploy these RSCs. The focus is on creating automation on top of existing dApps without altering their code. This track aims to broaden the accessibility of RSCs, allowing users to utilize them without needing to write new contracts. The app may have one or several templates to choose from.\n\nA successful application MUST:\n- Implement a Web3 app that allows users to connect their wallet, input some parameters needed for deployment (contract or wallet addresses, thresholds, etc.) and deploy a template Reactive Smart Contract without needing to write any code.\n- Contain the Reactive Smart Contracts and Destination smart contracts, the deploy script, and the instructions for it.\n- If the application uses its own Origin contracts, the repository MUST also include these contracts, along with their deploy scripts and instructions.\n- It MUST contain the address of the Reactive Smart Contracts deployed by the team.\n- It MUST contain the addresses of the Origins and Destination smart contracts.\n- It MUST contain a detailed explanation of the problem Reactive Smart Contracts solve in that use case and why it is more difficult or even impossible to achieve without them.\n- It MUST contain the step-by-step text description of how this setup works after being deployed.\n- The team MUST run this workflow. The application MUST include the transaction hashes for every step of the workflow, for Origin transactions, Reactive transactions, and Destination transactions.\n- The application MUST contain a presentation video not longer than 5 minutes. The video MUST contain the app demonstration and narration. The judges will watch the video, as well as read the code and the docs.\n\nThe applications will be evaluated based on the following criteria:\n- Whether Reactive Smart Contract templates in this application solve an important end user problem that could not be solved or could be solved less optimally without them.\n- How well the use case is explained and justified.\n- Code quality, security, readability.\n\n# 4. No-Code Track\n**Prizes:**\n- 1st place: 800 USDT\n- 2nd place: 400 USDT\n- 3rd place: 200 USDT\n\nThis track welcomes participants who may not have coding skills but can still contribute valuable ideas. They can participate by describing a use case, its business essence, and technical specifications in detail, and presenting it clearly and concisely. It may also include schemes or other visual materials. Since no code is required in this track, the expectations for the quality of the ideas, explanations, and presentation are high.\n\nA successful application MUST:\n- Contain a detailed text description of the use case.\n- It MUST contain a presentation video not longer than 5 minutes. The video might contain slides, narration, or mockup demonstration, depending on what the team finds more persuasive. The judges will watch the video, as well as read the text description.\n\nThe applications will be evaluated based on the following criteria:\n- Whether Reactive Smart Contracts in this use case solve an important problem that could not be solved or could be solved less optimally without them.\n- How well the use case is explained and justified.\n- Text and video quality.\n\n# 5. Bi-Weekly Challenges\n**Prizes:**\n- 1st place: 700 USDT for each challenge\n\nOn the 2nd, 4th, and 6th weeks of the Hackathon we will present Bi-Weekly Challenges. Each challenge will have 1 prize for the best application, the size of the prize will be 700 USDT. The submission deadlines will be at the end of 3rd, 5th, and 7th weeks, respectively. Make sure to apply for the corresponding [bounty](https://dorahacks.io/hackathon/reactive-hackathon/bounties)"},{"id":906,"name":"Workshop","slug":"workshop","description":"# Workshops (Dates to be finalized)\n| Date | Event | Link |\n|-------------------|------------------------------------------------------------|----------------------------------------------------------------------|\n| August 14 (Wed) | Reactive Network, ReactVM, and Dynamic Subscriptions (2:00 PM UTC) | [Watch](https://www.youtube.com/watch?v=Ur7N3TfQs-0) |\n| September 5 (Thu)| Master the Basics of Reactive Network: Workshop with EatTheBlocks (3:00 PM UTC) | [Watch](https://www.youtube.com/live/bNXmyipHoBM) | |\n| September 11 (Wed) | Introduction to Reactive Hackathon, Tracks, Judging Criteria, and Q/A (2:00 PM UTC) | [Watch](https://www.youtube.com/watch?v=30dfFXnueeI) |\n| September 18 (Wed) | Introduction to Reactive Smart Contracts (2:00 PM UTC)| [Watch](https://www.youtube.com/watch?v=VGKd0m5_6NQ) |\n| September 25 (Wed) | ReactVM and Important Tips (2:00 PM UTC) | [Watch](https://www.youtube.com/live/EH59XBdp9vk?si=dYcoKaFDH2-NxSy8) |\n| October 9 (Wed) | Reactive Hackathon: Reactive Bridge Challenge Winner (2:00 PM UTC) | [Watch](https://www.youtube.com/watch?v=vIC7TeFHiXI) |\n\n# Workshop 1: Reactive Network, ReactVM, and Dynamic Subscriptions (August 14 at 2:00 PM UTC)\n![youtube](https://www.youtube.com/watch?v=Ur7N3TfQs-0)\n\n# Workshop 2: Master the Basics of Reactive Network: Workshop with EatTheBlocks (September 5 at 3:00 PM UTC)\n[Watch on YouTube](https://www.youtube.com/live/bNXmyipHoBM)\n\n# Workshop 3: Introduction to Reactive Hackathon, Tracks, Judging Criteria, and Q/A (September 11 at 2:00 PM UTC)\n![youtube](https://www.youtube.com/watch?v=30dfFXnueeI)\n\n# Workshop 4: Introduction to Reactive Smart Contracts(September 18 at 2:00 PM UTC)\n![youtube](https://www.youtube.com/watch?v=VGKd0m5_6NQ)\n\n# Workshop 5: ReactVM and Important Tips (September 25 at 2:00 PM UTC)\n[Watch on YouTube](https://www.youtube.com/live/EH59XBdp9vk)\n\n# Workshop 6: Reactive Hackathon: Reactive Bridge Challenge Winner (October 9 at 2:00 PM UTC)\n![youtube](https://www.youtube.com/watch?v=vIC7TeFHiXI)"}],"skills":null,"applied":false,"isCurrentHackerRegistered":false,"buidlsCount":21,"applicationsCount":24,"organization":{"id":2445,"name":"Reactive Network","logo":"https://cdn.dorahacks.io/static/files/1906cff88f1ec6faf5376dd4eab9e7c9.png"},"description":"# 🚀 Reactive Hackathon\n\nWelcome to the [Reactive Hackathon](https://reactive.network/hackathon), where innovation meets opportunity! This hackathon is designed for blockchain developers who are ready to push the boundaries of decentralized technology and create groundbreaking dApps using Reactive Smart Contracts.\n\nReactive Network is at the forefront of blockchain evolution, offering a fully EVM-compatible execution layer that empowers developers to build the next wave of decentralized applications. Unlike traditional smart contracts, Reactive Smart Contracts leverage Inversion-of-Control to autonomously react to on-chain events, driving seamless interactions across multiple blockchains without user intervention. This innovation opens up new possibilities for automation, efficiency, and interconnectivity in the blockchain ecosystem.\n\n# ⚡️Why Reactive?\n\n![Screenshot 2024-08-07 151621.png](https://cdn.dorahacks.io/static/files/1912d3475c1b36d268bfb0f41b19dd9c.png)\n\n## Reactive Smart Contracts\nAutonomously react to blockchain events, automating complex financial instruments and DeFi applications. [Learn more](https://dev.reactive.network/reactive-smart-contracts)\n\n## ReactVM\nA specialized EVM enabling multi-threaded, random order transaction execution for efficient smart contract operations. [Learn more](https://dev.reactive.network/reactvm)\n\nFor more detailed information, visit our [documentation](https://dev.reactive.network/).\n\n## Start Building\nTo start building, use our [boilerplate repo](https://github.com/Reactive-Network/hackathon).\n\n# 🏆 Tracks and Prize Distribution\n- Open Track: 1st place: 5000 USDT, 2nd place: 2000 USDT, 3rd place: 1000 USDT.\n- Pangolin Track: 1st place: 2000 USDT, 2nd place: 1000 USDT, 3rd place: 500 USDT.\n- Template Deployer Track: 1st place: 2000 USDT, 2nd place: 1000 USDT, 3rd place: 500 USDT.\n- No-Code Track: 1st place: 800 USDT, 2nd place: 400 USDT, 3rd place: 200 USDT.\n- Bi-Weekly Challenges: 1st place: 700 USDT for each of 3 challenges.\n- Grant Program: 35 000 USDT allocated to the best projects (details to be announced).\n\nFor more detailed information, visit [Track Challenge](https://dorahacks.io/hackathon/reactive-hackathon/track-challenge).\n\n\n# 💬 Official Communication Channel\nWe will mainly provide support on the official Reactive Network [Telegram](https://t.me/reactivedevs)/ [Discord](https://discord.gg/D5ch9ajgfP) channel.\n\n# 📅 Key Dates\n\n| Date | Event | Link |\n|------------------------------------|------------------------------------------------------------------|----------------------------------------------------------------------|\n| August 14 (Wed) | Reactive Network, ReactVM, and Dynamic Subscriptions Workshop (2:00 PM UTC) | [Watch](https://www.youtube.com/watch?v=Ur7N3TfQs-0) |\n| September 5 (Thu)| Master the Basics of Reactive Network: Workshop with EatTheBlocks (3:00 PM UTC) | [Watch](https://www.youtube.com/live/bNXmyipHoBM) |\n| September 9 (Mon) | Hackathon kick-off & Submission period begins | | |\n| September 11 (Wed) | Workshop: Introduction to Reactive Hackathon, Tracks, Judging Criteria, and Q/A (2:00 PM UTC) | [Watch](https://www.youtube.com/watch?v=30dfFXnueeI) |\n| September 18 (Wed) | Introduction to Reactive Smart Contracts (2:00 PM UTC) | [Watch](https://www.youtube.com/watch?v=VGKd0m5_6NQ) |\n| September 25 (Wed) | ReactVM and Important Tips (2:00 PM UTC) | [Watch](https://www.youtube.com/live/EH59XBdp9vk?si=dYcoKaFDH2-NxSy8) |\n| October 9 (Wed) | Reactive Hackathon: Reactive Bridge Challenge Winner (2:00 PM UTC) | [Watch](https://www.youtube.com/watch?v=vIC7TeFHiXI) |\n| November 4 (Mon) | Final date of submission | |\n| November 5 (Tue) - November 10 (Sun) | Review period | |\n| November 11 (Mon) | Winners announced | |\n| November 13 (Wed) | Finalists demo (Livestream) | [Watch](#) | \n\n\n# 👥 Judging Panel and Partners\n\n![Screenshot 2024-09-02 130029.png](https://cdn.dorahacks.io/static/files/191b29d93209ddad2efd4cc47b387ddb.png)\n\n| Name | Company/Organization | Title |\n|----------------|---------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Abhinav Sharma | [Intract](https://www.intract.io/) | Vice President of Engineering at [Intract](https://www.intract.io/). An experienced software engineer with a rich background in leading tech teams and managing projects. He has held roles at Spyne, UXPotato, and Travographer. |\n| Kevin Callahan | [Uniblock](https://www.uniblock.dev/) | CEO and Co-Founder of [Uniblock](https://www.uniblock.dev/). Previously held roles at Coinbase and Twitter. Experienced in entrepreneurship, strategy, and product management, dedicated to building impactful products and tech education. |\n| Artem ZAITSEV | QSTN / [Idealogic](https://www.idealogic.io/) | VP of Engineering at [Idealogic](https://www.idealogic.io/), currently CTO at QSTN. A seasoned CTO, technical adviser, and startup mentor with over a decade of experience in software development and management. |\n| Lam Trinh | [Colors of Web3 & Entrepreneurship podcast](https://lamtrinh.xyz/) | Web3 Product Manager / Engineer, host of the Colors of Web3 & Entrepreneurship podcast, Full-stack data scientist, AWS-certified Solutions Architect. |\n| Idris Olubisi | [Axelar](https://www.axelar.network/) | Developer Advocate at [Axelar](https://www.axelar.network/). Accomplished software engineer and technical writer with expertise in open source, blockchain, software products, and serverless technologies. |\n| Andy Cho | [IQ](https://iq.wiki/) & [Frax Finance](https://frax.finance/) | COO at [IQ](https://iq.wiki/) and Director of Ecosystem & Strategies at [Frax Finance](https://frax.finance/). Leads all operations at IQ and oversees the expansion of Frax’s Ecosystem. |\n| AK | [Burve Protocol](https://linktr.ee/burveprotocol) | Co-founder of [Burve Protocol](https://linktr.ee/burveprotocol). Holds a Master of IT and a PhD in Economics. A serial entrepreneur with a deep belief in the transformative power of cryptocurrency. |\n| PETER PRADO | [Lekker Finance](https://lekker.finance/) | Creator of [Lekker Finance](https://lekker.finance/), winner of EthLisbon. Foundational protocol for onchain derivatives like leverage and token hedging. Provides access for dApps and DeFi projects to leverage billions in liquidity. |\n| Mary Tran | [Orochi Network](https://www.orochi.network/) | Cofounder and CEO of Orochi Network - Building the world first zero knowledge modular data availability layer. 9+ years of experience in blockchain and crypto space. |\n| Sameep Singhania | [QuickSwap](https://quickswap.exchange/) | Lead developer and advisor at ParaSwap and contributing to [QuickSwap](https://quickswap.exchange/).|","onboardingCompleted":false,"registerFormUrl":null,"preRegisterTime":0,"publicContactHackerHandle":"reactive","hackersCount":305,"tracks":["{\"schema\":\"HACKATHON_TRACK\",\"d\":{\"id\":1408,\"name\":\"Open Track\",\"judgingCriteria\":\"The prizes for the Open Track: 1st place – 5000 USDT, 2nd place – 2000 USDT, 3rd place – 1000 USDT. This track is designed for the most ambitious and competitive participants. We are looking for significantly new ideas on how Reactive Smart Contracts (RSCs) can be utilized. Applications may include RSCs, Ethereum smart contracts, and possibly backend and frontend components. The focus will be on creativity, business meaningfulness (e.g., saving money, generating revenue, or improving user experience). We encourage improvements to existing dApps or DeFi workflows, though completely new dApps are also welcome.\\n\\nA successful application MUST:\\n- Contain the Reactive Smart Contracts and Destination smart contracts, the deploy script, and the instructions for it.\\n- If the application uses its own Origin contracts, the repository MUST also include these contracts, along with their deploy scripts and instructions.\\n- It MUST contain the address of the Reactive Smart Contracts deployed by the team.\\n- It MUST contain the addresses of the Origins and Destination smart contracts.\\n- It MUST contain a detailed explanation of the problem Reactive Smart Contracts solve in that use case and why it is more difficult or even impossible to achieve without them.\\n- It MUST contain the step-by-step text description of how this setup works after being deployed.\\n- The team MUST run this workflow. The application MUST include the transaction hashes for every step of the workflow, for Origin transactions, Reactive transactions, and Destination transactions.\\n- The application MUST contain a presentation video not longer than 5 minutes. The video might contain slides, narration, app or code demonstration, depending on what the team finds more persuasive. The judges will watch the video, as well as read the code and the docs.\\n\\nThe applications will be evaluated based on the following criteria:\\n- Whether Reactive Smart Contracts in this use case solve an important problem that could not be solved or could be solved less optimally without them.\\n- How well the use case is explained and justified.\\n- Code quality, security, readability.\",\"weight\":5}}","{\"schema\":\"HACKATHON_TRACK\",\"d\":{\"id\":1521,\"name\":\"Pangolin Track\",\"judgingCriteria\":\"The prizes for the Pangolin Track: 1st place – 2000 USDT, 2nd place – 1000 USDT, 3rd place – 500 USDT. This track is sponsored by our partners Pangolin exchange. We ask the participants to use Reactive Smart Contracts to add new functionality to a DEX. The teams can build on top of the Pangolin smart contracts or emulate a DEX using their own smart contracts. The focus will be on creativity and business meaningfulness (e.g., saving money, generating revenue, or improving user experience).\\n\\nA successful application MUST:\\n- Contain the Reactive Smart Contracts and Destination smart contracts, the deploy script, and the instructions for it.\\n- If the application uses its own Origin contracts, the repository MUST also include these contracts, along with their deploy scripts and instructions.\\n- It MUST be integrated with a DEX.\\n- It MUST contain the address of the Reactive Smart Contracts deployed by the team.\\n- It MUST contain the addresses of the Origins and Destination smart contracts.\\n- It MUST contain a detailed explanation of the problem Reactive Smart Contracts solve in that use case and why it is more difficult or even impossible to achieve without them.\\n- It MUST contain the step-by-step text description of how this setup works after being deployed.\\n- The team MUST run this workflow. The application MUST include the transaction hashes for every step of the workflow, for Origin transactions, Reactive transactions, and Destination transactions.\\n- The application MUST contain a presentation video not longer than 5 minutes. The video might contain slides, narration, app or code demonstration, depending on what the team finds more persuasive. The judges will watch the video, as well as read the code and the docs.\\n\\nThe applications will be evaluated based on the following criteria:\\n- Whether Reactive Smart Contracts in this use case solve an important problem that could not be solved or could be solved less optimally without them.\\n- How well the use case is explained and justified.\\n- Code quality, security, readability.\",\"weight\":4}}","{\"schema\":\"HACKATHON_TRACK\",\"d\":{\"id\":1522,\"name\":\"Template Deployer Track\",\"judgingCriteria\":\"The prizes for the Template Deployer Track: 1st place – 2000 USDT, 2nd place – 1000 USDT, 3rd place – 500 USDT. Participants in this track will develop templates for simple RSCs that address specific use cases for end users or developers, along with a Web3 app to deploy these RSCs. The focus is on creating automation on top of existing dApps without altering their code. This track aims to broaden the accessibility of RSCs, allowing users to utilize them without needing to write new contracts. The app may have one or several templates to choose from.\\n\\nA successful application MUST:\\n- Implement a Web3 app that allows users to connect their wallet, input some parameters needed for deployment (contract or wallet addresses, thresholds, etc.) and deploy a template Reactive Smart Contract without needing to write any code.\\n- Contain the Reactive Smart Contracts and Destination smart contracts, the deploy script, and the instructions for it.\\n- If the application uses its own Origin contracts, the repository MUST also include these contracts, along with their deploy scripts and instructions.\\n- It MUST contain the address of the Reactive Smart Contracts deployed by the team.\\n- It MUST contain the addresses of the Origins and Destination smart contracts.\\n- It MUST contain a detailed explanation of the problem Reactive Smart Contracts solve in that use case and why it is more difficult or even impossible to achieve without them.\\n- It MUST contain the step-by-step text description of how this setup works after being deployed.\\n- The team MUST run this workflow. The application MUST include the transaction hashes for every step of the workflow, for Origin transactions, Reactive transactions, and Destination transactions.\\n- The application MUST contain a presentation video not longer than 5 minutes. The video MUST contain the app demonstration and narration. The judges will watch the video, as well as read the code and the docs.\\n\\nThe applications will be evaluated based on the following criteria:\\n- Whether Reactive Smart Contract templates in this application solve an important end user problem that could not be solved or could be solved less optimally without them.\\n- How well the use case is explained and justified.\\n- Code quality, security, readability.\",\"weight\":3}}","{\"schema\":\"HACKATHON_TRACK\",\"d\":{\"id\":1523,\"name\":\"No-Code Track\",\"judgingCriteria\":\"The prizes for the No-Code Track: 1st place – 800 USDT, 2nd place – 400 USDT, 3rd place – 200 USDT. This track welcomes participants who may not have coding skills but can still contribute valuable ideas. They can participate by describing a use case, its business essence, and technical specifications in detail, and presenting it clearly and concisely. It may also include schemes or other visual materials. Since no code is required in this track, the expectations for the quality of the ideas, explanations, and presentation are high.\\n\\nA successful application MUST:\\n- Contain a detailed text description of the use case.\\n- It MUST contain a presentation video not longer than 5 minutes. The video might contain slides, narration, or mockup demonstration, depending on what the team finds more persuasive. The judges will watch the video, as well as read the text description.\\n\\nThe applications will be evaluated based on the following criteria:\\n- Whether Reactive Smart Contracts in this use case solve an important problem that could not be solved or could be solved less optimally without them.\\n- How well the use case is explained and justified.\\n- Text and video quality.\",\"weight\":2}}","{\"schema\":\"HACKATHON_TRACK\",\"d\":{\"id\":1526,\"name\":\"Bi-Weekly Challenges\",\"judgingCriteria\":\"On the 2nd, 4th, and 6th weeks of the Hackathon we will present Bi-Weekly Challenges. Each challenge will have 1 prize for the best application, the size of the prize will be 700 USDT. The submission deadlines will be at the end of 3rd, 5th, and 7th weeks, respectively. Make sure to apply for the corresponding [bounty](https://dorahacks.io/hackathon/reactive-hackathon/bounties)\",\"weight\":1}}"],"sponsors":[{"id":585,"bounties":[{"id":719,"name":"Challenge One: Reactive Bridge dApp","token":"USDT","bonus":700,"link":"","description":"Develop a bridge that transfers tokens between two chains. When tokens on one chain are deposited, a Reactive Smart Contract triggers token release to the user on the other chain. The application should implement smart contracts (Reactive and usual) and the frontend. The frontend should provide links to transactions on all three chains (Origin, Reactive, Destination) after the tokens are transferred to another chain. Use any two or more chains supported by Reactive Network. \n\nA successful application MUST:\n- Be submitted before Wednesday, October 2, 2 PM UTC\n- Implement a Web3 Reactive Bridge dApp.\n- Include the Reactive contracts, Destination contracts, deploy scripts, and instructions.\n- If the application uses custom Origin contracts, the repository MUST also include these contracts with their deploy scripts and instructions.\n- Provide the addresses of the deployed Reactive contracts.\n- Provide the addresses of the Origin and Destination contracts.\n- Contain a step-by-step text description of how the setup operates after deployment.\n- Execute the workflow and include the transaction hashes for every step, including Origin, Reactive, and Destination transactions.\n- Include a presentation video no longer than 5 minutes with dApp demonstration. The judges will review both the video and the accompanying code and documentation.\n\nThe applications will be evaluated based on the following criteria:\n- How well the application solves the use case described above.\n- Code quality, security, readability."},{"id":744,"name":"Challenge Two: Reactive Cross-Chain Lending","token":"USDT","bonus":700,"link":"","description":"Develop a lending protocol that allows providing collateral on one chain and receiving and returning the loan on the other. The application should implement smart contracts (Reactive and usual) and the frontend. The frontend should provide links to transactions on all three chains (Origin, Reactive, Destination). Use any two or more chains supported by Reactive Network.\n\nA successful application MUST:\n- Be submitted before Wednesday, October 23, 2 PM UTC\n- Implement a Web3 Cross-Chain Lending dApp.\n- Include the Reactive contracts, Destination contracts, deploy scripts, and instructions.\n- If the application uses custom Origin contracts, the repository MUST also include these contracts with their deploy scripts and instructions.\n- Provide the addresses of the deployed Reactive contracts.\n- Provide the addresses of the Origin and Destination contracts.\n- Contain a step-by-step text description of how the setup operates after deployment.\n- Execute the workflow and include the transaction hashes for every step, including Origin, Reactive, and Destination transactions.\n- Include a presentation video no longer than 5 minutes with dApp demonstration. The judges will review both the video and the accompanying code and documentation.\n\nThe applications will be evaluated based on the following criteria:\n- How well the application solves the use case described above.\n- Code quality, security, readability."}],"bountyCount":2,"totalBonus":1400,"name":"Reactive Network","logo":"https://cdn.dorahacks.io/static/files/1906cff88f1ec6faf5376dd4eab9e7c9.png","weight":1,"description":"Reactive Smart Contracts (RSCs) represent a paradigm shift in how we interact with blockchain technology. Unlike traditional smart contracts that are run by user transactions, RSCs actively monitor events on EVM-compatible chains and react to them. They process these events according to the implemented logic and execute further actions on the blockchain autonomously. This innovation introduces a decentralized mechanism for automating responses to on-chain events without manual actions.","isCurrentOrg":true}],"bountiesCount":2,"amaciJudgingCount":0,"isPublicBountyJudging":false,"title":"Reactive Hackathon - Hacking the Next Generation of Smart Contracts","uname":"reactive-hackathon","imageUrl":"https://cdn.dorahacks.io/static/files/191235269845bfb1d5ff72241eb82a74.jpeg","originUrl":null,"startTime":1725890400000,"endTime":1730728800000,"timezone":"-60","city":null,"visible":true,"approvalStatus":6,"state":0,"voteUrl":null,"voteMechanism":null,"bonusPrice":50000,"bonusMechanism":null,"followersCount":0,"ecosystem":["Ethereum","BNB Smart Chain","Avalanche"],"applyGuide":null,"weight":9001,"participationForm":"Virtual","field":["Blockchain","Layer1","EVM","Solidity","AI","DeFi","Gaming","Social"],"email":null,"contacts":["Telegram","Kishan_79"],"externalContacts":null,"telegram":"Kishan_79","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":false,"question":null,"countryId":null,"cityId":null,"venueName":null,"venueAddress":null,"category":1,"isEnableBounty":true,"isBountyRequired":false,"isEndedBountyJudging":false,"bountiesLimitForBuidl":10,"isMultiTracksAllowed":false,"tracksLimitForBuidl":0,"status":1,"isOrganizer":false,"password":null,"isAdmin":false,"isTrackJudge":false,"isBountyJudge":false,"tracksCount":5,"path":"/hackathon/reactive-hackathon","originURL":null,"image":"https://cdn.dorahacks.io/static/files/191235269845bfb1d5ff72241eb82a74.jpeg","voteURL":null,"tabs":["{\"schema\":\"HACKATHON_TAB\",\"d\":{\"id\":903,\"name\":\"Submission Guide\",\"slug\":\"submission-guide\",\"description\":\"# **Getting Started [3-5 MIN]**\\n\\n**1.** **Submit your BUIDL via [DoraHacks.io](https://dorahacks.io/).** To begin, you’ll need a DoraHacks account. Click the **Login** button in the top-right corner to sign up.\\n\\n

\\n\\nYou can create an account with **GitHub, a crypto wallet**, or your **email address**. We recommend using **GitHub** to reach a wider audience with your project\\n\\n*Note: You may be asked to verify your email. The code can take a few minutes to arrive, but don’t worry—it will be valid for 10 minutes after you click “**send code**.”\\n\\n**2.** Make sure to add your GitHub link to your project before the submission deadline. You can submit first and make edits until the hackathon submission deadline.\\n\\nClick “**Submit BUIDL**” to open the Hackathon submission form.\\n\\n

\\n\\n> **→ Already have a BUIDL on DoraHacks?**\\n> \\n\\nClick “Use Existing BUIDL” and select your project. Choose the track you'd like to join, answer the organizer’s questions, and then click “Submit for review.”\\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

\\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 submission, you’ll see a notification confirming your project has been submitted.\\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/514/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# Need to Update Your BUIDL?\\n\\nTo make changes to your project, click [Avatar] -> [Profile] to access your Account Center. Then, click the \\\"**Edit**\\\" button on the top right of your BUIDL to update your BUIDL information.\\n\\n

\\n\\n

\"}}","{\"schema\":\"HACKATHON_TAB\",\"d\":{\"id\":904,\"name\":\"Developer Toolkit\",\"slug\":\"developer-toolkit\",\"description\":\"# Developer Resources\\n\\n- **Website:** [Reactive Network](https://reactive.network/)\\n- **Docs:** [Reactive Documentation](https://dev.reactive.network/)\\n- **Education:** [Educational course on Reactive Network](https://dev.reactive.network/education/introduction)\\n- **Testnet Information:** [Kopli Testnet](https://dev.reactive.network/kopli-testnet)\\n- **Start Building:** [**Boilerplate Repo**](https://github.com/Reactive-Network/hackathon)\\n- [**YouTube**](http://www.youtube.com/@0xReactive)\\n\\n# Developer Office Hours\\n\\n- Wednesday 19.09, 10:00 - 18:00 UTC+3\\n- Friday 21.09, 10:00 - 18:00 UTC+3\\n- Monday 24.09, 10:00 - 18:00 UTC+3\\n- Wednesday 26.09, 10:00 - 18:00 UTC+3\\n- Friday 28.09, 10:00 - 18:00 UTC+3\\n\\nIf you have any additional questions about the event or need technical support, feel free to reach out to us on our official Reactive Network [Telegram](https://t.me/reactivedevs) and [Discord](https://discord.gg/D5ch9ajgfP).\"}}","{\"schema\":\"HACKATHON_TAB\",\"d\":{\"id\":905,\"name\":\"Track Descriptions\",\"slug\":\"track-descriptions\",\"description\":\"# 1. Open Track\\n**Prizes:**\\n- 1st place: 5000 USDT\\n- 2nd place: 2000 USDT\\n- 3rd place: 1000 USDT\\n\\nThis track is designed for the most ambitious and competitive participants. We are looking for significantly new ideas on how Reactive Smart Contracts (RSCs) can be utilized. Applications may include RSCs, Ethereum smart contracts, and possibly backend and frontend components. The focus will be on creativity, business meaningfulness (e.g., saving money, generating revenue, or improving user experience). We encourage improvements to existing dApps or DeFi workflows, though completely new dApps are also welcome.\\n\\nA successful application MUST:\\n- Contain the Reactive Smart Contracts and Destination smart contracts, the deploy script, and the instructions for it.\\n- If the application uses its own Origin contracts, the repository MUST also include these contracts, along with their deploy scripts and instructions.\\n- It MUST contain the address of the Reactive Smart Contracts deployed by the team.\\n- It MUST contain the addresses of the Origins and Destination smart contracts.\\n- It MUST contain a detailed explanation of the problem Reactive Smart Contracts solve in that use case and why it is more difficult or even impossible to achieve without them.\\n- It MUST contain the step-by-step text description of how this setup works after being deployed.\\n- The team MUST run this workflow. The application MUST include the transaction hashes for every step of the workflow, for Origin transactions, Reactive transactions, and Destination transactions.\\n- The application MUST contain a presentation video not longer than 5 minutes. The video might contain slides, narration, app or code demonstration, depending on what the team finds more persuasive. The judges will watch the video, as well as read the code and the docs.\\n\\nThe applications will be evaluated based on the following criteria:\\n- Whether Reactive Smart Contracts in this use case solve an important problem that could not be solved or could be solved less optimally without them.\\n- How well the use case is explained and justified.\\n- Code quality, security, readability.\\n\\n# 2. Pangolin Track\\n**Prizes:**\\n- 1st place: 2000 USDT\\n- 2nd place: 1000 USDT\\n- 3rd place: 500 USDT\\n\\nThis track is sponsored by our partners Pangolin exchange. We ask the participants to use Reactive Smart Contracts to add new functionality to a DEX. The teams can build on top of the Pangolin smart contracts or emulate a DEX using their own smart contracts. The focus will be on creativity and business meaningfulness (e.g., saving money, generating revenue, or improving user experience).\\n\\nA successful application MUST:\\n- Contain the Reactive Smart Contracts and Destination smart contracts, the deploy script, and the instructions for it.\\n- If the application uses its own Origin contracts, the repository MUST also include these contracts, along with their deploy scripts and instructions.\\n- It MUST be integrated with a DEX.\\n- It MUST contain the address of the Reactive Smart Contracts deployed by the team.\\n- It MUST contain the addresses of the Origins and Destination smart contracts.\\n- It MUST contain a detailed explanation of the problem Reactive Smart Contracts solve in that use case and why it is more difficult or even impossible to achieve without them.\\n- It MUST contain the step-by-step text description of how this setup works after being deployed.\\n- The team MUST run this workflow. The application MUST include the transaction hashes for every step of the workflow, for Origin transactions, Reactive transactions, and Destination transactions.\\n- The application MUST contain a presentation video not longer than 5 minutes. The video might contain slides, narration, app or code demonstration, depending on what the team finds more persuasive. The judges will watch the video, as well as read the code and the docs.\\n\\nThe applications will be evaluated based on the following criteria:\\n- Whether Reactive Smart Contracts in this use case solve an important problem that could not be solved or could be solved less optimally without them.\\n- How well the use case is explained and justified.\\n- Code quality, security, readability.\\n\\n# 3. Template Deployer Track\\n**Prizes:**\\n- 1st place: 2000 USDT\\n- 2nd place: 1000 USDT\\n- 3rd place: 500 USDT\\n\\nParticipants in this track will develop templates for simple RSCs that address specific use cases for end users or developers, along with a Web3 app to deploy these RSCs. The focus is on creating automation on top of existing dApps without altering their code. This track aims to broaden the accessibility of RSCs, allowing users to utilize them without needing to write new contracts. The app may have one or several templates to choose from.\\n\\nA successful application MUST:\\n- Implement a Web3 app that allows users to connect their wallet, input some parameters needed for deployment (contract or wallet addresses, thresholds, etc.) and deploy a template Reactive Smart Contract without needing to write any code.\\n- Contain the Reactive Smart Contracts and Destination smart contracts, the deploy script, and the instructions for it.\\n- If the application uses its own Origin contracts, the repository MUST also include these contracts, along with their deploy scripts and instructions.\\n- It MUST contain the address of the Reactive Smart Contracts deployed by the team.\\n- It MUST contain the addresses of the Origins and Destination smart contracts.\\n- It MUST contain a detailed explanation of the problem Reactive Smart Contracts solve in that use case and why it is more difficult or even impossible to achieve without them.\\n- It MUST contain the step-by-step text description of how this setup works after being deployed.\\n- The team MUST run this workflow. The application MUST include the transaction hashes for every step of the workflow, for Origin transactions, Reactive transactions, and Destination transactions.\\n- The application MUST contain a presentation video not longer than 5 minutes. The video MUST contain the app demonstration and narration. The judges will watch the video, as well as read the code and the docs.\\n\\nThe applications will be evaluated based on the following criteria:\\n- Whether Reactive Smart Contract templates in this application solve an important end user problem that could not be solved or could be solved less optimally without them.\\n- How well the use case is explained and justified.\\n- Code quality, security, readability.\\n\\n# 4. No-Code Track\\n**Prizes:**\\n- 1st place: 800 USDT\\n- 2nd place: 400 USDT\\n- 3rd place: 200 USDT\\n\\nThis track welcomes participants who may not have coding skills but can still contribute valuable ideas. They can participate by describing a use case, its business essence, and technical specifications in detail, and presenting it clearly and concisely. It may also include schemes or other visual materials. Since no code is required in this track, the expectations for the quality of the ideas, explanations, and presentation are high.\\n\\nA successful application MUST:\\n- Contain a detailed text description of the use case.\\n- It MUST contain a presentation video not longer than 5 minutes. The video might contain slides, narration, or mockup demonstration, depending on what the team finds more persuasive. The judges will watch the video, as well as read the text description.\\n\\nThe applications will be evaluated based on the following criteria:\\n- Whether Reactive Smart Contracts in this use case solve an important problem that could not be solved or could be solved less optimally without them.\\n- How well the use case is explained and justified.\\n- Text and video quality.\\n\\n# 5. Bi-Weekly Challenges\\n**Prizes:**\\n- 1st place: 700 USDT for each challenge\\n\\nOn the 2nd, 4th, and 6th weeks of the Hackathon we will present Bi-Weekly Challenges. Each challenge will have 1 prize for the best application, the size of the prize will be 700 USDT. The submission deadlines will be at the end of 3rd, 5th, and 7th weeks, respectively. Make sure to apply for the corresponding [bounty](https://dorahacks.io/hackathon/reactive-hackathon/bounties)\"}}","{\"schema\":\"HACKATHON_TAB\",\"d\":{\"id\":906,\"name\":\"Workshop\",\"slug\":\"workshop\",\"description\":\"# Workshops (Dates to be finalized)\\n| Date | Event | Link |\\n|-------------------|------------------------------------------------------------|----------------------------------------------------------------------|\\n| August 14 (Wed) | Reactive Network, ReactVM, and Dynamic Subscriptions (2:00 PM UTC) | [Watch](https://www.youtube.com/watch?v=Ur7N3TfQs-0) |\\n| September 5 (Thu)| Master the Basics of Reactive Network: Workshop with EatTheBlocks (3:00 PM UTC) | [Watch](https://www.youtube.com/live/bNXmyipHoBM) | |\\n| September 11 (Wed) | Introduction to Reactive Hackathon, Tracks, Judging Criteria, and Q/A (2:00 PM UTC) | [Watch](https://www.youtube.com/watch?v=30dfFXnueeI) |\\n| September 18 (Wed) | Introduction to Reactive Smart Contracts (2:00 PM UTC)| [Watch](https://www.youtube.com/watch?v=VGKd0m5_6NQ) |\\n| September 25 (Wed) | ReactVM and Important Tips (2:00 PM UTC) | [Watch](https://www.youtube.com/live/EH59XBdp9vk?si=dYcoKaFDH2-NxSy8) |\\n| October 9 (Wed) | Reactive Hackathon: Reactive Bridge Challenge Winner (2:00 PM UTC) | [Watch](https://www.youtube.com/watch?v=vIC7TeFHiXI) |\\n\\n# Workshop 1: Reactive Network, ReactVM, and Dynamic Subscriptions (August 14 at 2:00 PM UTC)\\n![youtube](https://www.youtube.com/watch?v=Ur7N3TfQs-0)\\n\\n# Workshop 2: Master the Basics of Reactive Network: Workshop with EatTheBlocks (September 5 at 3:00 PM UTC)\\n[Watch on YouTube](https://www.youtube.com/live/bNXmyipHoBM)\\n\\n# Workshop 3: Introduction to Reactive Hackathon, Tracks, Judging Criteria, and Q/A (September 11 at 2:00 PM UTC)\\n![youtube](https://www.youtube.com/watch?v=30dfFXnueeI)\\n\\n# Workshop 4: Introduction to Reactive Smart Contracts(September 18 at 2:00 PM UTC)\\n![youtube](https://www.youtube.com/watch?v=VGKd0m5_6NQ)\\n\\n# Workshop 5: ReactVM and Important Tips (September 25 at 2:00 PM UTC)\\n[Watch on YouTube](https://www.youtube.com/live/EH59XBdp9vk)\\n\\n# Workshop 6: Reactive Hackathon: Reactive Bridge Challenge Winner (October 9 at 2:00 PM UTC)\\n![youtube](https://www.youtube.com/watch?v=vIC7TeFHiXI)\"}}"],"participation":"Virtual","escrowed":false,"bounties":[{"id":585,"bounties":[{"id":719,"name":"Challenge One: Reactive Bridge dApp","token":"USDT","bonus":700,"link":"","description":"Develop a bridge that transfers tokens between two chains. When tokens on one chain are deposited, a Reactive Smart Contract triggers token release to the user on the other chain. The application should implement smart contracts (Reactive and usual) and the frontend. The frontend should provide links to transactions on all three chains (Origin, Reactive, Destination) after the tokens are transferred to another chain. Use any two or more chains supported by Reactive Network. \n\nA successful application MUST:\n- Be submitted before Wednesday, October 2, 2 PM UTC\n- Implement a Web3 Reactive Bridge dApp.\n- Include the Reactive contracts, Destination contracts, deploy scripts, and instructions.\n- If the application uses custom Origin contracts, the repository MUST also include these contracts with their deploy scripts and instructions.\n- Provide the addresses of the deployed Reactive contracts.\n- Provide the addresses of the Origin and Destination contracts.\n- Contain a step-by-step text description of how the setup operates after deployment.\n- Execute the workflow and include the transaction hashes for every step, including Origin, Reactive, and Destination transactions.\n- Include a presentation video no longer than 5 minutes with dApp demonstration. The judges will review both the video and the accompanying code and documentation.\n\nThe applications will be evaluated based on the following criteria:\n- How well the application solves the use case described above.\n- Code quality, security, readability."},{"id":744,"name":"Challenge Two: Reactive Cross-Chain Lending","token":"USDT","bonus":700,"link":"","description":"Develop a lending protocol that allows providing collateral on one chain and receiving and returning the loan on the other. The application should implement smart contracts (Reactive and usual) and the frontend. The frontend should provide links to transactions on all three chains (Origin, Reactive, Destination). Use any two or more chains supported by Reactive Network.\n\nA successful application MUST:\n- Be submitted before Wednesday, October 23, 2 PM UTC\n- Implement a Web3 Cross-Chain Lending dApp.\n- Include the Reactive contracts, Destination contracts, deploy scripts, and instructions.\n- If the application uses custom Origin contracts, the repository MUST also include these contracts with their deploy scripts and instructions.\n- Provide the addresses of the deployed Reactive contracts.\n- Provide the addresses of the Origin and Destination contracts.\n- Contain a step-by-step text description of how the setup operates after deployment.\n- Execute the workflow and include the transaction hashes for every step, including Origin, Reactive, and Destination transactions.\n- Include a presentation video no longer than 5 minutes with dApp demonstration. The judges will review both the video and the accompanying code and documentation.\n\nThe applications will be evaluated based on the following criteria:\n- How well the application solves the use case described above.\n- Code quality, security, readability."}],"bountyCount":2,"totalBonus":1400,"name":"Reactive Network","logo":"https://cdn.dorahacks.io/static/files/1906cff88f1ec6faf5376dd4eab9e7c9.png","weight":1,"description":"Reactive Smart Contracts (RSCs) represent a paradigm shift in how we interact with blockchain technology. Unlike traditional smart contracts that are run by user transactions, RSCs actively monitor events on EVM-compatible chains and react to them. They process these events according to the implemented logic and execute further actions on the blockchain autonomously. This innovation introduces a decentralized mechanism for automating responses to on-chain events without manual actions.","isCurrentOrg":true}]}}