Skip to main content
AVOID.NET
← Juicebox V3reviewed 2026-10-17 · 21 claims checked

Fact-check findings

What an automated fact-checker found when it re-read Juicebox V3 against the sources the page cites. Only the most recent review is shown.

Read this first

These findings are produced by an automated reviewer, and its results vary between runs: the same page, checked three times on the same day, came back with 15%, 20% and 34% of its claims disputed, mostly because each run extracted a different number of claims. Treat what follows as leads, not rulings.

“Disputed” means the reviewer could not reconcile the claim with the evidence it cited. It does not mean the claim is false. “Unverifiable” means no reachable source settled it either way.

Nothing here changes the page on its own. A proposed correction is applied only after a human moderator approves it; until then the page reads as it did when reviewed.

disputed

1 claim

The reviewer could not reconcile the claim with the evidence it cited. This is a lead, not a ruling that the claim is false.

  1. #18[disputed][awaiting moderator]in section: Governance Token (JBX) and Tokenomics Risks
    “Coinbase, MEXC, and Bitget list JBX, though liquidity and market capitalization are limited.”
    reviewerCoinbase, MEXC, and Bitget list JBX, though liquidity and market capitalization are limited.Multiple independent exchange and aggregator pages contradict the claim that JBX is listed on Coinbase, MEXC, or Bitget; the weight of evidence indicates JBX trades almost exclusively on Uniswap V3 with very thin volume, and MEXC explicitly marks its own JBX page as 'Unlisted.'
    Proposed correction (not yet applied)
    JBX trades primarily on Uniswap V3 on Ethereum with very limited liquidity and market capitalization; it does not appear on the market listings of major centralized exchanges such as Coinbase, MEXC, or Bitget.

unverifiable

2 claims

No source the reviewer could reach confirms or contradicts the claim.

  1. #19[unverifiable][awaiting moderator]in section: ZachXBT Flag and On-Chain Risk Signals
    “ZachXBT, a pseudonymous blockchain investigator with a documented track record of exposing fraud and protocol exploits, has flagged Juicebox V3 as a notable risk entity.”
    reviewerZachXBT has flagged Juicebox V3 as a notable risk entity.No tweet, thread, Telegram post, or secondary report of any kind referencing a ZachXBT flag on Juicebox or JBX could be located. The section's own text concedes 'the precise basis for ZachXBT's flag has not been publicly elaborated...and the specific claims remain unverified,' which is itself an acknowledgment that the premise driving this entire section rests on an unconfirmed assertion.
  2. #21[unverifiable][awaiting moderator]in section: Regulatory Environment and Compliance Considerations
    “Juicebox V3 has not been the subject of any publicly documented SEC, CFTC, DOJ, or OFAC enforcement action as of this report.”
    reviewerJuicebox V3 has not been the subject of any publicly documented SEC, CFTC, DOJ, or OFAC enforcement action.A negative claim of this kind cannot be fully verified by search alone, but no contradicting enforcement record was found.

partially supported

5 claims

