FORESHOCK

Protocols

Request coverage

Every protocol here carries a dated score and the share of it backed by independently verified evidence. Where that share is still thin the assessment says so, is marked Low-signal rather than given a risk band, and holds every unevidenced category at the neutral midpoint instead of assuming it safe. Every score and its reasoning are free to read; the underlying dependency, incident and audit records are part of a plan. Each reading here is fixed at the date beside it. Re-scoring never stops, but a changed reading reaches plan holders on the day it changes rather than this page, which is what a plan is for. How a score is built, how to read one, and how the rubric was tested against real exploits are all in the methodology.

Coverage grows three ways: protocols Foreshock selects at its own discretion, protocols requested through the Request coverage button, and sponsored assessments delivered on an agreed timeline. No path has a guaranteed date except sponsorship.

Scores run from 0, the safest reading, to 100, the riskiest, where 50 is the neutral midpoint every unverified category is held at. Red marks a protocol scoring 50 or above, the band called Elevated: worse than neutral on the evidence gathered. Amber marks one below it, called Moderate. The boundary is fixed. It does not move as coverage grows, and it is not fitted to any backtest result.

WisdomTree

WisdomTree official site N/A

Multi-Chain

:

  • Evidence: this reading is based on 100% of the scored weight, verified against named sources. Categories without verified data are excluded from the reading, never counted as safe.
  • Validation: the rubric is backtested against past exploits of protocols in the same TVL, age and category bucket. Protocols of this scale and kind have no such history - a limit of the record itself, not unfinished work.
In short

Foreshock's independent reading of WisdomTree is Elevated risk, 57.0 out of 100, as of 7 September 2026. The largest single contributor to that reading is audit profile: 4 audits on record, most recent audit is 6-12 months old; the most recent audit found 0 High and 12 Medium severity issues. This reflects code quality at the time of that audit only, not a claim that these specific issues are still unresolved today; has an unresolved critical finding (hard floor applied). All nine scored categories are backed by verified evidence. Foreshock publishes the reading and the reasoning behind it. It is not a verdict on whether to use this protocol, and it is not investment advice.

Is WisdomTree safe?
Foreshock does not answer that as a yes or a no. Its independent reading of WisdomTree is Elevated risk, 57.0 out of 100, as of 7 September 2026, led by audit profile: 4 audits on record, most recent audit is 6-12 months old; the most recent audit found 0 High and 12 Medium severity issues. This reflects code quality at the time of that audit only, not a claim that these specific issues are still unresolved today; has an unresolved critical finding (hard floor applied). The score and the reasoning are published in full so the reading can be checked rather than trusted.
Has WisdomTree been audited?
4 audits on record, most recent audit is 6-12 months old; the most recent audit found 0 High and 12 Medium severity issues. This reflects code quality at the time of that audit only, not a claim that these specific issues are still unresolved today; has an unresolved critical finding (hard floor applied). An audit describes the code at the time it was reviewed. It is not a statement that the protocol is safe today.
Who controls WisdomTree?
Admin key: unknown, upgradeable without a meaningful timelock, open source. No governance token, and the controlling address could not be resolved, so this is scored as though control sits with an identified party. Immutability is only ever established by reading a contract with no owner and no upgrade path, never by failing to find one, so an unresolved controller is treated as a controller.
Has WisdomTree been exploited before?
No known own or inherited incidents. Foreshock records an incident against a protocol whether it originated there or was inherited from something it depends on.
When was this WisdomTree assessment last updated?
7 September 2026. Readings are recomputed as evidence changes, and every category carries the date of the evidence behind it.
Score by categories
Audit profile17.0

4 audits on record, most recent audit is 6-12 months old; the most recent audit found 0 High and 12 Medium severity issues. This reflects code quality at the time of that audit only, not a claim that these specific issues are still unresolved today; has an unresolved critical finding (hard floor applied).

Code characteristics9.8

Admin key: unknown, upgradeable without a meaningful timelock, open source.

Dependency risk9.0

Uses 1 oracle (This is a registered investment company, not a DeFi protocol, and the dependency set reflects that: the assurance layer is a Big Four auditor, a bank custodian and administrator, an SEC-registered transfer agent and an independent-majority board, not a smart-contract mechanism. Two facts reframe the on-chain part. First, TOKENS ARE NOT THE RECORD OF OWNERSHIP: WisdomTree's own words are that records are 'maintained on blockchain as part of an integrated recordkeeping system by the Digital Fund's transfer agent', so the transfer agent's book-entry record is official and the token is a secondary representation. Second, issuance is NATIVE PER CHAIN rather than bridged, so no bridge dependency exists and none is recorded. WisdomTree operates its own transfer agent, which its Legal Entity Disclosure confirms, and which its own press material describes as 'maintaining official share ownership records' in both book-entry and on-chain form. A SOURCING GAP worth carrying: the auditor, custodian and administrator are named only in WisdomTree Digital Trust's own SEC filing on EDGAR, and NO WisdomTree-owned page names any of them; its own About Digital Funds page says only that assets 'are held in a segregated custody account' without naming the custodian or the transfer agent. No SOC 1 or SOC 2 report is referenced anywhere first-party; the Prime security overview covers encryption, two-factor authentication and GLBA Safeguards Rule compliance and mentions no certification, penetration testing or disclosure process. One first-party ambiguity recorded rather than resolved: a 2025 press release names Foreside Fund Services as distributor while the current fund documents name WisdomTree Securities, so distribution appears to have moved in house.), composable with 5 other protocols.

Governance attack surface7.0

No governance token, and the controlling address could not be resolved, so this is scored as though control sits with an identified party. Immutability is only ever established by reading a contract with no owner and no upgrade path, never by failing to find one, so an unresolved controller is treated as a controller.

TVL profile5.5

TVL grew 59% recently, moderate inflow.

Bug bounty3.3

No bug bounty program on record.

Historical incidents2.2

No known own or inherited incidents.

Team factors1.7

Doxxed team, track record: unknown.

Protocol age1.5

1153 days live, past the ~1yr floor; treated the same as any older protocol, not scored progressively safer with more age.

Assets held (1)

Available with a plan. See pricing.

Dependencies (2)

Available with a plan. See pricing.

Incident history (0)

Available with a plan. See pricing.

Audit history (4)

Available with a plan. See pricing.

Also covered on Multi-Chain

This assessment follows Foreshock's published methodology. Exact category weights, scoring rules, thresholds, and aggregation logic are proprietary and not shown here. How to interpret this assessment

This reading will change.

This reading is fixed at the date above it, and it stays there. We keep re-scoring WisdomTree as the evidence moves, a new audit, a changed admin control, an incident, and this page is free to read and always will be. The updated reading is what a plan buys: you are told by email on the day it changes, instead of finding out the next time you happen to look.

Get told when this changesBrowse every protocol