NFT on Logos: dogfooding findings + PoC (private ownership) and LP-0001 readiness

[xAlisher]

TL;DR. I dogfooded NFTs on the Logos stack end to end: read the code and docs, forked the LEZ wallet to fill the gaps, built a proof-of-concept Basecamp app, and ran a 5-piece private NFT collection live on a local testnet node. This issue tracks the findings and links, and their relevance to Lambda Prize LP-0001 (Private NFT Ownership Proof).

Disclaimer: independent community R&D / proof-of-concept, developed to demonstrate capabilities of the Logos technology stack. Not built for, reviewed, audited, approved, or endorsed by Logos or IFT. Dev-mode / testnet only. Sole responsibility of the contributor.

What works today (proven live)

• NFT program on-chain: create, numbered copies, transfer.
• Private NFT ownership: owner and contents hidden on-chain; only a viewing key reveals them.
• Selective disclosure: prove you own a specific NFT to one verifier without exposing your wallet.
• Full lifecycle on a testnet node: define, print, shield (make private), transfer, unseal.
• A working Basecamp app renders and unseals a collection.

Findings (gaps hit by dogfooding)

• Wallet: the LEZ CLI wallet could not display, create, print, or trade NFTs, and NFT transfer to a fresh recipient was rejected. All fixed on an R&D fork (kept as R&D, not upstreamed).
• Docs: no official NFT documentation exists (only a fungible-token guide).

Insight: this de-risks LP-0001

• LP-0001 "Private NFT Ownership Proof" is currently draft, pending NFT-program readiness.
• This dogfooding shows the substrate is ready and gives a working private-ownership plus disclosure baseline.
• Delta to LP-0001's goal (prove you own one of a collection without revealing which): a set-membership proof plus a nullifier for replay resistance, on top of what is proven here.
• The PoC app is a reference for LP-0001's module/SDK plus Basecamp app GUI requirements.

Links

• Research and findings: https://github.com/xAlisher/nft-research-for-logos
• PoC Basecamp app: https://github.com/xAlisher/sealed-keys-basecamp
• LP-0001: https://github.com/logos-co/lambda-prize/blob/master/prizes/LP-0001.md
• Upstream (public): https://github.com/logos-blockchain/logos-execution-zone

Tracking / next steps

• Present findings and insights to the team.
• Feed the readiness evidence into the LP-0001 draft (help move draft to ready, inform criteria).
• Decide the vehicle for a real NFT wallet (and possibly a marketplace): Lambda Prize or RFP.
• Keep the fork and PoC app available as a reference starting point for an entrant.

The ask: track these findings and decide the vehicle (LP-0001 or RFP) for a full NFT wallet. Not proposing that we fix the LEZ wallet ourselves.

Suggested labels (I cannot apply labels on this repo): dogfooding, nft, lambda-prize.

[xAlisher]

Plain-language overview (for readers and agents), with the private-ownership explainer, the ETH/SOL/Ordinals comparison, and the LP-0001 connection: https://github.com/xAlisher/nft-research-for-logos/blob/main/docs/nft-on-logos-overview.md

[xAlisher]

Update: an official NFT-capable UI already exists (token_ui), it just isn't in the Basecamp catalog yet.

Per the recent NFT planning discussion, the official token program app lives in logos-blockchain/lez-programs. Two modules are relevant:

• token_module (core): https://github.com/logos-blockchain/lez-programs/tree/main/modules/token
• token_ui (ui_qml): https://github.com/logos-blockchain/lez-programs/tree/main/apps/token

Verified in code (2026-09-07):

• token_ui has a full non-fungible path (createNonFungible, printable supply, master-holding controls printing) plus an inspect view, so public NFT create/inspect UI is real.
• It is not in the module catalog yet, so it is not installable via Basecamp today.
• Ownership is public ("balances and ownership reflect network state"); there is no sealed / private-ownership path.

So the gap this issue tracks narrows to private ownership (the LP-0001 angle), not public NFT UI, which already exists. I am building both modules and dogfooding the token_ui journey against our own LEZ sequencers with real RISC0 / STARK proving (the same zk setup from our prior LEZ verification work), to confirm the public NFT path end to end, and will report findings here.

One question: is cataloguing token_module + token_ui part of the mainnet NFT plan? That is the difference between "exists in a repo" and "a user can install it."

[xAlisher]

Update: verified the official token_ui end-to-end by building and using it.

Built token_module + token_ui + lez_core from current source, ran them in Basecamp against the public testnet (testnet.lez.logos.co), and created + confirmed two definitions through the app:

• a fungible token (Tv51YD...TKBm), and
• a named NFT collection "EcoDev Glitchlings" (3UdVtS...C5MB), with metadata + master-holding print control stored on-chain.

So the public NFT UI in logos-blockchain/lez-programs/apps/token isn't just present, it works end-to-end on testnet. It's still not in the Basecamp catalog, so a user can't install it yet.

Dogfooding also surfaced 6 friction findings (biggest: a fresh wallet's sync is invisible, so it reads as frozen, and confirmed txs show as Pending until reconnect). Filed upstream as EcoDev feedback: logos-blockchain/lez-programs#359

Net: the public NFT path is real and working; the remaining gap this issue tracks is private ownership (LP-0001).