DEGENERUS PROTOCOL
Mechanics
Degenerus minimizes discretionary control; it does not eliminate trust or risk. The reviewed contract set has fixed module addresses and no general upgrade, pause, or arbitrary jackpot-withdrawal function. It still has privileged operating controls, sDGNRS-governed recovery paths, external dependencies, and the usual possibility of bugs or a bad deployment.
| Area | Constraint |
|---|---|
| Game logic | Core payout rates, eligibility rules, and odds are code paths rather than ordinary admin settings. |
| Upgrades and pauses | The reviewed contracts are not proxies and expose no general upgrade or pause switch. |
| Jackpot funds | There is no general owner function to withdraw a prize pool. Payouts, claims, and terminal distributions follow contract rules. |
Immutability narrows human discretion but also freezes defects. These statements describe the reviewed source; users should separately verify deployed addresses and bytecode.
The “vault owner” is whichever account holds more than 50.1% of the DGVE vault-share supply.
The one control that could actually ruin the game is the VRF escape hatch. If Chainlink stops delivering randomness, the vault owner can propose a replacement coordinator, and a malicious coordinator would control the game's randomness. Exploiting it requires the full parlay: Chainlink has to fail, the admin has to be hostile, and sDGNRS governance has to let the hostile swap through. The proposal gates and vote thresholds are detailed under governed recovery paths below. Everything else the owner controls is housekeeping:
| Control | Scope and consequence |
|---|---|
| Tune the lootbox reveal batch size | Changes the pending-volume threshold for an extra mid-day randomness request. It affects reveal timing and gas behavior, not the payout formulas. |
| Declare a future “thanos” level | May flag a level at least six ahead so its entry counts, and those of every level after, divide by up to 256×. A prospective redenomination for runaway-demand scale: it is undeclarable unless 40M+ entries survive the division, and it locks before any ticket for the level exists. The division is uniform, so no held ticket is touched and every holder's replacement cost and pot share are unchanged. |
| Manage Lido liquidity | May stake game ETH that the reserve calculation treats as excess, and may pay exact ETH to receive the same amount of game-held stETH. That swap is at par, so any stETH depeg discount lands on the admin, not the game. Vault and sDGNRS claims are treated as stETH-settleable in that reserve logic. |
| Set deity-pass presentation | May change renderer and color configuration. This affects metadata and presentation, with a built-in fallback; it does not change pass ownership or game payouts. |
| Curate the charity ballot | May fill the 20-address slate. Slots 0–2 lock once filled; edits to slots 3–19 are queued for the next update. sDGNRS votes choose among the available addresses, so curation still shapes the choice set. |
| Post-game GNRUS cleanup | After the final sweep, may redeem an inactive holder's GNRUS to that holder. After the additional three-year grace period, may sweep remaining GNRUS backing to the vault. |
The owner can also claim the contract's vested creator DGNRS, unwrap owner-held DGNRS into soulbound sDGNRS for a recipient, operate the vault's own positions, opt the vault into the salvage backstop (buying far-future entries with vault funds, with a configurable balance floor), and mint from WWXRP's uncirculating reserve. Those functions move assets the vault or creator already owns; they are listed here for completeness, not because they control the game.
The vault owner can propose emergency infrastructure changes after a verified outage, but execution requires an sDGNRS vote. A community holder with at least 0.5% of voting sDGNRS gets a later proposal path.
| Recovery | Proposal gates | Vote and scope |
|---|---|---|
| VRF coordinator | Vault owner after 44 hours since the last processed daily VRF word; community path after 7 days | Approval threshold decays from 50% to 5% over a seven-day proposal. It can replace the coordinator and key hash; a recovered VRF kills the proposal. |
| LINK/ETH price feed | Vault owner after 2 unhealthy days; community path after 7 days | Approval threshold decays from 50% to 15%. It can replace or disable the feed used to value LINK-donation rewards. |
The voting token may itself be concentrated. Governance gates reduce unilateral control; they do not guarantee a diverse or attentive electorate.
| Chainlink VRF | Supplies gameplay randomness. A prolonged failure delays draws and can lead to recovery or terminal handling. |
| Lido and stETH | Supply staking yield and part of the protocol's backing. Slashing, liquidity, or contract failure can reduce realized value. |
| Ethereum and deployment | Consensus, gas availability, correct addresses, constructor wiring, and deployed bytecode all matter. |
| The contracts themselves | Audits reduce uncertainty; they do not prove the absence of bugs, economic exploits, or denial-of-service paths. |
The liveness and endgame rules reduce the chance that value remains frozen forever, but terminal distribution is a fallback, not proof that normal play will continue or every participant will be made whole.
Ordinary ticket and lootbox ETH is routed to game pools without a purchase-time percentage removed as rake. The design still assigns creator DGNRS, routes most presale ETH to the vault, and lets protocol-controlled positions participate under fixed rules. Those are disclosed economic allocations, not contradictions to the narrow routing claim.
Read the source, but also verify the deployed addresses, bytecode, constructor wiring, privileged holders, live configuration, and any audit assumptions. Source-code immutability is useful only when the chain is running the source you reviewed.
Verify code, deployment, configuration, dependencies, and control concentration.
Read the Contracts sDGNRS