Loading...
Theme: Ethereum/Web3. General ETHGlobal rules do not exclude KZ.
Format and location: In-person; Mumbai, India
Period: 06.11.2026 — 08.11.2026
Registration or submission deadline: deadline not confirmed
Current status: Open
Kazakhstan eligibility: Yes — according to the rules
For whom: Web3 developers, designers, founders
Age and other criteria: Application + acceptance
Team: 1–5
Primary language: EN
Fee: Free; refundable ETH stake possible
Prizes: not published in verified materials
ETHGlobal Mumbai 2026 — is an event in the "Web3, digital assets, and verifiable transactions" track. The recorded thematic formulation is: Ethereum/Web3. General ETHGlobal rules do not exclude KZ.. The practical value of participation should be evaluated not only by the prize size, but also by the quality of the task, access to experts, suitability of the result for a portfolio, preparation costs, and the likelihood of completing a strong submission in the available time. The catalog status is Open, and the editorial priority is A — apply now. This helps determine the order of work, but is not an organizer rating and does not guarantee selection or victory.
For this theme, the central product question is: why does the task need decentralization, and what function of trust, ownership, or coordination cannot be implemented more easily with a regular database. A strong team will be able to answer this in a single sentence and then prove the answer with a working result. The most appropriate type of final artifact is a working contract or protocol, a minimal interface, a testnet, a state model, and a description of security and economic assumptions. This is an editorial recommendation derived from the theme; the official mandatory format must be taken only from the event website.
In the card, eligibility is marked as Yes — according to the rules. The recorded basis is: General ETHGlobal rules do not exclude KZ.. These two lines must be read together. The phrasing "Kazakhstan is not excluded" is weaker than a direct invitation to participants from all over the world, and the word "international" itself does not always mean the absence of restrictions on citizenship, residency, place of study, age, or sanctions compliance. If the value contains "conditionally", if the proof is indirect, or if the legal rules have not yet been published, it is worth getting a written response from the organizer before spending time.
The recommended inquiry to the organizer should state the country of residence and citizenship, the expected team composition, age or student status, the method of receiving the prize, and the chosen format of participation. It is best to save the response along with a snapshot of the rules version. Separately, check whether the platform applies its own restrictions, whether a Kazakhstani bank can receive the payout, whether a tax form is required, and whether participation on behalf of a company is allowed. These are not additional rules of this hackathon, but a standard risk check for an international application.
Target audience: Web3 developers, designers, founders. Recorded criteria: Application + acceptance. Team composition info: 1–5. Before registering, each participant must independently confirm compliance with age, student status, residency, and other personal conditions. If individual participation is not explicitly permitted, it should not be assumed to be allowed. If the maximum team size is unknown, do not register extra people before receiving the organizer's response.
For a task in the field of "Web3, digital assets and verifiable transactions," a rational distribution of roles looks like this: smart-contract engineer, frontend/product developer, security reviewer, and a person responsible for tokenomics or user value. One person can combine several functions, but there must be clear owners of the product, technical result, quality assurance, and final submission. It is useful to agree in writing in advance on the contribution, the right to represent the project, access to the repository, the use of the result after the event, and the distribution of a potential prize. Such an internal agreement is a recommendation and does not replace the platform's terms.
The working language is specified as EN. Even if the team communicates in Russian or Kazakh, prepare a unified glossary of terms in advance and designate a person capable of confidently answering the jury's questions in the required language. For an English-language submission, it is better to use short sentences, labels on diagrams, and subtitles for the demonstration. The goal is accuracy, not a complex style.
The confirmed format is In-person, location — Mumbai, India. Start: 06.11.2026; end: 08.11.2026; deadline: deadline not confirmed. Travel information: Travel, accommodation, and India visa are at the participant's expense. Presence of an online component by card: no; signs of mandatory in-person presence: yes. These signs are derived only from the text of the fields and do not override event-specific rules.
For an online format, it is important for a team from Kazakhstan to convert the deadline to their time zone, check the time of mandatory sessions, the upload speed of large videos, and the availability of all APIs. Create a technical buffer of at least a few hours and do not leave registration until the moment of submission. For an in-person or hybrid format, first calculate the full budget: visa, flight, accommodation, insurance, local transport, food, and refundable deposits. The wording "travel support" does not mean automatic coverage of all costs. The value recorded for this event: Travel, accommodation, and India visa are at the participant's expense.
The cost of participation is recorded as Free; refundable ETH stake possible. Prize information: not published in verified materials. Before making a decision, separate cash payments, grants, cloud platform credits, subscriptions, equipment, mentorship, and marketing wording about total value. Clarify the number of awarded teams, currency, deadlines, taxes, restrictions on receipt, and the need to be present at the ceremony. If TBA, page discrepancies, or a re-verification requirement appear in the field, the amount cannot be used as guaranteed income.
Even without a cash prize, an event can be useful if it provides a strong case, public demonstration, feedback, or access to a community. But paid services, travel, and several weeks of work have an opportunity cost. It is better to make the decision to participate based on three questions: is it possible to fulfill the mandatory requirements; is it possible to assemble a convincing result on time; will the created artifact be useful after the winners are announced.
For this direction, the following sequence is useful:
This strategy is not an official evaluation criterion. Its purpose is to help turn the broad topic Ethereum/Web3. ETHGlobal general rules do not exclude KZ. into an honest, verifiable, and complete prototype.
Documented risk: Event-specific deadline/prizes/stake are still TBA.. Next recommended step: Apply early and wait for acceptance.
The current card does not sufficiently confirm: the exact time and time zone of the deadline; the structure, currency, and payout order of prizes. These points should be considered open questions, not permission to act on the most convenient assumption.
Practical go/no-go criterion: you should apply if the team documentarily meets eligibility, has access to the required stack, has time to complete a verifiable scenario, and accepts financial and logistical risks. You should pause participation if the admission of Kazakhstan, submission rights, mandatory in-person presence, cost of critical services, or the payout order of a significant prize are unclear.