{"schema":"BUIDL","d":{"id":8513,"members":[],"pictures":["https://cdn.dorahacks.io/static/files/18c863fe81b58659a7278644239b12b3.png"],"roundProjects":[{"id":5642,"active":true,"createdAt":"2024-02-29T09:42:41.450587+08:00","name":"Tokenized Interchain Accounts","hash":"7","projectId":8513,"ownerAddr":null,"matchingPool":59.09,"contributions":2.1,"votes":182,"voters":134,"bounties":[],"roundInfo":{"path":"/grant/injective-grant-dao","id":71,"name":"Injective Grant DAO Round 1","uname":"injective-grant-dao","grantType":"","isBscGrant":false,"grantTitle":"Injective Grant Dao","grantName":"Injective Grant Dao","sponsors":1500,"contributions":150.7,"buidls":10,"votes":4873,"unit":"INJ","status":2,"roundSeq":"1","chainId":12345613,"contractAddr":"inj1ec8y6w5mwgrw56h2k5ssp9wwyuv5thav0tdqpd","startFrom":1710723600000,"endTo":1712620799000,"voteTime":1710766800000,"registerDueTime":1710766800000,"projects":[],"grant":{"path":"/grant/injective-grant-dao","id":59,"name":"Injective Grant Dao","owner":null,"extraInfo":{},"symbol":"Injective Grant Dao","uname":"injective-grant-dao","tags":[],"banner":"https://cdn.dorahacks.io/static/files/1873836f636a4cea57c21db46eeb45f5.jpg","bannerEn":"https://cdn.dorahacks.io/static/files/1873836f636a4cea57c21db46eeb45f5.jpg","detail":"Injective Grant Dao","detailEn":"Injective Grant Dao","startFrom":1680241755000,"endTo":1714456155000,"matchingPool":1500,"sponsors":1500,"contributions":150.7,"votes":4873,"voters":2247,"rounds":[],"currentRound":null,"doraGrantDaoTags":[]},"extraInfo":{}}}],"hackathonProjects":[{"id":9350,"hackathon":{"id":199,"tabSet":[{"id":394,"name":"Submission Guide","slug":"submission","description":"# Getting Started [3-5 MIN]\n\n**1.** **You should submit your BUIDL via [DoraHacks.io](https://dorahacks.io/). Before that, make sure that you already have an account.**\n\nUse the **Sign in/up button** at the upper right corner of the page to access the sign-up options.\n\n

\n\n**Github, crypto wallet** and **email** are supported for creating an account. For BUIDLers, we recommend you to connect the account to your **github** to make more people know what you are building at any time.\n\n*You may be asked to receive a verification code via email. The email may take some time to arrive. No worries! The code will not expire in 10 minutes when you click “send code”.\n\n**2. Before the submission of deadline, please make sure you have added your Github link to the project. You can submit the project first, edit it later before the deadline.**\n\nClick “Submit BUIDL”.\n\n

\n\n> **→ If you already have a BUIDL on DoraHacks**\n\nChoose your BUIDL project from **\"Apply with Existing BUIDL\"** and identify the track you want to join.\n\n> **→ If you want to submit a new BUIDL project**\n\nClick **“Create a new BUIDL”** and fill in the form as required. You'll be directed to \"Apply for Injective x Google Cloud Illuminate Hackathon\" page after the new BUIDL setup.\n\nFill in the form to offer the information about your project. Note that for demo, demo link and social media, please offer **URLs (with http/https://)**.\n\n

\n\nDon't forget to check \"I agree to the User Agreement\".\n\n

\n\nBack to Application window. Choose your BUIDL project from **\"Apply with Existing BUIDL\"** and identify the track you want to join.\n\nWhen submission succeeds, you'll see this notification.\n\n

\n\n# Project Verification\n\nWait! Don't just leave your BUIDL here and forget about it. Please contact DoraHacks staff on **Telegram** [@dorahacksofficial](https://t.me/dorahacksofficial) for project verification and promotional support. We'll make every BUIDL a poster and arrange a live project demo session for you via Youtube Live/Binance Live. Don't let go of the chance to receive huge visibility!\n\nOr, you can also reach us out at the **#buidl-verification channel** in the **Discord** https://discord.gg/gKT5DsWwQ5\n\n# Want to make some changes to your BUIDL?\n\nClick [Avatar] -> [Profile] to enter the Account Center, and click the \"Edit\" button on the top right of the BUIDL to update the BUIDL information.\n\n

\n\n
\n\n

"},{"id":399,"name":"Hackathon Ideas","slug":"hackathon-ideas","description":"# *Table of Contents*\n\n\n○ Copy Trading
\n○ Prediction Markets
\n○ Fixed Rate Lending
\n○ Interest Rate Swaps
\n○ Generic Ethereum Oracle
\n○ Ethereum AMM LP Hedging
\n○ Peer-to-Peer (P2P) Payment App
\n○ Margined Trading Product
\n○ DeFi Management Dashboard
\n○ NFT Dump-to-Earn
\n\n\n\n# Copy Trading\n\n### Overview\n\n[Copy trading](https://learn.bybit.com/copy-trading/what-is-crypto-copy-trading/) on DEXs is a less common feature compared to CEXs due to latency and gas constraints. Injective’s sub-second block times and low gas fees can enable automated copy trading through smart contracts.\n\n[Warp](https://docs.warp.money/) has integrated with Injective and can automate smart contract executions through a decentralized network of agents. Essentially, the user specifies the criteria under which the smart contract should execute and the agents will execute the contract accordingly.\n\nIn this case, the agents can observe the block events through dynamic logic queries to determine when a given address has executed a trade. As soon as this happens, the agents will automatically execute the same trade on behalf of the user in the next block.\n\nIn order to reduce complexity and risk, the user can delegate permissions to execute trades to the smart contract through [authz](https://docs.cosmos.network/v0.46/modules/authz/). This negates the need for the smart contract to hold the capital which is more appealing to users.\n\n### Hackathon MVP\n\n
\n\n- Create a website that allows the user to input the address they want to copy. The website should also show active INJ balance for the contract so the user can fund it accordingly. It should also redirect users to [helixapp.com](http://helixapp.com) so they can track performance of their trades and balances.\n- Develop the dynamic query as per the Warp [docs](https://docs.warp.money/). The block events for spot and derivative order creation and cancellation are: `EventCancelSpotOrder`, `EventCancelDerivativeOrder`, `EventNewSpotOrders` & `EventNewDerivativeOrders`. Keep in mind that the contract should open exposure relative to the active wallet balance. If the address we’re copying, executes a trade of 3% relative to its balance, the contract should open a trade of 3% relative to the user’s balance.\n- Develop the smart contract to execute the trades on behalf of the user through authz.\n\n
\n\n### Resources\n\n
\n\n- [Protocol docs](https://docs.injective.network/develop/modules/Injective/exchange/binary_options_markets)\n\n- Typescript [SDK](https://github.com/InjectiveLabs/injective-ts) & [docs](https://docs.ts.injective.network/)\n\n- [Warp docs](https://docs.warp.money/)\n\n
\n\n### Mentor\n\n
\n\n- **Achilleas Kalantzis, Integrations Engineer**\n\n- **Discord Username:** `achilleaskalantzis`\n\n# Prediction Markets\n\n### Overview\n\nInjective’s fully on-chain orderbook allows users to launch various financial instruments such as spot, perpetuals, expiry futures and binary options. Prediction markets have lately attracted a vast interest across the industry but none of the key players have achieved meaningful traction due to capital inefficiency present in AMM designs and high gas fees.\n\n[Frontrunner](https://www.getfrontrunner.com/) is a protocol focusing on sports-betting set to launch on Injective’s orderbook in the coming weeks.\n\nWe propose a more generic implementation of the binary options primitive akin to [Augur](https://augur.net/) and [Polymarket](https://polymarket.com/) which don’t focus on a specific niche (i.e. sports betting). Injective’s orderbook and extremely low gas fees would enable high retail engagement and capital efficiency. Even though bootstrapping liquidity on an orderbook is a major problem, [Mito](https://mito.fi/) set to launch in the upcoming months will allow users to bootstrap liquidity through vaults. Users can pull their capital into a vault which is going to be controlled by a sophisticated market-maker and provide liquidity to these markets.\n\n### Revenue Model & Incentives\n\nInjective incentivizes vault LPs, exchange dApps and market makers through a unique design. Protocol fees are split in two portions: the auction and the fee recipient. 60% of the fees go to the [auction pool](https://hub.injective.network/auction) whereby users can bid for a basket of tokens (mostly stablecoins) with INJ tokens. The winner receives the basket with all generated fees and the INJ used to bid, are burned.\n\nThe rest of the 40% can be set to a unique address which can be modified accordingly from the sender.\n\n**Vault LPs**\n\nUsers who LP into Mito vaults will generate APY through Injective’s incentives programs, namely [Trade & Earn](https://helixapp.com/trade-and-earn) and [OLP](https://trading.injective.network/) as well as the strategy’s performance. Market makers will make money off the bid-ask spread, thus utilizing the capital more efficiently and distribute it back to the LPs.\n\n**Exchange dApp**\n\nThe exchange dApp (the deliverable in this project), will set the fee recipient to an address of its choosing on the frontend page. Thus, all retail users who trade on the dApp will pay the full market fee but you will effectively receive 40% of those fees immediately to you wallet.\n\n**Market Makers**\n\nMarket makers who faciliate the trading activity of the vault, will set fee recipient to an address of their choosing. All LPs will pay the full protocol fees for each trade that will be faciliated by the market maker but 40% of the fees will go back to an address the market maker owns.\n\n# Hackathon MVP\n\n
\n\n- Develop an exchange dApp akin to [Helix](https://helixapp.com/) and [Frontrunner](https://www.getfrontrunner.com/) for generalized prediction markets.\n\n
\n\n### Resources\n\n
\n\n- [Protocol docs](https://docs.injective.network/develop/modules/Injective/exchange/binary_options_markets) on Injective’s binary options primitive\n\n- [API docs](https://api.injective.exchange/#binary-options) on Injective’s binary options\n\n- Polymarket’s [docs](https://docs.polymarket.com/#introduction) and [UI](https://polymarket.com/)\n\n- Augur’s [docs](https://docs.augur.net/) and [UI](https://augur.net/)\n\n- Helix (flagship DEX on Injective) [repository](https://github.com/InjectiveLabs/injective-helix). You may choose to fork the project and modify the front-end accordingly.\n\n- Typescript [SDK](https://github.com/InjectiveLabs/injective-ts) & [docs](https://docs.ts.injective.network/)\n\n
\n\n### Mentor\n\n
\n\n- **Bojan Angjelkoski, Technical Lead**\n\n- **Discord Username:** `bangjelkoski`\n\n# Fixed Rate Lending\n\n### Overview\n\nThe vast majority of lending protocols follow a peer-to-pool approach that consist of variable rate models and governance. Risk-related factors and parameters such as interest rates are determined by governance in a reactive fashion as market conditions change. Even though this approach has been an innovation in DeFi and offers utility, fixed-rate lending is an untapped area.\n\nFixed-rate lending would allow borrowers to predict the costs of a given loan in contrast to the existing approach where costs change over time, degrading UX.\n\nThe primary parameters can be set by governance but some parameters can be set freely by participants. This would be achieved by an overcollateralized zero coupon bond-based P2P lending protocol. \n\nZero coupon bonds are a debt instrument that pay no interest, they rather trade at a discount and thus generate profit for the holder at maturity when redemeed.\n\nBorrowers would set collateral in ratios pre-set by governance. Upon minting these bonds, users would be able to sell them on the market in return for the token they were looking to borrow.\n\nLenders would receive these bonds and exercise them for face-value at maturity.\n\nHere is a concrete example on the flow:\n\n- Alice wants to borrow 1,000 USDC for 1 year.\n- The current market price for 1,000 USDC is 1,100 1-year USDC bonds.\n- Alice provides enough INJ collateral to mint 1,100 1-year USDC bonds.\n- She then proceeds to sell them in the market* for 1,000 USDC.\n- Bob, who wanted to lend 1,000 USDC, had previously placed a limit order on the market to buy 1,100 1-year USDC bonds for 1,000 USDC.\n- When Alice sells the bonds, Bob receives the 1,100 1-year USDC bonds which, at maturity, would be redeemable for their face value: 1,100 USDC. If we assume this transaction happened at the start of the 1-year period, then the implied interest rate for this loan would be 10%.\n\nUpon maturity, borrowers have the ability to repay the loan or the system will automatically roll the maturity one additional period. This ensures that there’s always principal for lenders to redeem. This system is overcollateralized and borrowers are subject to liquidations when the ratio drops below governance-defined thresholds.\n\nWe believe an orderbook design is more expressive as lenders can quote based on their views about interest rates. As bonds reach maturity or liquidation, the system requires sophisticated market makers to supply liquidity.\n\n### Hackathon MVP\n\n
\n\n- A bond minting mechanism that accepts collateral and handles liquidations directly on Injective’s orderbook when it falls below a threshold.\n- Create a website to incorporate the above design. The front-end should reflect on open positions and liquidation thresholds.\n- The rollover mechanism does not need to be part of the MVP.\n\n
\n\n### Resources\n\n
\n\n- [Protocol docs](https://docs.injective.network/develop/modules/Injective/exchange/binary_options_markets)\n\n- Typescript [SDK](https://github.com/InjectiveLabs/injective-ts) & [docs](https://docs.ts.injective.network/)\n\n- Notional Finance [product](https://notional.finance/) and [docs](https://docs.notional.finance/notional-v2/)\n\n
\n\n### Mentor\n\n
\n\n- **Eric Chen, CEO**\n\n- **Discord Username:** `ericinjective`\n\n# Interest Rate Swaps\n\n### Overview\n\nInterest rate swaps are financial derivatives commonly used in Traditional Finance (TradFi) to manage and mitigate interest rate risk. They are agreements between two parties to exchange interest rate payments over a set period of time. These contracts allow entities to transform the terms of their debt or investments to better suit their specific needs and risk profiles.\n\nIn a typical interest rate swap, there are two legs:\n\n**1.** Fixed leg: One party agrees to pay a fixed interest rate on a notional amount throughout the life of the swap. The fixed rate is predetermined at the inception of the swap.\n\n**2.** Floating leg: The other party agrees to pay a variable interest rate, typically tied to a reference rate such as LIBOR (London Interbank Offered Rate) or an interbank lending rate, on the same notional amount. The variable rate is reset periodically, often every three or six months, to reflect changes in the reference rate.\n\nThe key objective of interest rate swaps is to allow participants to manage interest rate exposure and cash flow uncertainties. Some common reasons for using interest rate swaps include:\n\n**1.** Hedging: Businesses can use interest rate swaps to protect themselves against adverse interest rate movements. For example, a company with a variable-rate loan might swap it for a fixed-rate obligation if they expect interest rates to rise, thereby locking in a predictable interest expense.\n\n**2.** Yield enhancement: Institutional investors may use interest rate swaps to increase their overall investment yield by exchanging a fixed income stream for a potentially higher variable income stream.\n\n**3.** Asset-liability management: Financial institutions can use interest rate swaps to better match the duration and interest rate characteristics of their assets and liabilities, reducing potential mismatches and risk.\n\n**4.** Speculation: Some market participants may use interest rate swaps as a speculative tool, taking positions on future interest rate movements.\n\n### DeFi Landscape\n\nThere are mainly two mechanisms to implement interest rate swaps on-chain.\n\n**1.** Utilize CDPs to mint expiring derivatives known as “fyTokens” implemented by Yield Protocol.\n\n**2.** Mint two tokens to represent the principal and yield, “pTokens” and yTokens” , effectively splitting the yield-bearing assets as implemented by Pendle.\n\n**Purpose and Functionality**\n\n- Yield Protocol: Yield Protocol is a platform that enables users to create and trade interest rate derivatives. It allows users to mint fixed-term, fixed-rate debt tokens called fyTokens by depositing collateral (usually stablecoins). These fyTokens represent claims on the underlying collateral plus interest. Users can trade these fyTokens, enabling them to manage and speculate on interest rate exposure.\n- Pendle: Pendle is a protocol that facilitates the creation and trading of tokenized future yield streams. It allows liquidity providers (LPs) to lock their tokens, such as those obtained from providing liquidity on Automated Market Makers (AMMs), into smart contracts called Yield Tokens (yTokens). These yTokens represent future yield generated by the locked assets. Users can trade these yTokens, allowing for more efficient capital utilization and yield optimization.\n\n**Assets Supported**\n\n- Yield Protocol primarily supports stablecoins or other assets that can be used as collateral for creating fixed-term, fixed-rate debt tokens.\n- Pendle: Pendle supports a broader range of assets, allowing users to tokenize the yield of various assets locked in different protocols, including assets from AMMs and lending protocols.\n\n**Use Cases**\n\n- Yield Protocol: Its primary use case is interest rate management and speculation. Users can use fyTokens to hedge against interest rate volatility or speculate on interest rate movements.\n- Pendle: Pendle's main use case is yield optimization and trading. It enables LPs to tokenize their future yield streams and trade them to unlock additional capital or optimize their investment strategies.\n\n**References**\n\n
\n\n- Yieldspace AMM: https://yield.is/YieldSpace.pdf\n\n- Pendle: [https://docs.pendle.finance](https://docs.pendle.finance/)\n\n- Element: https://docs.element.fi/\n\n- TimelessFi: https://docs.timelessfi.com/\n\n### Hackathon MVP\n\n
\n\n- Create a fixed-yield primitive using the fyToken model where liquidity for fyTokens uses an on-chain order book. Choosing a single collateral token (e.g. ATOM), a single borrow token (e.g. USDC), and a single expiration date will simplify implementation. Scope can be further reduced by focusing on one side of the market (borrowing or lending).\n- Users should be able to either mint fyTokens with collateral (to borrow at a fixed rate) or purchase fyTokens from a market (to lend at a fixed rate). The user interface should simplify calculations about achieved fixed rates, and allow borrowers to monitor the health of any open positions.\n- To ensure healthy order book depth for the fyToken derivatives, design a mechanism to incentivize makers (e.g. emit tokens to makers that have orders at the top of the book multiple blocks in a row).\n\n
\n\n### Resources\n\n
\n\n- [Protocol docs](https://docs.injective.network/develop/modules/Injective/exchange/binary_options_markets)\n\n- Typescript [SDK](https://github.com/InjectiveLabs/injective-ts) & [docs](https://docs.ts.injective.network/)\n\n
\n\n### Mentor\n\n
\n\n- **Eric Chen, CEO**\n\n- **Discord Username:** `ericinjective`\n\n# Generic Ethereum Oracle\n\n### Overview\n\nWe propose the integration of a generic Ethereum oracle on Injective. Oracle providers such as Pyth and Band provide a limited set of feeds that have been vetted. These feeds are usually crypto assets or hard assets such as gold or silver.\n\nA generic Ethereum oracle would allow users to pass contract state from Ethereum to Injective and enable new use-cases. One example is Uniswap v3, uniswap pools can serve as [oracles](https://docs.uniswap.org/concepts/protocol/oracle) and would allow users to launch perpetual markets on Injective with arbitrary Uniswap pools as oracles.\n\nAdditionally, pool information on LPs and token ratios could enable a new product whereby users can hedge and reduce incurred IL (Impermanent Loss). A smart contract on Injective could place trades in a perpetual market for the same asset the user has incurred IL on AMMs like Uniswap.\n\n### Hackathon MVP\n\n
\n\n- Implement a generic query-response interface for requesting and relaying Ethereum state data along with a modular proof verification layer. This should include a production-ready centralized proof of concept. The Ethereum state data will be stored on an Injective smart contract which should be structured with data storage considerations in mind in order to scale.\n- The project can then expand in a decentralized implementation of such interface via bridging infrastructure such as Wormhole or Axiom. This should not necessarily be part of the MVP.\n\n
\n\n### Resources\n\n
\n\n- [Protocol docs](https://docs.injective.network/develop/modules/Injective/exchange/binary_options_markets)\n\n- Typescript [SDK](https://github.com/InjectiveLabs/injective-ts) & [docs](https://docs.ts.injective.network/)\n\n- Python [SDK](https://github.com/InjectiveLabs/sdk-python), [GO](https://github.com/InjectiveLabs/sdk-go) & [docs](https://api.injective.exchange/#introduction)\n\n
\n\n### Mentor\n\n
\n\n- **Albert Chon, CTO**\n\n- **Discord Username:** `albertchon`\n\n# Ethereum AMM LP Hedging\n\n### Overview\n\nThis document proposes a simple, Ethereum-centric application that enables Ethereum users to hedge their LP (liquidity provider) positions on CPMMs or AMMs such as Uniswap or Curve to avoid IL (impermanent loss) and maximize LP yields. Through a simple front-end, users can bridge stable assets such as USDT and hedge their qualifying LP positions on corresponding perpetual markets on Injective. The process of hedging is fully automated with a smart contract approach.\n\nLeveraging Injective’s infrastructure, a highly intuitive Ethereum-user facing application can be implemented with Injective interactions completely abstracted from the front-end. The application will suggest optimal amount of stable assets to hedge their existing qualifying LP positions, guide users through the bridging and Injective gas-free transactions through EIP712 signing, and begin helping users hedge their LP positions against IL (Impermanent Loss) in 1-click.\n\nRefer to [Logarithm](https://logarithm.fi/) for inspiration which is a project currently developing a similar product.\n\n### Hackathon MVP\n\n
\n\n- Implement a Cosmwasm smart contract that ingests hedging parameters upon user subscription and executes with user deposited funds when trigger conditions are met. The user should provide permissions to the smart contract through authz, this will negate the need for the contract to hold any funds.\n- On the front-end, implement a web application that queries user’s existing Ethereum LP position balance and derive the optimal hedging parameters to suggest to the user. Additionally, leverage Injective SDKs to guide users through the bridging and transaction signing process utilizing Ethereum native wallets for hedging and withdrawal. Applicants will receive bonus points if Injective is completely abstracted from the user experience.\n\n
\n\n### Resources\n\n
\n\n- [Protocol docs](https://docs.injective.network/develop/modules/Injective/exchange/binary_options_markets)\n\n- Typescript [SDK](https://github.com/InjectiveLabs/injective-ts) & [docs](https://docs.ts.injective.network/)\n\n
\n\n### Mentor\n\n
\n\n- **Bojan Angjelkoski, Technical Lead**\n\n- **Discord Username:** `bangjelkoski`\n\n# Peer-to-Peer (P2P) Payment App\n\n### Overview\n\nThis document proposes a simple payment app on Injective. Users should be able to tokens on Injective to a specified address or .inj name service (provided by [SpaceID](https://space.id/)) from their mobile. The product should have an integration with all wallets available on Injective dApps.\n\nUsers should also be able to transfer any token on Injective beyond INJ.\n\n### Hackathon MVP\n\n
\n\n- Develop a mobile application (iOS & Android) with support only for MetaMask or Keplr. The application can support only specified addresses and INJ as a token in the beginning.\n- The product can be further improved to include support for all wallets, .inj domains as well as custom tokens on Injective.\n\n
\n\n### Resources\n\n
\n\n- [Protocol docs](https://docs.injective.network/develop/modules/Injective/exchange/binary_options_markets)\n\n- Typescript [SDK](https://github.com/InjectiveLabs/injective-ts) & [docs](https://docs.ts.injective.network/)\n\n
\n\n### Mentor\n\n
\n\n- **Bojan Angjelkoski, Technical Lead**\n\n- **Discord Username:** `bangjelkoski`\n\n# Margined Trading Product\n\n### Overview\n\nThis document proposes a platform that combines trading in a model akin to [Rollbit](https://rollbit.com/). These platforms have attracted vast interest from the crypto community in the past few months. They allow traders to deploy capital in assets with extremely high leverage and potentially attain huge rewards.\n\nEven though the design of these platforms is not sound and might be prone to insolvency, aggressive liquidation framework and fees’ distribution can bootstrap liquidity in the early phases. The majority of the fees can be distributed back to the protocol to increase the pool size and potential losses when users make sizeable successful trades.\n\nThe product can expand to Sports, NFTs and more but the scope should be kept to trading and perpetual markets in the beginning for the MVP. The entire product should be fully decentralized with on-chain execution through CosmWasm smart contracts.\n\n### Hackathon MVP\n\n
\n\n- Develop a web application focused on perpetual markets with a peer-to-pool design. There should be a single pool for all markets and only launch top 20 tokens that are relatively non-volatile to ensure there’s a low risk of insolvency.\n- The product should also have relatively low leverage in the beginning (30-40x) with fee distribution back to the pool and LPs until the ecosystem grows. Tokenomics can be further improved with a token buy-back mechanism or fee discounts.\n- Pyth oracle prices from Injective’s oracle module should be utilized in the formula designs.\n\n
\n\n### Resources\n\n
\n\n- [Protocol docs](https://docs.injective.network/develop/modules/Injective/exchange/binary_options_markets)\n\n- Typescript [SDK](https://github.com/InjectiveLabs/injective-ts) & [docs](https://docs.ts.injective.network/)\n\n- Injective’s [oracle module](https://docs.injective.network/develop/modules/Injective/oracle/)\n\n- Rollbot [docs](https://rollbit.com/trading/price-formulation)\n\n
\n\n### Mentor\n\n
\n\n- **Achilleas Kalantzis, Integrations Engineer**\n\n- **Discord Username:** `achilleaskalantzis`\n\n# DeFi Management Dashboard\n\n### Overview\n\nThis document proposes a DeFi management dashboard akin to [DeFi Saver.](https://defisaver.com/) The Injective ecosystem has seen a surge in ecosystem growth with DeFi dApps such as [Mito](https://mito.fi/), [Helix](https://helixapp.com/), [Elixir](https://elixir.finance/), [Black Panther,](https://blackpanther.fi/) [Neptune](https://nept.finance/) and many more. The DeFi dashboard would allow users to view exposure and interact with DeFi applications on Injective from a single page.\n\nEffectively, they would be able to see and close LP positions in dApps such as Mito and Elixir. Additionally, users could add also view positions on dApps such as Helix and Neptune as well as interact with these protocols (i.e. add margin to avoid liquidation).\n\n### Hackathon MVP\n\n
\n\n- Create a web application that shows open positions across the aforementioned dApps on Injective.\n- Add CTA buttons to close positions and increase margin for the respective dApps. For the MVP, these buttons should redirect the user to the respective dApp for the interaction.\n- The product can be further improved by adding functionality to interact with these protocols from the web application and remove redirection which degrades UX.\n\n
\n\n### Resources\n\n
\n\n- [Protocol docs](https://docs.injective.network/develop/modules/Injective/exchange/binary_options_markets)\n\n- Typescript [SDK](https://github.com/InjectiveLabs/injective-ts) & [docs](https://docs.ts.injective.network/)\n\n- DeFi saver [product](https://defisaver.com/) and [docs](https://docs.defisaver.com/)\n\n
\n\n### Mentor\n\n
\n\n- **Bojan Angjelkoski, Technical Lead**\n\n- **Discord Username:** `bangjelkoski`\n\n# NFT Dump-to-Earn\n\n### Overview\n\nNFTs on Injective have seen massive growth with more and more marketplaces and collections go live. We propose an NFT dump-to-earn protocol whereby users can dispose their NFTs in return for a token or “fish” NFTs disposed by others akin to [JunkYard](https://junkyard.wtf/junkpaper).\n\nUsers might want to dispose NFTs they consider as useless and can’t be sold in a marketplace. In return they receive “JunkCoin”.\n\nUsers can also “fish” for NFTs disposed by others by paying a small fee.\n\n### Hackathon MVP\n\n
\n\n- Develop a FE site and smart contracts for the NFT disposal. The “fish” functionality can be added at a later stage and should not necessarily be part of the MVP.\n\n
\n\n### Resources\n\n
\n\n- [Protocol docs](https://docs.injective.network/develop/modules/Injective/exchange/binary_options_markets)\n\n- Typescript [SDK](https://github.com/InjectiveLabs/injective-ts) & [docs](https://docs.ts.injective.network/)\n\n- [JunkYard docs](https://junkyard.wtf/junkpaper)\n\n
\n\n### Mentor\n\n
\n\n- **Achilleas Kalantzis, Integrations Engineer**\n\n- **Discord Username:** `achilleaskalantzis`"},{"id":541,"name":"Results","slug":"results","description":"# Injective Illuminate Hackathon Finalist\n\nThe Injective X Google Cloud Illuminate Hackathon was a huge success and brought hundreds of hackers together. It’s time to announce the winners... 🥁\n\n# DeFi, Infrastructure and Tooling\n\n**First Prize**\n\n**[Aeroscraper](https://dorahacks.io/buidl/7509)**\n\nAeroscraper is a user-centric decentralized lending-borrowing protocol that revolutionizes the DeFi space with its interest-free, over-collateralized stablecoin and DeFi loans.\n\n**Second Prize**\n\n**[Yield Nest](https://dorahacks.io/buidl/8497)**\n\nYield Nest is a protocol that implements a Fixed Rate Lending protocol through the emission of Zero Coupon bonds. It is deployed on the Injective testnet blockchain and makes use of its native modules, including the TokenFactory and the Exchange modules.\n\n**Third Prize**\n\n**[Chain Defender AI](https://dorahacks.io/buidl/7249)**\n\nChain Defender is building software and AI tools that are not only faster and cheaper, but unlock a new product category: continuously monitor your smart contract code for vulnerabilities.\n\n# Web3 (NFT, GameFi, SocialFi)\n\n**First Prize**\n\n**[Tokenized Interchain Accounts](https://dorahacks.io/buidl/8513)**\n\nTokenized Interchain Accounts are a new paradigm that tokenizes account ownership across multiple chains using IBC.\n\n**Second Prize**\n\n**[Ninja Blaze](https://dorahacks.io/buidl/8294)**\n\nNinja Blaze is a gaming platform with fully blockchain-based games that is revolutionizing the market and providing players with full transparency and integrity. Our games are built on the Injective blockchain, providing players with numerous benefits and facilities. Our platform provides the UX that we know from web2 delivering excitement and keeping every participant in the thrill.\n\n**Third Prize**\n\n**[Ninjakits](https://dorahacks.io/buidl/8485)**\n\nNinjaKits is an all-in-one DeFixNFT management tool for your assets and positions, providing you with non-custodial, trustless access to decentralized finance."}],"skills":null,"applied":false,"isCurrentHackerRegistered":false,"buidlsCount":109,"applicationsCount":114,"organization":{"id":592,"name":"Injective","logo":"https://cdn.dorahacks.io/static/files/18a87369fa2b16550f533fb4e449994c.png"},"description":"# Introduction\n\nWe are excited to introduce the Injective X Google Cloud Illuminate Hackathon co-hosted with DoraHacks. \n\nThe Injective x Google Cloud Illuminate Hackathon is the prime builder launchpad for Web3 finance applications with a $100,000 prize pool. Developers globally are invited to join to build innovative Web3 projects that can revolutionize the blockchain industry as a whole.\n\nIt is a unique opportunity for builders to continue showcasing their creativity and innovation within the Injective ecosystem. As we’ve witnessed applications across all sectors building on Injective, this hackathon has expanded its track options, allowing for even more projects to participate. In addition, Injective and Google Cloud will be providing technical guidance, mentorship and prizes to help accelerate startups into the next stages of their growth.\n\nYou are encouraged to participate regardless of your project stage. The Injective Illuminate Hackathon encourages all builders to create native projects on Injective which currently stands as the fastest layer 1 blockchain. Participants can create projects in areas such as DeFi, NFTs, SocialFi, gaming, tooling and more. A list of potential hackathon project ideas will also be published in the coming days.\n\n# Tracks and Prize Pool\n\n*A $10K prize pool will be distributed to the finalists according to community voting results. This prize pool is additional to the below track prizes. \n\n**DeFi, Infrastructure, and Tooling**\n\n- 1st: $30,000\n- 2nd: $20,000\n- 3rd: $10,000\n\n**Web3 (NFT, Gaming and SocialFi)**\n\n- 1st: $20,000\n- 2nd: $10,000\n- 3rd: $5,000\n\nCommunity Choice Award: $5,000\n\n## Knowledge Partner Bonus: [Decentralised.co](decentralised.co) Premium Subscription\n\n[Decentralised.co](decentralised.co), a leading Web3 analytics platform & newsletter, publishes three weekly articles for investors and developers who like to stay updated on Web3 without being glued to Twitter. Senior executives from 140+ enterprises trust us to keep them updated on what's going on in crypto. As a bonus, Decentralised.co offers a premium subscription plan to the hackathons winners for free. \n\n\n# Schedule\n\n- **Online Submission Deadline(Updated)**: December 21, 2023\n\n- **Project Evaluation**: 2 weeks after the submission deadline\n\n# Why should I participate?\n\nThe Injective Illuminate Hackathon isn’t just a competition; it’s a revolutionary experience to ignite your passion and bring your idea to life. It’s the place to mingle with the best minds, forge teams with fellow visionaries, and confront real-world dilemmas directly. Here, you will be able to sculpt the next-generation applications and pioneer the frontiers of blockchain. It’s your launchpad to the future of innovation and your platform to create the next big Web3 project.\n\n# What can I expect?\n\nThere will be a wide array of workshops, insightful panels, and dedicated office hours to guide you through your journey of building on Injective. In addition, there are developer resources across Injective and DoraHacks alongside direct mentorship from the Injective Labs team available.\n\nThe heart of this hackathon lies in the vast horizons of unlocking boundless potential for you and your project. You will be able to showcase your creation to esteemed judges, connect with industry experts, and expand your network in the space. This is your chance to be the spotlight in the blockchain universe.\n\n# How can I get started?\n\n- Register for the hackathon: [here](https://dorahacks.io/hackathon/illuminate/detail)\n- Familiar yourself with Injective: [Injective Docs](https://docs.injective.network/)\n- Join the official Injective Discord server: [here](https://discord.gg/injective).\n\n# Submission Requirements\n\n**1.** **All submissions need to deploy on the Injective Testnet or Mainnet and include the following**\n\n- Project Description\n - Name and summary of the project\n - Name of team member(s) and roles\n - An overview of what problem is being addressed and how the team resolves the identified problem through this creation\n - The design process behind the project\n - The value this project brings to the Injective Ecosystem\n- A demo video illustrating the project\n- Github repo link\n\n**2.** Single entry submission: Participants may submit a maximum of ONE project by the hackathon deadline.\n\n**3.** Submission Materials: All submission materials must be in English, including the demonstration video, text description, and testing instructions, as well as any other materials submitted.\n\n**4.** **Disclosure:**\n - Projects submitted to other hackathons or challenges need to be disclosed in the submission or README of the project.\n - Our judges will evaluate project submissions based on how the team implements their features and the uniqueness of the application.\n\n# Judging Criteria\n\nOnce all submissions are collected, Injective will distribute a list to the judges for evaluation. Teams and individuals who submitted projects will be evaluated on the following criteria:\n\n- Project Sustainability\n - Can this project continue to grow and evolve?\n- Design\n - Is the user experience and design of the project well thought out?\n- Security\n - Is the contract properly tested?\n - Have relevant test cases been covered with unit tests?\n- Originality and Innovation\n - How creative and unique is the project?\n- Mass Usability\n - Is the idea feasible?\n - How adaptable is it across other ecosystems and integrations?\n- Ecosystem Impact:\n - How impactful and useful is the submission for the larger Injective ecosystem?\n- Technical Complexity\n - Does the interaction with Injective demonstrate quality software development?\n - How well was the idea executed by the developer?\n - Does the project work as designed?\n - What is the level of skill or knowledge required to build the project?\n\n# About Injective\n\nInjective is a lightning fast interoperable layer one blockchain optimized for building the premier Web3 finance applications. Injective provides developers with powerful plug-and-play modules for creating unmatched dApps. Incubated by Binance, the Injective ecosystem is also supported by leading Web3 institutions such as Pantera, Jump Crypto, Mark Cuban, and more.\n\n# Useful Links\n\n- Injective Twitter: [@Injective_](https://twitter.com/Injective_)\n\n- Injective Website: [https://injective.com](https://injective.com/)\n\n- Injective Developer Doc: [https://docs.injective.network](https://docs.injective.network/)\n\n- Injective Discord: https://discord.gg/injective\n\n# Developer Resources\n\n- Dev Tools: https://docs.injective.network/develop/tools/\n\n- Dev Guides: https://docs.injective.network/develop/guides/\n\n- Injective Modules: https://docs.injective.network/develop/modules/\n\n- Cosmos SDK Modules: https://docs.injective.network/develop/modules/Core/auth/\n\n- CosmWasm Smart Contracts: https://docs.injective.network/develop/guides/cosmwasm-dapps/","onboardingCompleted":false,"registerFormUrl":null,"preRegisterTime":0,"publicContactHackerHandle":null,"hackersCount":353,"title":"Injective x Google Cloud Illuminate Hackathon","uname":"illuminate","imageUrl":"https://cdn.dorahacks.io/static/files/18b89d740156395708fbce44e1383fd0.jpg","originUrl":null,"startTime":1696204800,"endTime":1703221200,"timezone":"-480","city":null,"visible":true,"approvalStatus":6,"state":0,"voteUrl":null,"voteMechanism":null,"bonusPrice":100000,"bonusMechanism":null,"followersCount":0,"ecosystem":"Injective","applyGuide":null,"weight":33,"participationForm":"Virtual","field":"Blockchain,defi,web3,infrastructure,tooling,nft,gaming","email":"contact@injectivelabs.org","contacts":"Telegram,@vivianmaa","externalContacts":null,"telegram":null,"discord":null,"whatsapp":null,"wechat":null,"prizeFundingEscrowed":0,"token":"USD","prizeSafeForm":0,"prizeSafeNetwork":null,"prizeSafeOwner":null,"prizeSafeWallet":null,"prizeSafePublishDate":null,"hasOnboarding":false,"isPublicTrackJudging":false,"isEndedTrackJudging":false,"question":null,"countryId":null,"cityId":null,"venueName":null,"venueAddress":null,"category":0,"isEnableBounty":true,"isBountyRequired":false,"isEndedBountyJudging":false,"bountiesLimitForBuidl":10,"isPublicBountyJudging":false,"status":2},"status":4,"bounty":null,"track":null,"table":"0","trackObj":{"id":391,"name":"NFT","judgingCriteria":"","weight":0},"bountyObjs":[]}],"chain":[],"chainList":[],"appliedGrant":true,"acceptRewards":false,"owner":100537,"ownerInfo":{"nickname":"srdtrk","username":"srdtrk","avatar":"https://cdn.dorahacks.io/static/files/18dff9c7301a2d5d8781f9e45c8bcbda.png"},"visible":true,"deleted":false,"continuousSponsoring":false,"pageView":0,"sponsoredCount":0,"starCount":0,"sponsoredAmount":"37.80","sponsoredPersons":134,"followers":8,"voteCount":182,"projectMembers":[],"bnbRound":null,"doraGrantDaoTags":[],"techTrees":[0],"infrastructureTags":[4,53,62,68,70,79,91],"otherInfrastructures":[],"lastEditor":{"id":100537,"username":"srdtrk","date":1705763018000},"upvoted":false,"followed":false,"upvoters":{"count":19,"list":[{"id":8372,"hacker":{"username":"Samuel739","avatarUrl":"https://cdn.dorahacks.io/static/files/18eaf39ef24ecfc24efd9c640d3a7c05.jpg","nickName":"Sam Injective PGF","introduction":"Hongkonger interested in next gen, web3, decentralized (無大台) world and try to be \"Beyonders\" (超越者 - 不冒死抗爭，不費勁遊說，把精力用於建立新制度，讓時代改變或淘汰舊體制 -- 引自\"區塊鏈社會學\")."},"createdAt":"2024-04-01T01:45:59.039584+08:00","upvotes":"0.00","followed":false},{"id":6871,"hacker":{"username":"adair","avatarUrl":"https://cdn.dorahacks.io/static/files/18e006c41f94920eefa1e0e47bf98713.png","nickName":"adairrr","introduction":"I'm Adair!"},"createdAt":"2024-01-31T09:26:13.803240+08:00","upvotes":"0.00","followed":false},{"id":6507,"hacker":{"username":"U_752d7c263bbf72","avatarUrl":"https://cdn.dorahacks.io/static/files/18dffd109b5142cff3d3acd4dc4a7b3b.jpeg","nickName":"luminaryphi","introduction":""},"createdAt":"2024-01-12T06:38:42.358560+08:00","upvotes":"0.00","followed":false},{"id":6452,"hacker":{"username":"U_d7c99ea17a1d4a","avatarUrl":"https://cdn.dorahacks.io/static/files/18dfff0d4fea6aafadcdfe546679a319.jpeg","nickName":"FSoaresDev","introduction":""},"createdAt":"2024-01-04T21:20:53.649777+08:00","upvotes":"0.00","followed":false},{"id":6343,"hacker":{"username":"arifintahu","avatarUrl":"https://cdn.dorahacks.io/static/files/18dfff387a9ea09465f47834e79ab64f.jpeg","nickName":"arifintahu","introduction":"Backend Engineer"},"createdAt":"2023-12-30T22:38:48.959992+08:00","upvotes":"0.00","followed":false}]},"kycStatus":0,"ideas":[],"name":"Tokenized Interchain Accounts","techniqueField":"","source":"-","vision":"Accounts across all chains are abstracted, can be traded, and as a result, all dApps are multi-chain.","projectDescription":"Tokenized Interchain Accounts are a new paradigm that tokenizes account ownership across multiple chains using IBC.\n\n## Problem Overview\n\n### Infrastructure Layer\n\nThis journey began with an ambitious goal: to develop a CosmWasm implementation of ICS-27. I achieved this, creating a robust infrastructure that allows contracts on Injective to manage accounts on other chains, bypassing the need for deploying contracts on counterparty chain. This infrastructure overcomes the [limitations of the existing Go implementation](https://github.com/CosmWasm/wasmd/issues/947) of ICS-27 in CosmWasm environments that make it unusable, unlocking new potential in cross-chain DeFi, such as:\n\n- Managing accounts on chains lacking native smart contract support.\n- Deploy applications to other chains that might not even support smart contracts.\n- Pioneering in Interchain SocialFi and DAO initiatives.\n\n### Application Layer\n\nAt the application forefront, we introduce an NFT model that tokenizes multi-chain account ownership. This concept ushers in a new era for DeFi, allowing for accounts themselves to be a part of the DeFi ecosystem. Enabling use cases such as:\n\n- Trading accounts on NFT marketplaces.\n- Using accounts (and their delegations) as collateral in lending protocols.\n- Airdrop auctions where users can sell their accounts to the highest bidder (if the account is eligible for an airdrop).\n\n## Design Process\n\nThe project comprises three critical components:\n\n- [CosmWasm Interchain Account (ICA) Controller Contract](https://github.com/srdtrk/cw-ica-controller)\n- [NFT-ICA Contracts](https://github.com/srdtrk/cw-nft-ica)\n- [NFT-ICA UI](https://github.com/srdtrk/nft-ica-ui)\n\nThe project's development was a meticulous process, beginning pre-hackathon with a basic `cw-ica-controller` prototype. The hackathon's announcement spurred its evolution into a mature, production-ready infrastructure component, demanding rigorous testing and refinement over two months. This phase garnered attention from various blockchain entities.\nAn audit of `cw-ica-controller` would be the next step if this project is selected as a winner.\n\nThe final month was dedicated to showcasing the infrastructure's capabilities through the `cw-nft-ica` and `nft-ica-ui`, demonstrating the practical applications of our innovations via a novel paradigm of NFTs that tokenizes account ownership across multiple chains.\n\n## Demo Video\n

\n\n## Value Proposition for Injective Chain\n\n1. **Robust infrastructure**: Post-audit, our `cw-ica-controller` can be a cornerstone for Injective. Historically, ICA has only been accessible to Go developers building their own chains (such as Stride, and Quicksilver), other attempts to implement ICA in CosmWasm through chain specific bindings (such as in Neutron) have been unsuccessful due to users not wanting to be vendor locked. Our implementation opens the door to CosmWasm developers, enabling them to create and control accounts on other chains. This infrastructure can be used in any way builders utilize including the benefits listed here:\n\n - Cross-chain DAO functionalities.\n - Interchain lending mechanisms.\n - Multi-chain passive income streams.\n - Enhanced dApp interactions and event-based cross-chain actions.\n - User tailored cross-chain DeFi offerings.\n\n1. **NFT Innovation**: `cw-nft-ica` is a proof of concept for a new paradigm that tokenizes account ownership across multiple chains. This new paradigm should be very attractive to the NFT and DeFi communities and should bring attention to Injective and differentiate the NFT marketplaces on Injective. This project can foster:\n - A vibrant marketplace for trading blockchain accounts.\n - Airdrop auctions.\n - Utilization of accounts as collateral.\n - Cross-chain SocialFi and tailored DeFi solutions.","teamDescription":"- Serdar Turkmenafsar - [Github Profile](https://github.com/srdtrk)\n - Role: Product Engineer @ IBC Protocol, Interchain Foundation.\n - Contributions: Crafted all smart contracts and developed the user interface for this project.","githubPage":"https://github.com/srdtrk/cw-nft-ica","githubVerify":0,"demoLink":"https://srdtrk.github.io/nft-ica-ui","demoVideo":"https://www.loom.com/share/4e85206379354f5182d21d8e384aba74?sid=6b0143d2-c45c-4e8f-93a9-ff4ff08ca7f8","ownerTitle":null,"ownerIntroduction":null,"twitterVerified":false,"weibo":null,"nft":null,"scOwner":"","editTime":1705763018,"upvotes":"0.00","isRecruitingEnabled":false,"recruitingInfo":"","recruitingLink":null,"twitter":"srdtrk","facebook":null,"instagram":null,"socialTelegram":null,"socialDiscord":null,"socialLinks":[],"showedFunding":false,"createdAt":"2023-12-20T16:07:39.107733+08:00","updatedAt":"2024-01-20T23:03:38.399710+08:00","milestoneEditor":100537,"path":"/buidl/8513","techField":"","techFieldAry":[],"techTree":[0],"tags":[4,53,62,68,70,79,91],"otherTags":[],"origin":"-","intro":"Tokenized Interchain Accounts are a new paradigm that tokenizes account ownership across multiple chains using IBC.\n\n## Problem Overview\n\n### Infrastructure Layer\n\nThis journey began with an ambitious goal: to develop a CosmWasm implementation of ICS-27. I achieved this, creating a robust infrastructure that allows contracts on Injective to manage accounts on other chains, bypassing the need for deploying contracts on counterparty chain. This infrastructure overcomes the [limitations of the existing Go implementation](https://github.com/CosmWasm/wasmd/issues/947) of ICS-27 in CosmWasm environments that make it unusable, unlocking new potential in cross-chain DeFi, such as:\n\n- Managing accounts on chains lacking native smart contract support.\n- Deploy applications to other chains that might not even support smart contracts.\n- Pioneering in Interchain SocialFi and DAO initiatives.\n\n### Application Layer\n\nAt the application forefront, we introduce an NFT model that tokenizes multi-chain account ownership. This concept ushers in a new era for DeFi, allowing for accounts themselves to be a part of the DeFi ecosystem. Enabling use cases such as:\n\n- Trading accounts on NFT marketplaces.\n- Using accounts (and their delegations) as collateral in lending protocols.\n- Airdrop auctions where users can sell their accounts to the highest bidder (if the account is eligible for an airdrop).\n\n## Design Process\n\nThe project comprises three critical components:\n\n- [CosmWasm Interchain Account (ICA) Controller Contract](https://github.com/srdtrk/cw-ica-controller)\n- [NFT-ICA Contracts](https://github.com/srdtrk/cw-nft-ica)\n- [NFT-ICA UI](https://github.com/srdtrk/nft-ica-ui)\n\nThe project's development was a meticulous process, beginning pre-hackathon with a basic `cw-ica-controller` prototype. The hackathon's announcement spurred its evolution into a mature, production-ready infrastructure component, demanding rigorous testing and refinement over two months. This phase garnered attention from various blockchain entities.\nAn audit of `cw-ica-controller` would be the next step if this project is selected as a winner.\n\nThe final month was dedicated to showcasing the infrastructure's capabilities through the `cw-nft-ica` and `nft-ica-ui`, demonstrating the practical applications of our innovations via a novel paradigm of NFTs that tokenizes account ownership across multiple chains.\n\n## Demo Video\n