How I Built a Decentralized NFT Gift Protocol (and why digital gifting is broken)

Jayant kurekar — Thu, 04 Dec 2025 17:36:16 +0000

*The Problem with Digital Gifts *

It started with a frustrating realization: Digital gifting is broken.

I recently wanted to send a crypto gift to a friend. Sending a sterile transaction of 50 USDC felt like a bank transfer, not a gift. I looked at traditional gift cards, and they felt even worse—centralized, prone to expiry, and locking value into one specific store.

So, I decided to build a solution. I call it the NFT Gift Protocol.

Here is the story of how I built it, the tech stack I used, and how I used Kiro to help me document and structure the entire journey.

The Idea 💡

I wanted to combine the emotional value of art with the financial value of crypto.

The concept is simple:

Generate Art: Use AI to create a unique image based on a prompt (e.g., "Cyberpunk Birthday Cake").

Embed Value: "Lock" ERC-20 tokens (like USDC) inside that image.

The Result: An NFT that acts as "wrapping paper." The recipient can keep it as a collectible or "tear it open" (burn/liquidate) to get the money inside.

*The Tech Stack *

To make this trustless and decentralized, I needed a robust stack:

Blockchain: Polygon Amoy (Testnet). Low fees, EVM compatible.

Smart Contracts: Solidity & Hardhat.

Frontend: React 19, TypeScript, & Vite.

Storage: IPFS (via web3.storage). We can't store images on-chain!

AI: Hugging Face Inference API (Stable Diffusion).

*The Architecture: The "Vault" Pattern *

The technical crux of the project was the Vault Pattern. I didn't want a centralized database holding the gift card values.

Instead, the NFT Contract itself acts as a bank.

When I mint an NFT, I send tokens into the contract.

The contract maps that specific tokenId to the amount sent.

Only the ownerOf(tokenId) can access the funds.

This means even if I disappear, the protocol keeps working.

The Code: Navigating ERC-721 and ERC-20

The hardest part was managing the interaction between the NFT standard (ERC-721) and the Token standard (ERC-20).

I had to use the approve workflow. The user must approve the contract to spend their tokens before the minting transaction happens. I also implemented SafeERC20 from OpenZeppelin because—pro tip—not all tokens return true on success, and you don't want silent failures when money is involved.

*How Kiro Changed My Workflow
*
This is where the development process got interesting. Usually, I build the code and dread writing the documentation or the "About" page.

I used Kiro to analyze my entire repository. I asked it to help me visualize my "Project Journey."

Instead of me staring at a blank screen, Kiro scanned my GiftCardNFT.sol and my frontend structure and generated a comprehensive narrative of how I built the project. It identified that I used the Vault Pattern and highlighted the security measures I took (like ReentrancyGuard) without me having to list them out manually.

It essentially acted as my AI Technical Writer, turning my raw code into a story that I could share with the world.

The Final Product 🚀

The app is now live on the Amoy testnet. Users can:

Connect their wallet (RainbowKit).

Type a prompt ("Golden Dragon holding Bitcoin").

Mint the NFT and send it to a friend via email (using EmailJS).

What's Next?

I plan to move this to Mainnet and explore Zero-Knowledge proofs to hide the gift amount until it's opened.

If you're building in Web3, don't underestimate the power of good documentation. It turns code into a product. And if you hate writing docs, get an AI tool like Kiro to help you tell your story.

#kiro #web3 #react #solidity

DEV Community: Jayant kurekar

How I Built a Decentralized NFT Gift Protocol (and why digital gifting is broken)