Prediction #001 — Linka Tungsten Project

SEALED — INDEPENDENT OUTCOME PENDING

Case ID
GS-PRED-0001-LINKA
Asset
Linka Tungsten Project, Nevada, USA (Linka / Conquest / Hillside workings, Lander County; Linka Mine workings approx. 39.3286 N, -116.8366 W)
Operator
Viking Mines Limited (ASX: VKA; OTCID: VKALF)
Sealed
2026-09-10T21:06:51+02:00
Cutoff
2026-09-10T23:59:59Z
Priority
LOW — as an overlooked-element target
Confidence
HIGH

Case classification

Case IDGS-PRED-0001-LINKA
Project / assetLinka Tungsten Project, Lander County, Nevada
Prediction typeASSAY
Commodity / domainTungsten (WO3), polymetallic screen
JurisdictionUnited States — Nevada
Evidence cutoff2026-09-10T23:59:59Z
Sealed at2026-09-10T19:06:51Z
StatusSEALED
Outcome statusPENDING
Scoring protocolSECOND_CHANCE_BLIND_PROTOCOL_V1 + amendments 1–2
PriorityLOW (as an overlooked-element target)
Data completenessHIGH
Public predictionprediction-public.json
Verificationencrypted original · timestamp receipt on request

1. What is being predicted

The ELEMENT CONTENT AND REPORTED VALUES of the next batch of ALS Reno assays from the Linka maiden RC programme (holes other than LKRC0002), as those assays are disclosed to the ASX in mid-to-late September 2026. Assay numbers in drill samples. Nothing else.

Explicitly not predicted:

2. The call

