• © Goverland Inc. 2026
  • v1.0.8
  • Privacy Policy
  • Terms of Use
JuiceboxDAOJuiceboxDAOby0x50e70c43a5DD812e2309eAcea61348041011b4BAgnance.eth

JBP-528: Refund 1 ETH to Juiceworks for fronting cost to fix JBToken representation on DEXScreener

Voting ended about 1 year agoSucceeded

Synopsis

BiohackerDAO, and other JB projects, were concerned with the fact that DEXScreener and other token analyzers showed inaccurate red flags to consumers of tokens launched from Juicebox. Jango made connections with the sources of these flags (quickintel.io) and paid them their ask of 1 ETH to resolve current inaccurate alerts for all tokens launched from Juicebox V3, and all tokens that will be launched on Juicebox V4. This amount was paid from the Juiceworks multisig in this tx: https://etherscan.io/tx/0x30fd0e7b7c75e2a80e45fa66a8862d2a6ea261422aeac5ae172d445055d2f325.

The V3 work has been completed, the V4 work is pending my documentation for the quickintel folks to operate with.

Specification

Pay 1 ETH from the JuiceboxDAO multisig to the Juiceworks multisig at 0xD1F6bE4e4cd3AeB48c8F7EA4a8922e5e48ce4D9D.

Rationale

The token reporting services have leverage here, the 1 ETH was the price to get the attention to resolve JB Token reporting issues now and into the future.

Risks

quick intel has leverage here. if we care about accurate reporting on these services as some of our customers do, we may be asked to pay more. I dont expect this, my report with Ninja Dev (https://x.com/ninja_dev3) at quickintel has been good.

Timeline

Asap.

--- nance-actions
- type: Transfer
  uuid: ad6e8573fcba42658dc7515aff177f46
  payload:
    chainId: 1
    to: "0xD1F6bE4e4cd3AeB48c8F7EA4a8922e5e48ce4D9D"
    amount: "1"
    contract: ETH
  governanceCycles:
    - 96
  pollRequired: false

Off-Chain Vote

For
123.95M JBX99.6%
Against
551.25K JBX0.4%
Abstain
0 JBX0%
Quorum:156%
Download mobile app to vote

Discussion

JuiceboxDAOJBP-528: Refund 1 ETH to Juiceworks for fronting cost to fix JBToken representation on DEXScreener

Timeline

Mar 11, 2025Proposal created
Mar 11, 2025Proposal vote started
Mar 15, 2025Proposal vote ended
Feb 25, 2026Proposal updated