NFT / Marketplace·Polygon · Arbitrum · Ethereum · Avalanche · BNB Chain
Arianee
Digital product passport protocol for phygital goods and brand NFTs: dynamic NFT metadata, ownership transfer via passphrase, and on-chain authenticity.
- 01phygital product NFTs
- 02luxury brand digital passports
- 03warranty / e-maintenance booklets
- 04tokengated brand experiences
- 05anti-counterfeit authentication
- pnpm add @arianee/arianee-sdk
| Variable | Scope | Description |
|---|---|---|
| ARIANEE_NMP_TOKEN | Server | Arianee Network Management Platform (NMP) bearer token for the issuer/brand account. |
| ARIANEE_BRAND_PRIVATE_KEY | Server | Issuer wallet private key used to sign mint and content updates. Server-side only. |
Use Arianee to mint and update digital product passports. Initialize `const sdk = new ArianeeSdk({ core: Core.fromPrivateKey(process.env.ARIANEE_BRAND_PRIVATE_KEY!) })`. Mint a passport with `sdk.protocol.createAndStoreSmartAsset({ protocolName: 'polygon', content: { name, description, medias }, tokenAccess: { fromPassphrase: true } })` — the returned passphrase is the claim secret you ship with the physical product. Update content over the lifecycle with `sdk.protocol.updateSmartAsset({ smartAssetId, content })`. Read state with `sdk.protocol.getSmartAsset({ smartAssetId })`.
- ⚑Each protocol deployment (Polygon, Arbitrum, etc.) is an independent contract set with its own token ID space — `smartAssetId` is unique per protocol, not globally; always pass `protocolName` alongside the ID.
- ⚑Royalty enforcement is not the primary use case — Arianee passports are typically non-transferable or gated by passphrase, so do NOT treat them as standard ERC-721 for marketplace listings; OpenSea integrations require explicit configuration.
- ⚑Content updates push the latest JSON to Arianee's RPC server which pins to IPFS — but the on-chain `imprint` only stores a hash; if the RPC server drops a record, on-chain verification still works but the human-readable content disappears unless you self-host the JSON.
- ⚑Passphrase-based claims are single-use — once a customer claims, the passphrase is burned; printing the same passphrase on multiple physical units silently lets only the first claim succeed.
- ⚑Arianee charges credits per mint (Aria token / fiat-backed credits in NMP) — running out of credits causes mint API calls to fail with `InsufficientCredits` rather than throwing during transaction simulation.
- ⚑Brand identity must be approved (NMP onboarding) before mints render correctly in Arianee Wallet — anonymous issuer addresses produce passports that show 'Unknown Brand' to customers.