Deployer address prior on-chain history
OpenEden's assessment for RD-F-114 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Deployer EOA 0x7C699ABc0118e5d0fac0a7f317da79275364C50 created TBILL vault v2 (0xdd50C053...) in block 18,376,020 (October 2023). No Chainalysis/Arkham/Nansen public label associating this address with rug-deployer class or sanctioned entity found in OSINT. Yellow (not green) because exact first-inbound funding transaction was not enumerated in this assessment: Etherscan direct fetch of deployer EOA returned 'Invalid Address' error (case-sensitivity issue in WebFetch tool). The address is confirmed as the vault creator from the contract page. OpenEden's regulatory posture (Bermuda DABA, Elliptic compliance, Coinbase Prime) is inconsistent with a rug-class deployer. Curators should manually verify funding provenance for full green.
Sources #
- DocsOpenEden — Trust and TransparencyOpenEden trust and transparency page — Elliptic compliance partner, Coinbase Prime on-ramp, regulatory posture inconsistent with rug-class deployerretrieved 2026-05-16
- Openeden TBILL Vault — Etherscan (contract creator field)TBILL vault v2 Etherscan — contract creator 0x7C699ABc...364C50, block 18,376,020, tx 0xae72beb042ac06b1027b833a42598d3f1a7f461d807cb95810fe30d8515e02e0retrieved 2026-05-16
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 →