Claims index — every fact in the dossier as an atomic, citable claim.

NG-FIN — Financial (5)

• NG-FIN-001 · kind: inferred · Aggregate primary sales across the catalogued cohort of Nifty Gateway-deployed BuilderInstance contracts total at least $1,129,248,787 USD. The figure is a strict lower bound.
  Method: For each contract: revenue = (units sold reported by the platform's product index) × (lowest applicable minted price in the same index). Where multiple price tiers exist, the minimum is used. Project-level totals (where multiple BuilderInstance contracts back the same project) are deduped to be counted once.
  Limitations: Excludes 33% of contracts that have no recoverable USD figure in the platform's index. Excludes secondary-market activity. Excludes off-chain primary settlements such as the Beeple Spring Collection auctions, where the catalog records primaryUSD as null and the project total is independently corroborated. Lower-bound by construction.
  Last verified: 2026-04-21
• NG-FIN-002 · kind: observed · The Nifty Gateway product index, as crawled, surfaces 10,090 distinct on-chain BuilderInstance contract addresses deployed by the platform.
  Method: Two-letter and two-digit alphabet-sweep of the platform's unauthenticated search endpoint at search-api.niftygateway.com/api/v2/indexes/products/search, deduplicated by contract address.
  Limitations: The platform's own meta object reports approximately 10,128 collections; the alphabet-sweep recovers 10,090. The remaining ~38 collections are not surfaced by any two-character substring used in the sweep and are not represented in the catalog.
  Last verified: 2026-04-21
• NG-FIN-003 · kind: observed · Of 10,090 catalogued contracts, 6,728 (66.7%) have a recoverable USD figure in the platform's index; the remaining 3,362 (33.3%) do not.
  Method: Direct count of catalog entries whose totalUSD field is non-null.
  Limitations: Recoverability is a property of the platform's published index, not of whether the underlying drop generated revenue. Contracts with no USD figure are excluded from the NG-FIN-001 aggregate.
  Last verified: 2026-04-21
• NG-FIN-004 · kind: observed · The platform exposes an unauthenticated search endpoint at search-api.niftygateway.com/api/v2/indexes/products/search that returns per-token records including original mint price, units sold, current floor, and last-sale timestamp.
  Method: Direct observation: endpoint accepts unauthenticated POST, returns the fields named.
  Limitations: The endpoint's pagination silently fails past page one; recovering the full catalogue requires substring sweeps rather than paged enumeration. Endpoint behaviour may change at any time, particularly as the platform approaches its closure date.
  Last verified: 2026-04-21
• NG-FIN-005 · kind: inferred · Sibling-contract deduplication is applied to the aggregate so that conceptual drops backed by multiple BuilderInstance contracts (notably Beeple: Spring Collection) are counted once at the project level rather than once per contract.
  Method: Project totals are recorded against each backing address; the aggregate sums project totals once per unique project key.
  Limitations: Project-grouping relies on manual identification of sibling addresses. Unidentified sibling pairs (if any) would cause the aggregate to be slightly overstated; the published headline.siblingDuplicatesSuppressed field reports the count of dedupes applied.
  Last verified: 2026-04-21

NG-TECH — On-chain mechanics (5)

• NG-TECH-001 · kind: observed · On Nifty Gateway BuilderInstance contracts, the standard ERC-721 tokenURI(tokenId) function returns an HTTPS URL on api.niftygateway.com. The metadata JSON it returns typically contains an 'image' field pointing back to nftcdn.niftygateway.com.
  Method: Reproducible by any reader: any Nifty Gateway contract on Etherscan, Read Contract tab, call tokenURI(tokenId).
  Limitations: A small minority of contracts may use other host patterns; users should verify per-contract by calling the function directly. Future contract-owner action via setBaseURI() can change the returned host at any time.
  Last verified: 2026-04-22
• NG-TECH-002 · kind: observed · Nifty Gateway BuilderInstance contracts typically expose a setBaseURI() function callable by the contract owner, which mutates the prefix returned by tokenURI() for every token in the collection.
  Method: Read from the BuilderInstance template's published bytecode and the function selectors exposed on individual contracts. Per-contract presence verifiable on Etherscan's Read/Write Contract tabs.
  Limitations: A subset of contracts does not expose setBaseURI; for those, the metadata host is fixed at deploy time and cannot be re-pointed by anyone — including by Nifty Gateway. The split between mutable and immutable contracts has not been separately enumerated in this dossier; the word 'typically' should not be read as a quantified claim.
  Last verified: 2026-04-22
• NG-TECH-003 · kind: observed · 1,596 of 10,090 (15.8%) Nifty Gateway-deployed contracts show on-chain linkage to the registry contract at 0x6e53130ddff21e3bc963ee902005223b9a202106 by either the niftyRegistryContract() getter or as a bytecode literal. 8,464 (83.9%) show neither signal. 28 addresses have no code; 2 produced an RPC error.
  Method: For each of 10,090 contracts: (1) eth_call of selector 0xbe772d4c (= niftyRegistryContract()), (2) fetch deployed bytecode and scan for the literal string of the registry address. Positive on either signal => classified registry-linked.
  Limitations: These two signals are necessary conditions for the standard NG transfer-gate pattern, not formal proofs that any specific contract's transfer function defers to the registry on every call. False negatives possible (storage-loaded address, proxy/delegatecall path that the scan misses). False positives possible (registry address embedded in non-transfer code). Per-token certainty requires reading the specific contract's source or disassembly.
  Last verified: 2026-04-22
• NG-TECH-004 · kind: observed · The fraction of registry-linked contracts is sharply time-sliced: 97.1% of 2020 deployments, 82.3% of 2021, 6.4% of 2022, and 0% of contracts deployed from 2023 onwards. The latest registry-linked drop date observed is 2022-03-29.
  Method: Cross-tabulation of the per-contract classification against the drop date recorded in the project catalogue.
  Limitations: Drop date is taken from the platform's own product index. Contracts with no recoverable drop date (34 in the scan) are reported in a separate 'unknown' bucket.
  Last verified: 2026-04-22
• NG-TECH-005 · kind: observed · A withdrawal from a Nifty Gateway custodial wallet to a self-custodial wallet is an on-chain transferFrom call that changes the result of ownerOf(tokenId). It does not change the result of tokenURI(tokenId).
  Method: Direct observation, reproducible per token: read tokenURI on Etherscan before and after a withdrawal transaction settles.
  Limitations: If the contract owner separately calls setBaseURI() at any time (including as part of a future Arweave migration), the returned URL will change independent of withdrawal. The distinction described here is between what a withdrawal does and what setBaseURI does, not a prediction about future setBaseURI calls.
  Last verified: 2026-04-22

NG-CORP — Corporate (4)

• NG-CORP-001 · kind: observed · Nifty Gateway operates as Nifty Gateway LLC, a limited liability company organised under Delaware law, founded in 2018 by Duncan and Griffin Cock Foster, acquired by Gemini Trust Company, LLC in November 2019, and remaining a wholly-owned subsidiary of the Gemini group.
  Method: Direct quotation from primary corporate sources.
  Limitations: Subsidiary status is asserted on the basis of Gemini's own announcement; no separate filing has been independently verified post-acquisition.
  Last verified: 2026-04-22
• NG-CORP-002 · kind: legal · Delaware charges every domestic LLC a flat $300 per year in franchise tax to remain in good standing. The fee is the same regardless of revenue.
  Method: Direct quotation from the Delaware Division of Corporations published instructions.
  Limitations: States the Delaware franchise-tax obligation only. Does not speak to federal income tax, state income tax in any other jurisdiction, or any other obligation Nifty Gateway LLC may have.
  Last verified: 2026-04-22
• NG-CORP-003 · kind: legal · Delaware LLCs are not required to file an annual report. There is no public Delaware filing of revenue, profit, members, managers, or any other financial measure.
  Method: Direct reading of Delaware's published LLC obligations vs. the separate annual-report obligation imposed on Delaware corporations.
  Limitations: States only what Delaware law requires. Does not address voluntary disclosure, parent-level disclosure obligations Gemini may face elsewhere, or filings required in other jurisdictions in which Nifty Gateway LLC may have nexus.
  Last verified: 2026-04-22
• NG-CORP-004 · kind: inferred · No income statement, balance sheet, or tax return for Nifty Gateway LLC has been located in any publicly searchable source known to this dossier. As a privately-held Delaware LLC inside a private group, the entity has no statutory obligation to publish such information; whatever Nifty Gateway LLC paid — or did not pay — in income tax cannot be determined from public sources.
  Method: Follows from NG-CORP-001 and NG-CORP-003: a privately-held Delaware LLC has no statutory public-disclosure obligation; absence of a published filing is therefore expected, not anomalous.
  Limitations: Asserts non-availability in the public sources searched (Delaware Division of Corporations, EDGAR, the entity's own communications, contemporaneous press), not formal non-existence. Confidential filings made to tax authorities are not addressed. Parent-level disclosures Gemini may have made in private fundraising documents are also not addressed.
  Last verified: 2026-04-22

NG-TOS — Terms of Use (verbatim quotation) (15)

• NG-TOS-001 · kind: legal · TOS § 2 (2024 revision) defines 'NFTs or Nifties' as 'non-fungible tokens (i.e. units of data stored on a blockchain), exclusive of any Artwork or other off-chain file or asset referenced in the code or metadata of the NFTs or otherwise associated with the token.'
  Method: Verbatim quotation from the dated TOS revision and its Wayback capture.
  Limitations: Materially narrower than the 27 Dec 2022 revision (NG-TOS-001-prior). The current live TOS as of this dossier's lastVerified date is the 18 Jan 2024 revision; no later revision has been observed before the closure notice.
  Last verified: 2025-12-29
• NG-TOS-001-prior · kind: legal · TOS § 2 (27 Dec 2022 revision) defined the term as: 'Nifties means non-fungible tokens.' The qualifier excluding artwork was not present in this revision.
  Method: Verbatim quotation from the dated TOS revision and its Wayback capture.
  Limitations: Superseded by the 18 Jan 2024 revision. Retained in the index for historical comparison; not the operative wording today.
  Last verified: 2023-07-24
• NG-TOS-002 · kind: legal · TOS § 12 (2024 revision) states: 'Purchasing an NFT conveys ownership of the non-fungible token but does not necessarily convey ownership to the Artwork or other files or assets referenced by the NFT.'
  Method: Verbatim quotation.
  Limitations: This paragraph was not present in the 27 Dec 2022 revision of § 12; it is an addition introduced in the 2024 revision.
  Last verified: 2025-12-29
• NG-TOS-003 · kind: legal · TOS § 12 states: 'No refunds or returns are permitted except with respect to any statutory warranties or guaranties that cannot be excluded or limited by law.'
  Method: Verbatim quotation.
  Limitations: The carve-out points back to statutory rights that cannot be excluded by contract; the scope of those rights varies by jurisdiction.
  Last verified: 2025-12-29
• NG-TOS-004 · kind: legal · TOS § 11 states: 'We do not undertake any obligation with respect to the Artwork or other files or assets referenced by NFTs, including any obligation to ensure that such files will be available or that any reference to an off-chain file in the NFTs on-chain record will remain functional.'
  Method: Verbatim quotation.
  Limitations: States the published contractual position. Does not address whether such a disclaimer is enforceable in any given jurisdiction against any given consumer.
  Last verified: 2025-12-29
• NG-TOS-005 · kind: legal · TOS § 11 includes a provision describing insolvency outcomes for users' NFTs as 'unsettled and not guaranteed.'
  Method: Verbatim quotation.
  Limitations: Quoted phrase as it appears in the published clause; legal effect depends on the applicable insolvency regime.
  Last verified: 2025-12-29
• NG-TOS-006 · kind: legal · TOS § 18 (Risks) names file unavailability as a disclosed risk inherent to the platform.
  Method: Verbatim quotation.
  Limitations: Disclosure of a risk is not the same as a representation that the risk has materialised; the clause speaks to what users have been told to expect.
  Last verified: 2025-12-29
• NG-TOS-007 · kind: legal · TOS § 22 states (in capitals as published): 'WE DO NOT GUARANTEE THAT NIFTY GATEWAY OR ANY NIFTY GATEWAY PARTY CAN EFFECT THE TRANSFER OF TITLE OR RIGHT IN ANY NFTs.'
  Method: Verbatim quotation. Capitalisation preserved as in source.
  Limitations: States only the published contractual disclaimer. Does not address the relationship between this clause and the on-chain transfer-gate observations in NG-TECH-003.
  Last verified: 2025-12-29
• NG-TOS-008 · kind: legal · TOS § 17 reserves the platform's right to modify any part of the Service without notice.
  Method: Verbatim quotation.
  Limitations: Quoted as written; enforceability of unilateral-modification clauses varies by jurisdiction.
  Last verified: 2025-12-29
• NG-TOS-009 · kind: legal · TOS § 28 states: 'We reserve the right, without notice and in our sole discretion, to terminate your license to access or use Nifty Gateway, the Services, or the Site, at any time and for any reason. You understand and agree that we shall have no liability or obligation to you in such an event.'
  Method: Verbatim quotation.
  Limitations: The clause governs the licence to access the platform. It does not, on its face, address the on-chain status of tokens already in users' self-custody wallets.
  Last verified: 2025-12-29
• NG-TOS-010 · kind: legal · TOS § 27 reserves a security interest in user accounts and a right of set-off in favour of Nifty Gateway.
  Method: Verbatim quotation.
  Limitations: Quoted as written; perfection and priority of any such interest in any specific jurisdiction is not addressed.
  Last verified: 2025-12-29
• NG-TOS-011 · kind: legal · TOS § 23 caps Nifty Gateway's aggregate liability to the user.
  Method: Verbatim quotation. Specific cap amount as published in the source.
  Limitations: Liability caps are routinely subject to challenge under consumer-protection law; the existence of the clause is the claim, not its enforceability.
  Last verified: 2025-12-29
• NG-TOS-012 · kind: legal · TOS § 4 reserves the right to confiscate NFTs at the platform's sole discretion.
  Method: Verbatim quotation.
  Limitations: The clause speaks to assets within Nifty Gateway's custody. It does not, on its face, claim a right to seize tokens already withdrawn to user-controlled wallets.
  Last verified: 2025-12-29
• NG-TOS-013 · kind: legal · TOS § 11 contemplates that custody of users' NFTs may be held on an 'omnibus' basis — multiple users' assets pooled in a single wallet.
  Method: Verbatim quotation.
  Limitations: Describes a permitted custody model under the contract. Whether any specific wallet operated by Nifty Gateway is in fact omnibus or segregated is a separate factual question not resolved by this clause.
  Last verified: 2025-12-29
• NG-TOS-014 · kind: legal · TOS § 26 requires individual binding arbitration for disputes, includes a class-action waiver, and adopts a 'mass-filing' bellwether protocol.
  Method: Verbatim quotation.
  Limitations: Arbitration clauses, class-action waivers, and mass-arbitration bellwether protocols have all been the subject of contested case law in multiple jurisdictions; this index records the contractual text, not its enforceability in any given forum.
  Last verified: 2025-12-29

NG-EVENT — Dated events (5)

• NG-EVENT-001 · kind: observed · On 24 January 2026, the Nifty Gateway platform published a closure notice on its own homepage and TOS page; contemporaneous press reporting on the same date covered the announcement and described the platform as having entered withdrawals-only mode.
  Method: Primary source: Gemini's own announcement, preserved as the closure-notice PDF capture. Cross-referenced against three independent contemporaneous outlets reporting on the same date.
  Limitations: The exact local time of the public announcement is not asserted. 'Withdrawals-only mode' is the platform's own characterisation, repeated in press; the underlying API-level changes that constitute that mode are not separately enumerated here. The underlying corporate decision and its internal timing are not addressed.
  Last verified: 2026-04-22
• NG-EVENT-002 · kind: observed · The original shutdown date of 23 February 2026 was subsequently extended; the platform homepage stated that the platform would close on 23 April 2026 and instructed users to withdraw their assets by that date. The platform shut down on that date.
  Method: Direct observation of the platform's homepage, corroborated by Wayback capture of the TOS page bearing the closure notice.
  Limitations: Date may be further revised by the platform; cited as accurate as of lastVerified.
  Last verified: 2026-04-22
• NG-EVENT-003 · kind: observed · Gemini has stated on the Nifty Gateway homepage that it will 'migrate the metadata and media hosting on Nifty Gateway to a permanent, decentralized solution on Arweave,' and that for legacy NFTs minted in 2021 or earlier whose contracts cannot be updated, it will 'continue to host this metadata in perpetuity.'
  Method: Verbatim quotation from the platform's published closure notice.
  Limitations: The statement is a published commitment, not a smart-contract guarantee. Whether and when the migration is executed (a deliberate setBaseURI() call by the contract owner) is not on-chain-enforceable. The 'in perpetuity' commitment depends on Gemini's continued operation and continued payment of hosting costs indefinitely.
  Last verified: 2026-04-22
• NG-EVENT-004 · kind: observed · The current published Nifty Gateway Terms of Use are marked 'Last revised: January 18, 2024.'
  Method: Direct reading of the document header.
  Limitations: Captures known up to 2026-03-20 still bear the same revision date in the document body even after the closure banner was prepended.
  Last verified: 2026-04-22
• NG-EVENT-005 · kind: observed · The Nifty Gateway Terms of Use revision immediately prior to the current one was marked 'Last revised: December 27, 2022.'
  Method: Direct reading of the document header.
  Limitations: Earlier revisions exist; the 27 Dec 2022 revision is referenced here as the immediately prior published version to the operative 18 Jan 2024 text.
  Last verified: 2026-04-22

NG-EDIT — Editorial framing (explicit opinion) (1)

• NG-EDIT-001 · kind: editorial · Editorial framing: Nifty Gateway's co-founders publicly described the company's mission, in interviews through 2021–2022, as onboarding hundreds of millions to a billion new collectors. The reconstructed catalogue totals at least $1.13B in primary sales (NG-FIN-001), after which the platform announced its closure (NG-EVENT-001). The contrast is offered as commentary on the public record. No allegation of intent is made.
  Method: Editorial juxtaposition of two independently-sourced facts.
  Limitations: Explicitly editorial. Not a fact claim. The claim that the founders said this is grounded in contemporaneous press interviews (2021–2022) which are not individually catalogued in this index.
  Last verified: 2026-04-22

How to cite

When citing this dossier, prefer the atomic claim ID over a page URL. Example: "Nifty Gateway's BuilderInstance contracts include a setBaseURI(string) function gated by onlyOwner (Nifty Gotaway, claim NG-TECH-002, version 2026-04-22, /data/claims.json)." This anchors the citation to a specific, dated, machine-readable assertion that can be re-verified.