Do not rebuild it from scratch and do not remove the current animated card, token search, PNG/video download, profile links, QR code, or X sharing features.

1. Redesign the “Open profile” view

The current profile is too dark, text-heavy, and difficult to scan. Turn it into a clean dashboard made of clearly separated cards.

Use a slightly lighter charcoal background, brighter panels, clear borders, generous spacing, larger headings, and high-contrast text. Keep the current IdentityMD cyber style and each NFT’s dominant colors.

Use a two-column card grid on desktop and one column on mobile.

Display these sections as separate cards:

• Identity
• Live status
• Performance
• Rankings
• Rewards and launch allocations
• Work history
• Reviews
• Onchain verification links

Important numbers such as accepted work, acceptance rate, rank, rewards, and last activity should be visually prominent.

Do not display large paragraphs for unavailable data. Use a small muted “Unavailable” badge with a short explanation or tooltip instead.

Keep the animated SIMCARD visible at the top of the profile.

2. Fix the “Held for” calculation

The existing “Held for” value is incorrect. Calculate it from the Ethereum ERC-721 Transfer event in which the current owner most recently received this specific IdentityMD NFT.

Contract: 0x0000ec93127baa929e58e97dd0095a2bfb38ec1d

Do not use the agent pairing date, latest activity, API snapshot date, or unrelated contract activity.

Show both the readable duration and exact acquisition date, for example:

Held for: 34 days

Acquired: Aug 26, 2026

If the correct acquisition transaction cannot be verified, show “Unavailable” instead of an estimated or incorrect duration.

3. Improve live IdentityMD data handling

Retrieve the freshest available public data for the entered token ID from the official IdentityMD endpoints, including:

• /seats/:tokenId
• /seats/:tokenId/standing
• /seats/records
• /wallets/:ownerAddress/earnings
• the public Explorer agent page
• Ethereum onchain ownership, metadata, and Transfer logs

Show:

• online/offline state
• runtime
• queue
• last activity
• attempts
• accepted
• rejected
• failed
• pending
• acceptance rate
• accepted-work rank
• attempts rank
• acceptance-rate rank
• percentile
• payouts
• launch allocations
• recent work
• reviews

This remains a static IPFS frontend. If the official IdentityMD API blocks browser requests because of CORS, do not use an untrusted public CORS proxy and do not fabricate live values. Use verified onchain data plus the latest bundled snapshot, label snapshot values clearly with their timestamp, and keep a Refresh button for retrying the official API.

Structure the data-access code so a trusted first-party API proxy can be added later through one configurable base URL.

4. Improve usability

• Preserve token-ID search and direct hash routes such as #/agent/222.
• Make the profile readable without opening technical JSON.
• Place technical API and explorer links inside a compact collapsible “Verification” card.
• Add loading, invalid-token, unavailable-data, and network-error states.
• Maintain full mobile responsiveness and keyboard accessibility.
• Do not require a wallet connection.
• Do not expose private keys, API keys, or secrets.
• Ensure PNG and video exports still work after the redesign.
• Ensure the QR code and share link open the correct token profile.
• Keep the site name “SIMCARD” and the tagline “One card. Every agent. Verified onchain.”