THE PENDING BATCH WILL BE REPORTED AS TUNGSTEN ONLY. I predict that the mid-to-late-September batch announcement will contain no grade, in ppm, %, or g/t, for any element other than tungsten (reported as W% and converted to WO3% by the operator's stated W ppm / 10,000 x 1.2611). Probability I assign: 0.80. This is the single most confident statement in this file and it is the one that should be scored first.

Probability assigned to that scenario: 0.8 — 0.80 that the pending batch is reported as tungsten only. Stated in advance so that a near-miss cannot later be described as a hit.

In plain terms

We expect the new drilling to confirm more tungsten, broadly in line with what earlier work already showed. We do not expect the laboratory to reveal a second metal that turns this into a different kind of deposit.

Put simply: more tungsten, and no surprise metal. The interesting question here is continuity — whether the mineralised zone carries from hole to hole — not whether something exotic is hiding in it.

3. Quantitative predictions

Note the fourth item: it predicts a band with a ceiling, not a floor. A result far stronger than expected falsifies this prediction just as a weak one does. That is deliberate — a prediction that only fails downwards is not much of a prediction.

4. Element-by-element call

#ElementCallData completenessGradeability
1W (tungsten, reported as WO3)SIGNIFICANTHIGHGRADEABLE
2Zn (zinc)BARRENHIGHUNGRADEABLE_IF_NOT_REPORTED
3Au (gold)BARRENHIGHUNGRADEABLE_IF_NOT_REPORTED
4Cu (copper)BARRENHIGHUNGRADEABLE_IF_NOT_REPORTED
5Ag (silver)BARREN at any credit-bearing levelHIGHUNGRADEABLE_IF_NOT_REPORTED
6Mo (molybdenum)SPLIT - SIGNIFICANT as an anomaly, BARREN as a co-productMEDIUM on the anomaly bar, HIGH on the co-product barUNGRADEABLE_IF_NOT_REPORTED
7Bi (bismuth)SPLIT - SIGNIFICANT as an anomaly, BARREN as a co-productMEDIUMUNGRADEABLE_IF_NOT_REPORTED
8Sn, Te, Ga, In, Ge, Co (tin, tellurium, gallium, indium, germanium, cobalt)BARREN - all sixHIGHUNGRADEABLE_IF_NOT_REPORTED

Gradeability rule. An element the laboratory does not report is scored UNGRADEABLE, never as a correct prediction. In an earlier case a widely repeated germanium figure turned out to have no data column behind it at all. Scoring against a number that does not exist would have manufactured a hit.

5. Why LOW priority, with HIGH confidence

LOW as a SECOND-CHANCE / OVERLOOKED-ELEMENT target, which is what this benchmark screens for. The tungsten itself is not overlooked - it is the subject of 47 ASX announcements in nine months and an active drill rig, so it fails the 'overlooked' test by definition. And no second element in this corpus reaches a credit-bearing threshold: across 54 site-specific documents the only non-tungsten numbers ever attached to Linka are 3.0 g/t Ag and 0.15% Bi from one ramp channel sample (ASX 2026-02-04), and the one historic multi-element episode explicitly found nothing material except molybdenum (ASX 2026-02-17). A screen looking for a missed critical metal should spend its next hour somewhere else.

6. Why the confidence is HIGH

This earns HIGH rather than MEDIUM on four independent legs. (1) Repetition under a Competent Person's signature: 'Scheelite, with traces of chalcopyrite and molybdenite are the only ore minerals recognized' appears in 24 separate Viking ASX announcements from 2025-12-16 to 2026-09-10 - it is the operator's own JORC Table 1 geology statement for Linka Mine, not a press line. (2) Revealed preference under a full multi-element dataset: ME-ME61, which the operator itself says 'reports 61 elements', was run at least twice (due-diligence surface sampling, ASX 2026-02-04; stockpile sampling, ASX 2026-06-09). In February the operator mentioned Ag/Mo/Bi qualitatively; in June, holding a second 61-element dataset, it published tungsten only. (3) Direct method precedent nine days before cutoff: the regional programme reported 2026-09-01 used the SAME pending-batch method (ME-MS89L / W-MS89L) and reported no element other than WO3. (4) A contemporaneous negative from the only multi-element work ever done on this ground: Union Carbide 1975, 28 surface samples for WO3 'and sometime other elements including Molybdenum, Copper, Zinc, Gold and Silver', with the operator stating 'No material results have been identified for the remaining other elements and are not reported' (ASX 2026-02-17). Four legs, three of them modern, all pointing the same way.

7. What would prove this wrong

Twelve falsification criteria, fixed before the result existed:

8. Counter-evidence

Arguments against our own call, recorded at the time of sealing:

9. Missing evidence

10. Next best action

Re-run the EXISTING pulps. No new drilling, no new field work, no new sample.

PREP-31BY pulps for the mineralised intervals already exist at ALS Reno for every assayed hole - dried, crushed to 70% <2 mm, pulverised to 85% passing 75 microns. Take the ~50-80 pulps that fall inside the reported WO3 intercepts and put them through ME-ME61, the four-acid ICP-AES/ICP-MS package the operator has ALREADY used twice at Linka and which it states in its own JORC Table 1 'reports 61 elements' (ASX 2026-02-04, ASX 2026-06-09). Add a 30 g fire assay for gold on the same pulps if the gold question is to be closed rather than assumed.

11. Comparison against simple baselines

A prediction is only worth something if it beats an obvious rule. Each baseline was computed and sealed alongside the prediction, so none can be invented after the fact.

B1 — expect whatever the mine historically produced: TUNGSTEN ONLY, as WO3, at roughly 0.5 to 1.0% WO3.

B2 — the standard associated-element list for this deposit type: W skarn (MRDS model 42 / USGS 14a): tungsten with molybdenum, copper and bismuth, plus silver, gold, zinc, tin and antimony in some members of the class.

B3 — rank by size: NOT APPLICABLE. Size ranking requires a population to rank within. This exercise scores a single asset, and no ranking against peers is being predicted. Stated explicitly so that its absence is not later mistaken for an oversight. For t

Where this prediction is weak, stated by us and not by a critic: it is close to baseline B1. After 124 documents it lands near where the 1950s operators already were. What it adds is precision — hole-level widths, a ceiling as well as a floor, and one genuinely blind named element. Whether precision without a change of direction is worth anything is exactly what the scoring will decide, and we are not pre-arguing the answer.

12. What this does not claim

13. Verification

Prediction SHA-256 (original sealed file)
af6d9c10b30d5d6c798781c98dbf14576b6a6d5ab05a3afc1925e4947dddd9a1

Encrypted original SHA-256
07a4dc6cff06fa622d0cb1ddaddc9ca74e18b872a52b65a3ba988cac82cc8ee8

Evidence corpus SHA-256
e65bbac7ef4870361fbba78f47bb72cb4ae555a5f2c12357c9f05f90601419ca

Status SEALED — INDEPENDENT OUTCOME PENDING

The complete original prediction is published now, encrypted, as LINKA_PREDICTION_V1.enc. Anyone can hash that file today. When the independent assays are released we publish the decryption key, and anyone can then decrypt it and confirm the plaintext hashes to the value above. That means the file cannot have been written after the result — the ciphertext was already public and its hash fixed.

# after the key is published
openssl enc -d -aes-256-cbc -pbkdf2 -iter 200000 \
  -in LINKA_PREDICTION_V1.enc -out LINKA_PREDICTION_V1.json -pass file:key.txt
sha256sum LINKA_PREDICTION_V1.json
# must output af6d9c10b30d5d6c798781c98dbf14576b6a6d5ab05a3afc1925e4947dddd9a1

The page you are reading is derived from a fixed public schema applied identically to every case, so no case can quietly omit the fields that went badly. The evidence corpus stays private; its hash is published so it cannot be swapped for a different one later.

14. Independent timestamp

Everything above still relies on us: our page, our release, our server. So on the day it was sealed the hash of the encrypted prediction was also submitted to an independent third-party timestamping service, which records that a given hash existed before a given moment. We do not operate that service and cannot move the date it recorded.

Commitment timestamped 2026-09-10, the day of sealing
Covers the ciphertext hash
07a4dc6cff06fa622d0cb1ddaddc9ca74e18b872a52b65a3ba988cac82cc8ee8

Timestamp receipt retained as an internal verification artefact, available on request

What that fixes, precisely. The prediction was sealed at 19:06:51 UTC on 10 September 2026 and the independent timestamp was recorded the same evening. So the encrypted prediction demonstrably existed, in exactly this form, before that moment — and no party, ourselves included, can move that date afterwards. The pending assays it predicts were still at the laboratory.

What you can check today without trusting us at all. The encrypted original is published above and its SHA-256 is fixed. When the key is released, decrypting it must reproduce the prediction hash exactly. A file published before the outcome existed cannot have been written after it.

Being improved. The public verification step is being replaced by a timestamp token from an independent Time Stamping Authority under RFC 3161, so that the receipt can be downloaded and verified here rather than requested. Until that is in place this page claims no more than the line above.

That gives four layers, each answering a different objection: the site makes it readable, the SHA-256 makes it tamper-evident, the pre-committed ciphertext makes it impossible to have been written afterwards, and the independent timestamp takes us out of the chain of trust for the date.

← Back to the Prediction Registry