CONFIDENTIAL PATENT POSITION REVIEW
PATENT POSITION18/856,095
Evidence Gaps

WHAT PUBLIC EVIDENCE DOES NOT ESTABLISH

Public material describes capability, not implementation. The matters below cannot be determined from public sources and are recorded rather than assumed.

Further technical discovery / confidential evaluation required. No inference is drawn about any item listed on this page.

Evidence gap

KEY TECHNICAL QUESTIONS FOR FURTHER EVALUATION

These are technical due-diligence questions for further evaluation. They are not assertions about ILLUST's implementation.

Q01

Transaction mechanics

How are purchases, trades, offers or bids technically executed within the ILLUST architecture?

Q02

Asset used in transaction

Can one digital asset or tokenised asset be used to acquire or trade another digital asset?

Q03

Blockchain architecture

Which blockchain or blockchains record asset ownership?

Q04

Cross-chain operation

Does the platform support movement or transfer of digital assets between blockchain environments?

Q05

Smart contracts

What smart-contract operations are initiated during an ownership transfer?

Q06

Lock / unlock architecture

Does any transfer process involve locking an asset or contract state and subsequently unlocking or releasing the asset within another blockchain environment?

Server-side processing

Exact server-side processing of placement and discovery requests.

FURTHER TECHNICAL DISCOVERY / CONFIDENTIAL EVALUATION REQUIRED

Smart-contract implementation

Exact contract architecture used for listing, sale and transfer.

FURTHER TECHNICAL DISCOVERY / CONFIDENTIAL EVALUATION REQUIRED

Transaction sequence

Precise ordering of marketplace, settlement and ownership-update steps.

FURTHER TECHNICAL DISCOVERY / CONFIDENTIAL EVALUATION REQUIRED

Internal databases

Structure and persistence model of asset-to-location associations.

FURTHER TECHNICAL DISCOVERY / CONFIDENTIAL EVALUATION REQUIRED

Ownership-state logic

Internal logic determining and updating ownership state.

FURTHER TECHNICAL DISCOVERY / CONFIDENTIAL EVALUATION REQUIRED

Cross-chain architecture

How cross-chain positioning is technically implemented.

FURTHER TECHNICAL DISCOVERY / CONFIDENTIAL EVALUATION REQUIRED

Backend geolocation

Backend geolocation calculation, thresholds and tolerance logic.

FURTHER TECHNICAL DISCOVERY / CONFIDENTIAL EVALUATION REQUIRED

Internal APIs

Internal API surfaces between AR, registry and marketplace layers.

FURTHER TECHNICAL DISCOVERY / CONFIDENTIAL EVALUATION REQUIRED

Deployment architecture

Current production deployment architecture and active components.

FURTHER TECHNICAL DISCOVERY / CONFIDENTIAL EVALUATION REQUIRED

U.S. implementation

Current U.S.-facing implementation and operational footprint.

FURTHER TECHNICAL DISCOVERY / CONFIDENTIAL EVALUATION REQUIRED

Element-level verification items

Drawn directly from the claim-level mapping, these are the specific points that public evidence does not resolve for each element.

1.aPhysical / geographic positionExact selection UI and permitted location types to be confirmed.
1.bDigital asset associationPersistence model of the association not publicly detailed.
1.cMap-based discoveryWhether map markers indicate purchase availability requires confirmation.
1.dPhysical user locationTolerance/threshold logic for presence determination not public.
1.eAR access or interactionNone material at concept level.
1.fMarketplace transactionLive transaction flow and current availability require verification.
1.gDigital ownership transactionOn-chain transfer sequence and contract addresses not verified.
KNOWN / INFERRED / UNKNOWNEvidence discipline

PUBLICLY ESTABLISHED

  • Map interface
  • Geolocation
  • Digital asset placement
  • AR functionality
  • Marketplace activity
  • Blockchain ownership concepts

TECHNICALLY INFERRED

  • Certain transaction relationships
  • Potential sequencing
  • Some backend interactions

NOT ESTABLISHED FROM PUBLIC SOURCES

  • Exact server-side processing
  • Internal APIs
  • Exact smart-contract architecture
  • Internal ownership-state logic
  • Cross-chain mechanics
  • Current proprietary backend structure

Technical Correspondence — Not a Legal Conclusion

This analysis identifies areas of apparent technical correspondence between the patent architecture and publicly documented ILLUST technology. It does not constitute an allegation or legal conclusion concerning infringement, validity, enforceability or freedom to operate. Determination of those matters requires analysis by qualified patent counsel and, where appropriate, access to non-public technical information.

Patent Mapping Disclaimer

This presentation has been prepared for preliminary commercial and technical evaluation purposes. The analysis is based primarily on publicly available information and does not constitute a complete claim analysis, allegation of infringement, legal opinion or legal advice. References to technical correspondence indicate areas identified for further evaluation and should not be interpreted as a determination of infringement or legal liability. Certain technical operations cannot be established from public information and may require further confidential technical review. Patent prosecution status and claim scope should be independently confirmed with qualified patent counsel before reliance is placed upon this analysis.