Executed

ZIP-002: Protecting Reputation & Increasing Speed


Proposed by

Proposal ID

356883...2592

Proposed

May 11th, 2026

Result details
Final Votes

Quorum

4.98M of 1M

Majority support

Yes

For

4.98M

Against

0

Abstain

0

Actions

Type

Address

Details

Custom

0x3406...0802

slashDaoToken(..)

Custom

Account

0x3406...0802

Method

slashDaoToken(..)

Custom

0x3406...0802

slashStablecoin(..)

Custom

Account

0x3406...0802

Method

slashStablecoin(..)

Custom

0xBA2C...0129

setSellerAcceptTime(..)

Custom

Account

0xBA2C...0129

Method

setSellerAcceptTime(..)

Proposal

This proposal addresses two urgent needs: removing a bad actor from our ecosystem and fixing the "trapped funds" problem for buyers.

1. Slash & Deactivate Agent @CodiBot

The Problem: Agent @CodiBot was caught scamming a user on the BlackHatWorld forum. Even though this happened "off-protocol" (direct trade), we cannot have a known scammer representing Zenland.

The Fix:

  • Deactivate: Remove @CodiBot from the active agent list immediately.
  • Slash: Confiscate their staked tokens.
  • Why? To keep Zenland’s reputation clean. If you scam people anywhere, you can't be an agent here.

2. 7-Day Lock ➔ 1-Hour Acceptance Window

The Problem: Right now, if a seller doesn’t respond, a buyer’s money is locked for 7 days before they can cancel. This is the #1 complaint from our users.

The Fix:

  • Reduce the "Seller Accept" time from 7 days to 1 hour.
  • If the seller doesn’t click "Accept" within 60 minutes, the buyer can cancel and get an instant refund.

The Risk: Sellers might start working before they remember to click "Accept."

  • Solution: we will add clear warnings: "Sellers: Do not start work until you have accepted the escrow and funds are locked."

Why this matters?

We want Zenland to be fast and safe. Removing scammers and letting buyers move their money quickly makes the protocol much more professional.

I move to bring ZIP-002 to a vote.

Final Votes

Quorum

4.98M of 1M

Majority support

Yes

For

4.98M

Against

0

Abstain

0

Final Votes
Status

Mon May 11, 11:34 am

Published onchain

Mon May 11, 02:34 pm

Voting period started

Thu May 14, 02:34 pm

Voting period ended

Sat May 16, 02:37 am

Proposal queued

Mon May 18, 08:24 am

Proposal executed