The cited evidence supports part of the claim but not all of it.

  1. #2[partially supported][awaiting moderator]in section: Protocol Overview and Architecture
    “V3 was deployed to Ethereum mainnet on September 20, 2022, following audits by PeckShield, Certik, and a Code4rena competitive audit contest.”
    reviewerJuicebox V3 was deployed to Ethereum mainnet on September 20, 2022.Deployment date and Code4rena contest are confirmed directly. A Juicebox town hall transcript references PeckShield and Certik audits 'a few months back' without specifying they covered the V3 contract set specifically (the Certik report described elsewhere on the page is dated March 2022, before V2); PeckShield coverage of V3 specifically could not be independently located.
  2. #4[partially supported][awaiting moderator]in section: Protocol Overview and Architecture
    “Juicebox V3 TVL as of early 2026 is approximately $132,000, down from a peak of several million dollars, reflecting migration of activity to later protocol versions and general DAO treasury decline.”
    reviewerJuicebox V3 TVL as of early 2026 is approximately $132,000.Direction (steep decline from a multi-million-dollar peak to a sub-$200K figure) is confirmed, but the archived source cited for this page (archive_timestamp 2025-09-14) predates 'early 2026', so the exact $132,000 figure for that specific window could not be independently pinned down; current live TVL is in the same ballpark.
  3. #8[partially supported][awaiting moderator]in section: V3 Protocol Logic Incidents and Patch History
    “the root cause was a missing OR condition in an if-statement, and resolution required redeploying JBDirectory, JBController, and payment terminal contracts along with project migration”
    reviewerA medium-severity bug in JBFundingCycleStore (May 2022) was caused by a missing OR condition and required redeploying JBDirectory, JBController, and payment terminal contracts along with project migration.Date and root cause are confirmed verbatim against the primary postmortem; the specific list of redeployed contract names in the page is more specific than the source supports.
  4. #15[partially supported][awaiting moderator]in section: Permissionless Architecture and Fundraising Abuse Risk
    “Community members proposed legal action against the founding team, and CoinTelegraph analysts urged caution given suspicious on-chain activity.”
    reviewerCoinTelegraph analysts urged caution regarding the 2022 AssangeDAO transfers, alongside community calls for legal action.The 2022 transfer facts are independently confirmed elsewhere, but the page attaches a 2024 CoinTelegraph report to the 2022 narrative as though it is contemporaneous coverage of the same event, which conflates two distinct incidents two years apart.
  5. #17[partially supported][awaiting moderator]in section: Governance Token (JBX) and Tokenomics Risks
    “JuiceboxDAO sets no maximum supply cap on JBX; tokens are minted continuously to contributors, with issuance declining by 10% per ETH every two weeks. Approximately 35% of JBX tokens are reserved for designated team and contributor addresses, with 65% distributed to contributors.”
    reviewerJuiceboxDAO sets no maximum supply cap on JBX, with issuance declining 10% per ETH every two weeks and approximately 35% of tokens reserved for team/contributors versus 65% distributed to contributors.The no-supply-cap claim is plausible and consistent with Juicebox's continuous-issuance design, but the precise reserved-rate percentages are DAO-governance-set parameters that changed multiple times; one of the two sources cited for this section does not actually address tokenomics.

confirmed

13 claims

