What Changed on Nexus
A notebook of quiet shifts on Nexus Market
Three Nexus addresses, published as supplied. No labels, no ranking, no claim any of them opens right now.

Nexus invoices are shown PGP-signed now

in the past few months ยท money

The invoice screen now shows a PGP signature block under the amount and address, produced against the market signing key.

A signature block on an invoice is the market saying, in plain cryptographic terms, that the invoice you are looking at came from it and has not been tampered with in transit. The change is quiet in the layout. It sits below the amount and above the fine print. It changes what a careful reader can prove before sending money.

How it read before

The old invoice was plain text. It carried the amount, the address, and the fine print. It carried no signature. The reason a reader trusted the invoice was the URL. If the URL was the real market URL, the invoice was assumed to be real. That chain of trust was fine on paper, but it required the reader to have already checked the URL, which is a check that is easy to skip when the reader is used to visiting the site every day.

The failure mode was phishing. A lookalike site could present a plausible invoice with an address the operator of the lookalike controlled. The reader would follow the on-page instructions in good faith and the money would land in the phisher wallet, not the market wallet. There was nothing on the invoice itself that could be checked against a key the reader already had.

How it reads now

The invoice sits above a signature block. The block contains the amount and the address in a normalised form, signed with the market key. A reader who has the market public key imported into their PGP tool can copy the block and verify it. Verification either passes or fails. A pass means the signature was made by the holder of the market key against exactly that amount and that address.

Nothing about the block looks impressive. It is a chunk of hyphens and letters and slashes. That is what a signature is supposed to look like. The point is not the aesthetics; it is that a machine can now tell you whether the invoice is what it says it is.

Why this probably shifted

The most likely reading is a response to phishing pressure. Lookalike sites have got closer to the real one in the way they render, and the same pattern that gets readers ordering before verifying also gets them paying invoices on lookalike sites without noticing. A signed invoice moves the trust check off the URL and onto the key. The URL can be spoofed. The key held by the operators cannot be, provided a reader has the real one.

A related reading is that vendors are moving in the same direction. PGP keys are being quoted in the listing header rather than hidden in a profile tab. If both the market and the vendors are pushing keys forward, the reader is being invited to build a habit around checking them. The invoice signature is the market side of that invitation.

What to change on your side

Import the market public key into your PGP tool once, from a source you trust, and keep it. Verify at least the first invoice per session. The check takes a moment. It rules out an entire class of failure that used to be invisible.

  • Import the key once, from a source you can defend, and store the fingerprint separately.
  • Copy the signature block, verify it against the market key, and check the address inside the signed payload matches the one on the page.
  • If the signature does not verify, do not send. That is the whole point of the check.
  • Follow the first-PGP habits rather than the shortcut you were tempted by the first time you saw a signature block; the shortcut turns off the very thing the block is for.

The check is not a substitute for verifying the market itself. Read the current addresses page before you land on the invoice, then verify the signature after you land on it. The two checks answer different questions; do both.

What this entry is not claiming

This entry is not claiming that a signed invoice makes you safe on any site, that the signature protects you from a fake key, or that verifying is optional. It is claiming that the invoice screen now carries a signature block, that verifying it against the real market key answers a question that used to be unanswerable from the invoice itself, and that a reader who never verifies is leaving that signal on the floor.