ETHKyiv 2025

## Build a Privacy-First Application Using INTMAX **Use INTMAX to create a real-world application where privacy, scalability, or ultra-low gas fees unlock new possibilities.** --- ### 🧠 **Why INTMAX?** INTMAX is a zkRollup that offers: - 🔒 **Full privacy**: Sender, receiver, and amount are hidden by default. - ⚡ **Ultra-fast settlement** with minimal on-chain footprint. - 🪙 **Constant ultra-low fees** — ideal for microtransactions and frequent activity. - 👻 **Stateless architecture**: No account needed to start using it. Hackers can build apps that simply **can’t be done on other chains** due to fee or privacy limitations. --- ### 🧩 **Suggested Directions** Pick any of the following, mix & match, or create something totally new — as long as it makes INTMAX shine. ### 🧾 **1. Privacy-First Payments (Core Theme)** > Build a simple yet powerful crypto payment experience using INTMAX. > Examples: - Peer-to-peer wallet with **invisible tx history** - Merchant-facing **checkout module** - zkReceipts: verifiable payment proofs without revealing details - Pay & verify with zero address or token exposure --- ### 🌐 **2. Cross-Border Stablecoin Transfers** Create a remittance or international payout tool using privacy-preserving transfers and **stablecoins on INTMAX** (ITX, bridged USDC/DAI, etc.). --- ### 🪙 **3. Scalable Microtransactions** Use INTMAX's negligible fees to build: - Per-click, per-second, or per-API-call payment models - Streaming payments for music, content, compute time --- ### 🎯 **4. zk-Based Subscription Models** Design recurring payments or subscriptions (daily, weekly, monthly) using **zkProofs of payment**, without revealing user identity or usage history. --- ### 💸 **5. Privacy-Preserving Donations** Enable anonymous donations to individuals, NGOs, DAOs, or creators — without exposing wallet addresses or on-chain records. --- ### 🧰 **6. Merchant Tooling on L2** Create dashboards, invoicing, receipts, or tax tools for small businesses using **INTMAX-based private payments**. --- ### 📶 **7. Offline-Friendly Crypto Payments** Design a payment mechanism (e.g., QR codes, one-time secrets, NFC) that works offline and is settled privately on INTMAX when online. --- ### 🤖 **8. AI Agents with Autonomous Crypto Payments** Build a bot or AI agent that can: - Make or receive INTMAX payments autonomously - Pay for services like APIs, datasets, or compute cycles - Use zk identity/payment proof to interact with other agents or humans --- ### 🛡️ **9. Conditional Payments for Insurance Use Cases** Use INTMAX to build private, conditional payment systems for things like: - Health or travel insurance - Automatic payouts upon verified (private) conditions - zkProof-based payout logic (e.g., proof of delay, damage, or eligibility) Maintain full privacy of both the user and event conditions, while enabling reliable automation. --- ### 🧰 **What We Provide** - [Developer Docs (Gitbook)](https://intmax-wallet.gitbook.io/intmax-developers-hub) - SDK & JS wallet integration code - Direct chat with our team during the hackathon --- ### 🏆 **Judging Criteria** - **Impact** – Does this solve a real problem or enable new types of apps? - **Creativity** – Is the idea novel or does it combine features in a new way? - **INTMAX Integration** – Does it use our protocol’s unique strengths (privacy, statelessness, low fees)? - **Polish** – Is the UX smooth and usable? --- ### 💥 **Bonus Points For** - Bridging or integrating with other projects at ETH Kyiv (e.g., EVM projects) - Showing clear benefits of **privacy** in your UX - Using **zkProofs** for receipts, access, or identity --- ### 📬 Questions? Ping the INTMAX team at the venue or contact us at： Telegram chat, ETHKyiv channel - https://t.me/c/1783523395/1 Discord - https://discord.gg/Fs85pjvEKB

# General Track by ETHKyiv

