Deployer address prior on-chain history

Sanctum's assessment for RD-F-114 — scored green on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.

Evidence summary #

Solana-native protocol; programs deployed via Igneous Labs operational keypairs, not persistent pseudonymous EOAs. Data-cache deployer.address: null (non-EVM substrate gap; expected). Unstake program unpXTU2Ndrc7WWNyEhQWe4udTzSibLPi25SXv2xbCHQ and Router stkitrT1Uoy18Dk1fTrgPw8W6MVzoCfYoAFT4MLsmhq confirmed Solana BPF programs under igneous-labs GitHub org. No rug-deployer history found for any Igneous Labs operational address. Upgrade authority held by named Squads multisig (governance-admin-analyst to confirm on-chain).

Sources #

URL
Sanctum Unstake Program on SolscanSolscan — Unstake program addressretrieved 2026-05-04
Docs
00-profile.md §3 Deployments — program addresses and upgrade authority notesProtocol profile §3 — deployment tableretrieved 2026-05-04
GitHub
Igneous Labs — building the Sanctum protocol (97 repos)Igneous Labs GitHub orgretrieved 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 →

rubric_version v1.7.0 protocol sanctum factor RD-F-114 score green collected_at 2026-05-04 18:49:23