project screenshot 1
project screenshot 2
project screenshot 3

HumanChain

A way to check if content on social networks is ai using blockchain protocol

HumanChain

Created At

ETHGlobal Cannes

Project Description

Project Description:

Humain Chainé is a revolutionary, unnecessary, but somehow essential blockchain-based NFT project that aims to solve a problem nobody asked to fix: proving that a piece of content was created by a human, not a soulless AI. In a world full of deepfakes, ChatGPT essays, and robot-generated memes, Humain Chainé delivers humanity back to the timeline — one ridiculous NFT at a time.

Every NFT is a “Certificate of Human Content” (CHC), which attests that a social media post, image, video, or even a TikTok thirst trap was created using authentic, squishy brain matter.


Key Features:

  • NFTs that prove content is not made by AI.
  • Tags for each NFT: "human" or "ai".
  • Hash-based content fingerprinting using SHA256.
  • Link NFTs to tweets, Instagram posts, or other platforms.
  • Users can "verify their humanity" by minting a certificate on-chain.
  • Zero AI detection; entirely based on trust and user input.
  • Optional DAO governance to vote on controversial content.

Technical Architecture:

  1. Smart Contract (Solidity):

    • Built on ERC-721 standard.
    • Each NFT includes:
      • contentHash: SHA256 hash of the content
      • platform: Name of the social media platform
      • contentLink: URL to the original content
      • tag: "human" or "ai"
      • timestamp: block.timestamp at minting
    • Optional verifier role for human-certified validation
    • Emits ContentCertified event: ContentCertified(address user, string tag, string platform)
  2. Frontend (React + Ethers.js):

    • Connect wallet via MetaMask or WalletConnect.
    • Input content link or content text.
    • Generate hash on client side.
    • Select "Human" or "AI".
    • Click "Mint Now" to send transaction.
    • Display newly minted NFT.
    • Verification tool to check NFT status from a pasted link.
  3. Metadata Storage:

    • Metadata stored on IPFS or Arweave.
    • Example metadata format: { "name": "Proof of Human Content #42", "description": "Certified by Humain Chainé", "image": "ipfs://QmSomeUglyLogo.png", "attributes": [ {"trait_type": "Tag", "value": "human"}, {"trait_type": "Platform", "value": "Twitter"}, {"trait_type": "Verification", "value": "Self-certified"} ] }
  4. Verifier System (optional feature):

    • Users with 3 or more NFTs can apply to be a verifier.
    • Verifiers can confirm content as "human" or "ai" on others' behalf.
    • DAO governance model to review or revoke verifier rights.
    • Verifiers accumulate reputation points (purely symbolic).

Disclaimer:

  • This system does not detect AI.
  • It only registers what the user claims.

How it's Made

The contract is an ERC-721 implementation using OpenZeppelin’s ERC721URIStorage, which allows token metadata to be stored off-chain and linked via a URI. Each minted token represents a certification of a piece of content. The content itself is not stored on-chain; instead, a SHA256 hash of the content is generated off-chain and passed as a string to the contract. Along with the hash, the user submits the platform name (like "Twitter"), a link to the content, and a tag indicating if the content was made by a "human" or by "ai". These values are stored in a mapping that links a tokenId to a struct containing those four strings. The mint function increments a counter, mints a token to the sender, sets the token URI (usually pointing to a JSON file on IPFS with name, description, image, and attributes), stores the certificate struct in the mapping, and emits an event for off-chain indexing. The metadata structure follows the standard NFT format and includes information such as tag, platform, and verification type. The frontend computes the hash using ethers.js, asks the user to label the content, and then sends the transaction to the contract using Metamask or another wallet. No actual AI detection is performed; the system relies on the user to label honestly. The contract provides read-only functions to access the metadata and struct data by tokenId. Deployment is handled via Hardhat and can target testnets or mainnet.

background image mobile

Join the mailing list

Get the latest news and updates