Build and publish a website called:

IMDerivatives

PURPOSE

IMDerivatives is an independent directory of projects, tokens, NFTs,

strategies, apps and experiments built around or supporting the

Identity MD / IMD ecosystem.

The core idea:

BUILT AROUND IMD ≠ BUILT BY IMD.

This is NOT an official Identity MD website.

Do not imply that any project is official, endorsed, partnered with,

or approved by Identity MD unless a primary authoritative IMD source

explicitly proves that relationship.

Do not call a project fraudulent or a scam without strong verifiable

evidence.

Automated security warnings are risk signals, not proof of fraud.

DISCLAIMER

Display prominently:

"IMDerivatives is an independent community resource and is not

affiliated with Identity MD. Listed projects may be built by third

parties. Inclusion does not imply endorsement by Identity MD.

Always verify contracts and links independently."

Also display:

"Nothing on this site is financial advice."

INITIAL PROJECTS

Research and include these four projects.

1. SWARM PEPE

https://opensea.io/collection/swarm-pepe

Known contract to verify: 0x999ce0ce8c5f7661e0c74a568ffe27ceb9177bdb

Determine:

• what it does
• blockchain
• verified contract
• creator/provenance where possible
• relationship to IMD
• evidence of official IMD affiliation, if any
• risk signals
• evidence sources

Do not infer official affiliation merely because the project references

Identity MD holders or the IMD swarm.

2. IMD STRATEGY / TOKENWORKS

https://www.tokenstrategy.com/strategies/0x80271ce20184e38f4afe90d4ca134304d197aca2

Contract: 0x80271ce20184e38f4afe90d4ca134304d197aca2

Research TokenStrategy / TokenWorks documentation.

Explain what the strategy actually does and how it relates to

Identity MD NFTs.

Clearly distinguish TokenWorks from Identity MD.

Do not call it an official IMD product unless primary IMD evidence

explicitly establishes this.

3. PROJECT HIVE

https://projecthive.fun/dashboard.html

Research carefully.

Verify where possible:

• site behavior
• contracts
• chain
• creator/provenance
• relationship to IMD
• security warnings
• official IMD references

Automated warnings must be described as automated warnings, not proof

of fraud.

If important evidence cannot be verified, classify the project

UNVERIFIED and explain why.

Never invent contracts, affiliations, or security findings.

4. IMD STRATEGY / NOSH

https://www.usenosh.app/coins/0xE749C8Bf545DA0db1aA6664c63c072c96f25acA1

Token: 0xE749C8Bf545DA0db1aA6664c63c072c96f25acA1

Research Nosh documentation.

Explain:

• what the token/strategy does
• how it interacts with Identity MD / its NFTs
• chain
• relevant contracts
• creator/provenance where verifiable
• audit status
• risks and trust assumptions
• evidence of official IMD endorsement, if any

CLASSIFICATION SYSTEM

Give every project one primary status:

OFFICIAL IMD

Only when a primary Identity MD source explicitly establishes that

the project is official.

INDEPENDENT — VERIFIED

Project and relevant contracts are independently verifiable, but it

is not established as an official Identity MD product.

INDEPENDENT — SUPPORTS IMD

A third-party project whose mechanism supports, purchases, burns,

uses, funds, or otherwise interacts with IMD / Identity MD.

UNVERIFIED

Insufficient evidence exists to verify important claims.

FLAGGED

Specific credible security concerns have been identified.

Risk signals can additionally include:

UNAUDITED

NEW CONTRACT

NEW DOMAIN

UPGRADEABLE

ADMIN CONTROL

EXTERNAL KEEPER

AUTOMATED SECURITY WARNING

UNVERIFIED CONTRACT

WALLET CONNECTION

UNKNOWN TEAM

A risk signal must NEVER automatically mean "fraud".

ABSENCE FROM OFFICIAL IMD SOURCES ≠ FRAUD.

It means official affiliation has not been established.

EVIDENCE

Every important factual claim should have a source.

Prefer:

1. on-chain contracts and transactions
2. official Identity MD sources
3. project documentation
4. blockchain explorers
5. reputable independent sources
6. automated scanners/social posts as supporting context only

Clearly distinguish:

VERIFIED FACT

PROJECT CLAIM

THIRD-PARTY CLAIM

AUTOMATED WARNING

UNKNOWN

If sources disagree, show the disagreement.

Never fabricate missing evidence.

DESIGN

Create a polished dark cyber / terminal / subtle pixel-art aesthetic.

It should feel related to the autonomous-agent / on-chain world of

IMD without pretending to be an official IMD interface.

Responsive desktop + mobile.

Homepage hero:

IMDerivatives

"Map the ecosystem. Verify the relationship."

Secondary line:

"Built around IMD ≠ built by IMD."

Show ecosystem counters such as:

Projects

Official

Independent

Unverified

Flagged

Only show counters calculated from actual project data.

FILTERS

All

NFT

Token

Strategy

App

Official

Independent

Unverified

Flagged

PROJECT CARDS

Each card should show:

name

category

short description

affiliation status

risk badges

chain

contract/address when applicable

last reviewed date

external project link

detail/evidence button

PROJECT DETAIL

Each project page or expandable detail view should contain:

Overview

What does it do?

Why is this related to IMD?

Official or independent?

Contracts

How it works

Security / trust assumptions

Risk signals

Official endorsement evidence

Evidence & sources

Last reviewed

For addresses include copy buttons and blockchain explorer links.

External links should clearly indicate that the user is leaving

IMDerivatives.

For UNVERIFIED or FLAGGED projects, display a warning before the

external link.

SAFETY

The website is informational and read-only.

NO wallet connection.

NO trading.

NO swaps.

NO token approvals.

NO minting.

NO investment recommendations.

NO price predictions.

Do not create fake live metrics.

DATA

Keep all listings in a structured file such as:

projects.json

or

projects.ts

Each project should support:

id

name

category

description

relationshipToIMD

affiliationStatus

affiliationEvidence

chain

contracts

links

riskFlags

securityNotes

sources

lastReviewed

Make it easy to add future IMD ecosystem projects.

RESEARCH

Create RESEARCH.md documenting what was actually verified for every

listing and the sources used.

Do not silently convert assumptions into facts.

DELIVERABLE

Build and publish the complete static website.

Site name:

IMDerivatives

Return:

• public website URL
• repository/commit
• project data file
• RESEARCH.md
• build status
• publication evidence

The website succeeds if a visitor can quickly answer:

1. "What does this project have to do with IMD?"

2. "Is this actually an official Identity MD project, or an independent project built around it?"

The site should be a neutral ecosystem map, not a promotional page.