OWNly-Hackathon-Prpoject/.github

OWNly Project - hack the mountain hackathon

The OWNly project is an own and share NFT Copyright Platform. You can literally put a price on almost anything-U in the digital space.

Project Repos:

UI/UX

Smart Contract

Frontend

Table of content

• OWNly Project - hack the mountain
  • Table of content
  • Ideation
  • UI
  • Frontend
  • Contracts
    • Overview
    • Tests
    • Deployed Contract
    • Deployed NFTs

Ideation

• What are you doing with your digital and social footprint? How much has blockchain benefitted you as you go along on your normal online social engagements? How about monetizing your digital footprints and other of your intellectual properties in the digital space?
• The OWNly project is an own and share NFT Copyright Platform. You can literally put a price on almost anything-U in the digital space. We categorise the digital space into two: the Social-U and the Non-Social-U. The Social-U comprise of post from all social media platforms like Twitter, Facebook, Instagram, TikTok etc. The Non-Social-U comprise of books, biography, video tutorials, whistleblower's account, blog, news, declassified and classified secrets etc. These digital items can be minted, shared and sold or even rented since they are intellectual digital footprints.
• The MVP for this HTM hackathon is the Social-U of Twitter NFT. Tweet owners can deploy their tweets and allow the general public, followers alike to mint their tweets. The usage of these NFTs are very important. We have two variants:
  • The Transferrable & the Non-transferrable. The transferrable are like the normal NFTs while the non-transferrable are specially designed for fundraising purposes. The NFT only serves as a receipt for participation in a fundraising that the deployer might have organized.

UI

• The Figma design can be found here.
• The landing page below projects the entire cycle of the product line up while we focus on the Twitter version.

• The Launch App button loads the tweetNFT page. Here users can input a tweet url and proceed to either deploy or mint. (Only deployed tweets can be minted and only tweet owners can deploy). Deploy simply means alerting the blockchain and giving it the permission to mint your tweets.

• Other Products highlighting.

Frontend

• The frontend implementation of the UI has not been perfected. The work done shows minimal interaction with backend-smart contracts.

• LandingPage

• App page

• App page test

Contracts

Overview

Contract allows to mint ERC721 NFT with metadata from NFT.storage API. Content creator can easily deploy their valuable tweets with customizable fees and supply. Followers in order to support the creator can mint the NFT paying some fee (established by content creator). Users can use their personal balance in vault for paying for transactions without any signing of transaction. This abstraction allows for users to only send in some bulk amount to vault once in a while to prevent having to always sign transaction using a provider.

Tests

The integration test imitates well, how the general flow looks like:

1. Contract owner can set some deploy fee
2. Tweet with certain ID is loaded to the website - this case ID 1844 is assumed
3. Content creator deploys his tweet with some certain parameters - pays minor fee from his vault or inludes fee in transaction.
4. Follower mints deployed tweet with customizable image - pays fee established by content creator from his vault or inludes fee in transaction.
5. Some basic metadata about tweet and customized image is stored in IPFS via NFT.storage API
6. URI to this metadata is stored in the blockchain

Deployed Contract

The contract is fully verified and visible on Polygonscan. Once tests are performed here, you can see some results in polygonscan:

Deployed NFTs

The followers should see minted NFTs on OpenSea thanks to compatible URI and metadata: