The problem NEAW - A NFTs Marketplace for repos solves

Monetizing GitHub Repositories with Ethereum Transactions Using Coinbase Wallet SDK

Our solution bridges the gap between open-source contributions and blockchain-powered monetization by enabling seamless Ethereum transactions on EVM-compatible chains directly through GitHub repositories. Leveraging the Coinbase Wallet SDK, we introduce an ownership model where contributors and repository owners can receive rewards, donations, or licensing payments in crypto, fostering a more sustainable and transparent ecosystem for open-source development.

users can purchase repos in the form of nfts which earlier was not possible wholely.
Also we are using the AGENTKIT for the verifying that the repos do not include any licensing assets in it.

User Interaction and Data Flow

1. Connect Wallet & GitHub
   The user visits our platform and is prompted to connect their Coinbase Wallet (or any EVM-compatible wallet).
   Simultaneously, they authenticate with their GitHub account through OAuth, verifying repository ownership or contribution rights.
2. Mint NFTs from GitHub Repos
   Once authenticated, users can select their GitHub repositories.
   They can mint NFTs representing ownership, contributions, or licenses tied to these repositories.
   NFTs are minted on Ethereum or any EVM-compatible chain, secured by smart contracts.
3. Buy & Sell Repository NFTs
   Users can list their NFTs for sale, setting prices in ETH (or supported tokens).
   Other users can purchase NFTs directly through seamless crypto transactions powered by the Coinbase Wallet SDK.
4. Ownership & Monetization
   NFT ownership verifies rights and access to repository perks, such as licensing or premium content.
   The entire process is decentralized and transparent, ensuring fair compensation and verifiable ownership on-chain.

The project architecture and development process

This platform enables monetization of GitHub repositories by minting NFTs that represent the ownership or licensing rights of codebases. It integrates GitHub OAuth, IPFS for decentralized storage, Supabase for data management, and Ethereum/EVM chains via smart contracts. Payments and ownership transfers are powered by ETH transactions using the Coinbase Wallet SDK.

ALso validate the overview of zip file from AGENTKIT

1. User Authentication & Wallet Connection
   Users visit the DApp.
   Connect Coinbase Wallet (or any EVM-compatible wallet).
   Authenticate with GitHub OAuth 2.0, granting access to their repositories.
2. Fetch and Package Repository Code
   After authentication, users select one of their GitHub repositories.
   The backend fetches the repository code, compresses it into a ZIP file.
3. Upload to IPFS
   The compressed repository (ZIP) is uploaded to IPFS using services like Pinata or Web3.Storage.
   The IPFS CID (Content Identifier) is generated and returned to the backend.
4. Metadata Creation & Supabase Integration
   Metadata for the NFT is created, including:
   Repo name, description.
   Contributor/Owner wallet address.
   IPFS CID link to the codebase.
   Metadata and NFT details are stored in Supabase for indexing and easy querying in the marketplace.
5. Mint NFT & Smart Contract Interaction
   The minting transaction is initiated on Ethereum (or another EVM chain).
   The smart contract mints an NFT with the metadata, including the IPFS link.
   Ownership of the NFT is recorded on-chain, tied to the wallet address.
6. Marketplace Listing
   After minting, the NFT is automatically listed on the marketplace UI.
   Listings are pulled from Supabase, which tracks active NFTs and sales data.
   Users can set prices, accept bids, or transfer NFTs.
7. Purchase & Ownership Transfer
   A buyer selects an NFT and initiates a purchase with ETH via the Coinbase Wallet SDK.
   The smart contract handles:
   Transfer of NFT ownership to the buyer.
   Transfer of ETH payment to the seller’s wallet.

Key differentiators and uniqueness of the project

The developer's are getting Money. Basically for their work and no one can stole their efforts.
And also Eliminate third party interference.
ALso do not hurt the sentiment of opensource community

This platform pioneers the concept of tokenizing GitHub repositories into NFTs, turning codebases into digital assets with verifiable ownership and licensing rights on EVM-compatible blockchains.

Unlike existing NFT projects that focus on art or collectibles, we:

Capture the value of open-source contributions by allowing developers to mint, sell, and license their entire repositories or specific code modules.
Provide a decentralized proof of ownership tied to GitHub repositories through blockchain-backed NFTs.
Empower creators to monetize their intellectual property without relying on traditional licensing agreements, middlemen, or closed platforms.

Trade-offs and shortcuts while building

Yes, We had to fetch whole zip file of code base for which we figured out the classical github project acess and all apart from it figured out the ownership transfer and made api for it.

Additional Features

All everything was build during the hackathon.
But in future in place of using github as the api-point We would create our once like owm decentralised storage through CLI commands