### **About** [Nitrolite](https://www.yellow.org/) is a powerful state channel framework that enables developers to build high-performance decentralized applications with near-instant finality and minimal gas costs. Yellow invites developers to explore the capabilities of ERC-7824 and the Nitrolite Protocol, contributing or utilizing to the Nitrolite SDK ### **Qualification Requirements** - Integrate Nitrolite SDK: Demonstrate the use of ERC-7824 in facilitating state channel mechanisms within your application - Or contribute improvements, issue resolution to the protocol repository nitrolite and clearnode - Provide a Working Demo: Submit a functional demonstration of your application, showcasing the integration - Open Source Your Code: Ensure your project’s codebase is publicly accessible for evaluation **Useful Links:** - Workshop from ETHPrague: https://youtu.be/dF0SeIYbyJY?si=zvbcrdSzkYbhEbRC - ERC-7824 — https://erc7824.org/ - Nitrolite Pragma Taipei 2025 — https://www.youtube.com/watch?v=FCpXOnprbSg - Nitrolite TypeScript SDK — https://ethglob.al/e81do - GitHub Clearnode — https://github.com/erc7824/clearnode

# **Sniper-Cashbackers on Base** 🤑 > *“Let bots pay for alpha. Let creators farm their greed.”* > ## 🧠The Premise: Token creators get sniped — and usually walk away with nothing, while sniper bots farm all the upside. Let’s fix that. Build a system that lets **token creators auction off the right to snipe** their tokens. Snipers compete with **ETH bribes** to get included early. Bribes go directly to the token creator. More bots ⇒ more bribes ⇒ more profit for the creator. Maximize chaos. Monetize attention. --- ## 🔧 What You’ll Build: ### 1. 🔫 Telegram Bot (for Snipers) Let snipers: - `/register`: create a wallet (PK stored backend-side) - View wallet balances (ETH + tokens) - `/snipe <token_address> <bribe_in_ETH>` → Submit a desired token address (which is not live yet) and offer a bribe to be included in the snipe bundle On LP_ADD (tx signal will be shared from RPC component): - Bot constructs bundle: - TX 0: LP_ADD from token creator - TX 1...N: sniper swaps - UniV2 swap buy of desired Token (unlimited slippage) - Bribe (ETH) sent to token creator (LP_ADD tx origin) as internal transfer. - Sniper Buy swaps must be strictly sorted by bribe size. How to sort: each tx has gasPrice = previous - 1 wei, so Base sequencer will respect the ordering. - Final bundle = `[LP_Add, Sniper1, Sniper2, ..., SniperN]` - Submit to Base sequencer ### 2. 🤑 Custom RPC (for Token Creators) Token creators use a custom RPC endpoint in their Metamask/Rabby: - Non-LP_ADD txs → pass through to Base sequencer normally - If LP_Add detected: - Forward to Telegram bot backend - If active sniper bids exist → trigger bundle build - Sniper bribes go directly to creator --- ## ⚒️ Tech Stack - Any language - Preferred: **Rust** / **Go** for backend & RPC proxy (but not required) - Constant Product Pool (uniV2-like dex) - Base network (or Base testnet) --- ## 📬 Contact Us If you have any questions about the task — don’t hesitate to DM [@apadenko](https://t.me/apadenko) on Telegram.

# The Graph Builders DAO **1. Has to be synced on studio or the graph network (not alchemy or goldsky) 2. Have to submit the code 3. Have to submit the dev query endpoint from studio**

# Peanut Trade You should build a constant-product DEX with some additional features which should be optional on pool deployment: 1. **Dynamic Swap Fee**, which increases at high volatility 2. **Snipe Protection**, which means high swap fee on pool deployment which decreases over time (either linearly or exponentially) 3. **Launchpad**, which lets the token dev to create a pool with only one token without prodividing WETH/stables 4. The protocol should be as **gas-optimized** as possible, meaning a one-hop swap on a pool without features should take ~150k gas, meanwhile a one-hop swap on a pool with all features enabled should take ~200k gas. 5. **UI** for pool deployment, position managing & swapping is welcome.

# Issue Fix / Protocol Improvement **For meaningful contributions such as fixing GitHub issues, resolving bugs, or proposing improvements to ERC-7824 or Nitro.**

# Docs Improvements **For helpful pull requests improving clarity, coverage, or structure of our documentation (Nitrolite SDK, Nitro Protocol, or ERC-7824).**