• © Goverland Inc. 2026
  • v1.0.8
  • Privacy Policy
  • Terms of Use
DecentralandDecentralandby0xBB7B59Afa3A0E5Be143b8fE9C641F00c1ecB9d690xBB7B…9d69

Removal of SAB Member Kyllian Hprivakos Due to Active Legal Dispute

Voting ended about 1 month agoSucceeded

by 0xbc02db030361121dd43bbb2fcbcb4f9f98c1dc7d (Ghost)

Removal of Security Advisory Board (SAB) Member Kyllian, Hprivakos Due to Active Legal Dispute and Governance Conflict

Summary This proposal seeks to remove Kyllian Hprivakos member of the Decentraland Security Advisory Board (SAB) due to an ongoing legal dispute involving unreturned DAO-related funds, combined with actions that directly conflict with DAO-approved governance decisions.

The goal is to protect DAO integrity, security trust, and governance legitimacy, not to adjudicate guilt. This proposal focuses solely on fitness to serve in a critical security governance role while under active dispute with the ecosystem.

Pause or cancel DAO Committee actions

Approve or block sensitive smart-contract and treasury operations

Act as a final security safeguard for DAO governance

At present:

A current SAB member is a former Decentraland employee.

The Decentraland Foundation (RL) is pursuing legal action to recover approximately 550 ETH allegedly not returned after employment termination.

This same individual has actively opposed or attempted to override DAO decisions that successfully passed all governance stages.

While legal matters are handled outside the DAO, DAO governance roles depend on trust, neutrality, and alignment with community decisions.

Problem Statement Regardless of the eventual legal outcome, the situation creates:

A conflict of interest between personal legal exposure and DAO security oversight

Erosion of trust in the SAB’s neutrality and independence

A precedent risk, where an SAB member may act against DAO-approved outcomes

The SAB exists to protect the DAO — not to be a point of contention with it.

Rationale This proposal is not a legal judgment and does not assume guilt.

Instead, it is based on three governance principles:

Accountability – Governance roles are conditional on continued community trust

Conflict Avoidance – Security roles must be free from active disputes involving DAO funds

DAO Supremacy – No individual governance role should undermine or resist decisions passed through the DAO’s established process

DAOs function on legitimacy. When trust in security oversight is questioned, decisive governance action is required.

Proposed Action If this proposal passes:

The named individual will be removed from the Security Advisory Board.

The DAO will initiate the standard process to appoint a replacement SAB member in accordance with existing governance procedures.

This action will not affect the individual’s legal rights, claims, or defenses in any external legal proceedings.

Scope and Limitations This proposal does not determine legal guilt or innocence.

This proposal does not confiscate funds or impose penalties.

This proposal applies only to DAO governance roles.

Legal matters remain solely within the jurisdiction of courts and relevant legal entities.

Benefits to the DAO Restores confidence in DAO security governance

Reduces governance and reputational risk

Reinforces the principle that DAO roles are earned and revocable

Protects the DAO from conflicts of interest at the highest security level

Conclusion The Decentraland DAO is strongest when its governance bodies are trusted, impartial, and aligned with community decisions.

Removing an SAB member under active dispute involving DAO funds is a measured, governance-focused response that prioritizes security, credibility, and decentralization — without prejudging legal outcomes.

DAO governance must always remain above individual interests.

  • Yes
  • No
  • Invalid question/options

This proposal is summarized due to technical limitations. To view it complete and vote on it, visit the DCL DAO Governance dApp

Off-Chain Vote

Yes
960.91K VP65.7%
No
498.63K VP34.1%
Invalid question/options
2K VP0.1%
Download mobile app to vote

Timeline

Feb 05, 2026Proposal created
Feb 05, 2026Proposal vote started
Feb 10, 2026Proposal vote ended
Feb 10, 2026Proposal updated