Add "Hot & Cold Inventories" advanced-mechanics guide#28
Merged
Conversation
Documents a best-practice pattern for real-time games: keep tradeable assets on-chain (the cold inventory, which is the player's wallet) and keep consumable, fast-action items in an off-chain hot inventory, moving items across the boundary with on-chain mints and melts. Covers the mintable/non-mintable decision, the mint-in/melt-out lifecycle, a GraphQL worked example, and correctness pitfalls (finalization before crediting, the optimistic-consume exploit, collapsing-supply, and treating the hot ledger as production-critical). Adds glossary entries for hot/cold inventory and mintable/non-mintable items. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
The 'A managed wallet doesn't fix this' warning pre-empted an objection the reader hasn't formed yet and referenced moving items between two wallets before the hot/cold move is introduced. The substantive point (a second/managed on-chain wallet is still slow) is already made in context by the later 'One wallet per player, not two' tip. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…ks and jargon - Remove the 'One wallet per player, not two' and 'Items stay hot between sessions' callouts: both only made sense as rebuttals to ideas raised while drafting, and answer questions a fresh reader hasn't asked. - Replace WalletConnect links with the native wallet-request flow (sending-wallet-requests), which is the direction the docs are moving; link the linking step to its Step 1 anchor. - Replace the unexplained 'boundary' jargon with explicit 'between inventories' wording. - Minor phrasing tightening in the hot-ledger pitfall. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Replaces the blanket 'don't use Collapsing Supply for mintable items' with guidance to match the cap to the movement pattern: fixed supply for items that round-trip between hot and cold (so they can be re-minted), Collapsing Supply for one-way items minted to cold once (e.g. a non-consumable sword). Links Collapsing Supply to the enforced-rarity guide. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Adds inbound links so the new pattern is discoverable from where readers hit the problem: the Enjin Farmer breakdown (as the production follow-up to its on-chain melts), Using Managed Wallets (cold inventory), Melting/Burning Tokens (the move-to-hot operation), and Sending Wallet Requests (instant alternative to on-chain consumption). Phrased as 'can be used as/to' rather than asserting one canonical use. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Drops the tip added on the melting/burning page in b90ad2c, per request. The other three backlinks (managed wallets, Enjin Farmer breakdown, sending wallet requests) remain. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a new Integration Guides → Platform → Advanced Mechanics page for a best-practice
pattern for real-time games: keep tradeable assets on-chain (the "cold" inventory — the
player's wallet) and keep consumable, fast-action items in an off-chain "hot" inventory,
moving items between them with on-chain mints and melts.
The page covers:
GetTransaction finalization, batching, and fuel tanks for fee sponsorship
matching the supply cap to one-way vs two-way movement, and treating the hot ledger
as production-critical data
Also in this PR:
Sending Wallet Requests