We've completely redesign our network isolation code.
When Wasabi Wallet development began, .NET lacked native support for routing HTTP traffic through Tor, despite having an excellent HttpClient. There was no built-in SOCKS proxy support, so Wasabi's creator implemented the SOCKS protocol to interact with Tor's SOCKS proxy and developed a custom HTTP/1.1 implementation from scratch. This allowed us to maintain network-level privacy by isolating identities behind different types of requests.
However, as time passed, our custom HTTP implementation started showing its limitations. It lacked support for redirects, so we had to build that feature in. When response compression became necessary, we had to add support for a couple of compression algorithms. Additionally, our coordinator announcer uses the Nostr protocol, which is based on WebSocket, meaning we would have had to implement the WebSocket protocol ourselves, too.
It became clear that we needed better building blocks. Continuing to implement low-level network protocols ourselves wasn't sustainable. For example, making a request to an HTTP/2 server would have required extensive work.
The good news is that with .NET 6, proxying HTTP traffic through a SOCKS proxy is now natively supported. This means we can replace all of our custom code with a higher-quality, more performant, efficient, and less memory-hungry HttpClient. This significantly reduces the complexity and volume of our code, improving both maintenance and performance.
#wasabiwallet #privacy #coinjoin #bitcoin
lontivero
npub1nc…dz7mj
2024-10-16 14:46:11
Author Public Key
npub1nccwjspr3nv7h67xx2qhdh2dzzvpyy55gte2dsu8yl7xd7n74y9qydz7mjPublished at
2024-10-16 14:46:11Event JSON
{
"id": "000020533c9dfd63c1d5fa7857a26eb05fba0bd339d91eaa57d68bdbf0acaccf",
"pubkey": "9e30e940238cd9ebebc6328176dd4d109812129442f2a6c38727fc66fa7ea90a",
"created_at": 1729089971,
"kind": 1,
"tags": [
[
"t",
"wasabiwallet"
],
[
"t",
"coinjoin"
],
[
"nonce",
"2433",
"16"
]
],
"content": "We've completely redesign our network isolation code.\n\nWhen Wasabi Wallet development began, .NET lacked native support for routing HTTP traffic through Tor, despite having an excellent HttpClient. There was no built-in SOCKS proxy support, so Wasabi's creator implemented the SOCKS protocol to interact with Tor's SOCKS proxy and developed a custom HTTP/1.1 implementation from scratch. This allowed us to maintain network-level privacy by isolating identities behind different types of requests.\n\nHowever, as time passed, our custom HTTP implementation started showing its limitations. It lacked support for redirects, so we had to build that feature in. When response compression became necessary, we had to add support for a couple of compression algorithms. Additionally, our coordinator announcer uses the Nostr protocol, which is based on WebSocket, meaning we would have had to implement the WebSocket protocol ourselves, too.\n\nIt became clear that we needed better building blocks. Continuing to implement low-level network protocols ourselves wasn't sustainable. For example, making a request to an HTTP/2 server would have required extensive work.\n\nThe good news is that with .NET 6, proxying HTTP traffic through a SOCKS proxy is now natively supported. This means we can replace all of our custom code with a higher-quality, more performant, efficient, and less memory-hungry HttpClient. This significantly reduces the complexity and volume of our code, improving both maintenance and performance.\n\n#wasabiwallet #privacy #coinjoin #bitcoin",
"sig": "9452f49943389121bb99168574e6a3ec86ac393708bcd5ff0c7cc9e35d9dfbd4f02c6e86a91f4e1dfedb678e5359f5fcde7595a5ee464a8a74503f95abc77ea3"
}