# Doginal Dogs Marketplace Incident Archive - full text Independent archive; not affiliated with Doginal Dogs or its operators. Information as of Oct 28 2026. Published pseudonymously by Ledger Hound. Canonical site: https://doginaldogs.info ====================================================================== Doginal Dogs marketplace exploit, October 26 2026 - https://doginaldogs.info/ ====================================================================== On October 26 2026 (UTC), six Dogecoin transactions spent 264 Doginal Dogs inscriptions out of wallets that had listed them on the Doginal Dogs Marketplace (market.doginaldogs.com). The six transactions pay out one small amount in total, 0.338582 DOGE, to one address. This archive collects the public, checkable facts, with a primary link for each. Summary of what is documented What happened on-chain. Six transactions, first seen between 10:56:10 and 10:56:48 UTC on Oct 26 2026, confirmed in Dogecoin blocks 6431226 and 6431231. They spend 264 inscription-carrying inputs and each has one output, to the same recipient address. See the timeline and transactions.csv. What the inputs have in common. All 264 inputs carry a seller signature of type 0x82 (SIGHASH_NONE|ANYONECANPAY). That type commits to the one input being signed and to no outputs, so it does not fix a price or a payee. See the technical explainer. What the code says. Archived and live client code of the marketplace uses 0x82 for seller listing signatures. A comment in the same source file describes SIGHASH_SINGLE|ANYONECANPAY. See evidence and methodology. Where the inscriptions went. In our analysis of ordinal sat flow, 201 of the 264 inscriptions reached the recipient address and 63 went to miner coinbase outputs. Estimated size. Our estimates range from about USD 0.3 million to about USD 1.5 million depending on the price basis. These are estimates, not realizable proceeds. See scale and value. Current state. As of Oct 28 2026 the marketplace site shows a “Trading temporarily paused” notice. We did not find an official statement about the Oct 26 transactions. See the status log. What this archive does not claim This archive does not state why the transactions happened, who is behind the recipient address, or whether anyone acted with any intention. The evidence we have is consistent with a design flaw in how listing signatures were constructed. Intent cannot be determined from public data. Read what we cannot know and the open questions. Where to read next Timeline of dated events with links. Technical explainer: 0x82 versus 0x83, with a short code excerpt. Scale and value: estimate method and the “largest incident” question. Evidence and methodology, with SHA-256 hashes and archive links. Precedent: how other marketplaces responded to a similar signature problem. Other markets: a comparison of seller-signature handling. Community reactions, attributed and limited to public posts. Timing and public silence: dated public X posts around the transactions, elapsed times, posting counts and unanswered public questions. Status log: dated, append-only checks of the live site. Claims and sources, FAQ, corrections policy, about. Date note: the transactions were first seen at 10:56 UTC on October 26 2026, which is 3:56 AM Pacific time on Oct 26. Some public posts date the event to Oct 27, probably by when they noticed it. This archive uses the on-chain timestamps. ====================================================================== Timeline - https://doginaldogs.info/timeline ====================================================================== Each entry has a time and, where possible, a link to a primary source. Times are shown in UTC and in Pacific time (US Pacific). The same list is available as timeline.json. 2025-10-26 16:14:29 UTC / 2025-10-26 09:14:29 AM PDT (US Pacific) — Earliest Wayback Machine capture we found of the marketplace client code containing the listing-signing constant 130 (0x82). Later archived captures that we checked up to 2026-08-31 also contain it. evidence manifest 2026-10-04 16:16:39 UTC / 2026-10-04 09:16:39 AM PDT (US Pacific) — Wayback Machine capture of the marketplace homepage that references the earlier deployment (dpl_Bw2ugc...). We diffed its client code against the live deployment saved on Oct 27 (dpl_HqzywgG...). The live deployment adds a maintenance banner and a pause notice. In our diff the listing-signing code is otherwise unchanged. When the later deployment went live is not known to us. Wayback capture 2026-10-21 09:09:24 UTC / 2026-10-21 02:09:24 AM PDT (US Pacific) — On-chain marketplace sale transaction: the seller's input uses sighash 0x82 and the seller output is 45,599.05 DOGE. transaction 2026-10-21 17:45:19 UTC / 2026-10-21 10:45:19 AM PDT (US Pacific) — On-chain marketplace sale transaction: the seller's input uses sighash 0x82 and the seller output is 57,000 DOGE. transaction 2026-10-26 10:56:10 UTC / 2026-10-26 03:56:10 AM PDT (US Pacific) — First of six transactions first seen on the Dogecoin network. Each spends many inscription-bearing outputs previously signed with sighash 0x82 and pays a single output to one address (D6ZJ...). The six transactions are first seen between 10:56:10 and 10:56:48 UTC. first transaction 2026-10-26 11:09:31 UTC / 2026-10-26 04:09:31 AM PDT (US Pacific) — Block 6431226 confirms four of the six transactions (200 inputs). In our analysis, 153 of the inscriptions in these inputs reached the recipient address and 47 went to the block's coinbase output. 2026-10-26 11:13:08 UTC / 2026-10-26 04:13:08 AM PDT (US Pacific) — Block 6431231 confirms the other two transactions (64 inputs). In our analysis, 48 inscriptions reached the recipient address and 16 went to that block's coinbase output. 2026-10-27 04:44:18 UTC / 2026-10-26 09:44:18 PM PDT (US Pacific) — Archive snapshot of the live marketplace site (index, terms page, client chunks, public API responses). The site displays a notice titled 'Trading temporarily paused'. evidence manifest 2026-10-28 17:26:46 UTC / 2026-10-28 10:26:46 AM PDT (US Pacific) — Second snapshot of the live site. The homepage, terms page and the checked JavaScript chunks are hash-identical to the 2026-10-27 snapshot. See the status log. status log Public posts before and after these events, with elapsed hours from the first-seen time, are on the Timing and public silence page. The six transactions Output is the amount paid to the recipient address D6ZJAGkdFJn9cb3y2QAVwv5QtMXfVHihZ4. Fee is the difference between input and output values, in koinu (1 DOGE = 100,000,000 koinu). TransactionFirst seen (UTC)BlockInputsOutput (koinu)Fee (koinu) 270923fb…efd0910:56:106431231506,216,4001,483,600 afc108a0…9603010:56:246431226507,116,8001,483,200 a30d52e7…435d410:56:3164312265011,615,0001,485,000 c63498b5…0ecf2e10:56:386431226503,517,6001,482,400 75eb61bb…83f05f10:56:446431226503,514,4001,485,600 20381ce9…464ab10:56:486431231141,878,000422,000 Total output: 33,858,200 koinu (0.338582 DOGE). Total fee: 7,841,800 koinu (0.078418 DOGE). First-seen times are the timestamps recorded in our analysis, to the millisecond, in transactions.csv. ====================================================================== Technical explainer: sighash 0x82 versus 0x83 - https://doginaldogs.info/technical-explainer ====================================================================== This page explains, in plain terms, the signature detail that all 264 spent inputs have in common. It describes mechanics only. It does not say why the code was written that way or who is responsible for any outcome. What a sighash type controls A Dogecoin (Bitcoin-style) signature is made over a hash of selected parts of a transaction. A one-byte “sighash type” appended to the signature says which parts the signer committed to. Anything not committed to can be changed by whoever assembles the final transaction without invalidating that signature. ByteNameInputs committedOutputs committed 0x01SIGHASH_ALLall inputsall outputs 0x82SIGHASH_NONE | SIGHASH_ANYONECANPAYonly the signed inputno outputs 0x83SIGHASH_SINGLE | SIGHASH_ANYONECANPAYonly the signed inputonly the output with the same index as the signed input For an inscription listing, the seller signs the input that holds the inscription. With 0x83 the seller can pin one output, for example the seller’s payout. With 0x82 the signature leaves every output open, so it does not fix a price or a payee. Bitcoin documentation describes these types: see the Bitcoin Wiki on signature hash types. What the archived code says The marketplace client code is served publicly together with source maps. We extracted the file lib/wallet/listing-signer.ts from the live site on Oct 27 2026 UTC (04:44 UTC; the evening of Oct 26 Pacific time) (SHA-256 in the evidence manifest). Two short excerpts follow, quoted for analysis. /** * Listing signer builds the seller-side template for Doginal marketplace listings using * a pure P2PKH flow. The seller signs their inscription input with SIGHASH_SINGLE | * SIGHASH_ANYONECANPAY so that buyers can later rewrite the inscription output while * outputs at index 0 and 1 (seller payout + marketplace fee) remain fixed. */ 38: const SIGHASH_TYPE = 0x82; // SIGHASH_NONE | SIGHASH_ANYONECANPAY ... 138: const sighashFlag = crypto.Signature.SIGHASH_NONE | crypto.Signature.SIGHASH_ANYONECANPAY; The header comment describes SIGHASH_SINGLE|ANYONECANPAY (0x83). The constant and the flag used in the signing function are SIGHASH_NONE|ANYONECANPAY (0x82). Whether the difference was intended, known, or noticed before Oct 26 is not something the code can tell us. See open questions. How long the 0x82 constant has been in the client code Archived copies of the marketplace’s app JavaScript from the Internet Archive contain the value 130 (0x82) in the listing-signing code. The earliest capture we found is dated 2025-10-26. Captures we checked up to 2026-08-31 also contain it. Each capture has a link and a SHA-256 on the evidence page. In the captures we compared, we did not see the signing code differ in this respect. What the six transactions show Every one of the 264 inputs carries a signature ending in byte 0x82 (inputs.csv, one row per input). Each of the six transactions has exactly one output, to address D6ZJAGkdFJn9cb3y2QAVwv5QtMXfVHihZ4. Marketplace sales on Oct 21 2026 that we checked also show 0x82 on the seller’s input (see the timeline), so the type was in ordinary use before Oct 26. What on-chain data does not show is how the signed inputs came to be in the hands of whoever built the six transactions. That is covered in what we cannot know. Why 63 inscriptions went to miners A doginal inscription is attached to a specific unit (a koinu) inside an output. When a transaction spends inputs, units flow to outputs in order. If the outputs’ total value is smaller than the position of an inscribed unit, that unit flows into the transaction fee and then to the miner of the block, in the coinbase transaction. In these transactions the single output was small (0.019 to 0.116 DOGE) compared with the combined value of up to 50 inputs, and the fee was about 0.0148 DOGE for each of the five 50-input transactions (0.0042 DOGE for the 14-input one). In our analysis, 201 of 264 inscriptions reached the recipient address and 63 went to the coinbase outputs of the two blocks. Per-input results are in inputs.csv. This is our computation from the ordinals flow rules; it can be checked with any doginal indexer, and indexers may differ. The 63 are discussed in open questions. What the marketplace terms say The Terms page served at market.doginaldogs.com/legal (archived and hashed on the evidence page) describes the service as provided “as is”, includes a limitation of liability that mentions “loss of funds”, and states that a user’s sole remedy is to stop using the site. It describes the operator as “an independent online collective”. We quote these only for completeness. We express no view on how they apply. ====================================================================== Scale and value - https://doginaldogs.info/scale-and-value ====================================================================== The six transactions spent 264 inscriptions. Our estimate of their market value is about USD 0.3 million to USD 1.5 million, depending on which price is used. This is an estimate of what the items were priced at, not of what anyone received or lost. A floor price is not a realizable value. How many 264 inscription-carrying inputs were spent in the six transactions (inputs.csv). Public posts have also said 265; we count 264. 201 reached the recipient address in our sat-flow analysis; 63 went to miner coinbase outputs (how). The 264 inputs were signed by 194 distinct seller addresses in our analysis. 49 of those addresses had at least one inscription go to a miner, and 42 had all of theirs go to a miner. A third-party post on X also says “194 wallets”, which matches our count. Seller addresses are not published here. Method Choose a DOGE price per item (four scenarios below, each from a cited source). Multiply by the item count (264 or 201). Convert with a DOGE/USD reference price. We use USD 0.07704 per DOGE, the CoinGecko hourly value near the transactions (2026-10-26 11:00 UTC). The range across Oct 26 to Oct 28 was 0.0767 to 0.0804 (doge_usd_reference.csv). ScenarioPrice basisDOGE per itemUSD per itemUSD total, 264 itemsUSD total, 201 items S1Lowest listed price on doggy.market, page retrieved Oct 28 202619,9001,533405,000308,000 S2Floor price in the marketplace’s own stats API, snapshot Oct 27 UTC (may be stale; see below)47,0003,621956,000728,000 S4Mean of two on-chain marketplace sales on Oct 21 2026 (57,000 and 45,599.05 DOGE)51,3003,9521,043,000794,000 S330-day average sale price in the marketplace’s stats API (29 trades), snapshot Oct 27 UTC71,4095,5011,452,0001,106,000 Full figures, including totals at the low and high DOGE/USD prices, are in value_estimates.csv. Rounded to the nearest thousand dollars. Why these are estimates, and why floor is not realizable value Thin market. On the doggy.market page we read, 36 items were listed. Selling hundreds of items into that depth would have moved the price. Items differ. A floor price is the cheapest listing, usually for common traits. Items with rarer traits may be worth more or less. Stale data. The marketplace’s own stats API reported 0 listed items on Oct 27 UTC and Oct 28, with the same floor price (47,000 DOGE). That floor may therefore be carried over from before trading was paused. Few sales. S4 uses two sales; S3 uses 29 trades over 30 days, a small sample. Not a loss figure. We do not know what holders realized, what they would have realized, or whether any items will be returned or restored. Dogecoin price moves also change every USD figure. Checking common public figures Figure seen in public discussionWhat we found About 264 to 265 items264 spent inputs. 265 not supported by our count. Floor around USD 1,500 on doggy.marketConsistent: 19,900 DOGE, shown as about USD 1,586 on the page on Oct 28 (USD 1,533 at our reference price). Floor around USD 4,500 on the marketplaceNot supported at Oct 26 prices. The marketplace’s stats floor of 47,000 DOGE is about USD 3,600. We did not find a primary source for USD 4,500 on Oct 26. “Biggest NFT hack ever”Not supported by our estimates. See below. Is it the largest incident? We do not rank incidents here, because the incident types differ and values are estimates. For context, on the precedent page two earlier incidents that we verified had reported USD figures higher than our upper estimate: the OpenSea phishing wave of Feb 2022 (254 NFTs, about USD 1.7 million reported) and the Bored Ape Yacht Club Instagram compromise of Apr 2022 (about 91 NFTs, about USD 2.8 million reported). By item count, 264 is higher than both. Larger incidents involving other assets exist, and we did not attempt a full survey. Within the Dogecoin inscription ecosystem, we did not find a larger single event, but our search was not exhaustive, so we do not assert that this is the largest. ====================================================================== Evidence and methodology - https://doginaldogs.info/evidence ====================================================================== Every factual statement on this site is meant to be checkable. This page lists the primary sources and shows how each finding was derived. Third-party files are not republished here; the manifest gives the original or archive URL and the SHA-256 of the file as we retrieved it, so you can re-fetch and compare. On-chain evidence All six transactions can be opened in any Dogecoin block explorer. The full IDs, block heights, input and output counts, fees and explorer links are in transactions.csv. Per-input results (sighash byte and where each inscription ended up) are in inputs.csv. Recipient address: D6ZJAGkdFJn9cb3y2QAVwv5QtMXfVHihZ4 (SoChain). Blocks: 6431226 (confirmed 2026-10-26 11:09:31 UTC) and 6431231 (confirmed 2026-10-26 11:13:08 UTC). Methodology Transactions. We read the six transactions and their previous outputs from a public block-explorer API (BlockCypher transaction format; SoChain links are given for convenience), and parsed each input script to read the final byte of the signature (the sighash type). Inscription location. For each input we looked up which inscription it held using a public inscription-lookup API for inscription numbers and holdings, and computed its position with the ordinals sat-flow rule (units flow from inputs to outputs in order, and then to the fee, then to the miner). This gave 201 delivered and 63 to coinbase outputs. Indexers can differ. The six transactions are public, so the computation can be repeated and checked. Client code. We downloaded the live marketplace pages, JavaScript chunks and publicly served source maps on Oct 27 UTC (Oct 26 Pacific time) and Oct 28 2026, hashed them, and extracted the signing source file. We compared archived chunks from the Internet Archive across 2025 and 2026 to see when the 0x82 constant appeared. Deployment comparison. We diffed the client code of an archived deployment (Oct 4 2026) with the live deployment saved on Oct 27 UTC (Oct 26 Pacific time) 2026. The differences we found were a maintenance banner, a new “Trading temporarily paused” notice component, deployment identifiers and styling classes. We found no change in the signing code or listing structures. Live-site re-check. On Oct 28 2026 we re-fetched the same files. The homepage, terms page and the JavaScript chunks we listed were byte-identical (same SHA-256) to the Oct 27 UTC (Oct 26 Pacific time) files. See the status log. Prices. Documented on scale and value. Limits The Internet Archive does not capture every file on every day. Absence of a capture is not evidence of absence of a change. Source maps show the source that was compiled. We did not see the marketplace’s server-side code or databases. Our reading of 0x82 describes what the signature commits to. It does not tell us how the signed inputs were obtained (see what we cannot know). We may be wrong. If you find an error, use the corrections process. How to verify a hash Download the file from the URL in the table (for archived files use the “id_” raw form where given) and run sha256sum file. The value should match. For live files, the live site may have changed since the capture time shown. Evidence manifest (44 items) Machine-readable: evidence_manifest.json. IDCaptured (UTC)DescriptionSourceSHA-256 wb-js-20251026161429-5050e6bc2025-10-26T16:14:29ZArchived client JavaScript chunk from the marketplace site in which the seller listing-signing constant 130 (0x82) appearsarchivea91ee49630f5d98279d66e13c56e178ca3a15a7370d70b4fb8c98960d6532a90 wb-js-20251031020111-e470a9592025-10-31T02:01:11ZArchived client JavaScript chunk from the marketplace site in which the seller listing-signing constant 130 (0x82) appearsarchived6e6344d3348c263b107f7931a63dc36b9828a210adffb5b2d001dc3156607af wb-js-20251111233905-6d89bcfb2025-11-11T23:39:05ZArchived client JavaScript chunk from the marketplace site in which the seller listing-signing constant 130 (0x82) appearsarchive0d22b5d4ad8c390ce2ce755dbf8cc21d3b736fdcd3d1015d81d74fb412a95ac1 wb-js-20260107222614-f70a69442026-01-07T22:26:14ZArchived client JavaScript chunk from the marketplace site in which the seller listing-signing constant 130 (0x82) appearsarchive0b52e570e5d079c73e91d00ba513f890d8a65c472634bce61a7cf3c975133511 wb-js-20260130052958-d52a24332026-01-30T05:29:58ZArchived client JavaScript chunk from the marketplace site in which the seller listing-signing constant 130 (0x82) appearsarchiveaec14258986bcdde15041366cba3ef160b90d47106a358c3f2531e4271ecdb84 wb-js-20260227140714-832f6de72026-02-27T14:07:14ZArchived client JavaScript chunk from the marketplace site in which the seller listing-signing constant 130 (0x82) appearsarchiveb59efb64a5fcdea88fcf3833dbba1c1cda3aa353f24ce2ad56ec46a7bcdebae3 wb-js-20260228065807-e9ac76e72026-02-28T06:58:07ZArchived client JavaScript chunk from the marketplace site in which the seller listing-signing constant 130 (0x82) appearsarchive6efb80f39d7fee77a24b8e1e0d83f0c41265988e649eebcdea638b10b2fa102c wb-js-20260302054918-fede95ac2026-03-02T05:49:18ZArchived client JavaScript chunk from the marketplace site in which the seller listing-signing constant 130 (0x82) appearsarchive932dc71eab938f2665e93fda7b8585943ca38077533a20233ef30fc098e2f3cd wb-js-20260325225327-b654bb3b2026-03-25T22:53:27ZArchived client JavaScript chunk from the marketplace site in which the seller listing-signing constant 130 (0x82) appearsarchivee5d2c65b8603d549a56e6e0b1f145476124915860a97be70b9cbe71c3e8952c0 wb-js-20260401195139-68f206382026-04-01T19:51:39ZArchived client JavaScript chunk from the marketplace site in which the seller listing-signing constant 130 (0x82) appearsarchive754cd8e799306888a320af557bc65dab135f00e3f7d76df13e998b3462ac4175 wb-js-20260412222709-157d6e572026-04-12T22:27:09ZArchived client JavaScript chunk from the marketplace site in which the seller listing-signing constant 130 (0x82) appearsarchive3c146c3306f30b061f42ad5dc5c4e1a833a315cbae9f2d2f6c26abc02e06bfaf wb-js-20260415034827-3f15b4b22026-04-15T03:48:27ZArchived client JavaScript chunk from the marketplace site in which the seller listing-signing constant 130 (0x82) appearsarchive7efb5e5ccc9b3f382008489ce35ef263577e99bee4987053fb1b372295b6e4ec wb-js-20260428034724-ca7a38472026-04-28T03:47:24ZArchived client JavaScript chunk from the marketplace site in which the seller listing-signing constant 130 (0x82) appearsarchive95cd947e656ee60b832bab6d6df87ad71793959332ee45522b7b2e3df111baa2 wb-js-20260506183612-a3dd3e692026-05-06T18:36:12ZArchived client JavaScript chunk from the marketplace site in which the seller listing-signing constant 130 (0x82) appearsarchiveaa7136fcf2268b65a2f65cc6d2d0dec2c65190dcb2c07bbb5099a98447db51d9 wb-js-20260611001254-7ac6615b2026-06-11T00:12:54ZArchived client JavaScript chunk from the marketplace site in which the seller listing-signing constant 130 (0x82) appearsarchivebbd9bc17007f11917b10a4a94f2674cddd50d17b9bb3713643634fd7160b3efd wb-js-20260831091024-27593a1b2026-08-31T09:10:24ZArchived client JavaScript chunk from the marketplace site in which the seller listing-signing constant 130 (0x82) appearsarchive0fa26c52e1291c08805250ce6fd3e6a5d643ef46899cdc7b9ed23d8faf54f208 wb-js-20260831091039-6132006f2026-08-31T09:10:39ZArchived client JavaScript chunk from the marketplace site in which the seller listing-signing constant 130 (0x82) appearsarchive1f5e5ecc549455a83ca7d845472b5ba38b6cf74a42937cf6ea2a920000358aea wb-home-202510261614012025-10-26T16:14:01ZArchived marketplace homepagearchive2d61175d9cf504637405c434d58d349499aeea7991f2b620059b012aa02a107d wb-home-202511112243552025-11-11T22:43:55ZArchived marketplace homepagearchive9934b372b035468189e0dcf7ebd3f5afb1d37feb0438e9f431acd201952508f6 wb-home-202601071008282026-01-07T10:08:28ZArchived marketplace homepagearchive789fd8dd5199aa7b191200611ad88169440fb70c84e156b7ca7e5cd3829997a6 wb-home-202603020148222026-03-02T01:48:22ZArchived marketplace homepagearchiveef025d6a78fa24ee154ce3714d163784db3c0f0913988d960f3d4233378ec27b wb-home-202603252253252026-03-25T22:53:25ZArchived marketplace homepagearchive165839c30fc214186451c9f8060e883c94a323ca92b1964b8e9be306de93c41f wb-home-202604011838232026-04-01T18:38:23ZArchived marketplace homepagearchive8b3debf069148166bef62a65949064985f872070cfb7949b59fd06af508e53c4 wb-home-202605061751542026-05-06T17:51:54ZArchived marketplace homepagearchive34f34da221c35e4018a37b4683bf5569fd1cd96cc3a3c0e15fa4b0fd0120d95b wb-home-202606110012542026-06-11T00:12:54ZArchived marketplace homepagearchive006535e786243acb59468402c81a75b40f56669a45591b3c38611ae2934fc358 wb-home-202608310910342026-08-31T09:10:34ZArchived marketplace homepagearchive6ce6f37d207cb21933fa9b6ffe769f89aa26fee8808792994ab770b6e036c42c wb-home-202610041616392026-10-04T16:16:39ZArchived marketplace homepagearchive6ce6f37d207cb21933fa9b6ffe769f89aa26fee8808792994ab770b6e036c42c wb-legal-202608310910342026-08-31T09:10:34ZArchived marketplace terms (legal) pagearchivef98fdc792757c24dbb0e35b8889ff2b2f358e715ce42c304eb486ae73b2e2370 wb-legal-202610042255322026-10-04T22:55:32ZArchived marketplace terms (legal) pagearchivef98fdc792757c24dbb0e35b8889ff2b2f358e715ce42c304eb486ae73b2e2370 live-oct27-index.html2026-10-27T04:44:18ZLive marketplace homepage HTMLoriginal URL5b4f408a6c2824523c50d70c0211cb3d528c8da6148b037fa974b706c53278ae live-oct27-legal.html2026-10-27T04:44:18ZLive marketplace terms (legal) page HTMLoriginal URLb6dad3c033b26c584687af6d483581c6ca2521b10018c23eeaf0a6759263db5e live-oct27-page-62026-10-27T04:44:18ZLive client chunk app/page (contains the listing-signing code)original URL85dace8c5509178f3c07db5219eb4c9e402fbb9152ad8ae133bc4fc4d64ebb20 live-oct27-layout2026-10-27T04:44:18ZLive client chunk app/layout (contains the paused-trading notice)original URL13102d7401e58b432b28cb2d125e20c58faef06282549c03752d3067995a90e1 live-oct27-listings.getStats.json2026-10-27T04:44:18ZLive listings.getStats API response (public read)original URL1d43214524b81b58c2087b89e795ac46a1eaad2460b7786cbe0ef52ae64ec7dc live-oct27-team.getPublicConfig.json2026-10-27T04:44:18ZLive team.getPublicConfig API response (public read)original URL66a9a6c1d30fd6bbd67f4712d276f5e084968497acf6785c4a721ba1dcd8cd50 live-oct28-index.html2026-10-28T17:26:46ZLive marketplace homepage HTMLoriginal URL5b4f408a6c2824523c50d70c0211cb3d528c8da6148b037fa974b706c53278ae live-oct28-legal.html2026-10-28T17:26:46ZLive marketplace terms (legal) page HTMLoriginal URLb6dad3c033b26c584687af6d483581c6ca2521b10018c23eeaf0a6759263db5e live-oct28-page-62026-10-28T17:26:46ZLive client chunk app/page (contains the listing-signing code)original URL85dace8c5509178f3c07db5219eb4c9e402fbb9152ad8ae133bc4fc4d64ebb20 live-oct28-layout2026-10-28T17:26:46ZLive client chunk app/layout (contains the paused-trading notice)original URL13102d7401e58b432b28cb2d125e20c58faef06282549c03752d3067995a90e1 live-oct28-listings.getStats.json2026-10-28T17:26:46ZLive listings.getStats API response (public read)original URL229f7668b71ca35faaf73033dca3d87bfdb56643c01a9652e5e9350eddf64aef live-oct28-team.getPublicConfig.json2026-10-28T17:26:46ZLive team.getPublicConfig API response (public read)original URL66a9a6c1d30fd6bbd67f4712d276f5e084968497acf6785c4a721ba1dcd8cd50 wb-save-202610281728362026-10-28T17:28:36ZWayback Machine capture of the live marketplace homepage, requested 2026-10-28; the Internet Archive availability API listed this capture when checked 2026-10-28archiven/a (link only) src-sourcemap-app-page2026-10-27T04:44:18ZSource map served publicly by the marketplace for the app/page client chunk (contains the original text of lib/wallet/listing-signer.ts)original URL6f3ca5718f0793c7ebb75513d8f9ab8b1a2ccf7cf3f7faf2b2fb3bc63ca3f891 src-listing-signer-ts2026-10-27T04:44:18Zlib/wallet/listing-signer.ts as extracted from the source map above (sourcesContent entry); excerpts are quoted on the technical explainer pageoriginal URL809f2abba9e9558c9d5d5e950fad7f39c76bd190a18cb2b1741b9e69f76c2969 ====================================================================== What we cannot know - https://doginaldogs.info/what-we-cannot-know ====================================================================== Public blockchain data and archived web pages show what happened to the inscriptions. They do not show why, who was involved, or what anyone knew. This page lists what the evidence cannot establish. Intent is unproven. The evidence we have is consistent with a design flaw in how listing signatures were constructed, and it is also consistent with other explanations that we cannot rule in or out. Intent of any person We do not know why the 0x82 type was chosen, whether the difference between the code comment (SINGLE|ANYONECANPAY) and the constant (NONE|ANYONECANPAY) was noticed, or whether anyone at the marketplace knew of the risk before Oct 26. A code comment that disagrees with the code is a common kind of mistake in software, and we do not read intent into it. Nothing on this site states or implies that the marketplace’s developers, operators or any other named or unnamed person acted deliberately, took anything, or wished anyone harm. Who controls the recipient address The six transactions paid one address. An address on a blockchain is not an identity. We do not know who controls it, whether one person or several do, or whether they are connected to the marketplace, to any holder, or to anyone else. We do not name or speculate about anyone. How the signed inputs were obtained A 0x82 signature can be attached to a different transaction by anyone who has the signed input. The chain data does not show where the six transactions’ builder obtained the 264 signed inputs: from a marketplace interface, from stored data, from intercepted traffic, or in some other way. The marketplace’s server-side behavior is not visible to us. What was known, and when We know the 0x82 constant appears in archived code from 2025-10-26 onward. We do not know when anyone first understood its consequences. We know that between archived deployments of Oct 4 2026 and Oct 27 2026 a maintenance banner and a “Trading temporarily paused” notice were added, and that the notice mentions “AI-driven exploits on the rise across the internet” and “upgraded protections”. We do not know the date these were enabled, and we do not know whether they relate to the Oct 26 transactions. The sequence is shown on the evidence page and in the status log; we draw no conclusion from it. Private communications Public posts say that the team has contacted at least one holder privately. We have not seen any such message and cannot verify it. We do not know what, if anything, has been said or promised in private. What will happen next We do not know whether the inscriptions will be returned, whether any holders will be compensated, whether the recipient will respond, or whether the 63 inscriptions that went to miner outputs can be recovered. We also do not know the true number of affected people beyond our count of 194 distinct seller addresses, since one person can control many addresses and one address can be shared. Value Our dollar figures are estimates based on listed and sold prices (scale and value). They are not a measure of anyone’s loss. Limits of this archive We can make mistakes. We read public data only and did not contact the marketplace’s operators before publishing. Anyone named by implication or affected may point to a public, verifiable source; see the corrections policy. ====================================================================== Open questions - https://doginaldogs.info/open-questions ====================================================================== These are factual questions that public sources do not answer. They are addressed to the operators of the Doginal Dogs Marketplace and, where noted, to others. They are not accusations, and they do not assume any particular answer. If a public, verifiable source answers one of them, the page is updated and the change is logged (corrections policy). Timing. When did the operators first learn that listing signatures made with 0x82 do not commit to any output? Was this before or after Oct 26 2026 at 10:56 UTC? Design choice. Why does the signing code use SIGHASH_NONE|ANYONECANPAY (0x82) while the comment in the same file describes SIGHASH_SINGLE|ANYONECANPAY (0x83)? Has the difference been reviewed? Access to signed listings. How are signed listing templates stored and served, and who could retrieve them before Oct 26? Maintenance notice. On what date were the maintenance banner and the “Trading temporarily paused” notice enabled, and what do “AI-driven exploits” and “upgraded protections” refer to? Statement. Is an official account of the Oct 26 transactions planned? As of Oct 28 2026 we did not find one (status log). Compensation. Will affected holders be compensated or restored, and on what basis? If so, how and when would affected holders be contacted? Terms. The Terms page includes an “as is” clause and a limitation of liability that mentions “loss of funds”. How do the operators view the application of those terms to these events? The 63. In our analysis, 63 inscriptions went to miner coinbase outputs in blocks 6431226 and 6431231. Who holds them now? Is there a plan to ask the holders to return them? (This question is also for the miners or pool operators concerned.) The recipient. Has anyone contacted the holder of the recipient address, and has that holder responded or returned anything? We do not know who that holder is. Remaining listings. Are other active listings signed with 0x82 still exposed? What has been done to cancel or invalidate them? Independent audit. Will the operators commission an independent security review of the listing and signing flow and publish its findings? Verification. Can the operators confirm or correct the figures on this site (264 inputs, 201 delivered, 63 to miners, six transaction IDs)? ====================================================================== Timing and public silence - https://doginaldogs.info/timing-and-public-silence ====================================================================== Last checked: 2026-10-29 00:10:00 UTC (Oct 28, 5:10:00 PM PDT). Reference time: the six transactions were first seen at 2026-10-26 10:56:10 UTC (Oct 26, 3:56:10 AM PDT) (see the timeline). All elapsed times below are measured from that moment. Pacific time is PDT (UTC−7) throughout this page. Key facts Before. On Oct 25 at 8:58:38 PM PDT (03:58:38 UTC on Oct 26), 6 h 57 min before the transactions were first seen, @barkmeta posted: “The entire internet is about to be one shot by AI.”, and “It’s only a matter of days.” After. 3 h 53 min after first seen, @barkmeta posted: “The entire internet is about to get hacked.” At 6 h 09 min after, it posted “Do not do anything important on the internet for the foreseeable future”, with the words “do NOT move money around right now” and “landmine”. “The great reset.” At 11 h 50 min after, @barkmeta posted “The great reset is here.” “The Great Reset” is also the name of a recurring X Space that @barkmeta hosts, documented in public posts since at least Aug 22 2026 (evidence below). Silence. Between 10:00 UTC on Oct 26 and the check time above, @barkmeta posted 71 times and @GodsBurnt 65 times (counts in the table). We did not find a post, reply or quote from either account that refers to the marketplace transactions, the lost inscriptions, or the marketplace. Not claimed. This page does not say that either account knew about, planned, took part in, or is responsible for the transactions, and it does not say who operates either account or the marketplace. See How to read this. What this page covers Two public X accounts, @barkmeta and @GodsBurnt, are quoted because other users’ public posts name them in connection with the Doginal Dogs project, and because they post often. We have not verified who operates either account, or whether they operate the marketplace. All quotes are short, exact, and linked. Each link is to a public post. Timestamps are the creation times reported by X’s public API. The data is also available as timing_posts.json. The same accounts also posted many times a day before and after the transactions; their counts are in the table below. Selecting a few posts from many is a limit of this page, and the list is not a complete record of everything either account posted. Visual timeline ● circle = @barkmeta post ■ square = @GodsBurnt post Heavy vertical line = transactions first seen (0 h) Numbers = hours before (−) or after (+) first seen One row per post. Circles are @barkmeta posts and squares are @GodsBurnt posts. The vertical line marks 10:56:10 UTC on Oct 26 2026. The table below lists the same posts with exact times.Oct 23Oct 24Oct 25Oct 26Oct 27Oct 28UTC midnights shown as grid lines@GodsBurnt Oct 22 20:34: THE WORLD AS YOU KNOW IT IS EN…−86.4 h@GodsBurnt Oct 23 02:12: EVERYTHING IS GETTING HACKED.−80.7 h@barkmeta Oct 23 14:58: Everything is getting hacked by…−68.0 h@barkmeta Oct 24 14:45: Everyone thought we had years t…−44.2 h@barkmeta Oct 25 16:00: You don't have enough crypto fo…−18.9 h@barkmeta Oct 25 17:43: Pretty soon, the internet as we…−17.2 h@barkmeta Oct 25 18:44: AGI is here. You’ve been warned.−16.2 h@barkmeta Oct 26 03:58: The entire internet is about to…−7.0 hFirst seen: Oct 26 10:56:10 UTC (3:56 AM PDT)0 h@barkmeta Oct 26 14:49: The entire internet is about to…+3.9 h@barkmeta Oct 26 17:05: Do not do anything important on…+6.2 h@GodsBurnt Oct 26 17:26: We’re about to experience a CY…+6.5 h@barkmeta Oct 26 19:05: Shut your devices off…+8.2 h@barkmeta Oct 26 22:46: The great reset is here.+11.8 h@GodsBurnt Oct 27 14:05: Any moment now everything is g…+27.2 h@barkmeta Oct 27 14:39: In the next few days, there wil…+27.7 h@barkmeta Oct 27 19:42: The Great Reset is starting.+32.8 h@GodsBurnt Oct 28 14:52: This was all a big bear trap...+51.9 h The scale is linear in hours, from 90 h before to 56 h after. Posts that are close in time overlap in the horizontal position but have separate rows. The tables below give the exact times. 1. Posts before the transactions These are posts by the two accounts in the four days before the transactions that describe AI-driven hacking or collapse. They are general statements about AI, banks, crypto and websites. None of them mentions the marketplace. Some were written 3 days before, and the latest was written 6 h 57 min before. Posted (UTC / Pacific)AccountQuoteRelative to first seen (10:56:10 UTC)Link 2026-10-22 20:34:58 UTC 2026-10-22 01:34:58 PM PDT (US Pacific)@GodsBurnt“THE WORLD AS YOU KNOW IT IS ENDING.” Opening line of a longer post about AI and preparing. Does not mention the marketplace.3 d 14 h 21 min before (-86.35 h)post 2026-10-23 02:12:24 UTC 2026-10-22 07:12:24 PM PDT (US Pacific)@GodsBurnt“EVERYTHING IS GETTING HACKED.” Quote post. The same post continues: "Now Quest Diagnostics just got hacked too."3 d 8 h 43 min before (-80.73 h)post 2026-10-23 14:58:43 UTC 2026-10-23 07:58:43 AM PDT (US Pacific)@barkmeta“Everything is getting hacked by AI…” Continues: "Banks, Crypto, Investment portfolios, Websites, etc" and "what do we buy at this point?"2 d 19 h 57 min before (-67.96 h)post 2026-10-24 14:45:31 UTC 2026-10-24 07:45:31 AM PDT (US Pacific)@barkmeta“Everyone thought we had years to prepare for AI. We don't.” About AI and jobs.1 d 20 h 10 min before (-44.18 h)post 2026-10-25 16:00:32 UTC 2026-10-25 09:00:32 AM PDT (US Pacific)@barkmeta“You don't have enough crypto for what's about to happen next.” No further detail in the post.18 h 55 min 38 s before (-18.93 h)post 2026-10-25 17:43:55 UTC 2026-10-25 10:43:55 AM PDT (US Pacific)@barkmeta“Pretty soon, the internet as we know it won’t exist.” About AI replacing apps and browsers.17 h 12 min 15 s before (-17.20 h)post 2026-10-25 18:44:10 UTC 2026-10-25 11:44:10 AM PDT (US Pacific)@barkmeta“AGI is here. You’ve been warned.”16 h 12 min 00 s before (-16.20 h)post 2026-10-26 03:58:38 UTC 2026-10-25 08:58:38 PM PDT (US Pacific)@barkmeta“The entire internet is about to be one shot by AI.” Continues: "Every website. Every software. Every IP. It’s only a matter of days."6 h 57 min 32 s before (-6.96 h)post The Oct 25 8:58:38 PM PDT post (2114567352373350429) is the closest to the transactions in time. Its text was posted on Oct 26 at 03:58:38 UTC; the first transaction was first seen at 10:56:10 UTC the same day. 2. Posts after the transactions These posts continue the same theme after the transactions. None names the marketplace or the Oct 26 transactions. Posted (UTC / Pacific)AccountQuoteRelative to first seen (10:56:10 UTC)Link 2026-10-26 14:49:11 UTC 2026-10-26 07:49:11 AM PDT (US Pacific)@barkmeta“The entire internet is about to get hacked.” @barkmeta’s first post after a gap of 9 h 12 min (see the posting-gaps table).3 h 53 min 01 s after (+3.88 h)post 2026-10-26 17:05:49 UTC 2026-10-26 10:05:49 AM PDT (US Pacific)@barkmeta“Do not do anything important on the internet for the foreseeable future.” Continues: "Especially money… do NOT move money around right now." The post uses the word "landmine".6 h 09 min 39 s after (+6.16 h)post 2026-10-26 17:26:45 UTC 2026-10-26 10:26:45 AM PDT (US Pacific)@GodsBurnt“We’re about to experience a CYBER PANDEMIC.” Also: "Everything will crash or be hacked and life as you know it will cease to exist."6 h 30 min 35 s after (+6.51 h)post 2026-10-26 19:05:37 UTC 2026-10-26 12:05:37 PM PDT (US Pacific)@barkmeta“Shut your devices off…” Continues: "The world is about to change forever."8 h 09 min 27 s after (+8.16 h)post 2026-10-26 22:46:48 UTC 2026-10-26 03:46:48 PM PDT (US Pacific)@barkmeta“The great reset is here.” Starts "It’s happening…". Edited 31 seconds later; the first version contained "Buckle up." and the edited version (2114851397565075737) does not. "The Great Reset" is also the name of a recurring Space (see below).11 h 50 min 38 s after (+11.84 h)post 2026-10-27 14:05:20 UTC 2026-10-27 07:05:20 AM PDT (US Pacific)@GodsBurnt“Any moment now everything is going to go parabolic.” Tone change: describes AI harm as "so small compared to all the good that is about to happen."1 d 3 h 09 min after (+27.15 h)post 2026-10-27 14:39:47 UTC 2026-10-27 07:39:47 AM PDT (US Pacific)@barkmeta“In the next few days, there will be a massive data leak.” Posted after other accounts had begun posting about the marketplace on X.1 d 3 h 43 min after (+27.73 h)post 2026-10-27 19:42:14 UTC 2026-10-27 12:42:14 PM PDT (US Pacific)@barkmeta“The Great Reset is starting.” Quote post of a Reuters post (2115155318585930226) about an attempted breach of the US Federal Election Commission.1 d 8 h 46 min after (+32.77 h)post 2026-10-28 14:52:28 UTC 2026-10-28 07:52:28 AM PDT (US Pacific)@GodsBurnt“This was all a big bear trap... A final shakeout.” Also: "Everything was getting hacked, people we're afraid to touch the internet" and "the world did, in fact, not end."2 d 3 h 56 min after (+51.94 h)post One post was edited 31 seconds after it was published The “great reset is here” post was published at 2026-10-26 22:46:48 UTC (Oct 26, 3:46:48 PM PDT) and edited at 2026-10-26 22:47:19 UTC (Oct 26, 3:47:19 PM PDT). The first version (2114851265851330655) contained the line “Buckle up.” The edited version (2114851397565075737) does not. X’s API lists both IDs in the post’s edit history. We do not know why the edit was made. “The Great Reset” is also the name of a recurring Space Public posts by other users, and two announcement posts by @barkmeta, show that “The Great Reset” was already the name of a daily X Space at about 5 PM Eastern time (21:00 UTC) before the transactions: Posted (UTC / Pacific)AccountWhat the post saysLink 2026-08-22 21:01:27 UTC (Aug 22, 2:01:27 PM PDT)@zackmetax“Bark is live with the great reset”post 2026-08-25 21:02:22 UTC (Aug 25, 2:02:22 PM PDT)@KeyMetaXReply to @barkmeta: “The space to be” and “The Great Reset”post 2026-09-08 21:43:44 UTC (Sep 8, 2:43:44 PM PDT)@carbonemetax“Bark, Shibo and Shield are live in The Great Reset @doginaldogs space”post 2026-10-02 21:10:55 UTC (Oct 2, 2:10:55 PM PDT)@WellMetaXReply to @barkmeta: “Join Bark for THE GREAT RESET! Live now!”post 2026-10-25 21:00:46 UTC (Oct 25, 2:00:46 PM PDT)@barkmetaSpace announcement; the linked Space is titled “Happening now: THE GREAT RESET 🚨 GROK BOT METAVERSE”. Posted 13 h 55 min before first seen.post 2026-10-26 21:02:42 UTC (Oct 26, 2:02:42 PM PDT)@barkmetaSpace announcement; the linked Space is titled “Happening now: THE GREAT RESET 🚨”. Posted 10 h 06 min after first seen.post So the phrase has two uses in @barkmeta’s timeline. As the show title, it appears in public posts from Aug 22 onward, including the day before the transactions. In plain posts about events, the first use we found is the Oct 26 22:46:48 UTC post above (the next is the Oct 27 post quoting the Reuters item). A search of @barkmeta’s posts for the phrase “great reset” returned these two plain posts and some reposts of other users’ Space promotions. We cannot see what was said inside any Space. Earlier statement about other marketplaces (Mar 22 2026) On 2026-03-22 23:11:32 UTC (Mar 22, 4:11:32 PM PDT), in a reply to @Rollmeta, @DDSalesBot and @doginaldogs, @barkmeta wrote: “Many of these inscriptions on other marketplaces are not real / stolen. The ONLY place for dogs is the official MP”. The post it replies to is no longer retrievable, so we do not know what it was responding to. We include it only because it is a public statement by this account about stolen inscriptions on marketplaces. 3. Public silence about the transactions “We did not find” means we looked and did not find it. It does not mean it does not exist. We could not see deleted posts, blocked accounts, private messages, other platforms, or the content of Spaces. Posting counts before, during and after Counts come from the public timelines of each account (posts, replies, quote posts and reposts) as retrieved on the check date. Windows do not overlap. Window (UTC)Length@barkmeta: total (reposts / replies / other)@GodsBurnt: total (reposts / replies / other) Before: Oct 25 10:56:10 to Oct 26 10:00:0023.1 h20 (11 / 1 / 8), about 20.8 per 24 h8 (1 / 3 / 4), about 8.3 per 24 h Around first seen: Oct 26 10:00:00 to 14:00:00 (contains 10:56:10)4.0 h01 (0 / 1 / 0): a reply at 13:46:02 UTC, “the devil is real” After: Oct 26 14:00:00 to Oct 29 00:10:0058.2 h71 (21 / 31 / 19), about 29.3 per 24 h64 (1 / 46 / 17), about 26.4 per 24 h “Other” means original posts and quote posts. Posts per UTC day were: @barkmeta 15 (Oct 25, from 14:07), 18 (Oct 26), 31 (Oct 27), 27 (Oct 28, to 23:19); @GodsBurnt 8 (Oct 25, from 14:01), 23 (Oct 26), 23 (Oct 27), 19 (Oct 28, to 22:52). Both accounts posted at a similar or higher daily rate after the transactions than before. Both also kept posting links to their regular Spaces (we cannot see what was said in them). What we did not find: in the posts retrieved for both accounts after 10:00 UTC on Oct 26, no post, reply or quote refers to the transactions, the missing inscriptions, a hack or theft of the marketplace, the marketplace’s paused trading, compensation, or an investigation. A keyword search of both accounts (stolen, theft, exploit, drained, marketplace, compromised, reimburse, compensation, paused, maintenance, statement, refund, and similar terms, excluding reposts) from Oct 26 00:00 UTC returned no results on 2026-10-29 00:10:00 UTC (Oct 28, 5:10:00 PM PDT). Public replies addressed to the accounts Three public replies ask the accounts directly. In each conversation, a search for posts by @barkmeta, @GodsBurnt and @doginaldogs found only the original post being replied to, and no answer. We did not find a reply from the addressed account. Posted (UTC / Pacific)FromToExact textLink 2026-10-27 14:53:55 UTC (Oct 27, 7:53:55 AM PDT)@0xDFV@GodsBurnt“Is it true your marketplace got hacked? And you’re acting like it never happened?”post 2026-10-27 19:24:30 UTC (Oct 27, 12:24:30 PM PDT)@MrSilly_eth@barkmeta“Talking about everything but your own @doginaldogs hack.”post 2026-10-28 18:30:02 UTC (Oct 28, 11:30:02 AM PDT)@pistolpete_sol@doginaldogs“You going to talk about your marketplace getting hacked and draining everyone?”post These are other users’ words. We have not verified their claims and list them only to show that the question was asked in public and, as far as we found, was not answered. The third reply was posted under an advertisement for an event (DDMIAMI 2026), posted by @doginaldogs at 2026-10-28 14:00:02 UTC (Oct 28, 7:00:02 AM PDT) (post). It is the only original post by @doginaldogs that we found between Oct 26 00:00 UTC and the check time. It does not mention the incident. Reposts, and the “Together we build” posts @barkmeta reposts of other users’ posts. On Oct 27 and Oct 28 it reposted four posts written by community members about the project: 2115107457928507876 (“The @doginaldogs are still here even with everything going on right now…”), 2115175308152205719 (“Haters gonna hate. The builders will just keep building anyway.”), 2115300242937528399 (“Haters are going to hate. Builders Build.”) and 2115451049045897715. Oct 28. At 2026-10-28 19:18:36 UTC (Oct 28, 12:18:36 PM PDT), @barkmeta posted: “Together we build / Together we win / Doginal Dogs never stop”. From 20:43:56 UTC to 23:54:54 UTC the same day, @doginaldogs reposted at least 25 posts by other accounts, each with the same or near-identical text. We do not know whether those posts were coordinated. Change in tone from @GodsBurnt The “hacked” theme in @GodsBurnt’s posts changed within two days of the transactions. On Oct 26 at 2026-10-26 17:26:45 UTC (Oct 26, 10:26:45 AM PDT) it posted that “We’re about to experience a CYBER PANDEMIC.” On Oct 27 at 2026-10-27 14:05:20 UTC (Oct 27, 7:05:20 AM PDT) it posted that “Any moment now everything is going to go parabolic.” On Oct 28 at 2026-10-28 14:52:28 UTC (Oct 28, 7:52:28 AM PDT), 51 h 56 min after first seen, it posted: “Everything was getting hacked, people we're afraid to touch the internet” and “the world did, in fact, not end.” and “This was all a big bear trap... A final shakeout.” We quote the words only. We do not say what they refer to. Gaps in posting The longest gaps in each account’s retrieved posts overlap the time when the transactions were first seen. The same accounts have similar-length gaps on other days: AccountGap (UTC)Length @barkmetaOct 26 05:36:49 to 14:49:11 (contains first seen)9 h 12 min @barkmetaOct 27 04:56:22 to 14:30:439 h 34 min @barkmetaOct 28 04:42:21 to 14:19:049 h 37 min @GodsBurntOct 25 23:13:20 to Oct 26 13:46:02 (contains first seen)14 h 33 min @GodsBurntOct 27 22:51:25 to Oct 28 13:00:2714 h 09 min @GodsBurntOct 27 03:09:48 to 14:01:1210 h 51 min These hours are late night to morning in US Eastern time (UTC−4 until Nov 1). The first-seen time is 6:56 AM Eastern and 3:56 AM Pacific. We make no inference from gaps; we list them so that readers can see them. 4. How to read this What the data shows. Dated, public posts, exact short quotes, and the time between each post and the first-seen time of the transactions. What it does not show. It does not show who operates either account or the marketplace, who sent the transactions, what anyone knew, or why anyone posted or did not post. We make no claim about intent, foreknowledge or responsibility. Similar posts occur on both sides of the time. The “hacked” and AI-collapse theme appears in posts from Oct 22 and continues after Oct 26. Other public accounts also posted about AI-driven hacking in the same days, and news reports of cyber incidents (for example the Reuters item quoted on Oct 27) were in circulation. None of the posts we quote names the marketplace. “The Great Reset” has two meanings in the timeline. It is a Space title documented since Aug 22 and a phrase in posts from Oct 26. Silence has several possible explanations. A lack of public posts could be a decision not to comment, a lack of knowledge, a statement made somewhere we could not see (a Space, private channel, or another platform), or a deleted or blocked post. We cannot tell which. Timing is a fact, not a conclusion. Readers can compare the posting times with the transaction times and judge for themselves. Limits We had no archive access, so deleted posts and deleted replies cannot be seen. Edits are visible only where X reports an edit history. We could not hear any Space. The public search index may not return every post, so a keyword search with no results is not proof that no post exists. Counts depend on what the public API returned at the check time. Counts for the “before” window start at 10:56:10 UTC on Oct 25; earlier days are not counted. Third-party summary accounts and automated recaps were not used for any fact on this page. Posts by other users are quoted as their words, not as findings of this archive. Corrections If either account, or anyone else, believes a quote, time or count above is wrong, or a public statement is missing, see the corrections policy. A public, verifiable statement by the marketplace operators would be added to the status log and to this page with its date. Related pages: open questions, what we cannot know, community reactions. ====================================================================== Precedent: how others responded - https://doginaldogs.info/precedent ====================================================================== This page records, with dates and links, how some other projects responded after asset-loss incidents. It presents facts only. A cell reads “not found” when we could not find a source; that does not mean that nothing happened. Incidents differ in mechanism, size and chain, and we draw no conclusion from the comparison. Closest documented match: Atomicals Market, November 2023 The closest match we found in mechanism is Atomicals Market, a Bitcoin ARC-20 token marketplace. Per the analysis by MetaTrust Labs, its seller signatures used SIGHASH_NONE|ANYONECANPAY instead of SIGHASH_SINGLE|ANYONECANPAY, which allowed listed assets to be taken without paying the seller. Dated facts from the sources: 2023-11-21: a post from the market describing the flaw and pausing its markets, as reported by MetaTrust Labs. 2023-11-24: a news item reporting the market’s reply to criticism (Coinlive) and one reporting a letter, written by a community member, that said the founder was stepping back and that full compensation was promised (Coinlive). 2023-12-02: a market post pledging to airdrop 33,000 ATOM within 48 hours (Coinlive). 2023-12-04: a press report that the market said it had airdropped the amount (ChainCatcher). We did not locate the on-chain disbursement transactions. 2023-12-15: a market post pledging a further 28,000 ATOM airdrop, a compensation pool funded by 20% of monthly fees, and default compensation of 50% of loss value for future incidents, as reported (ChainCatcher). Table: incident, time to public notice, compensation IncidentDateMechanismTime to public notice (as found)Compensation (as found) Atomicals Market (ARC-20), first two incidents2023-11-14 and 2023-11-23 (dates per the market's Dec 2 post)Seller signatures used SIGHASH_NONE|ANYONECANPAY instead of SIGHASH_SINGLE|ANYONECANPAYMarket post on 2023-11-21 describing a flaw and pausing markets (as reported by MetaTrust Labs). 7 days after the first stated loss date.Nov 21-24: market said it would replace lost tokens (reports). Nov 24: a community member reported the founder stepping back and a full-compensation promise. Dec 2: market post pledging to airdrop the 33,000 ATOM within 48 hours. Dec 4: press report that the market said it had airdropped it. We did not locate the on-chain disbursement transactions. Atomicals Market (ARC-20), Nov 25 incident2023-11-25Same signature typeNot found separately from the above (the Dec 2 post said it was still dealing with it).Dec 15 2023: market post pledging 28,000 ATOM airdrop within 48 hours, a compensation pool funded by 20% of monthly fees, and a default compensation of 50% of loss value for future incidents (as reported). Disbursement not independently verified. OrdiBots mint (Bitcoin Ordinals)2023-11-28Mempool sniping of whitelisted users' mint transactions (a different mechanism from a signature flaw)Reported 2023-11-28 or 2023-11-29 (press)2023-11-29: team pledged to airdrop a replacement item to each affected address (as reported). Delivery not verified. OpenSea Wyvern phishing (Ethereum)2022-02-19Users signed malicious orders after a phishing message (a different mechanism)Press reports 2022-02-19 to 2022-02-20Not found for this incident. Some items were returned by the attacker and three were recovered by another marketplace (press). Bored Ape Yacht Club Instagram compromise (Ethereum)2022-04-25Official social account compromised and used to post a phishing link (a different mechanism)Same day, 2022-04-25 (press)Not found Doginal Dogs Marketplace (Dogecoin)2026-10-26Seller signatures of type 0x82 (SIGHASH_NONE|ANYONECANPAY); see the technical explainerAs of Oct 28 2026 we did not find an official statement; a pause notice is displayed on the site (status log)Not found as of Oct 28 2026 Reported losses IncidentReported loss Atomicals Market (ARC-20), first two incidents33,000 ATOM (per the market's Dec 2 2023 post) Atomicals Market (ARC-20), Nov 25 incident23,000 ATOM, plus 5,000 ATOM lost by 5 users in similar incidents (per the market's Dec 15 post) OrdiBots mint (Bitcoin Ordinals)Not found OpenSea Wyvern phishing (Ethereum)254 NFTs from 17 users, about USD 1.7 million (press) Bored Ape Yacht Club Instagram compromise (Ethereum)About 91 NFTs, about USD 2.8 million (press) Sources https://www.metatrust.io/blogs/post/the-analysis-of-the-atomicals-market-user-asset-loss https://www.coinlive.com/news-flash/337072 https://www.coinlive.com/news-flash/337405 https://www.coinlive.com/news-flash/349954 https://www.chaincatcher.com/article/2107595 https://www.chaincatcher.com/en/article/2108697 https://www.theblockbeats.info/en/news/48050 https://www.influencive.com/mempool-sniping-exploit-plagues-ordibots-mint/ https://www.theverge.com/2022/2/20/22943228/opensea-phishing-hack-smart-contract-bug-stolen-nft https://blockworks.com/news/opensea-scammers-went-phishing-and-caught-over-250-nfts-from-17-users https://decrypt.co/93608/mintable-recovers-three-nfts-stolen-from-opensea-users https://www.theblock.co/news/web3/2022-04-25-bored-ape-instagram-account-hacked-nfts-worth-2-8-million-stolen-143328 https://decrypt.co/98614/bored-ape-yacht-club-instagram-hacked-ethereum-nfts-stolen https://therecord.media/bored-ape-yacht-club-says-instagram-hacked-nfts-stolen Data: precedent_incidents.csv. Press reports are secondary sources; where we could not open a primary post we say so. Errors can be reported through the corrections process. ====================================================================== Comparison with other markets - https://doginaldogs.info/comparison ====================================================================== This page compares what public documentation says about seller listing signatures on other inscription marketplaces. It is limited to documents we could open and quote. It is not a survey of all marketplaces, and it says nothing about the security of any marketplace beyond what the cited text states. Documentation describes intended design, which we have not tested. MarketplaceChainSeller listing signature (as documented)Where the signed listing is kept (as documented)Source Doginal Dogs MarketplaceDogecoin0x82 (SIGHASH_NONE|ANYONECANPAY) in client code; a comment in the same file describes SIGHASH_SINGLE|ANYONECANPAYNot documented publicly. Client code refers to a listing template field. We did not find public documentation of storage or access rules.Technical explainer, evidence Doge Soft Art (beta, documented as live on mainnet since 2026-10-15)Dogecoin0x83 (SINGLE|ANYONECANPAY) for list and auction start; the buyer signs 0x01 (ALL)Documentation says listings are kept server-side and are not sent to a browser; buyers sign a copy without the seller’s signature and the server joins the twodocs.dogesoft.io/marketplace OpenOrdex (open-source order format)BitcoinSell-order PSBT with one input and one output, signed with SIGHASH_SINGLE|ANYONECANPAYThe signed PSBT is published as the content of a Nostr eventNIP.md ORD.NETBitcoinSeller signs the sale transaction with SIGHASH_SINGLE|ANYONECANPAY; the marketplace also signs the inscription input with SIGHASH_DEFAULT, committing to the full transactionNot specified on the page we readdocs.ord.net How to read the table In each documented design other than the Doginal Dogs client code, the seller signature fixes the seller’s own payment output (SINGLE) and the table says so in the cited text. The Doge Soft Art documentation states the effect directly: such a signature authorizes “this Doginal for this price, paid to me.” The 0x82 type commits to no outputs. With such a signature the protection of a listing depends on other controls, for example on who can obtain the signed listing. We did not find documentation of those controls for the Doginal Dogs Marketplace (see open questions). The OpenOrdex format publishes signed sell orders openly. We read this as an example of a design in which a published signature remains bound to its stated price, because that is how SINGLE|ANYONECANPAY is described. We have not tested any of these other marketplaces and make no claim about their security. If you operate one of them and the description above is wrong, please use the corrections process. ====================================================================== Community reactions - https://doginaldogs.info/community ====================================================================== This page summarizes public posts on X between Oct 26 and Oct 28 2026 about the transactions. Selection method: public search for posts about the marketplace and the transactions, read without logging in to any account. It is a small, non-representative sample. Each post is attributed by public handle, date (UTC) and link, and quotes are short. Opinions in these posts belong to their authors. We have not verified their claims, and listing a post is not endorsement. We did not feature posts that name or identify an individual as responsible, that allege theft or fraud by a named or unnamed person without proof, that contain threats or personal information, or that are automatically generated. Several posts of those kinds were seen and left out. Themes Holders reporting affected items and tracing the transactions themselves. Several holders posted that listed items were moved and shared transaction details. Requests for an official statement. Multiple posts addressed to the project’s account ask for an explanation. As of Oct 28 2026 we did not find one (status log). Expressions of trust and hope for reimbursement. Some holders said they trust the team or hope affected holders are reimbursed. Caution about attribution. At least one post said it is not known who is behind the transfers. Frustration. Several posts expressed frustration at the lack of a public response. We summarize these here and do not reproduce them. Selected posts AccountDate (UTC)What it says @realXRPL2026-10-27A holder reports that one of their items was moved on Oct 26 in a batched transaction using 0x82 signatures, and gives the inscription ID. @KillerWhaleHbar2026-10-27A holder reports a similar loss and shares their own trace: six transactions, 264 items from 194 wallets, every input using 0x82. Our counts match these figures (scale and value). @Star_crystal___2026-10-27Replies “Hopefully the people in charge who made the site reimburse them all.” @BillyXBT2026-10-27“Asking questions after 200+ holders got drained isn’t hate.” The post also makes claims about other marketplaces and the signature type; see comparison for what we could verify. @TurboMetaX2026-10-27Says their wallet was completely drained and that they trust the team: “We will run it back.” @Heimdall_Bull2026-10-27Cautions that it is not known who is behind the transfers. @GambitMeta2026-10-27Describes it as looking like an exploit, says affected items appeared to be “bought” for nothing, and hopes it gets addressed. @HNmetax2026-10-27Asks why the project’s leaders have said nothing, and says over 200 dogs were affected. @pistolpete_sol2026-10-28Asks the project’s account whether it will address the marketplace incident. We also saw a post on Oct 28 asking the project account about the lack of mention of the incident on its website (@MrSilly_eth, 2026-10-28). The tone was critical; we summarize it under theme 5. Posts by the project’s own accounts We read the public timelines of the project’s official account and of the accounts of people associated with it on Oct 28 2026. We did not find a post about the Oct 26 transactions. Details and limits of that check are in the status log. A search can miss posts, deleted posts, replies, private groups and other platforms. Note This page does not endorse any claim made in the posts. Claims about who is responsible are not supported by public evidence and are explained on what we cannot know. ====================================================================== Status log - https://doginaldogs.info/status-log ====================================================================== This log is append-only. New checks are added as new dated entries; earlier entries are not edited, except to correct an error, and any correction is marked as such. Each entry shows when we last checked, in UTC and in Pacific time (US Pacific). “We did not find” means that we looked and did not find it; it does not mean it does not exist. The source data is status_log.json. Checks of public X posts around the incident are on Timing and public silence. Oct 28 2026 check of public X posts around the transactions (new page) Last checked: 2026-10-29 00:10:00 UTC · 2026-10-28 05:10:00 PM PDT (US Pacific) We added the page Timing and public silence. It lists dated public X posts by @barkmeta and @GodsBurnt before and after the first-seen time (10:56:10 UTC on Oct 26), with elapsed hours and exact short quotes. Between 10:00 UTC on Oct 26 and 00:10 UTC on Oct 29 we retrieved 71 posts from @barkmeta and 65 from @GodsBurnt. We did not find a post, reply or quote from either account that refers to the transactions or the marketplace. We did not find an answer from the addressed account to three public replies that ask about the incident (listed on the page). We could not see deleted posts, blocked accounts, private messages, or what was said in X Spaces. Sources: timing_posts.json Timing and public silence Oct 28 2026 search of public X posts by the team accounts Last checked: 2026-10-28 22:16:00 UTC · 2026-10-28 03:16:00 PM PDT (US Pacific) We searched public X posts (excluding reposts) from @doginaldogs, @barkmeta and @GodsBurnt between Oct 26 00:00 UTC and Oct 28 22:16 UTC for the terms marketplace, market, exploit, hack, paused, maintenance, reimburse, compensation, 0x82, sighash and statement. We did not find a post that addresses the Oct 26 transactions. Two posts matched the search terms; neither refers to the marketplace or the transactions. The search covers only public posts that the X search index returns. It does not cover deleted or hidden posts, private groups or Discord servers that need an account or invitation, or posts made after the time shown. Absence in this search is not proof that no statement exists. Oct 28 2026 re-check of the live marketplace site Last checked: 2026-10-28 17:26:46 UTC · 2026-10-28 10:26:46 AM PDT (US Pacific) The homepage (SHA-256 begins 5b4f408a6c28…), the terms page (b6dad3c033b2…) and every JavaScript and CSS file we saved are byte-identical to the Oct 27 snapshot (same SHA-256 values, same deployment identifier and ETag). The maintenance notice is still in the site and the public config API still returned maintenanceMode=true. The listings endpoint returned no listings and the statistics endpoint returned listed=0 (floorPrice still 47000). Trading-volume statistics changed slightly (trades30d 29 to 30). We did not find an official statement about the Oct 26 transactions on the marketplace site. The maintenance notice is unchanged from Oct 27. We requested Wayback Machine captures of the homepage and two code files at 17:28 UTC. We did not confirm that these captures were stored. Sources: Evidence manifest Oct 26 2026 (UTC) transactions and first site snapshot Last checked: 2026-10-27 04:44:18 UTC · 2026-10-26 09:44:18 PM PDT (US Pacific) Six Dogecoin transactions were first seen between 10:56:10 and 10:56:48 UTC on Oct 26 2026 and confirmed in blocks 6431226 and 6431231. See the timeline and transactions.csv. Together they spend 264 inscription inputs, all signed with sighash type 0x82, and each has a single output to the same address. In our analysis, 201 of the inscriptions reached that address and 63 went to miner coinbase outputs. At 04:44:18 UTC on Oct 27 2026 (9:44:18 PM on Oct 26 Pacific time) we saved a snapshot of the live marketplace site. It showed a notice titled “Trading temporarily paused”, and the public config API returned maintenanceMode=true. The notice does not mention the Oct 26 transactions. The public statistics endpoint returned listed=0 and floorPrice=47000. We did not find an official statement about the Oct 26 transactions on the marketplace site in that snapshot. Sources: Evidence manifest ====================================================================== Claims and sources - https://doginaldogs.info/claims-and-sources ====================================================================== This page lists statements made in or about this incident that we could check against a primary source, with the result. It lists only items that can be checked that way. Claims we could not check against a primary source are not repeated here, because repeating them can spread an error. “Verified” means that we reproduced it from the source on the date shown; it does not mean it is the whole story. StatementStatusPrimary source Six transactions spent inscriptions listed on the marketplace on Oct 26 2026.Verified on-chaintransactions.csv; explorer links in the timeline 264 inputs were spent and every one carries a 0x82 signature.Verified on-chaininputs.csv; the transactions The six transactions have a single recipient address, which received 0.338582 DOGE in total.Verified on-chainThe transactions 201 inscriptions reached the recipient address and 63 went to miners.Our computation from ordinals flow rules; can be repeatedTechnical explainer The marketplace client code uses 0x82 when signing listings.Verified in archived and live codeEvidence manifest A code comment in the same file describes SIGHASH_SINGLE|ANYONECANPAY.Verified in extracted sourceManifest item src-listing-signer-ts The 0x82 constant appears in archived code from 2025-10-26.Verified (earliest capture we found)Manifest item wb-js-20251026161429-5050e6bc The marketplace shows “Trading temporarily paused” as of the Oct 27 UTC (Oct 26 Pacific time) and Oct 28 2026 snapshots.Verified in live code and capturesManifest items live-oct27-layout, live-oct28-layout The marketplace Terms contain an “as is” clause and a limitation of liability mentioning “loss of funds”.Verified in the Terms pageManifest items live-oct27-legal.html, wb-legal-20261004225532 Sales on Oct 21 2026 used 0x82 on the seller input.Verified on-chainsales_reference.csv A floor price of about USD 1,500 was shown on doggy.market on Oct 28 2026.Verified (19,900 DOGE, about USD 1,586 shown)doggy.market; scale and value The incident involved 265 items.Not supported by our count (264)inputs.csv A floor price of about USD 4,500 applied on Oct 26 2026.Not supported; the marketplace’s own stats floor was about USD 3,600 at the Oct 26 DOGE pricescale and value This is the largest NFT hack ever.Not supported by our estimatesscale and value The affected items came from 194 wallets.Matches our count of distinct seller addressesOur analysis; community Who controls the recipient address, and anyone’s intent.Not established by public evidenceWhat we cannot know ====================================================================== Frequently asked questions - https://doginaldogs.info/faq ====================================================================== Short answers with links. Information as of Oct 28 2026. What happened to the Doginal Dogs on October 26 2026? Six Dogecoin transactions, first seen between 10:56:10 and 10:56:48 UTC on Oct 26 2026, spent 264 Doginal Dogs inscriptions that had been listed on the Doginal Dogs Marketplace. Each transaction has a single output to the same address (D6ZJAGkdFJn9cb3y2QAVwv5QtMXfVHihZ4). The total paid out was 0.338582 DOGE. See the timeline for transaction links. Read more. What is sighash 0x82? It is a signature hash type (SIGHASH_NONE|ANYONECANPAY). A signature of this type commits to the input being signed and to no outputs, so it does not fix a price or a payee. The type 0x83 (SIGHASH_SINGLE|ANYONECANPAY) instead fixes the output at the same index as the input. All 264 spent inputs carried 0x82 signatures. Read more. Does the marketplace code use 0x82? Yes. Archived and live client code contains the constant 0x82 in the listing-signing function. A comment in the same file describes SIGHASH_SINGLE|ANYONECANPAY. The earliest archived capture with the 0x82 constant that we found is dated 2025-10-26. Read more. How many Doginal Dogs were affected? 264 inscriptions were spent. In our analysis, 201 reached the recipient address and 63 went to miner coinbase outputs. They came from 194 distinct seller addresses. Read more. What is the value of the affected items? Our estimates range from about USD 0.3 million to USD 1.5 million depending on the price basis (floor price, recent sales, or 30-day average). These are estimates of listed or sold prices, not realizable proceeds and not a measure of anyone's loss. Read more. Was it the biggest NFT hack ever? We could not support that claim. We do not rank incidents. Two earlier incidents that we verified had reported USD figures above our upper estimate (the OpenSea phishing wave of 2022 and the Bored Ape Yacht Club Instagram compromise of 2022), although 264 items is a higher item count than either. We did not find a larger event in the Dogecoin inscription ecosystem, but our search was not exhaustive. Read more. Was it done on purpose? Public evidence cannot show intent. The evidence we have is consistent with a design flaw in how listing signatures were constructed. This site does not say or imply that anyone acted deliberately. Read more. Who controls the recipient address? We do not know. An address is not an identity, and we do not name or speculate about anyone. Read more. Has the Doginal Dogs team made a statement? As of Oct 28 2026 we did not find an official statement about the Oct 26 transactions. The marketplace site displays a notice titled 'Trading temporarily paused'. A search can miss posts or other channels. Check the status log for updates. Read more. Have other marketplaces had a similar problem? Atomicals Market, a Bitcoin ARC-20 marketplace, reported a flaw in November 2023 involving seller signatures of the same type. The precedent page lists dated facts, including its stated compensation steps. Read more. How can I check these facts myself? Every transaction ID, archive link and SHA-256 hash is listed on the evidence page and in the downloadable data files. Read more. Who runs this site? A pseudonymous independent researcher using the name Ledger Hound. The site is not affiliated with Doginal Dogs. See the about page. Read more. How are errors corrected? The publisher is anonymous and publishes no contact address. Factual corrections are made on the pages and logged in the status log when a verifiable source supports them. Read more. ====================================================================== Corrections - https://doginaldogs.info/corrections ====================================================================== This archive aims to be accurate and fair. If something here is wrong, incomplete or unfair, it should be corrected. The publisher is anonymous The publisher is anonymous and publishes no contact address, form or messaging account. This page does not offer any way to send the publisher a message, and none should be assumed to exist. Correcting errors Factual corrections are made on the page itself, and are logged in the status log with the date, when they are supported by a verifiable source. We do not silently change numbers or statements. If a statement cannot be supported by a primary source, we will remove it and note the removal. No response time is promised. Anyone named Anyone named or affected, including the operators of the Doginal Dogs Marketplace, may point to a public, verifiable source (for example an official statement, a transaction on the Dogecoin chain, or an archived page) that shows something here is wrong or out of date. When such a source is found and checked, the relevant page is corrected or updated and the change is logged in the status log with the date. This site does not accept or publish unsourced statements and does not verify the identity of anyone who claims to speak for a person or project. Personal information We do not publish the names of individuals beyond those who appear in the cited public sources, and we publish affected holders only in aggregate. The recording page reproduces the names and handles as they were spoken and as identified there, as unverified material. Updates The site states its information date on every page (“as of Oct 28 2026”). Pages are updated when facts change, for example if an official statement, a compensation plan or a code change appears. ====================================================================== Data files - https://doginaldogs.info/data-files ====================================================================== All files are licensed CC BY 4.0. They describe the state of knowledge as of Oct 28 2026. Third-party files are not republished; see the evidence manifest for source links and SHA-256 values. FileContents transactions.csvThe six transactions: ID, first seen, block, inputs, output, fee, inscriptions delivered or lost, explorer link inputs.csvOne row per spent input (264): transaction, input index, sighash byte, outcome timeline.jsonDated events with source links timing_posts.jsonQuoted public X posts with times, links and the reference first-seen time (source of the Timing and public silence page) status_log.jsonAppend-only log of site checks (source of the status log page) evidence_manifest.jsonArchived and live files with URLs, capture times and SHA-256 hashes value_estimates.csvUSD estimate scenarios with the method and caveats doge_usd_reference.csvDOGE/USD reference prices used sales_reference.csvTwo on-chain marketplace sales on Oct 21 2026 precedent_incidents.csvOther incidents: mechanism, reported loss, first public notice found, compensation found, sources Other machine-readable entry points: llms.txt, llms-full.txt, sitemap.xml. ====================================================================== About this archive - https://doginaldogs.info/about ====================================================================== The Doginal Dogs Marketplace Incident Archive is a source-linked record of the Doginal Dogs marketplace transactions of October 26 2026 (UTC). It is published by Ledger Hound, a pseudonym used by an independent, anonymous on-chain researcher. Independence This site is independent and is not affiliated with, endorsed by, or connected to Doginal Dogs, the Doginal Dogs Marketplace, or any of their operators, holders, or service providers. The publisher is not a member of the project’s team, has no inside information, and is not a whistleblower. Everything here comes from public sources that you can check yourself. Aims Record what is verifiable, with a source for each fact. Separate facts from inferences and say what cannot be known. Correct errors on the pages and log them in the status log when a verifiable source supports it (corrections policy). Avoid accusations. This site does not call anyone a scammer or say that anyone acted intentionally. Methods See evidence and methodology. Data are downloadable in data files under CC BY 4.0; please link back and mention the date shown on the page you use. Text on this site is provided for information only and is not legal, financial or investment advice. Contact The publisher is anonymous and publishes no contact address. See the corrections policy. Privacy This site has no analytics, advertising, cookies or third-party scripts. The hosting provider may keep standard server logs.