House rules

Intrusion, access sales, and the work that follows them.

1. 39Scope is written before funding: target, access level, deadline, and what proof of completion looks like.
2. 40Proof of delivery is demonstrated access or delivered artifacts — a working panel, a dump, screenshots taken inside the target. Claims are not artifacts.
3. 41Persistence after payout is a new contract. Re-entering access you already sold is theft, and it resolves against the seller every time.
4. 42After handover, the target's own defenses — resets, patches, WAFs — are the buyer's problem. You bought access, not the future.

Cards, dumps and carded goods — physical and electronic.

1. 43Per-unit details in the terms: BIN, level, country, balance where it applies, and the checked-at date. “Good cards” is not a detail.
2. 44Replacement terms are written numbers: “dead-on-arrival replaced 1:1 within 6 hours of the delivery report.” No number, no replacement.
3. 45Live check windows beat claims. If the goods allow it, agree a check window in the contract and inspect together — it is the cleanest dispute prevention there is.
4. 46Physical carded goods: once the seller posts proof of shipment, the shipping risk is the buyer's. Electronic carded goods follow the normal inspection window.
5. 47Chargebacks after release are between the buyer and their bank. The escrow is closed; do not try to reopen it.

Bank logs, aged accounts, mail access, socials.

1. 48The seller hands over the original email and the recovery paths, not just a password. An account the buyer cannot hold is half-delivered.
2. 49The buyer changes credentials immediately and posts “received, changed” on the timeline — that timestamp starts the warranty clock.
3. 50Recovery or lock claims within 72 hours of handover are disputes; after that, the account is the buyer's, entirely.
4. 51Selling one account to two buyers is fraud, and it resolves that way every time.

Databases, mail lists, fullz, leads.

1. 52Sample before coins. The seller provides a verifiable sample; the buyer checks it before funding. Arbitration treats a refused sample as a bad sign.
2. 53Freshness, row count and dedupe policy are contract terms. Bulk is not quality.
3. 54The data must be what it claims to be — working mails, real rows, the named source. Sold-as-X, delivered-as-Y resolves against the seller.

Turning dirty digits into clean coins, at a written percentage.

1. 55Percentage, window and minimum are fixed numbers in the contract. “Market rate” is not a number.
2. 56Clean coins in, clean coins out. Complaints about the taint of your own inputs are your complaints.
3. 57Chargeback risk after release belongs to whoever accepted it in the terms — which was both of you.

Custom malware, stealers, exploits, 0-days, tooling.

1. 58Split large builds into milestone contracts — fund, deliver the stage, release, repeat. One contract per milestone; nothing here limits how many you open.
2. 59Delivered means source or binary plus build and run instructions on the timeline. “Works on my machine” is a support question, not a delivery dispute.
3. 60Exclusivity for private exploits and 0-days is a written term of the contract. Selling the same 0-day to someone else mid-escrow is fraud.

DDoS, boosting, SEO spam, documents, doxxing, tutorials.

1. 61DDoS, boosting, SEO spam, forged documents, doxxing reports, tutorials, write-ups — all escrowable. State the output, the duration, and how completion gets verified.
2. 62Time-based services state their measurement: monitored uptime, delivered followers, indexed links — verified how, and by when.
3. 63Unlisted category? If it is not in the prohibited list below, it is probably fine — ask the operator by PGP before funding.