01 / NULLSHIFT

Begin with the item, not the ledger

NULLSHIFT’s Web3 design concerns optional records for cosmetic items. A record could identify an item and its current holder under rules defined by a future service. The actual artwork, in-game display rights and ability to use that item would still depend on the game and its published terms. Owning a record is not the same as owning the game, the underlying artwork or a share of a company. This website issues none of those records.

02 / NULLSHIFT

A cosmetic boundary

The design boundary is that recorded cosmetics do not grant stronger weapons, exclusive combat abilities or improved matchmaking outcomes. The same competitive rules should apply regardless of whether a player uses any ownership feature. A visual variant must also remain readable to opponents. Optionality is meaningful only if the ordinary play path works on its own; a future design that requires a wallet merely to understand or enjoy a match would break this proposal’s starting principle.

03 / NULLSHIFT

A record cannot promise a market

A transferable record does not guarantee that anyone will want it, that a marketplace will list it or that a game will continue to support it. Fees, access restrictions and service changes may matter if a real system is ever introduced. There is no return, appreciation or liquidity promise here. No token sale, trading interface or purchase flow is active. Treat the art and fiction as creative material, not an invitation to finance an imagined economy.

04 / NULLSHIFT

What this website stores

The current static website remembers language and motion preferences in the browser’s local storage. It does not connect a wallet, collect an account profile, accept payments or submit a registration form. Browsing the field guide creates no game inventory. Hosting infrastructure may still process ordinary request information, so the draft privacy notice separates browser preferences from hosting details that the operator must confirm. No invented audit, corporate identity or blockchain partner is used to fill those gaps.

05 / NULLSHIFT

What must be settled before activation

Before any ownership service could go live, its operator, infrastructure, item rights, support process and security approach would need to be specified and reviewed. People would need clear explanations of what happens when access is lost, a service closes or an item is removed. Those are open product questions, not details this website can safely assume. Until answers and working infrastructure exist, there are no transactions or item entitlements available through the site.