Reference
Every pair
The whole board, grouped the way the site is grouped, with the separating test in the last column so you can find what you need without opening pages.
If you know roughly what your situation is, scan the middle column. If you know what you are able to check, scan the right one instead. Both routes land on the same page.
Addresses
| No | Pair | The test between them |
|---|---|---|
| 01 | An outage against A market that has ended | Silence never tells you. Wait for a second signal: a changed page or a changed set |
| 02 | A retired address against A lookalike address | Read the middle of the string. Edges right, middle wrong means it was built to fool you |
| 03 | A mirror against A copy of the site | Judge the address in full against a published set. The page itself is not evidence |
| 04 | A shortened link against The address it hides | Count it. Fifty-six characters plus .onion is an address. Anything less is a promise |
| 05 | A circuit that is dying against A site that is down | Change only your side. New circuit, then a different onion service you already know |
| 06 | A list that changed against An address you copied wrong | Count to fifty-six, then look for 0, 1, 8 or 9. A real address contains none of those |
| 07 | A page that loads against A market that is open | Name the action you came for, then see whether that completes. The front page is not it |
Getting in
| No | Pair | The test between them |
|---|---|---|
| 08 | Rate limiting against A wrong password | Stop attempting, wait out the window, then spend one attempt you are sure of |
| 09 | A captcha that will not pass against A captcha you are typing wrong | Reload the challenge without typing and see whether it comes back new and legible |
| 10 | An account you are locked out of against An account that was taken | Retrace where you last entered the credential and whether that address came from you |
| 11 | A session that expired against A session that was ended for you | Log in once more and read the first screen after it, not the one that threw you out |
| 12 | A code that is wrong against A clock that is wrong | Compare the clock on the code device against a trusted one, down to the seconds |
| 13 | An account that is not there against A name spelled differently | Read the name you hold against the record you made at the time, one character at a time |
| 14 | A queue against A market that is overloaded | Ask whether the wait is a page somebody designed or a request that never finished |
Money
| No | Pair | The test between them |
|---|---|---|
| 15 | A slow deposit against A lost deposit | Look the transaction up and read the destination address off the chain record |
| 16 | A deposit address that expired against An address that was never yours | Does your own signed-in deposit record list that address at all |
| 17 | Escrow against The market holding your money | Can you name the event that releases it, and is it tied to one order |
| 18 | A fee the market charges against A fee the network charges | Anything missing before broadcast is the operator, anything the chain records is not |
| 19 | A discount for ordering more against A discount for paying differently | Does the lower price survive an ordinary order through the ordinary flow |
| 20 | A partial refund against A settlement | Ask whether accepting the amount ends the claim, then read the order state after |
| 21 | A withdrawal that is queued against A withdrawal that was rejected | Check the spendable balance: missing means queued, returned means refused |
| 22 | A payment that is unconfirmed against A payment that is short | Compare the amount that arrived at the address with the amount the invoice asked |
Orders
| No | Pair | The test between them |
|---|---|---|
| 23 | A delivery window against A delivery estimate | Ask what happens on the day after. A window has an answer, an estimate has none |
| 24 | A request for more time against A request to release funds | Ask where the balance sits one minute after you press. Held is time, gone is release |
| 25 | A dispute against A report | Ask what the process ends with. Money moving is a dispute, a note on conduct is a report |
| 26 | An order marked shipped against An order that has shipped | Ask whether any record outside the market says the same thing. If not, it is a claim |
| 27 | Tracking that is not moving against A parcel that is lost | Is there a new entry saying something changed, or only an absence of new entries |
| 28 | An automatic timer against A deadline a vendor gives you | Ask who can move the date. If the person who named it can move it, it is a preference |
People
| No | Pair | The test between them |
|---|---|---|
| 29 | Silence against Being ignored | Whether the account has done anything at all inside the market since you wrote |
| 30 | A vendor gone quiet against A vendor account gone | Whether the account still appears in the market listings when you look it up fresh |
| 31 | Feedback against Evidence | Whether a stranger could look at the same thing and reach the same conclusion |
| 32 | A signed message against A claim to be somebody | Where your copy of the key came from, and whether you had it before this message |
| 33 | Market support against Somebody using the name | Whether you navigated to it yourself or it arrived in front of you |
| 34 | A new vendor against An old vendor on a new account | Whether the continuity is anchored anywhere outside the new account itself |
Words
| No | Pair | The test between them |
|---|---|---|
| 35 | A good signature from the wrong key against A good signature from the right key | Compare the fingerprint of the verifying key against one you already held |
| 36 | An old signed statement against A current one | Look for a date the signer wrote into the signed text itself |
| 37 | A picture of a signed block against A signed block | Try to select the text. If it will not select and copy, there is nothing to verify |
| 38 | A fingerprint that matches against A name that matches | Ask which string a person could have typed, then compare the one they could not |
| 39 | An announcement on the site against An announcement about the site | Ignore where it sits. Ask whether it is signed by a key whose fingerprint you hold |
| 40 | A badge against An identity | Ask for a signed line and check it against a fingerprint you already hold |
| 41 | A signed list against A published list | Check whether the addresses sit inside the signed text or merely beside it |
How the groups were chosen
Six groups, and the boundaries are about where the answer lives rather than what the reader is feeling. Addresses covers anything decided by a string or by the route to it. Getting in covers refusals at the door. Money covers anything with a record underneath it. Orders covers rules, timers and flags. People covers the other side of a conversation. Words covers signatures and statements.
A few pairs could sit in two groups. A dying circuit is arguably a getting in problem and a deposit address that expired is arguably an address problem. Where that happened the pair went to the group that matches the test rather than the one that matches the feeling, because the test is what the reader has come for.
What the numbers mean
Nothing. They are an ordering so pages can be referred to without quoting a title. They are not a difficulty rating, not a severity grade and not a reading order, though reading them in order does work if you want to.
If your situation is not on the board
Then either it is not a pair, or it has no single test between its halves, or nobody thought of it. The first two are reasons a candidate gets dropped. If a case genuinely splits five ways it belongs somewhere that handles it as five things rather than being forced into a fork it does not have.