These ‘field values’ are stored off-chain in a DB attached to the issuance.

They are also optionally included in the metadata JSON (so wallets and verifiers can display them cleanly).

On Base chain – (tx hash + token id + metadata URI).

Privacy note

The party wallet addresses are public once included which is part of the proof of the party.

1) The Share Certificate file(s)

• The PDF certificate you upload gets pinned as a file.
• Result:
  • CID (content identifier)
  • IPFS URI: ipfs://<certificateCID>
  • Optional browser link via a gateway: https://gateway.pinata.cloud/ipfs/<certificateCID>

2) The Issuance Metadata JSON (the “token info”)

• SharesMint generates a JSON record for the issuance and pins it.
• Result:
  • Metadata CID
  • IPFS URI: ipfs://<metadataCID>
  • Gateway link: https://gateway.pinata.cloud/ipfs/<metadataCID>

What’s inside the metadata JSON

It includes:

• Contract address (your registry)
• Network (Base)
• Issuance / agreement id (once created)
• Receiver wallet address
• Share class + units
• Certificate number (if provided)
• SHA-256 document hash(es)
• IPFS links to the pinned PDF(s)
• Verifier link (your SharesMint verify page)

“SharesMint stores your share certificate PDF and a metadata record on IPFS (pinned via Pinata). The on-chain token references the IPFS metadata, while the certificate itself remains a public IPFS file identified by its CID.”