PatchMyBox.

CYBER SALVAGE · WORKING PROTOTYPE

Patches,
not ransoms.

Give someone who reaches your system a reason to repair it and leave.

Leave a local offer: meet the repair and conduct conditions, receive owner forgiveness and the promised reward. It grants no advance permission to enter.

Create your patchmybox.txt

No account. No upfront deposit.
Your draft stays in this browser.

01 / A LOCAL OFFER

On your host.
On your terms.

Place patchmybox.txt in a predictable local directory. Public publication is optional. The offer promises conditional forgiveness after a qualifying repair; it does not authorize entry beforehand.

02 / THE WHOLE EPISODE

A good patch.
An honest record.

Review the repair and conduct separately, including what happened before the file was found. Evidence can be incomplete: no receipt proves nothing was ever copied.

03 / A PAYMENT PROMISE

Promise now.
Fund after repair.

Choose the reward and review rules in the offer. Once the conditions are met, the reward is due. No upfront deposit means the patcher still bears the risk that the owner fails to pay.

YOUR FIRST STEP

Make your local offer.

Download a draft, review and authenticate it, then place it on your host. This page does not verify your authority or install the file.

OFFER DETAILSBrowser-local

Never enter credentials, customer data, or exploit details. A local file may be read by someone who gains access. Required fields are marked *.

Include only assets within your authority. The offer does not extend to other owners or shared infrastructure.

For example, a previously verified signing identity or organizational contact. A key found only on the host is insufficient. This maker does not sign or verify the file.

The default is conditional forgiveness. No advance access authorization, no required pre-repair conversation, and no deposit to install the offer. Define the commitment before anyone relies on it.

The owner promises this payment if the stated conditions are met. It is unsecured until funded after repair.

Local placement and policy validity

/etc/patchmybox.txt is a proposed convention, not an existing standard. Choose a natural directory on your host; public web hosting is optional.

The file records this instant in UTC. Review how expiry and withdrawal affect work already undertaken.

The authentication and status route may be private. A public URL is not required; keep an independent record of the terms.

If you choose a public mirror, use HTTPS and keep its version consistent. Publishing it does not authorize initial access.

Qualifying repair and conduct

These are conditions for retrospective forgiveness and payment, not a grant of access permission. Review every default.

Add exclusions, evidence, and mediation details
Additional evidence to request

Owner forgiveness concerns only claims and choices you control. It cannot guarantee legal immunity or bind prosecutors or third parties.

Entries disappear when this page reloads.
LIVE PREVIEW

patchmybox.txt

TXT

A local, conditional offer. Review the reward, conduct conditions, and limits of owner forgiveness.

AFTER DOWNLOADING

Review and authenticate the file, then place it at your chosen local path. Keep a matching independent record. Public publication is optional; the file grants no advance permission to enter.

FOLLOW AN EXAMPLE CASE

From repair to reward.

Explore qualification, unresolved evidence, a missed payment promise, and challenged escrow release.

SIMULATION ONLYNo wallet, real money, blockchain calls, verified conduct, or legal determination. “Demo units” have no value.
EXAMPLE CASE / ONE REPAIR
  1. Offer
  2. Patch
  3. Review
  4. Fund
  5. Settle

The offer promises 100 demo units for qualifying conduct. The owner funds after repair and review. Souk would assess evidence and gate settlement; a contract cannot collect an unfunded promise or grant legal forgiveness.

Inspect the initial contract.

The simulation explains the intended workflow. Contract source is a separate, unaudited prototype; it is not deployed or connected to this page.

Solidity source ↓Contract notes ↗

THE PROPOSED GROUP COMPANION

Build the tools.
Work through the hard cases.

At patch.souk.network, offensive and defensive researchers would develop common tools and protocols, mediate private patch cases, and gate payment decisions.

A proposed destination. Confirm availability and the identities of individual mediators before relying on them. No case is opened by this static page.

Explore the Souk companion