Deployer address prior on-chain history
Babylon Protocol's assessment for RD-F-114 — scored gray on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
No EVM deployer EOA exists. 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 via EOA. Data cache: deployer.address: null, non_evm_substrate: true. No deployer address history is assessable. This is a structural not-applicable condition for the non-EVM substrate. Scored gray (cannot assess — prerequisite data does not exist for this architecture) rather than not_applicable (which would imply the factor definition itself is N/A for this protocol type).
Sources #
- Docs00-data-cache.json: deployer.address: null, non_evm_substrate: trueData cache deployer fieldretrieved 2026-05-04
- Babylon BTC Staking Script DocumentationBabylon staking script docs — no singleton addressretrieved 2026-05-04
Methodology #
Classify the deployer address history as: none (fresh address) / normal-dev-history (prior protocol deploys, non-flagged activity) / linked-to-prior-rug (deployer used in prior known rug).
See the full factor methodology and distribution across all protocols →