DEIS // Governance

propose, review, and approve -- nothing here executes without real threshold consensus
Not connected
Setup -- deployed contract addresses
Click "Auto-fill" to read these straight from deis-chain/deployed-addresses.json (via deis-chain's server, port 4004), or paste them in manually.
What do you want to do?
05 Onboard an institution
Propose a new action
Click a function below to fill it in. Proposing also counts as your own approval automatically -- same as the contract's behavior.
Search entity contacts -- fraud pattern check
Searches names and emails across EVERY registered entity, including already Suspended/Revoked ones -- a flagged director re-onboarding under a brand-new identityID looks completely unrelated by ID alone. Their name or email reappearing is the real signal.
Manage controller keys for any identity
Add or remove a controller key for any identity -- used for guardian revocation at age of majority, officer changes, or any sovereign governance decision. Cannot remove the last remaining key.
DAN curriculum review queue
Submissions the Canonical Mapping Engine couldn't confidently auto-resolve -- either a node needs a governance pick among plausible candidates, or nothing scored high enough to accept at all and needs a final call. Resolving here is a single-governance-signer action, same trust level as authority status and contact search -- not a full multisig proposal.
Orphan DAG claim requests
A Provider requesting ownership of a DEIS_GOVERNANCE-curated curriculum. Approving proposes the on-chain call to DEISDAGClaims directly -- same multisig propose/approve flow as everything else, just pre-filled instead of hand-encoded. Load the governance overview above first (needs DEISDAGClaims loaded) before proposing. Finalizing afterward syncs dan-registry-service's record to match what actually executed on-chain.
Proposed exams awaiting review
A Provider proposed an exam for a canonical node -- exams are DEIS-authored by design, so this proposal isn't live until approved here. Only one exam can be approved per canonical node at a time; approving a second one for an already-covered node is rejected.
Approved exams -- retire one to fix a content mistake
Review is one-time -- once approved, an exam can't be edited or un-approved. If a content mistake is found after approval (wrong correctAnswer, a typo, etc.), retiring is the only fix: it moves the exam out of APPROVED status, freeing that canonical node's slot so a corrected version can be proposed and approved. Anyone who already attempted the retired exam keeps their result -- this never touches attempts or completions, it only stops NEW ones and frees the slot. Deliberately one-way, same as review itself.
Curricula -- archive to hide from student browsing
Archiving hides a curriculum from student-facing browsing without deleting anything -- existing progress and completions tied to it stay exactly as they are. A Provider can archive their own work, or governance can archive (or restore) any curriculum regardless of who submitted it.
Platform access status -- gates login entirely
Sets sectorAuthorityRegistry's authorityStatusGranted for DEIS's own entry against this identity. Suspended or Revoked blocks them from logging in to ANY DEIS portal at all -- this is the actual platform-access gate, checked at the single login endpoint every portal relies on. Defaults to Active if never explicitly set.