ENS/NameStone identity bound to deployer

Babylon Protocol's assessment for RD-F-117 — 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 Protocol operates on Bitcoin (UTXO-based; no ENS-equivalent on Bitcoin mainnet) and Babylon Genesis chain (Cosmos SDK; bech32 bbn1... addresses, no ENS). There is no EVM deployer EOA to bind an ENS name to. Per profiler: non_evm_substrate: true, evm: false. ENS binding is an EVM-specific factor inapplicable to Bitcoin + Cosmos SDK architecture. This is the same structural N/A applied to EigenLayer (prior reference) for ENS when deployer.address is null.

Sources #

Docs
00-data-cache.json: non_evm_substrate: true, evm: false (00-profile.meta.json)Data cache non_evm_substrate flagretrieved 2026-05-04

Methodology #

Determine whether the deployer address has a bound ENS or NameStone name resolvable to a verifiable identity.

See the full factor methodology and distribution across all protocols →

rubric_version v1.7.0 protocol babylon-protocol factor RD-F-117 score not_applicable collected_at 2026-05-04 19:43:27