Two things that look the same

Pairs people confuse on Nexus Market, and the one test between them

Home Money

Nexus market mirrors

nexusb2l7fmqnefwphyy7m5zjhlkytlbo7qbb5lu5dlczr3azgii2gyd.onion
nexusma2iegzo7atzwbrwxhcdopyri3vare2twibldnlc3txqjdeb5yd.onion
nexusabcdpvtnivv6owtqjkvd22k5x3hlpofkgjqjmgzltlde6mwe2qd.onion

Published as supplied. Nothing here is monitored, so none of this is a claim that any address opens right now.

Group three of six

Money

Money problems on a market almost always arrive as the same picture: an amount that is not where you expected it to be. That picture covers a boring delay and a permanent loss equally well.

The advantage this group has

Money leaves a record, and that makes this the easiest group on the board. A transaction either exists somewhere public or it does not, and that fact does not depend on anybody being honest with you.

The catch is that the public record answers a narrower question than people think. It says a payment was made and where it went. It says nothing about whether a market credited it, matched it to your account, or noticed it at all. Those are separate questions with separate answers, and half the pairs here exist because the two get run together.

A slow deposit against A lost deposit

One is queued on the chain. The other went somewhere the market has no key for.

The test: Look the transaction up and read the destination address off the chain record

OPEN

A deposit address that expired against An address that was never yours

Both strings look equally legitimate. Only one was ever issued to your account.

The test: Does your own signed-in deposit record list that address at all

OPEN

Escrow against The market holding your money

Escrow is a rule with a stated end. Holding is the same money with no end named.

The test: Can you name the event that releases it, and is it tied to one order

OPEN

A fee the market charges against A fee the network charges

One figure is chosen by an operator. The other is set by demand for block space.

The test: Anything missing before broadcast is the operator, anything the chain records is not

OPEN

A discount for ordering more against A discount for paying differently

One saving is priced in goods. The other is priced in the protection you give up.

The test: Does the lower price survive an ordinary order through the ordinary flow

OPEN

A partial refund against A settlement

The figure can be identical. What differs is whether your claim survives it.

The test: Ask whether accepting the amount ends the claim, then read the order state after

OPEN

A withdrawal that is queued against A withdrawal that was rejected

The withdrawal page is the wrong screen. The spendable balance answers it in one number.

The test: Check the spendable balance: missing means queued, returned means refused

OPEN

A payment that is unconfirmed against A payment that is short

One is queued and will settle. The other arrived and does not match the invoice.

The test: Compare the amount that arrived at the address with the amount the invoice asked

OPEN

The mistake this group keeps punishing

Acting on the balance shown to you rather than on the record underneath it. A balance is a number a market chose to display. Under normal circumstances it is correct and there is no reason to look further. When something is wrong, it is the first thing that stops being reliable, and it is also the last thing people think to distrust.

The order that works is the other way round. Check whether the money moved. Then check whether it arrived. Then, and only then, ask why a screen is showing what it is showing.

Where the asymmetry sits

In most of this group, treating a loss as a delay is the cheap error, because waiting costs you time and nothing else. Treating a delay as a loss is the expensive one, because the usual reaction to a believed loss is to send the payment again, and now there really are two of them. The costs page lays that out for every pair on the site at once.

Every page here

AddressesGetting inMoneyOrdersPeopleWordsDown for now, or finished for goodOld address, or one built to be misreadSame page at two addresses, and only one is theirsThe redirect and the string it stands in forYour path through Tor, or the far endDid the set move, or did your copy slipLoading proves a server answered, and nothing moreRate limiting against a password that no longer matchesWhen the puzzle is broken and when the reader isA door you shut yourself against a lock somebody changedLogged out by a clock against logged out by a decisionA code that does not match against a clock that does notAn absence against a single character out of placeA wait somebody planned against a wait nobody didA deposit that is slow, or a deposit that is goneThe address expired, or it was never issued to youA rule about release, or a decision about youWho took the difference, the operator or the networkA saving on quantity, or a saving on protectionMoney back, or the end of the argumentStill moving, or already refusedStill settling, or short by a fractionA date with something behind it, and a date withoutOne request moves a clock, the other moves the moneyAsking for a ruling, or handing over informationA word in a database, and an event in a recordNothing new to report is not the same as bad newsA rule that runs by itself, and a date somebody prefersSilence and being ignored look identicalQuiet is not the same as goneFeedback tells you a mood, evidence tells you a factWhat a signature actually provesThe market only speaks in one placeAn empty history and a claimed historyThe result is good. Whose key was it?The same clean result, months apartYou cannot check an image, however clear it isOne of these strings was chosen by somebodyPosted where, and written by whomWho granted it, and what were they promisingTwo lists of addresses, two different guaranteesHow to read a pairEvery pairThe testsThe costsMirrorsQuestions