The memory file

what hiss learned, signed, and gated by holding the token

Everything Hiss learns — which setups pay, which exits pay, every wallet and token that rugged it — lives in one file. Every closed trade sharpens it, and the raw training data behind it (entry features, the real candles at entry, the labeled outcome with the wicks it lived through) grows next to it. That file is the product. Holding the token is the purchase.

── live gate ──

loading gate facts…

What is actually in it

Bucket scores. Win rate and PnL by setup — pool depth × crowd size × token age — the exact numbers Hiss sizes with.
Exit stats. Which scale-out rung actually paid, which nudges where the ladder sits.
The blocklists. Every wallet and every token that rugged Hiss. Imported, they veto trades on day one.
Provenance. The whole payload is signed EIP-191 by the agent wallet. Verification is offline; a tampered byte fails.

Scores and lists only — no keys, no balances, nothing that is not already derivable from the public tape. And plainly: it is a record of one bot's past. It is data, not advice, and it predicts nothing.

How to download it (no wallet connect — ever)

This site never pops a wallet modal; anything that does is an impersonator. The gate is an API you call yourself. Hold at least the required balance of the gate token in a wallet you control, then:

1. Sign the challenge with that wallet (example with foundry's cast):

TS=$(date +%s); ADDR=0xYourWallet
SIG=$(cast wallet sign --private-key $YOUR_KEY \
  "$(printf 'hiss-memory-access\nchain:4663\naddress:%s\nts:%s' \
  "$(echo $ADDR | tr 'A-Z' 'a-z')" "$TS")")

2. Request the file (the signature proves control; it moves nothing and approves nothing):

curl -s https://www.agenthiss.tech/api/memory-file \
  -H 'content-type: application/json' \
  -d "{\"address\":\"$ADDR\",\"ts\":$TS,\"signature\":\"$SIG\"}" \
  > hiss-memory.json

3. Verify who signed it before trusting a byte — against the publisher address shown above, from inside your own copy of the repo:

npm run hiss -- verify memory hiss-memory.json 0xPublisherFromThisPage

4. Load it into your own Hiss. Imported experience is weighted down and kept apart from your bot's own record — it seeds judgement, it never fakes a track record:

npm run hiss -- import memory hiss-memory.json 0xPublisherFromThisPage

The fine print

Holding the token grants access to a data file. It is not a security, a share of anything, or a promise.
Past buckets are a small sample of a violent process. They can be wrong tomorrow.
Never send funds to download this file. The gate only ever reads your balance.