Portaldot Hacker house 2026

Portaldot Network V3.0 is now fully compatible with the EVM contract ecosystem, supporting both WASM and EVM contract execution, as well as ERC-20 / ERC-721 token standards. This Hacker House is initiated and supported by the Portaldot Network Ecosystem Foundation, and is open to teams and individual developers with proven independent Web3 product development capabilities and the ability to deliver and maintain projects over time. # Highlights - Focused on Portaldot V3.0 core features, including WASM/EVM compatibility, modular architecture, and multi-chain capabilities. - In addition to Hacker House prizes, participants can apply for long-term resources and funding from the Portaldot Network Ecosystem Foundation. - Outstanding projects may enter the ecosystem Builder long-term support program, with access to technical, traffic, community, and funding support. - Projects that do not win awards but are committed to continued building are also eligible to apply for the ecosystem support program. # Tracks 1. **Modular Cloud & Middleware** Build decentralized middleware, storage/data components, and APIs based on Portaldot's modular architecture. 2. **Multi-Chain & Cross-Chain Infra** Leverage Portaldot's cross-chain capabilities to build asset/data bridges and liquidity engines. 3. **Node Operations & Tooling** Node monitoring, automated staking, node data visualization, and network security analysis tools. 4. **Ecosystem DApps** Innovative DeFi, RWA tokenization, and consumer-facing applications. # Prize Pool & Awards **Total Prize Pool: 5,200 USDT** - 2,600 USDT paid in USDT - 2,600 USDT equivalent paid in POT tokens Awards: - **Grand Prize (highest overall score): 1,000 USDT** - **Track First Place: 800 USDT each** - **Ecosystem DApps Second Place: 500 USDT** - **Ecosystem DApps Third Place: 300 USDT** - **Community Choice Award: 200 USDT** Notes: - The Community Choice Award is a standalone award determined by community voting in a dedicated Discord channel. It is not included in judges' scoring and does not affect other award results. - The Community Choice Award can be stacked with other awards. - If the same project wins both the Grand Prize and first place in a track, the Grand Prize will be retained, and the track award will be passed to the next highest-scoring project in that track. - Track awards are subject to the actual quality of projects and are not guaranteed to be fully distributed. If no project in a track meets the minimum award threshold, that track's award may remain vacant. # Key Dates - Kick-off Meeting & Workshop: Oct 14, 20:00 – 22:00 UTC+8 - Check-in Submission Deadline: Oct 24, 20:00 UTC+8 - Feedback Results Announcement: Oct 26, 24:00 UTC+8 - Office Hour Application Deadline: Oct 30, 20:00 UTC+8 - Office Hours: Oct 31 – Nov 1, 14:00 – 18:00 UTC+8 - Final Submission Deadline / Code Freeze: Nov 6, 12:00 UTC+8 - Live Demo Day: Nov 7 – Nov 8 - Community Choice Voting: Nov 9, 00:00 – 24:00 UTC+8 - Winners Announcement: Nov 10 - Winner Information Collection: Nov 11 – Nov 13 - Reward Distribution: Nov 13, 20:00 UTC+8 # Communication & Platforms - **Application & Project Submission, Check In:** Dorahacks - **Kick-off Meeting, Workshop, Office Hours, Live Demo Day, Community Choice Voting, and all key activities will take place on Discord.** **Please make sure to join the official Discord to avoid missing important updates:** 👉 **[https://discord.gg/portaldot](https://discord.gg/portaldot)** # Participation Requirements - Open to teams or individual developers with full independent Web3 product development capabilities and the ability to deliver and maintain projects sustainably. - Tech stack includes but is not limited to Rust / ink!, Solidity, Web3 frontend, and full-stack development. - Projects must effectively leverage Portaldot Network V3.0 core features and complete deployment on the Portaldot testnet. - Code must be primarily produced during this Hacker House period, i.e., Oct 14 – Nov 6. # Submission Requirements ### Check-in Submission Teams should submit the following materials on DoraHacks before the check-in deadline: - Current project progress - Outstanding items - Public GitHub repository - Publicly accessible - Complete README - Continuously updated development records - Product architecture diagram - Portaldot testnet deployment information - Contract address - Transaction hash - Explorer link, if available - Initial demo material, choose one of the following: - Live demo / Web3 DApp link - Demo video no longer than 3 minutes, showing at least one core function At the check-in stage, projects should already have a demonstrable prototype or core product flow, rather than remaining only at the concept design stage. Demo materials may use simulated data, but teams are encouraged to include real Portaldot testnet interactions whenever possible. ### Office Hour Application Teams that would like to join Office Hours should submit the following materials before the Office Hour application deadline: - Current project progress - GitHub repository - Completed modules - Testnet deployment status - Product demo link, if available - Questions to discuss with mentors Suggested discussion topics include: - Technical issues: contract development, cross-chain interaction, performance optimization - Product issues: product positioning, user growth, MVP design - Tokenomics issues: incentive design, token allocation, governance mechanism ### Final Submission All finalist teams must complete the final submission on DoraHacks before the final submission deadline. Final submission materials include: - Project name - Team members - One-sentence project overview - Public GitHub repository - Complete README - Deployment instructions - Project documentation - Reproducible or runnable final code - Testnet deployment information - Runnable demo - Web / DApp link, or clear local deployment instructions in README - Demo video - No longer than 3 minutes - Shows a real product - Demonstrates core functions - Shows Portaldot integration or usage - Publicly accessible link - Pitch deck - PDF or publicly accessible link - Should cover the problem addressed, why Portaldot is essential, proof of product functionality, and reasons for continued future support - Contract address and transaction hash, if applicable ### Code Compliance - The GitHub repository must remain public during the event. - The repository must have at least 3 valid commits during the Hacker House period. - Code should be primarily produced during this Hacker House period. - Core module final versions must not be committed all at once within the last 24 hours before the final submission deadline. - Teams should retain commit timelines, pull requests, and other development records as supporting evidence. - After the final submission deadline, projects enter Code Freeze. Teams must not make substantial changes that affect core functionality, architecture, or evaluation results. - If a serious bug must be fixed after Code Freeze, the team should report it to the organizer and keep a clear modification record. - Submitting an existing complete project as competition work is not allowed. - Open-source frameworks, official SDKs, and third-party dependencies are allowed, but sources must be properly disclosed. # Intellectual Property - All code and materials submitted by participants remain the property of the respective teams. - By submitting a project, participants grant Portaldot Network Ecosystem Foundation a non-exclusive, royalty-free license to display, promote, and share project information, demos, and related materials for event and ecosystem purposes. - Participants must ensure their submissions do not infringe any third-party intellectual property rights. Any third-party code, assets, or data used must be properly licensed and attributed. - The Foundation is not liable for any IP disputes arising from participant submissions. Teams found to have committed plagiarism or unauthorized use of third-party materials may be disqualified and barred from future events. # Evaluation Criteria - **Technical Feasibility (30%):** Evaluates technical approach, system architecture, code completeness, and actual delivery. Focuses on whether core functions are completed, whether GitHub shows genuine and sustained development activity, and whether the project is deployed on Portaldot testnet with verifiable on-chain interactions. - **Innovation (30%):** Evaluates innovation in technical solutions, product models, and application scenarios. Focuses on effective use of Portaldot V3.0 features such as WASM/EVM compatibility, modular architecture, and multi-chain capabilities, and whether the project delivers real value beyond existing solutions. - **Ecosystem Contribution (20%):** Evaluates the project's contribution to Portaldot infrastructure, developer tools, node ecosystem, application ecosystem, and user growth. Also considers the project's potential for sustained building, open-source value, and long-term ecosystem collaboration. - **Business Potential (20%):** Evaluates whether the project addresses real market needs, whether target users and use cases are clear, whether the business model and growth path are feasible, and whether the team has the capability to continue development, operations, and delivery. Evaluation will be based on objective evidence including GitHub repositories, commit timelines, testnet transaction records, contract addresses, transaction hashes, and live demo performance. # Post-Hackathon Ecosystem Support The Hacker House is not only a competition. It is also a starting point for teams that want to continue building within the Portaldot ecosystem. After the event, outstanding projects may apply for the Portaldot ecosystem support program. Selected teams may receive long-term support across product development, technical integration, community growth, ecosystem exposure, and funding resources. Potential support includes: - Mainnet launch support Technical guidance for migrating from testnet to Portaldot mainnet, including contract deployment, integration review, and architecture suggestions. - Product building subsidies Eligible teams may apply for support covering part of their product development costs, including servers, databases, DApp infrastructure, data services, and other necessary building expenses. - Technical advisory and architecture review Direct support from the Portaldot technical team on smart contracts, cross-chain interaction, modular architecture, API integration, RWA data mapping, Oracle/data synchronization, and security boundaries. - Debug and development support Selected teams may receive debugging assistance, code-level feedback, developer tool support, and joint troubleshooting sessions. - Ecosystem exposure Projects may be featured through Portaldot official channels, ecosystem updates, social media promotion, project spotlights, and community campaigns. - Community growth support Support may include community operation guidance, task design, onboarding campaigns, Discord/Telegram growth planning, and user engagement strategies. - Joint campaigns and ecosystem tasks Selected projects may be included in official ecosystem missions, joint AMAs, Spaces, user campaigns, and partner-facing activities. - Liquidity, trading, and gas incentive opportunities Projects with tokens, trading use cases, or meaningful on-chain activity may apply for further ecosystem incentives, including liquidity support, trading growth support, user conversion incentives, or gas fee rebates. - Official ecosystem listing Projects that reach product and operational milestones may be considered for inclusion in the Portaldot official ecosystem directory. Projects that do not win prizes but show strong execution, clear product direction, and continued commitment to building on Portaldot may also apply for ecosystem support. Support resources will be unlocked based on project progress, product readiness, on-chain activity, community growth, and milestone review. Application details will be announced after the Hacker House. # **Official Discord** **[https://discord.gg/portaldot](https://discord.gg/portaldot)**