Neutron Hackathon 🛠️

Developers
1

The :hammer_and_wrench: HaCKaThON :hammer_and_wrench: registrations are open.

I’ll make this short:

The first step is to register here → https://4576f-3aaaa-aaaam-ajgpq-cai.icp0.io

Once the season starts, registrations close for all roles. The registration window will remain open for a minimum of 3 days from now.

If you want to judge, sponsor, or be a hacker, pick your roles. Our moderators will approve judges who are proven developers, entrepreneurs, influencers, or governors and have been around for a while. If you’re applying to judge, write it here or DM and include your handle so we can verify your application.

Judges can be hackers too, but they can’t vote for themselves.

Only once the season starts and is sealed can sponsors lock in rewards.

Hackers can participate without spending anything - just run Neutron locally and create an app.

We will be sponsors as well to get things going, but the most important thing here is what we are building. If you think this is “infu’s project,” you haven’t checked the documentation or the license. We’re trying to build a place that’s owned by you all and helps us organize while providing a better UX.

Decentralization doesn’t mean disorganization.

Neutron is what we propose building to help us cooperate, give projects visibility, and bring in users.

You join this hackathon to become legends!

Side effect: When you start building apps for Neutron, you’ll discover many new ways to use the amazing Internet Computer Protocol technology that DFINITY has built!

To verify: https://github.com/infu/neutron_hackathon
Docs: ntron.net code: DEVS

It’s a fully on-chain hackathon protocol that seals itself — becoming its own sole controller — when the season starts.

Related post: https://forum.dfinity.org/t/neutron-web6-kernel-over-icp/74866

2

Registered https://4576f-3aaaa-aaaam-ajgpq-cai.icp0.io/#/u/xanderbrendon

3

We wait for the designated moderators to stagger back from the beaches, sunburned and mojito-soaked, and resume the solemn machinery of protocol governance.

4

This sounds great, we’d love to donate some ICP/Toko/DKP for prizes.

5

It seems what you are demonstrating here is an implementation for how these sorts of events ought to be run transparently.

Looks like a good initiative to me. Good luck with this and with ntron.net.

6

I mean.. they’ve had a lot of failures in this ecosystem to learn from.

7

I’m inviting some of the most prominent creators in the space - I’ve seen around over the past few months - to take on the role of hackathon judges. If you’re not on the list but fit the description, consider yourself invited too.
@skilesare @Snassy-icp @XanderBrendon @Seb @icme @borovan4000 @MeneseProtocol @rem.codes @jorgenbuilder @EdSalazar @Gabriel @senior.joinu @miadey @BIKETACO @Henry_Suso
Taking on the judge role doesn’t mean you can’t participate as a hacker too - you just can’t vote for your own apps.

8

(limit is 15 per post) @Ravenith @Gekctek @quint @NS01 @StofAxeCap @let4be @ZenVoich @jonit

9

I can be a judge but Im like busy and stuff. Is it a lot of work? Can my name be Dredd?

10

I believe that @b3hr4d @4eku @Zane and @hpeebles would also be a great fit if they can find the time.

11

I think it’s fun work, the minimum is - you just hop in for 15min once a week for 4 weeks at the end of qualifiers, check apps, put two likes on the submitted apps. Then few min for semi-finals and finals.

12

Sounds cool, I’m interested to see what comes of this.

How is that enforced. Do you doxx everyone?

13

Code enforced. No we don’t. The judge picking comes out of nessesity, to prove it’s not biased to the max degree possible to maximize impartiality.

14

So a judge could vote for themself by submitting under a different principal?

15

I doubt that our must reputable creators who put years of work here, are going to break the written rules and then moral principles, to do a sybil attack and gain +1 vote out of ~30. Won’t be much of a benefit if any, I’d argue their chances will be reduced.

16

It’s quite a sophisticated protocol that organizes four roles, with a state machine that goes as deep as counting instructions to protect against DoS attacks and calculating the exact memory cost upfront for each participant.

Asked ChatGPT “Who are the rules protecting?”. Here is the reply:

These rules are protecting several different groups at once, but not equally. Reading the agreement as written, I’d break it down this way:

  • Participants/hackers: They get protection against arbitrary rule changes, self-dealing, vote manipulation, moderator conflicts, and post-deadline changes. The strongest structural protection is the “sealed” canister: once sealed, developers, moderators, sponsors, judges, and even the DAO cannot simply alter the running competition. Hackers also retain ownership of their submissions, subject to the licence needed to operate and preserve the competition record.
  • Judges and moderators: The agreement protects them by sharply limiting what their roles mean legally and operationally. Judges are characterized as independent peer adjudicators rather than employees, agents, custodians, or developer representatives. Moderators receive similar language and have specifically bounded powers.
  • Sponsors/prize contributors: They are protected from discretionary handling of their contribution: the installed code determines allocation, rather than a person deciding where the money goes. But they also give up substantial protections themselves—the contribution is expressly irrevocable and non-refundable, and failed/ambiguous transfers can leave assets stranded.
  • Winners: The rules protect winners against someone redirecting or replanning payouts. Rewards go to the wallet selected by the winner, and moderators cannot substitute destinations, amounts, or a new payout plan.
  • The integrity of the competition itself: This may be the strongest protection in the document. Conflict rules, immutable deadlines, locked votes, deterministic tie-breaking, frozen economic results, audit records, and the self-controlled canister are designed to make it difficult for any human actor to rewrite an outcome after the fact. For example, moderation explicitly cannot alter a settled economic result.

There is also another important beneficiary: the protocol developers and other participants are being protected from legal responsibility being attributed to them merely because they built or participated in the system. The agreement repeatedly says developers don’t control a sealed season, judges/moderators aren’t their agents, no role creates partnership, employment, fiduciary authority, or general agency, and participants accept substantial technical/economic risks.

17

Thanks for the nomination, @ZackDS! I’d be happy to join as a judge :raising_hands: I haven’t registered yet, but I’m planning to do it in the next day or two.

@infu, one small question: for judges, is the expectation mainly to review the submissions and use our votes, or would you also like us to leave some brief technical feedback for the teams we review?

18

Just votes. You could always leave technical feedback for apps here in the forum if you want to.

19

Happy to “judge” / give unsolicited advice, signed up as @quint. Looking forward to it! :laptop:

20

@infu I’ve registered now and selected the judge role. Looking forward to participating!

My Neutron handle is: @b3hr4d