The cited evidence supports the claim as written.

  1. #1[confirmed][no action needed]in the summary
    “Juicebox is an Ethereum-based programmable treasury and crowdfunding protocol first launched in July 2021 by a pseudonymous developer known as Jango”
    reviewerJuicebox protocol V1 was first launched in July 2021 by a pseudonymous developer known as Jango.Consistent with Juicebox docs and independent 2021-2022 press coverage.
  2. #3[confirmed][no action needed]in section: Protocol Overview and Architecture
    “High-profile projects that used earlier Juicebox versions include ConstitutionDAO (approximately $46 million raised in November 2021)”
    reviewerConstitutionDAO raised approximately $46 million in November 2021 via Juicebox to bid on a copy of the U.S. Constitution.Figure is within the commonly reported range across independent outlets.
  3. #5[confirmed][no action needed]in section: Protocol Overview and Architecture
    “The protocol applies a 2.5% membership fee on payout withdrawals, which is used to buy back JBX, the governance token of JuiceboxDAO”
    reviewerThe protocol applies a 2.5% membership fee on payout withdrawals, used to buy back JBX.Directly confirmed by primary documentation.
  4. #6[confirmed][no action needed]in section: Security Vulnerabilities and Audit Findings
    “The Code4rena competitive audit of Juicebox V3 contracts conducted between October 18 and October 23, 2022, identified 13 unique vulnerabilities: 5 rated HIGH severity and 8 rated MEDIUM severity.”
    reviewerThe Code4rena competitive audit of Juicebox V3 ran October 18-23, 2022, and identified 13 unique vulnerabilities: 5 HIGH and 8 MEDIUM severity.Verified word-for-word against the primary Code4rena report.
  5. #7[confirmed][no action needed]in section: Security Vulnerabilities and Audit Findings
    “A separate Code4rena audit of the Juicebox Buyback Delegate in May 2023 found 3 medium-severity issues including partial swap execution risk in Uniswap V3 and slippage protection inconsistencies.”
    reviewerA separate Code4rena audit of the Juicebox Buyback Delegate in May 2023 found 3 medium-severity issues including partial swap execution risk in Uniswap V3 and slippage protection inconsistencies.Matches primary source closely.
  6. #9[confirmed][no action needed]in section: V3 Protocol Logic Incidents and Patch History
    “DAO governance approved JBP-341 on February 17, 2023, and a more comprehensive fix was deployed on February 21, 2023 as Juicebox V3.1, introducing JBETHPaymentTerminal3_1 and JBController3_1”
    reviewerJuicebox V3.1 was approved via JBP-341 on February 17, 2023 and deployed February 21, 2023, introducing JBETHPaymentTerminal3_1 and JBController3_1.Directly confirmed.
  7. #10[confirmed][no action needed]in section: V3 Protocol Logic Incidents and Patch History
    “Version 3.1.1 was deployed on June 30, 2023, resolving a low-severity bug where payouts could revert if a recipient project lacked a configured terminal, along with gas optimizations.”
    reviewerVersion 3.1.1 was deployed on June 30, 2023, resolving a low-severity payout-revert bug plus gas optimizations.Directly confirmed.
  8. #11[confirmed][no action needed]in section: V3 Protocol Logic Incidents and Patch History
    “Version 3.1.2 was deployed on August 15, 2023, addressing a critical accounting error in fee calculations: the protocol miscalculated the expected deposit amount when funds were returned after payouts, using the pre-fee amount rather than the post-fee amount actually held by the recipient, leaving affected projects underfunded. The fix relocated fee calculation logic into a dedicated library.”
    reviewerVersion 3.1.2 was deployed on August 15, 2023, fixing a critical fee-accounting error (pre-fee vs post-fee deposit miscalculation) by relocating logic to a dedicated library.Directly confirmed, including the 'dedicated library' detail.
  9. #12[confirmed][no action needed]in section: V3 Protocol Logic Incidents and Patch History
    “On April 20, 2026, Juicebox V3 suffered an alleged protocol logic exploit described by DeFiLlama as a borrowFrom spoof attack on Ethereum, resulting in an alleged loss of approximately $52,000.”
    reviewerOn April 20, 2026, Juicebox V3 suffered an alleged $52,000 loss via a borrowFrom spoof attack, classified by DeFiLlama as a Protocol Logic exploit.No independent news write-up of this incident could be found beyond the DeFiLlama database entry itself, but the page already hedges with 'alleged' and attributes the classification to DeFiLlama specifically rather than asserting it as independently reported, which is an appropriately cautious framing given a single-source record.
  10. #13[confirmed][no action needed]in section: Permissionless Architecture and Fundraising Abuse Risk
    “The Code4rena V2 audit also identified a specific vulnerability permitting project owners to construct honeypots against contributors.”
    reviewerThe Code4rena V2 audit (July 2022) identified a vulnerability permitting project owners to construct honeypots against contributors.Directly confirmed by the cited GitHub issue.
  11. #14[confirmed][no action needed]in section: Permissionless Architecture and Fundraising Abuse Risk
    “AssangeDAO, one of the largest projects launched on Juicebox, became the subject of community fraud allegations in 2022 after unexplained ETH transfers of 583.755 ETH from the multi-signature treasury address without community approval on April 9 and 10, 2022.”
    reviewerAssangeDAO's multi-signature wallet transferred 583.755 ETH without community approval on April 9 and 10, 2022, triggering fraud allegations and calls for legal action.Figure and dates verified directly against the cited article.
  12. #16[confirmed][no action needed]in section: Governance Token (JBX) and Tokenomics Risks
    “JuiceboxDAO is governed entirely by JBX token holders with no board of directors, no CEO, and no formal corporate entity.”
    reviewerJuiceboxDAO is governed entirely by JBX token holders with no board of directors, no CEO, and no formal corporate entity.Directly confirmed.
  13. #20[confirmed][no action needed]in section: ZachXBT Flag and On-Chain Risk Signals
    “DeFiLlama independently recorded the April 20, 2026 incident under its tracked hacks database, classifying it as a Protocol Logic attack.”
    reviewerDeFiLlama independently recorded the April 20, 2026 incident in its tracked hacks database, classifying it as a Protocol Logic attack.Consistent with the DeFiLlama record checked elsewhere in this review.
How this fits together. The reviewer reads the published page and its cited sources and records one finding per claim. A human moderator decides whether each proposed correction is applied; those decisions, and the score changes they cause, appear in the audit log. Earlier review runs are not shown here; only the latest reflects the page as it stands.