★ Deployer wallet mixer-funded within 30 days
Babylon Protocol's assessment for RD-F-124 — scored not_applicable on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Structurally not_applicable. Babylon has no EVM deployer EOA. Bitcoin staking: each stake is a distinct Taproot UTXO with no singleton contract address. Babylon Genesis chain: launched via Cosmos SDK genesis file (not deployed by a single EOA). Data cache: deployer.address: null, non_evm_substrate: true. The 30-day-window mixer-funding test (RD-F-124 definition) presupposes a single deployer EOA from which Tornado Cash / Railgun proximity can be measured. That prerequisite is structurally absent for both Bitcoin UTXO and Cosmos SDK genesis deployment. This is not a data gap — it is a structural inapplicability of the factor definition to non-EVM architecture.
Sources #
- Docs00-data-cache.json: deployer.address: null, non_evm_substrate: trueData cache deployer null + non_evm_substrate flagretrieved 2026-05-04
- Babylon BTC Staking Script DocumentationBabylon staking script — UTXO-based, no singleton contract addressretrieved 2026-05-04
Methodology #
Determine whether the deployer wallet received funds via Tornado Cash, Railgun, or similar mixer within 30 days before the protocol's first deploy.
See the full factor methodology and distribution across all protocols →