Unisocks: The Moment a Token Becomes a Pair of Socks
Uniswap’s 2019 merchandise experiment offered a peculiar choice: keep trading a token, or consume it to request real socks. The interesting part was the handoff from an exchange to a shipping address.

Key Points
- Uniswap Labs launched Unisocks in May 2019; the original app described a pool seeded with 500 SOCKS tokens and ETH.
- Each token represented a claim to one pair. Buying and selling moved the pool price; redeeming used a separate burn flow.
- The redemption interface collected shipping details and displayed a delivery estimate. An onchain action still depended on offchain fulfillment.
Inside this story
Chronological Timeline
Uniswap Labs launches the experiment in merchandise priced through a token pool.
The official commit records the interface for shipping details, token redemption and order confirmation.
Merchandise without a fixed price tag
A pair of socks is usually the end of a purchase. In Uniswap Labs’ May 2019 experiment, it could remain a possibility instead. A buyer acquired SOCKS, a token representing the right to request a real pair. The holder could keep that claim, trade it, or redeem it. The merchandise had become something that could circulate before anybody decided to wear it.[1][2]
SOCKS at this stage was a fungible balance: one unit offered the same kind of claim as another, rather than identifying a particular illustrated character. The app tracked quantities and let the holder choose how many to redeem. That is why the token could be exchanged through an ordinary token pool. The bonus NFT advertised later in the order flow served a different purpose as a collectible.[4][7]
The original app explained that 500 SOCKS tokens were deposited into a Uniswap pool alongside ETH. Its price changed with purchases and sales, rather than staying at a shopkeeper’s fixed tag. A buyer could therefore acquire a claim from the pool without negotiating with a particular sock owner; a seller could return the token to that market. The quantity initially placed in the pool was not a promise that the same number would always remain available there.[2]
Why the next pair could have a different price
Consider a purchase paid in ETH. The pool receives ETH and sends out SOCKS, changing the two reserves used to quote the next trade. Uniswap V1’s exchange code calculates the output from the input amount and both reserves, including a trading fee. Repeated purchases therefore move the quote as the available SOCKS reserve falls. Selling SOCKS back reverses the direction of exchange; it does not return a parcel to a warehouse.[2][6]
Redemption uses a different operation. In the original app, selling calls an exchange function, while claiming socks calls the SOCKS token’s burn function. A sale passes the claim to the market; a burn consumes it. This difference explains why a traded token can be bought again, while the same redeemed claim cannot be used for another pair. Pool inventory and the supply of unredeemed claims are related quantities, but they are not the same counter.[7]
The distinction matters more than a spectacular quoted price. A price in a token pool describes an exchange under that pool’s conditions. It does not establish what the knitted object costs to manufacture, what every holder paid, or what every holder could receive by selling at once. The experiment let demand for the tradable claim interact with demand for the physical item. Those demands need not be identical.[2]
The order consumed the claim
On October 22, 2019, the official repository recorded its redemption launch. The interface asked holders how many SOCKS to redeem, then requested delivery details before the final order step. Its implementation called a burn operation for the selected quantity and waited for the transaction before showing the completion view. Buying a token and ordering a parcel were deliberately different flows.[3][4][5]
For the holder, redemption was a choice about what to keep. Leaving the claim unredeemed preserved the option to trade it or use it later. Redeeming committed the selected tokens to obtaining the physical product. The code made that choice visible as a change of state, not merely a new picture in a wallet. A pair that could be worn came with the loss of the same claim’s future use.[2][4]
A blockchain did not pack the box
The archived delivery form requested a name, postal address, country and email. It asked the wallet to sign a message containing the order details and submitted a web form; the burn transaction was a separate step in the redemption interface. After confirmation, the interface showed an estimated shipping time of two to three weeks, varying by region. That was the app’s estimate, not evidence that every parcel arrived on schedule.[4][5]
The wallet also performed two different jobs. Signing the order message associated the supplied delivery information with the wallet; sending the burn transaction changed the token balance on Ethereum. The source code sends the address form to a web service, not as the payload of that burn call. This division let a transferable onchain claim meet an ordinary shipping process, with the fulfillment service still responsible for turning the request into a delivery.[5][7]
This is where the playful experiment becomes useful to think with. The chain could record the use of a token, but people and delivery services still had to supply the socks. An order confirmation was not a proof of receipt. Unisocks made a physical claim easy to trade, then exposed the ordinary work needed to fulfill it. The most revealing moment was not a price milestone. It was the decision to stop holding a possibility and ask somebody to send a pair of socks. The flow described here is the archived design, not confirmation that an old token can still be redeemed or that a particular order was delivered today.[4][5]
Continue reading
Explore the topic through other cases and contexts.
An album and concert benefits reveal the work that remains after a token reaches a fan’s wallet.
CryptoPunks separates the ownership record, the image and the data needed to verify it.
Sources & References
- [1]Source 1: Uniswap’s account of the May 2019 launchUniswap Labs / Uniswap Foundation · 2025-11-10Accessed 2026-09-19Back to text1
- [2]Source 2: Original app: how SOCKS workedUniswap / GitHubAccessed 2026-09-26
- [3]Source 3: Redemption launch commitUniswap / GitHub · 2019-10-22Accessed 2026-09-19Back to text1
- [4]Source 4: Original app: redemption and shipping statesUniswap / GitHubAccessed 2026-09-19
- [5]Source 5: Original app: delivery-address formUniswap / GitHubAccessed 2026-09-26
- [6]Source 6: Uniswap V1 exchange: reserve-based pricing and swapsUniswap / GitHubAccessed 2026-09-26Back to text1
- [7]Source 7: Original Unisocks app: separate sale and burn operationsUniswap / GitHubAccessed 2026-09-26


