orders ยท post 02 of 7 in this channel
The delivery address field on a WTN market order
Every other field on this market is about the market. This one is about the physical world, which is a different category of thing entirely.
the three wethenorth market addresses
hn2paw7zfvndw3dovycegeqmvvnf4pl67b3g2p7pohjlzavloosh73id.onionhn2paw7zrgujyhnt6mgxlt2q6uhgbke4itpqitxhyfbumq3wtnckbuyd.onionhn2paw7zadwkcra3qzv5e4q547i7e5lvxm62cfxqftuqdu7moiu2ceyd.onionprinted the way they were handed over. no labels, no numbering, nothing here says which one to try first. this feed never opens them, so it has no status light, no percentage and no date of checking to give you.
what actually needs to be in it
The information a delivery needs to arrive. A name that will be accepted at the destination, the address itself, and whatever postal codes the country uses.
That is the complete list. Everything else people add is addition, and every addition is information that did not have to exist anywhere.
what people add that they should not
Instructions. Apologies. Explanations of why the name is different. Notes about when they are home. Requests about packaging. Small talk.
All of it feels helpful and polite. All of it goes into the same field, gets stored in the same place, and describes the person at the other end in ways an address alone does not.
The post on writing too much is about this instinct in general, because it shows up everywhere on a market and this field is where it costs most.
encryption is not a reason to relax
Details are normally encrypted to the vendor, which is genuinely good and is the arrangement you should expect. The post on pgp, the short version covers what that means.
What it protects is the message in transit and at rest on the market. What it does not do is control what the vendor does with it after decrypting.
Encryption moves the risk from many places to one place. It does not remove it, and a field that is encrypted is still a field that someone reads.
formatting matters more than you think
Write it the way the postal system in that country expects it. A correctly formatted address is handled by machines and a badly formatted one is handled by people.
This is a small practical point with a large practical effect, and it has nothing to do with security. It is simply how deliveries work.
check it twice, then check the name
A wrong number in a street address is not recoverable once the order is on its way. Neither is a name that will not be accepted at the destination.
Read it back once slowly before the confirm click, in the same spirit as the checks in how to read one. Reading forwards is fine here, because you wrote it and you know what it should say.
afterwards
If the market or the vendor offers a way to clear the details once the order is complete, use it. Information that no longer needs to exist should stop existing.
That is not paranoia, it is housekeeping, and it is the sort of thing that is trivial to do at the time and impossible to do later.
replies
a reader askedShould I use a different name than my own?
the answerThis feed does not advise on that. What it will say is that a name has to be one the delivery will be accepted under, and that this is a practical constraint people discover too late.
a reader askedIs it safe to put my real address in this field?
the answerSafe is not a word this feed uses about anything. The field is normally encrypted to the vendor, and beyond that you are trusting a person you have never met with a physical location.
a reader askedCan I send the address in a message instead?
the answerSome people do. It puts the same information in a different box on the same market, so the change is smaller than it feels unless the message handling is meaningfully different.
what this post is not Not advice about what to write in the name line, and not a claim that any particular arrangement makes a delivery untraceable.