链
开发者
生态
Staking
Earn BNB and rewards effortlessly
Tokenization Solutions
Get Your Business Into Web3
社区
Updated: 6 November 2023
Are you ready to dive into the world of blockchain and decentralized applications? We invite you to participate in the BNB Chain Hackathon, Istanbul, taking place from November 10th to November 12th, 2023. This three-day event promises to be an exciting opportunity to explore the limitless possibilities of blockchain technology.
Event Details:
For this hackathon, we're thrilled to introduce you to opBNB and Greenfield, two cutting-edge blockchain platforms that offer endless possibilities for developers and entrepreneurs.
BNB Greenfield provides decentralized storage infrastructure within the broader BNB Chain ecosystem. The idea is to help users and dApps to create, store, and exchange data with full ownership, and form a new data economy.
The opBNB network is the Layer 2 scaling solution for the BNB Smart Chain, powered by the bedrock version of Optimism OP Stack. It allows users to deposit and withdraw funds, use smart contracts, and view network data with high throughput and low fees, all while scaling beyond the constraints of the BNB Smart Chain.
We encourage you to develop in line with our Wishlist, which includes exciting tracks in both Greenfield and opBNB. Each track offers exciting challenges and opportunities for innovation. You can view the details list at the bottom of this announcement.
We're offering up to $100k in rewards for your hard work and innovation:
• 1st Prize: $15k
• 2nd Prize: $10k
• 3rd Prize: $5k
Plus, up to 70k in additional rewards across a variety of categories.
The event organizer, in its sole discretion, may award an additional reward of up to $2,000 USD per project based on the quality of the project. Up to a maximum of $70,000 USD of additional rewards will be awarded.
Please read and follow the competition rules to ensure a fair and enjoyable experience for all participants. These rules cover eligibility, participation requests, and conduct during the event.
Submission Requirements
Please note that you do not need to pitch your idea to us. All we need is your submission.
Projects will be evaluated based on 1) functional prototype highlighting a solution, 2) creativity, 3) readiness of the dApp and 4) usability.
Remember, hackathons are about learning, collaborating, and having fun. While some aim to win, most are here to explore new ideas. Keep the hacker spirit alive by working with other teams, mentoring newcomers, and enjoying yourself.
Join us in Istanbul for the BNB Chain Hackathon Istanbul, where innovation knows no bounds, and the future of blockchain technology is in your hands. Together, let's push the boundaries of what's possible and shape the future of finance and data management.
For more details, view the full rules of the competition at the bottom of this article.
Register now and see you at the hackathon!
Dapp Tracks on opBNB(Goals and Description)
Infrastructure Tracks on BNB Smart Chain(Goals and Description)
Infrastructure Tracks on opbnb(Goals and Description)
BNB Chain Istanbul track info:
The Hackathon has a number of diverse yet interconnected tracks. Each track is designed to push the boundaries of innovation.
Whether you are a newcomer to the blockchain space or an experienced developer, we have designed these tracks to challenge, inspire, and uplift your skills. Each track has its own specific focus, but all aim to encourage you to explore, innovate, and create real-world solutions harnessing blockchain technology.
Below you will information on all tracks provided by BNB Chain, Space ID and Polyhedra!
1. BNB Smart Chain for all ( infra/dapp wishlist of bsc);
2. Powering Next-gen dAppson opBNB ( infra/dapp wishlist of opBNB);
3. New Data Economy on Greenfield( infra/dapp wishlist of Greenfield.)
https://github.com/bnb-chain/community-contributions/tree/main
Supporting info: Please view our wishlist for more information on topics https://github.com/bnb-chain/community-contributions
Name: Novel Use Cases for SPACE ID Domains
Description: Interesting projects integrating SPACE ID, or projects that explore innovative ideas using SPACE ID. Potential ideas include but are not limited to cross-chain resolution, decentralized messaging, new types of resolvers, and account management systems.
Resources:
Hackers can use the following resources to learn about SPACE ID:
1. SPACE ID SDK Documentation
https://docs.space.id/developer-guide/web3-name-sdk/sid-sdk
2. EIP 3668 - Secure Offchain Data Retrieval
https://eips.ethereum.org/EIPS/eip-3668
3. SPACE ID Tutorials
https://docs.space.id/getting-started/tutorials
Name: Decentrailsed ID
Description:
opBNB provides a great solution for widespread adoption across multiple digital environments such as games, social networks, the metaverse, and high-frequency trading.
zkBridge provides the most secure design for general message passing and asset bridging between various L1 and L2 networks. The end-to-end system for zkBridge fast finality on opBNB (https://zkbridge.com/opbnb)offers a smooth cross-chain user experience with the high-security and low-latency zkBridge on opBNB.
In our track, we will instruct you to build on opBNB and explore the use case of zkBridge on opBNB.Resources:https://zkbridge.com/
Task 1:
In this scenario, we have a computational task denoted as 'f' that accepts an input 'x' and produces an output 'y'. Below, you'll find the interface for this computation task, as defined in Solidity:
```solidity
// SPDX-License-Identifier: MIT
pragma solidity ^0.8.0;
interface ComputationTask {
// This function carries out the computation task.
// It takes an input parameter 'x' and returns an output 'y'.
function compute(uint256 x) external returns (uint256 y);
}
```
On opBNB, the computation is executed optimistically, meaning there's no assurance that the computation will be performed correctly within the stipulated challenge period. To address this, we've introduced a committee responsible for executing the computation accurately. Committee members are required to provide their signature only if they confirm that the output 'y' is correct.
However, some committee members may exhibit laziness, choosing not to rigorously verify the computation. These "lazy" members might opt to request other committee members to supply the correct 'y' and then simply affix their signatures to it. Alternatively, they may blindly endorse whatever output obBNB generates.
Your task is to devise a mechanism capable of identifying and flagging these lazy committee members.
Task 2:
Computation on the L1 Blockchain is excessively costly. For instance, consider the following computationally expensive task:
```solidity
// SPDX-License-Identifier: MIT
pragma solidity ^0.8.0;
interface ComputationTask {
// This function performs the computation task.
// It takes an input parameter 'x' and returns an output 'y'.
function compute(uint256 x) external returns (uint256 y);
}
```
Executing the `compute(x)` function incurs a gas cost of approximately 1,000,000 gas.
Thankfully, opBNB provides a much more cost-effective platform for conducting such computations. Your objective is to delegate the computation from BSC to opBNB and then transfer the final result back to BSC via the Polyhedra Bridge.
It's worth noting that you can assume the client will request this computation every 10 seconds, offering the opportunity to batch transfer computation results to further reduce the cost.
Task 3:
On-chain random numbers are crucial for gaming applications. We deployed a verifiable random function on opBNB, and it’s now waiting for applications to use it. We provides following off-chain RPC calls and on-chain verification method:
VRFKey = await rpcCall("register");
It provides you a VRFKey that can be used in verifying the random number.
randomness, proof = await rpcCall("register");
```solidity
// SPDX-License-Identifier: MIT
pragma solidity ^0.8.0;
interface VRF {
// This function performs the computation task.
// It takes an input parameter 'x' and returns an output 'y'.
function register(address applicationAddress, uint256 VRFKey) external returns (bool result);
}
```
This function associates your VRF key with your dApp.
```solidity
// SPDX-License-Identifier: MIT
pragma solidity ^0.8.0;
interface VRF {
// This function performs the computation task.
// It takes an input parameter 'x' and returns an output 'y'.
function verify(address applicationAddress, uint256 randomness, uint256 proof) external returns (bool result);
}
```
This verifies the randomness is correctly generated against the proof.
You are allowed to freely use these interfaces. Now it’s your time to develop a fantastic application.
Name: Decentrailsed ID
Description: Develop a decentralized identity system on opBNB. Utilize its infrastructure to implement on-chain reputation scoring and DID credentials verification. Focus on leveraging DID for transparent and secure identity management and authentication, eliminating intermediaries and prioritizing data privacy.
Goals:
- New applications using DID beyond existing use cases
- Privacy focused on-chain credential and ID verification
- Accessible UX for the masses
- Reputation based scoring using DID
1. Eligibility:
Team Size:Teams may have a maximum of 5 hackers.
2. Participants Requests:
Hackers who have been accepted to compete on a team must not be event staff, volunteers, mentors, judges, sponsors, or anyone else with special access to the competition.
Participants, including organizers, volunteers, and sponsors, are available to offer teams guidance and assistance.
4.The hackathon is the only place where work can be done on a project.
5. Groups are allowed to implement a strategy they developed in advance of the competition.
6. Teams have the option of focusing on already completed ideas. There is no requirement for "innovation" in hacks. Anyone is welcome to contribute to a shared idea, and their work will be evaluated based on how well it is "hacked." (It's unusual to come across something wholly novel these days, and teams often aren't aware if they're recycling a concept.)
7. Groups are free to include third-party resources, such as code repositories, into their work. It is against the spirit of the guidelines to work on a project ahead of time and open-source it with the sole intention of using the code during the event.
8. It is acceptable to include additional functionality into ongoing projects. Winners will be determined solely based on the value of any new features or functionalities introduced during the hackathon.
9. When the clock runs out, teams must cease their hacking activities. After the allotted time has passed, however, teams are free to debug and make minor adjustments to their applications. e.g. It's acceptable to fix a bug that prevents you from demonstrating your hack if doing so involves adding only a few lines of code. You are not permitted to make any major alterations or introduce any new functionality.
10. Teams can be disqualified from the competition at the organizers' discretion. Reasons might include but are not limited to breaking the Competition Rules, breaking the Code of Conduct, or other unsporting behaviour.
When the hackathon is over, the teams will upload their finished products to Github for evaluation.
Judges will review all submissions and winners will be announced on Sunday 12th November
Teams can choose to participate in as many relevant sponsor categories as they like.
Website | Twitter | Telegram | Facebook | dApp Store | YouTube | Discord | LinkedIn | Build N' Build Forum