Two things that look the same

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

Home Money Who took the difference, the operator or the network

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.

Money / Pair 18 of 41

Who took the difference, the operator or the network

You asked for one number and a smaller one turned up. Two completely separate parties can be responsible for that gap, and only one of them is reachable.

Two subtractions that look like one

On screen it is a single difference between what you requested and what landed. Nobody labels the pieces. Where a site shows a fee line at all, it may show one figure covering both, and the amount at the far end says nothing about how the shortfall was split.

The two are not the same kind of thing. One is a decision somebody made. The other is weather.

A fee the market chargesA

Set by an operator, kept by an operator

An amount subtracted on the ledger the site keeps, before anything reaches the chain. Somebody chose the figure and somebody can change it, and it appears as a line in an order or a withdrawal. It goes to the operator and to nobody else.

A fee the network chargesB

Set by demand for block space

An amount paid to whoever includes the transaction in a block. It rises and falls with how many people want space at that moment. The market does not receive it, cannot waive it, and cannot push it below what the network will accept for a transaction that moves.

QuestionThe market feeThe network fee
Who sets itAn operator, by decisionDemand for block space that hour
Who receives itThe operatorWhoever includes it in a block
Where it showsA line in an order or a withdrawalThe gap between sent and received on the chain
Can it be waivedIn principle, by the operatorNo, by anybody
What makes it moveA policy changeThe hour you happen to send

That table is the whole distinction. Everything after it is arithmetic.

One arrangement blurs the line deliberately, and it is common enough to plan for. A site quotes a single flat figure described as covering the network, then builds the transaction whenever it suits and keeps whatever the estimate over-collected. The label says network, the surplus goes to the operator, and the chain record is the only place that difference shows up. Batching several withdrawals into one transaction works the same way, since the chain fee is shared while each account may have been charged as though it stood alone.

Who sets the number and who gets it

Money safety here is mostly about knowing which complaint is worth making. Arguing with an operator about block space wastes time on both sides. Accepting a cut set by an operator as though it were the tide is a slow leak you never notice, which is the more common of the two and by far the quieter.

Split the difference at the broadcast

Compare the amount the site said it was sending against the amount the chain records as sent. What went missing before broadcast belongs to the operator, and what the chain records as fee does not.

  1. Note the amount you requested and the amount the site said it would send.
  2. Find the transaction on the chain and read the amount it actually moved.
  3. Subtract what arrived from what was sent according to the chain record.
  4. The chain difference is the network. The gap between your request and the chain record is the site.

That works on a withdrawal, where a transaction exists to inspect. On an order it is simpler still, since a market fee on an order never touches the chain at all. Anything added to an order total before you pay is a decision by definition, whatever the line is called, and the network has not been involved yet.

The direction that compounds

If you read a market fee as a network fee
You treat a figure somebody chose as though it were unavoidable. You never ask about a line you are entitled to ask about, you never compare it against anything, and you pay it again on every order and every withdrawal for as long as the account lives.
If you read a network fee as a market fee
You accuse an operator of skimming something they never touched. The uglier version is that you then set your own fee low to dodge a cut that was never theirs, and the payment sits in the queue for a long while as a result.

The first compounds and the second does not. A network fee is paid once and forgotten. A share taken by an operator repeats on every movement, and a quiet change in it can pass unnoticed for months once you have decided in advance that the shortfall was nobody's doing. The second error is sharper but it teaches itself quickly, usually by way of a payment that will not move.

Acting on each

If it is the market fee
Find where the figure is published and read it before the next order rather than after. A change is a change by decision, and that is a fact about the operator worth filing alongside everything else you know about them.
If it is the network fee
Set the fee to suit the hour rather than the habit. Paying a little more when demand is high is cheaper than a transaction that sits, and paying less when things are quiet costs you nothing at all.

Questions readers send about this pair

Why does the fee differ between two withdrawals of the same size?

If the site line is identical and the total still differs, the moving part is the network. Space in a block is bid for, so the same transaction costs differently at different hours. Size in bytes matters more here than size in value.

Can a market waive the network fee?

No. They can pay it on your behalf and fold it into their own pricing, which is not the same thing. Nobody moves a transaction without paying whoever includes it in a block.

Should the fee line always be visible before I confirm?

A site that shows its own line before you commit is easier to reason about than one that does not. Where nothing is shown, the chain record still lets you work the split out afterwards, which is slower but just as conclusive.

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