MindMint
Claim the spark. License the fire.
MindMint turns ideas, prompts, workflows, characters, and creative outputs born in ChatGPT into verifiable, license-ready digital assets.
Inspiration
I’m a creative, so protecting intellectual property stays on my mind. Great ideas often arrive before the money, legal support, or patience required to navigate copyright filings, trademark applications, licensing contracts, and administrative paperwork.
AI has also become a powerful thought partner. People use ChatGPT to develop prompts, workflows, stories, visual concepts, products, and entire businesses. Valuable creative work now emerges inside conversations, but it can disappear into chat history without a clear record of origin, authorship, or licensing rights.
MindMint began with one question:
What if protecting an AI-assisted creation were as simple as pasting the conversation that produced it?
What it does
Creators paste a ChatGPT conversation, prompt, workflow, method, character, design, or creative output into MindMint.
GPT-5.6 analyzes the material and extracts the concrete creative expression:
- The creator’s original direction
- Human constraints, edits, and decisions
- Named methods and workflows
- Prompt sequences and reusable structures
- Examples and structured-output schemas
- Model-assisted language or content
- Potential authorship and licensing risks
MindMint then generates a DATA Foundation rights blueprint containing:
- IP Asset metadata for ownership and attribution
- Programmable IP License terms for commercial use and derivatives
- License Token economics for fees and creator revenue
- Confidential Data Rails for protecting private prompts
- Origin evidence using hashes, timestamps, signatures, and AI disclosures
- An ordered transaction plan for publishing the asset on-chain
Creator economics
Each license can combine an upfront minting fee with a percentage of downstream commercial revenue.
For a creator with (n) license sales, the estimated earnings are:
$$ E = nF + r\sum_{i=1}^{m}R_i $$
Where:
- (E) = total creator earnings
- (F) = License Token minting fee
- (n) = number of licenses sold
- (r) = creator revenue-share rate
- (R_i) = revenue from each licensed derivative
For example, if a creator sells 20 licenses for $12 each and receives 7% of $10,000 in derivative revenue:
$$ E = (20 \times 12) + (0.07 \times 10{,}000) = 940 $$
The creator earns $940 through licensing and downstream participation.
How I built it
I built MindMint using:
- Codex for research, architecture, implementation, debugging, testing, and documentation
- GPT-5.6 Sol for authorship analysis and rights-blueprint generation
- OpenAI Responses API with strict Structured Outputs
- React and TypeScript for the creator interface
- Vite for frontend development and production builds
- Express for the server-side AI integration
- DATA Foundation for IP Assets, PIL terms, License Tokens, and confidential access
Codex fetched the DATA Foundation’s complete documentation index before studying the relevant protocol pages. It helped refine the idea, design the interface, implement the full stack, build tests, and create the submission materials.
GPT-5.6 returns a predictable JSON contract containing the extracted asset, proposed license, protected material, risk analysis, creator decisions, and transaction plan.
{
"asset": "Signal Ladder",
"license": "Commercial Remix",
"mintingFee": 12,
"creatorRevenueShare": 7,
"aiTrainingAllowed": false,
"sourcePromptProtected": true
}
Key design decision
MindMint does not promise ownership over a vague idea.
A broad concept can be difficult to protect. MindMint focuses on its concrete expression:
- The named framework
- Original arrangement
- Prompt logic
- Sequence of steps
- Creative constraints
- Worked examples
- Output schema
- Human edits and selections
This creates a stronger, more honest record of what the creator actually contributed.
Challenges
Separating human and AI contributions
AI-assisted work can blend human direction with model-generated language. MindMint identifies the creator’s structure, constraints, edits, and selections while separately recording model assistance.
Translating licensing into plain language
Creators should not need to speak like attorneys. MindMint turns licensing into direct questions:
- Can buyers use this commercially?
- Can they create derivatives?
- Can they train AI models with it?
- Is attribution required?
- What does the license cost?
- What percentage returns to the creator?
Proving an artifact without exposing it
Publishing an entire prompt can destroy its commercial value. Hiding everything makes verification difficult.
MindMint separates the public fingerprint from the private source. Public metadata proves the artifact’s identity and origin. License-gated encryption protects the complete implementation.
Making the project easy to judge
Wallet funding and blockchain configuration create friction. MindMint includes a deterministic judge mode that demonstrates the complete workflow without API keys, testnet tokens, or a connected wallet.
What I learned
Provenance, ownership, access, and licensing solve different problems.
| Layer | Purpose |
|---|---|
| Origin evidence | Shows when and where the artifact was created |
| IP Asset | Represents ownership and creative metadata |
| PIL terms | Define permissions and economic conditions |
| License Token | Grants verifiable usage rights |
| CDR vault | Protects private source material |
The strongest system gives each responsibility its own layer while presenting creators with one simple experience.
What’s next
- [ ] Direct ChatGPT conversation import
- [ ] Wallet connection and creator signatures
- [ ] Live Aeneid IP Asset registration
- [ ] License Token purchasing
- [ ] Automatic fee and royalty distribution
- [ ] License-gated prompt decryption
- [ ] Version tracking for evolving prompts
- [ ] Parent-child relationships for remixes
- [ ] A marketplace for licensed AI-native IP
Closing vision
Creators deserve access to IP infrastructure before they can afford attorneys, administrators, or licensing teams.
MindMint gives them a simpler path:
Create the work. Document the spark. Define the rights. Share in the value.
Built With
- aeneid
- api
- blockchain
- codex
- css3
- data
- erc-721
- express.js
- foundationdb
- gpt-5.6
- html5
- json
- license
- node.js
- programmable
- protocol
- react
- responses
- schema
- sdk
- story
- testnet
- typescript
- web3
Log in or sign up for Devpost to join the conversation.