April 18, 2026
Kickoff session
The event opens with an in-person kickoff from 11:00 AM to 1:30 PM PDT. Participants should expect orientation, event context, and final logistics before the build window begins.
Participant Guide
Build boldly. Work solo. Submit by April 25, 2026.
MSX Hackathon begins with an in-person kickoff on April 18, 2026, followed by a one-week build window. This guide covers the key dates, participation rules, and submission requirements for participants selected through partner school organizations.
Venue: 6700 Ridge Park Rd, Newport Beach, CA 92657
Eligibility: selected through partner school orgs
AI policy: fully allowed
Judging: async review after deadline
Timeline
Two dates define the week.
April 18 to April 25, 2026
Development stage
After kickoff, participants build independently through the official development stage, which runs until April 25, 2026 at 11:59 PM PDT. There are no teams to coordinate, and no required live checkpoints have been announced.
April 25, 2026
Final submission deadline
Projects must be submitted by 11:59 PM PDT. Unless organizers state otherwise, late submissions should be considered ineligible.
Eligibility
Participation is intentionally limited.
Who can join
Participation is limited to people selected through partner school organizations. If you were not selected through one of those channels, do not assume you are registered.
Team format
This is a solo-only hackathon. Every submission should reflect the work of a single participant, not a pair or a larger group.
Build Rules
The rules are simple and meant to be followed.
Build something with a real web3 component.
Every submission must include a meaningful web3 component that plays a real role in the product. Web3 should shape the experience itself, not just the branding. All web3 directions are welcome, though judges may be especially interested in projects that show strong thinking in areas like trading, exchange flows, market structure, or financial infrastructure.
Start the actual project during the hackathon.
Submissions should be new work created for MSX Hackathon. Idea sketching, tool exploration, and machine setup beforehand are fine, but substantive product work should begin on April 18, 2026.
AI use is fully allowed.
You may use any AI tools you want. There are no special restrictions on AI assistance for coding, design, research, writing, or prototyping.
Submit only work you have the right to share.
Do not include plagiarized assets, unlicensed code, unsafe content, or material that violates platform terms, intellectual property rights, or other people’s work.
Stay respectful.
Harassment, hate, intimidation, or abusive behavior toward participants, organizers, or partner schools is grounds for removal from the event.
Examples of valid web3 components
- wallet-based identity or interaction
- smart contract or onchain data integration
- token-based mechanics
- trading, analytics, settlement, or portfolio workflows
- decentralized storage, attestations, or ownership systems when central to the product
What does not count on its own
- crypto-themed branding
- a wallet button with no real function
- vague token ideas without implementation
- a standard app with only a superficial blockchain reference
Submission
Your repository is your submission.
Submissions must be completed through the official submission form before the deadline and must include a public GitHub repository. The form is required for organizer tracking, and the repository remains the core project artifact.
Your repository should be clear enough for someone else to understand what you built, how to run it, and why it matters.
Because web3 is a required part of the project, your repository should also explain what the web3 component is, where it appears in the product, and why it matters to the overall experience.
The submission form is now closed. The form (previously hosted at tally.so/r/Zjz0Vo) collected basic project details, the repository link, and a brief explanation of the project’s web3 component. No new submissions are being accepted.
Required before you submit
- The completed official submission form
- Your name, email, school or partner organization, and project title
- A public GitHub repository for your project
- A short project summary
- A short explanation of the project’s web3 component and why it is essential
- A README with setup instructions and project context
- Clear setup and run instructions
- Enough context for judges to evaluate the project asynchronously
Submissions closed as of April 25, 2026 at 11:59 PM PDT.
The official submission form is no longer accepting entries. Direct any follow-up to
legal@msx.com.
Judging
Projects will be reviewed after the deadline.
Review format
Judging happens asynchronously after April 25, 2026. Participants should assume judges will review the repository and README without a live walkthrough.
Rubric emphasis
Expect a balanced evaluation across usefulness, execution quality, originality, and how clearly the project is presented in the repository.
Prizes: 1st place $500, 2nd place $200,
3rd place $100, 4th to 6th place $25 Amazon gift cards,
and 7th to 9th place $10 Amazon gift cards. Standout participants may
also be considered for internship or job opportunities.
Winners
Three builds, three places.
LP Autopilot
Atomic, permissionless rebalancing for Uniswap v3 LP positions, deployed live on Arbitrum Sepolia.
Web3 is structural here — the Solidity contract is the product. Atomic exit and re-mint preserve user custody, deployed with verifiable on-chain proof (real position tokenId 3042), 9 of 9 Foundry fork tests passing, and a Next.js dashboard reading live on-chain state. The clearest example in the field of "trading, exchange flows, market structure, or financial infrastructure," with a thoughtful argument for why this primitive must live on-chain.
Signum
Multi-chain crypto signal platform combining whale tracking, stablecoin supply, and AI synthesis.
A genuinely useful product that aggregates real on-chain data across five chains (Ethereum, BNB, Bitcoin via Mempool, Solana, XRP) and reads stablecoin supply directly from the contract, then folds it together with news and backtests via Claude into a directional signal. Bonus points for polished visual design. Falls just behind on technical depth because the web3 layer is read-only — no contracts deployed.
Web3 Arbitrage Analyzer
CEX vs. DEX arbitrage analyzer with execution-cost modeling and Monte Carlo simulation.
A sharp original framing — most tools show theoretical profit; this one models why you still lose money once latency, slippage, gas, and fees enter the picture. Smaller scope than the top two (Streamlit and Python only, web3 data via DexScreener rather than direct chain reads), but the insight is genuine and the execution holds together.
FAQ
Answers to the questions participants usually ask first.
Is AI allowed?
Yes. AI use is fully allowed for this event.
Can I work with a friend?
No. Team size is one person only.
Can I submit an existing project?
No. The submission should be new work created for this hackathon, even if you did light planning or environment setup ahead of time.
What if the venue has not been announced yet?
The kickoff venue is 6700 Ridge Park Rd, Newport Beach, CA 92657.
Do I need anything besides the GitHub repo?
Yes. You should expect to submit through the official form and include the public repository there. The repo is required, but the form is part of the submission flow.
Contact
Support will run through organizer email.
Support for this event will run through email at legal@msx.com. Use it for logistics questions, submission issues, or clarifications about the rules.