Technical record of an ERC-1155 NFT where the pre-mint entered name differed from the OpenSea display. IPFS JSON, UTF-8 encoding, baseURI, and contract verification documented.

Regarding the Fact That NFT Data Entered Before Mint Was Displayed as
“完全に無印で行く (To Proceed Completely Unbranded)” on OpenSea After Mint

Verification Date: February 17, 2026
(Confirmed via Etherscan and OpenSea at the time of review)

This is solely a record of facts.
No interpretation, evaluation, or speculation is included.

1. Conclusion

The name discrepancy on OpenSea typically results from metadata caching and ERC-1155 URI formatting issues (including token ID substitution and zero-padding).

Understanding how OpenSea retrieves and caches JSON metadata is essential when diagnosing unexpected name displays.

2. Possible Causes

  • OpenSea metadata cache – Delayed refresh or cached JSON.
  • {id} zero-padding – ERC-1155 requires 64-character hexadecimal formatting.
  • IPFS gateway redirects – Inconsistent retrieval behavior across gateways.
  • Collection vs item name confusion – Display layer differences, including token ID fallback behavior.

3. Technical Structure

This diagram separates on-chain record logic from off-chain metadata storage,
clarifying how display discrepancies can occur without altering blockchain data.

The following diagram illustrates how ERC-1155 metadata flows
from smart contract to marketplace display.

ERC-1155 metadata architecture showing contract, token URI, IPFS JSON, and OpenSea rendering layer

4. Metadata Flow Overview

ERC-1155 Metadata Resolution Flow

Contract
↓
URI (with {id})
↓
IPFS JSON
↓
OpenSea Metadata Cache
↓
Display Layer

5. Data Entered Before Mint

  • Collection Name: HANDY DIGITAL TALISMAN
  • Standard: ERC-1155
  • Total Supply Setting: 108
  • Creation Environment: OpenSea Studio (SeaDrop)
  • Individual Item Name: “HANDY DIGITAL TALISMAN” was entered

The string “完全に無印で行く (To Proceed Completely Unbranded)” did not appear in any of the pre-mint input data, drafts, file names, or description texts.

6. Post-Mint Display Confirmation

On OpenSea, it was confirmed that Token #1 was displayed with the item name:

“完全に無印で行く”

7. Contract Verification (Etherscan)

Contract Address:
0x913da03999a6255fdb9e33b7c5300e8e6fdf2f20

  • name() → HANDY DIGITAL TALISMAN (Collection-level name)
  • Under the ERC-1155 specification, individual token names are not stored on-chain
  • baseURI() → Points to an IPFS CID
  • No baseURI modification transactions were identified

8. IPFS Metadata Verification

When the relevant CID JSON is properly read as UTF-8, the name field contains:

“完全に無印で行く”

If misinterpreted using a different character encoding, it may appear as:

  • “蛍悟®縁祈・蜻–縁祈陣後”
  • “螳悟Q縺木辟。蜊-縺7隣後”

The underlying data is stored in UTF-8.

Additionally, within the JSON, the phrase appears as:

完全に無印で行く

In this case, the character “で” is stored in Unicode Normalization Form D (NFD),
specifically as U+3066 (“て”) + U+3099 (combining dakuten mark).
Visually, this is equivalent to the composed character “で”.

There is no record of this string being entered prior to mint.

9. Latest Contract Events (At Time of Verification)

Latest Event Timestamp:
2026-02-15 05:00:23 UTC

Related Transaction:
0xf1d0efcfa… (partially abbreviated)

  • BatchMetadataUpdate (uint256 _fromTokenId, uint256 _toTokenId)
  • TransferBatch
  • multiConfig(add…)

No events indicating URI updates or baseURI modifications were identified.

10. General ERC-1155 Specification

  • Individual token names depend on the name field of the JSON returned by uri(id)
  • The contract’s name() function returns only the collection-level name
  • OpenSea displays the name returned by uri(id)

Therefore, OpenSea’s display depends on the JSON content stored on IPFS.

11. Confirmed Facts

  1. No record was identified indicating that “完全に無印で行く” was entered prior to mint.
  2. The IPFS JSON (when properly read as UTF-8) contains “完全に無印で行く”.
  3. OpenSea displays “完全に無印で行く”.
  4. No baseURI modification history or URI update events were identified.

12. Record

A name not entered prior to mint exists in the IPFS JSON metadata and was displayed on OpenSea.

The precise mechanism by which this occurred has not been identified within the scope of this verification.

OpenSea Item Display Record

 


https://opensea.io/item/ethereum/0x913da03999a6255fdb9e33b7c5300e8e6fdf2f20/1

 

 

Interpretation Scope

This record limits itself to observable data and verifiable contract events.
No speculative causal attribution is included.

Frequently Asked Questions

What causes an ERC-1155 metadata name discrepancy?

A discrepancy can occur when the metadata JSON stored on IPFS differs from the data cached or rendered by a marketplace such as OpenSea.

Does this affect blockchain integrity?

No. The blockchain stores the token URI and ownership record. Rendering inconsistencies do not alter on-chain data.

How can metadata integrity be verified?

By directly accessing the token URI, retrieving the IPFS JSON, and comparing it with marketplace-displayed values.

Is this issue specific to ERC-1155?

No. Similar discrepancies can occur in ERC-721 if metadata caching or indexing behaves unexpectedly.

 

External Technical Note:

Unexpected Metadata Name in ERC-1155 — X Post Record

Our team website is built upon an Ecosystem model.
This page serves as a guide to that structure, illustrated through HANDY DIGITAL TALISMAN.

 

Philosophy | Ecosystem Layer | Gallery | Technical Record | Ecosystem Overview