Koko

Trust & Safety

Safety isn't a feature. It's the default.

Every deal on Koko inherits the same baseline: a shared blacklist, server-level alerts, and a paper trail you can hand to staff.

Scammer Shield

Active

A global blacklist of confirmed scam accounts, matched on Discord ID rather than display name — so a rename doesn't reset a reputation.

01

Evidence in, noise out

Reports are reviewed by staff before an account is listed. Screenshots alone are not enough: transaction hashes, Discord IDs and timestamps are required.

02

Automatic server alerts

Opt in once with /scammer subscribe. When a listed account joins your server, your moderators get a private alert with the report reference — never a public callout.

03

Appeals, not erasure

Listed users can contest an entry with staff. Listings are reviewed, never quietly deleted, so the record stays useful for the servers relying on it.

Four rules of a safe trade

P2P checklist
  1. Verify the counterparty

    Run /profile and /vouches. Check deal volume, average rating and how long the account has existed — not just the star count.

  2. Confirm the rail, then the address

    Agree the network before payment and run /checkaddy on the address. A valid address on the wrong chain is still a loss.

  3. Invoice, don't improvise

    Send an /invoice with amount, currency and client. Both sides then work from the same reference instead of a wall of chat messages.

  4. Close the loop

    After settlement, log it with /done and /vouch. The ledger is what protects the next trader.

Stop and walk away if

  • Someone asks for a private key, seed phrase, 2FA code or exchange login.
  • The "middleman" was invited by the counterparty, not found in the support server.
  • You are rushed, or told the invoice "expires in 60 seconds, send now".
  • A DM claims to be Koko staff offering to recover funds for a fee.

Reporting

Report a scammer

Reports are handled in the support server so every action is logged and reviewable. The stronger the evidence, the faster an account is listed.

Open the support server
01

Open a ticket, don't post publicly

Public accusations get deleted and help nobody. Open a ticket in the support server and state what happened in one paragraph.

02

Attach the evidence

  • Discord user IDs of everyone involved (enable Developer Mode → Copy ID).
  • Transaction hashes for every transfer, with the network named.
  • Uncropped screenshots showing the agreed amount and rail.
  • The invoice reference, if one was generated with /invoice.
03

Wait for review

Staff verify the hash against the claimed network and review the account's history before listing it. You'll be told the outcome in the ticket — never by DM.

Subscribe your server to alerts once. Koko handles the rest quietly, with no public shaming and no false positives on renamed accounts.

/scammer subscribe