Members of the Fellowship Collective involved in projects flagged by the OG tracker should provide a proper explanation, return the funds to the Treasury, or face expulsion.
#121 POLKADOT HACKATHON EAST ASIA Edition - HackaDOT 2023
East Asia is a region with a large number of great blockchain engineers to find new ecosystems to apply their skills.
We propose the FIRST-EVER hackathon in East Asia to unite this potential and promote the Substrate technology and Polkadot ecosystem.
The layout of this hackathon will combine a few components we had during Sub0 2022, such as Starters & Builders Spaces, to host various workshops for developers.
The HackaDOT 2023, will be the official side event of Buidl Asia 2023 and be held both online(Phase#1) and offline(Phase#2).
In total 2.5 months of execution, from 22 March to 11 June 2023 (30 days of registration, 30 days for Pre-online hackathon, 3 days of live hackathon, and 4 days for judging period).
HackaDOT 2023 aims:
-
To promote Substrate as an open-source framework for developers in East Asia.
-
To navigate local developers into Polkadot Ecosystem.
-
To showcase how Polkadot live-ecosystem leaders are building the use cases using our technology.
*Please see the full proposal here | Posted for Onchain Discussion
Show More
The poster seems awesome and organising a hackathon in East-Asia reads great! However we will vote nay in this for the following reasons:
- There is no mention on any Build Asia 2023 channels about this hackathon. If you are close to this organisation a mention of an upcoming event would be great.
- You ignored the discussion to engage with a specific bounty for events/hackathons. why?
- It would be great to get confirmation from the Parity DevRel Team, as the identity is less than 10 days old.
If new proofs come to light, we will change our vote.
Found the image from their website:
You can also find the confirmation conversation between Parity DevRel & Raf from the comment sections: https://drive.google.com/file/d/13pD-n2QY4MNCSiQd3vub9I5sdADhaKH_/view?usp=sharing
Hello there, I'm part of the Parity Marcomms team and perhaps I can chime in and help to clarify some of your questions:
-
I had a meeting with the Buidl Asia organizer last week as we are also exploring the potential opportunities for the Polkadot Ecosystem at the event. During our conversation, the HackaDot event was mentioned multiple times and was highly supported by the organizer. I believe an official comms is in the planning just a matter of time. I would also imagine that official comms will only come once the proposal is confirmed.
-
Although I'm not part of the DevRel team, but I can confirm that both Parity Marcomms team and the DevRel team has been working closely with the Poster - providing feedback and input on the event.
Korea is a very important market for Polkadot to tap into and I hope the HackaDot event will just be the start of many more initiative for region.
I hope my answers clarify some of your questions.
Thank you for confirming some unclarity of the proposal. Our organizing team is expecting that this East Asia edition hackathon will be the great trigger to grow Polkadot's Asia pressure, which would lead to true decentralization of Polkadot presence, where our ecosystem is mostly concentrated on Europe and Americas. Please let me know any other unclear from the proposal.
Hello team,
Good initiative,
However, we are voting Nay due to the magnitude of the amount requested and the potential market effects of liquidating such amounts in a relatively short period of time.
We would like to see certain level of coordination between this proposal and some others versing on the hackathon topic, so there are checks in place to ensure there is not too much schedule overlap, the overall public is kept motivated, and market conditions are kept relatively stable.
Additionally, it has been suggested that Polkadot Bounty 17 could be a more adequate / organised option to funding this proposal, which we agree with.
Regards
Miloš
Thank you for commenting for the reason of Nays.
-
Since this event is the first-ever largest hackathon in East Asia, our team has set the budget a bit high to host a well-branded event. I am sorry that I haven't considered the market impact. This cost is only for the operational cost for the hackathon.
-
We are discussing with the Polkadot Bounty 17
If you have any questions, I am happy to answer to adjust. Thank you
Nay Due to huge amount.
Yeah, but If you take a closer look into the schedules and the format of the event, the size of the hackathon is almost equivalent to a mini-conference, which quite make sense, and the proposer mentioned that unused fund will be returned back into the treasury ;)
There have been a few comments regarding nay votes due to the huge upfront asking amount.
Quite a bit of discussion is going on regarding the use of payout bounties to alleviate the problems associated with upfront payments and ensure voter confidence.
Perhaps this would be an interesting route for this proposal to ensure token holder support.
Dear team,
The location of the event is one of the best choices as it is a hub for technological innovations and has a vibrant tech community. Moreover, the idea of a hackathon as the type of event is a great opportunity for participants to showcase their skills and creativity by building amazing projects within a short timeframe. This event has a lot of potential to bring the new developers to the Polkadot ecosystem.
However, there are a few points that I do not agree with. I do not think that asking for funding from the treasury is a good idea. I agree with the comment above "there is a dedicated Polkadot Bounty 17 that could be a more adequate/organised option to funding this proposal".
Organization of event this size is not an easy task and it needs an adequate preparation. I hope you will take the advice and start the planning process early as it can help you avoid last-minute challenges and ensure that everything runs smoothly. By taking these steps, you can ensure that the hackathon event is well-organized, engaging, and successful.
Kind regards,
SB
Thank you for your kind explanation and advice, SB. Our team is planning to shift to Polkadot and closely looking at the Polkadot Bounty 17.
I didn't comment in the Discussion phase due to a busy schedule, but I always take a look at these on-chain referendums as I also do videos on them (at least once a week on a language channel, sometimes twice) and as of recently I started covering one video a week on my english Youtube channel so I also vote to tell my viewers the reason behind my vote.
What I like about this proposal:
-
Very clear structure of costs and I think every event / conference / hackathon organiser should follow the same so congrats on doing this! It's also something I will consider for myself in the future and I think this kind of structure with associated costs works best for anyone reviewing it.
-
Over $50k goes to the prize for the Developers which is how it should be. After all, this event is for Devs to build something cool and they should be rewarded for their time and effort, considering it is tough to get Devs to build something useful in Web3.
What I don't like about this proposal:
- That it's being launched on the Kusama Open Gov. I totally understand you want to skip the queue and not take the Polkadot route because of the long wait (28 days on chain) and I also understand that because it's a Hackathon you can't apply for Bounty funds from Zoe (Global Polkadot Ambassador) but to me, because the asking amount is so huge, I feel like it is definitely not appropriate to reach out to Kusama for this.
Just imagine that there were 20 Hackathons across the globe all doing the same as you, what would happen to the Kusama treasury? Yes, that's right, it would be empty and it would take a long time to refill small amounts which means nobody else would be able to get funding because of the Hackathons draining it.
Sorry, but I strongly insist you take the Polkadot route for this proposal even if it means waiting 28 days because the Polkadot treasury can stomach this kind of funding so to me, this is a strong Nay, however, when and if you will decide to take the Polkadot route, I will happily support you there as I like the idea, I just don't like the path you took.
I hope you understand where I'm coming from.
Regards,
Claudio
Agree
Thank you for your kind explanation and your support for our idea! Agree that cost of hackathon is kind of huge which could be burden to Kusama OpenGov. Applying to community opinions, we are planning to shift to Polkadot, maybe Bounty 17.
Hello,
We are in the process of validating a true need for a service to assist teams with crafting and completing successful treasury proposals, so they can focus on building. We would love to hear about your experience with this proposal. If you are willing to take a few minutes, please fill out this form about your experience with the OpenGov treasury proposal process: https://forms.gle/MwDij4adXEQd7Um79
Feel free to leave out any details that your team is not comfortable with sharing, but the more info you can provide, the better we will be able to assess the potential need for our services.
For more info, follow us on Twitter/X: https://twitter.com/OpenGovAssist
Discover similar proposals
Remove Gabe from the fellowship
See More
Fellowship Admin
Fellowship Admin
Members of the Fellowship Collective involved in projects flagged by the OG tracker should provide a proper explanation, return the funds to the Treasury, or face expulsion.
Invarch failed to provide the first two, so Gabe, a founding member of the team, does not meet the ethical standards required to have a voice in the Fellowship.
TENETS (extract from the fellowship manifesto)
"Members are expected to faithfully uphold the following tenets.
Clarifications to the rules should be in agreement with these tenets. Acting in clear breach of these tenets may be considered by voters as grounds for non-promotion, demotion or, in extreme cases, exclusion from the Fellowship.
(1) Sincerely uphold the interests of Polkadot and avoid actions which clearly work against it.
(2) Respect the philosophy and principles of Polkadot.
(3) Respect the operational procedures, norms and voting conventions of the Fellowship.
(4) Respect your fellow Members and the wider community"
See More
KSM RFP #1 - Shielded Kusama Hub Transfers - $50k Total Prize!
See More
Treasurer
Treasurer
This RFP was adapted over several weeks on AAG to turn a treasury proposal in discussion to an RFP with refined scope and oversight.
To apply for the prize pls fill out this form.
Prize Pool: $43,000
Finder’s Fee: $2,000 **
Supervisors: $5,000
Supervisors (Bounty Curators)
- Flipchan
- Byte (Erin)
- James Slusser
Excess or unused funds will be returned to the treasury by Bounty Curators.
Timeline
Monday, March 17 - AAG Discussion & this forum post! ✅
Monday, March 24 - Single-ref Bounty + Curators ✅
4 Weeks after Bounty Funding - Submission Deadline Thursday
July 31 - Project Completion (Pending Kusama Hub Launch)
Project Scope
Smart Contract Development
- A Solidity-based smart contract deployed on Kusama Hub
- ZK enabled for private deposits & withdrawals
- Compatibility with all Kusama Hub assets
User Interface
- Browser-based, mobile-ready UI hosted on IPFS
- Support for: Deposits, Withdrawals, Transfers, XCM Transfers
- Compatible with popular ecosystem wallets (Nova Wallet, Talisman, Subwallet)
Anti-correlation Attack Mitigations:
- Fixed deposit amounts (e.g. 1, 10, 100, 1000 units)
- Batch payouts for withdrawals to multiple users
Interoperability - Ability to receive assets via XCM from any Kusama-connected parachain and transfer them to Kusama Hub for use in shielded pool.
Open-Source Delivery
- All code (smart contracts and UI) published under the MIT license
- Publicly accessible repositories Project updates shared transparently via Polkassembly, Subsquare, or Polkadot Forum from Team with Milestone deliveries
- Developer & User documentation
Milestones
Milestone 1, Initial Pools & Basic UI:
$16,200 USD
1 month
- Tests - Smart contract test
- Smart contract - ZK shielded smart contract with KSM and multi asset support on Westend or Paseo
- Basic UI - A basic UI for interacting with the smart contract
Milestone 2, UI + XCM:
$9,900
1 month
- Tests - tests for all features
- User interface design - UI design
- XCM transfers - XCM transfer assets in UI
- Fixed amount transfer only - Allow fixed amount transfers in the UI
Milestone 3, Mainnet Deployment:
$16,900
1 - 1.5 months
- Contract Migration to Kusama Assethub - Migrate contract from Testnet to Kusama Hub
- Public documentation - Documentation for using Kusama shield and developer integration documentation
- Test - tests for contract
- V1 UI - User tested & something we can be proud of
** re: Finder’s Fee: this payment is set aside to incentivize a broad search for the right implementor. Finder’s Fees are paid out at time of team engagement. Teams that submit themselves can collect their own Finder’s Fee at completion of project.
See More