Being trustless and privacy preserving

As Sjors Provoost notes in the introduction to Bitcoin: A Work in Progress, “keeping open-source software free of money-stealing bugs” is an exceedingly difficult task, especially when such software handles funds. Potential exploits in code are visible to all, as are patches awaiting deployment.

For Wasabi, the challenge extends further, as clients participating in coinjoin must follow a coordinator’s lead—a third party whose code cannot be verified. We rarely break compatibility or force updates, meaning users on vulnerable versions will always exist if an exploit is discovered.

Wasabi has consistently been designed to empower clients against potential bad actors:

• Reproducible builds
• Minimal information transmitted to third parties (backend, coordinator, fee providers, etc.)
• “Smart client, Dumb backend” architecture

The complexity involved in building a trustless system is both underappreciated and staggering. Trustlessness invariably comes at the cost of user experience, and these suboptimal workflows must be carefully refined to remain competitive against privacy-degrading or trust-based alternatives.

A prime example of this trade-off is block filters. While alternative wallets allow users to see their balance instantly by connecting to an Electrum server or similar backend solution, how do you retain users when your software first requires them to download 2.6 GB of filters, then download each relevant (or false-positive) block using the Bitcoin peer-to-peer network? To lighten this problem, significant resources have been invested in refining our synchronization process to optimize and ensure the privacy gain is worthwhile for most users.

Clients still need to receive some information from the coordinator: round start times, phase durations, mining fee rates, etc. This information is used to compute the round ID, which clients then use to build and verify everything happening in the round. Two clients receiving different parameters therefore cannot participate in the same round, ensuring a malicious actor cannot mine information by selectively sending different round parameters.

Why the coordination fee concept is not a fit here

The coordination fee rate is a field provided by the coordinator and included in the round parameters. However, this field is unique, as it involves a non-standard agreement: the client must pay this fee only once (concept of free remixes). This is central to how the wallet functions: the client automatically participates in rounds until reaching a certain privacy threshold. If the rounds don’t provide privacy, the client will continue to coinjoin indefinitely. Therefore a coordinator not offering free-remixes could create fast rounds not providing privacy and drain its users. We identified this problem, but the time it took to deploy a mitigation led to the only occurrence in our project’s history that some users funds have been exploited

Free remixes are not the only “workaround” implemented in our client to improve the coordination fee system. Another crucial case for proper user experience is the “1-hop doesn’t pay” rule. This means that if a payment is made using a coinjoin output and this payment produces change, the change doesn’t incur another coordination fee. This rule is essential because clients don’t control the size of their outputs. For instance, a user might receive only outputs of 1 BTC but need to make a payment of 0.1 BTC. The resulting change would not be private and would need to be remixed. Without the “1-hop doesn’t pay” concept, this would result in paying the coordination fee again. Like free remixes, this rule is not enforced by the WabiSabi protocol. To be protected against coordinators that might not offer this “fee grace,” clients would need to carefully select inputs for payments to minimize change value, sometimes at the cost of privacy.

In summary, the coordination fee relates to the implementation layer, and free remixes are not enforced by the WabiSabi CoinJoin Protocol. The protocol paper mentions it only as part of Wasabi’s implementation. The client must trust the coordinator to allow its inputs into rounds indefinitely after the initial payment. A coordinator could decide against offering free remixes, in which case the client must trust it to produce rounds that provide substantial privacy, at least worth the cost.

In other words, the coordination fee concept involves an element of trust. It creates an incentive for the coordinator to act maliciously and forces the client to be highly discerning in recognizing when the coordinator might be attempting to extract more money than it should.

Resources could have been invested during the zkSNACKs era to build a guaranteed risk-free implementation of the coordination fee rate and free remixes concept. However, because the only coordinator used at the time belonged to the same entity funding client development, this type of development was not prioritized, as we knew this coordinator would not breach trust.

This is no longer the case, and the project’s trajectory has changed significantly: resources are now extremely limited, and we prefer not to allocate precious developer hours to ensuring confidence in the coordination fee rate concept. Instead, we choose to allocate these resources to increasing software resilience, improving maintainability, and delivering impactful updates

The post Why are we killing the Coordination Fee? appeared first on Wasabi Wallet - Blog.

Why is zkSNACKs shutting down?

Running a coordinator, especially for profit, involves many regulatory complexities. After careful consideration, they decided it wasn’t a path they wanted to continue pursuing.

What was the relationship between zkSNACKs and Wasabi Wallet?

The co-founder of zkSNACKs, nopara73, co-built Wasabi Wallet and co-authored the WabiSabi coinjoin protocol. His vision for zkSNACKs was to create a cycle where profits from the coordination service would be reinvested into developing better software. This collaboration allowed Wasabi Wallet to be well-funded and feature-rich, making it one of the best in the Bitcoin ecosystem, especially regarding privacy.

How will zkSNACKs shutting down affect Wasabi Wallet?

Wasabi will transition toward being more like other fully open-source projects with low and irregular funding. While Wasabi is already a fully functional, feature-rich Bitcoin wallet, maintaining and improving it without zkSNACKs’ funding will be challenging. Our focus now is to downsize the codebase, remove hard-to-maintain features, and make the software manageable for a few maintainers.

Can users still access their funds if zkSNACKs stops operating?

Absolutely. While some features like exchange rate and mempool updates will stop working, you can still open your wallet and send funds if zkSNACKs’ server goes down. We are currently working on making the wallet more resilient and backend-independent. Wasabi also enables connections to any backend, potentially leading to community-run backends. Last but not least, Wasabi Wallet is fully non-custodial and uses standard BIP39 seeds. You will always be able to recover your funds by entering the seed in another Bitcoin wallet.

What is the value of Wasabi Wallet without the ability to coinjoin?

Wasabi is much more than coinjoins. It’s available on most operating systems, includes Tor, uses BIP157 filters for synchronization, and employs various other privacy-preserving techniques such as change avoidance. Also, coinjoins are still implemented, and anyone can run a coordinator to gather users for coinjoins. In fact, we are already seeing many coinjoins with quite a lot of liquidity.

How can users discover a coordinator?

Currently, most coordinators are advertised through Nostr. There are software tools like WasabiNostr to discover them, pages tracking their liquidity such as LiquiSabi or wasabist.io, and the community also shares information. Wasabi Wallet does not promote any single coordinator, but we are working on an unbiased and spam-resistant coordinator discovery mechanism.

Is it risky to connect to a coordinator with no reputation?

Wasabi Wallet’s coinjoin client is designed to minimize trust in the coordinator. However, because zkSNACKs was the only coordinator, we’ve been complacent. Some attacks are possible to extract funds, but version 2.0.8.1 has significantly mitigated those risks. We are working to ensure it will be safe to connect to any coordinator and reduce attack surface.

How can someone run their own coordinator to coinjoin with their community?

The best way right now is using the BTCPayServer coinjoin plugin, which includes a customizable coordinator that is published on clearnet or as an onion service. We’re also working on integrating an easy way to run a coordinator directly from Wasabi Wallet.

Should Wasabi Wallet’s maintainers and contributors be worried about regulators?

No. Wasabi Wallet is an open-source tool for individuals seeking privacy and financial sovereignty. It’s not malware, doesn’t provide a service, and doesn’t generate revenue. It’s up to the coordinators and users to use our tools responsibly.

How can people help?

Contributions and funding are essential. We’re making it easier for open-source contributors, whether developers or not, to have a significant impact on the project. We’re also setting up donation channels for organizations and users to fund the project. Stay tuned for our first donation campaign announcement. Finally, simply use Wasabi Wallet and spread the word.

What about the long term? I’ve heard about Wasabi 3.

Our goal is to continue improving the best privacy-first Bitcoin wallet and set privacy best practices for the industry. We’re exploring changes for a hard fork of the coinjoin protocol to adapt to a more decentralized paradigm, including managing liquidity across coordinators, developing new revenue models for project resilience, and improving the engine in a small liquidity environment.

The post What’s next for Wasabi Wallet? appeared first on Wasabi Wallet - Blog.

Custom Coordinator Selection

With the sunset of the default coinjoin coordinator managed by zkSNACKs, Wasabi Wallet users must now connect to different coordinators to continue using the coinjoin feature. This selection is now more visible directly from the wallet user interface and in the coinjoin settings. 

Tor Bridges Support

Tor bridges have been added to improve connectivity and privacy for users in restrictive environments where standard Tor usage might be blocked. Tor bridges act as alternative entry points to the Tor network, helping users circumvent censorship, ensuring that Wasabi Wallet remains accessible and reliable at all times.

Whonix & Tails OS Support

Full support for Whonix and Tails OS, two operating systems renowned for their focus on privacy and security, is now available. Whonix is designed to run inside a VM and uses Tor for all network connections, while Tails is a live operating system that routes all traffic through Tor. Toggle your Tor setting to Enabled (connect-only mode) in order to use these tools.

Exclude Coins from Coinjoins

Users can now exclude specific coins from participating in coinjoins. This provides greater control over which coins are selected to participate in coinjoin transactions, allowing users to manage their UTXOs with better flexibility.

GitHub Repository Transfer

The GitHub repository for the Wasabi Wallet has been successfully transferred to a new location. This transfer allows Wasabi Wallet to be maintained as a fully standalone project, independent from any organization and open to multiple different contributors and supporters. The new repository will continue to be the central place for all development activities, issues tracking, and community contributions.

Notable UI and Functional Updates

• UI Adjustments: Multiple user interface improvements, including margin adjustments for labels to prevent shifting, removal of unused XML namespaces, and enhanced styles for various components.
• macOS Specific Fixes: Improved handling of window states to prevent crashes and ensure smoother operation on macOS. 
• Backend Enhancements: Added more statistics to the backend, and updates to various dependencies to improve performance and security.

Additional Improvements

• Statistics and Logging: Added response times to logging, enhanced Statista performance, and included more detailed error handling for output registration. 
• Code and Dependency Updates: Cleaned up code, removed unused components, and updated tooling versions to streamline development and maintenance. 
• Error Handling: Improved handling of reorganization errors and handshake warnings, ensuring robust and resilient operation.

Download the Wasabi Wallet 2.0.8 release at wasabiwallet.io.

The post Wasabi Wallet 2.0.8 Release Post appeared first on Wasabi Wallet - Blog.

Wasabi Wallet will continue to function as a regular bitcoin wallet, users can generate private keys to receive and send bitcoin. Even without coinjoins, Wasabi’s client-side filtering architecture, Tor integration and custom coin selection make it the most private light wallet available. However, the nature of the bitcoin blockchain prevents users from obtaining complete privacy without coinjoins.

This also affects users of other wallet clients that connect to the zkSNACKs coordinator, like Trezor Suite and BTCPayServer.

Wasabi Wallet is a free and open-source software and will continue to be maintained. Anyone can contribute, open new issues, submit pull requests, or even fork it. zkSNACKs will fund the continuous maintenance of Wasabi Wallet’s basic features.

When Wasabi Wallet was launched back in 2018, privacy on bitcoin was only an idea, a dream of cypherpunks. After years of research, trial and error, we proved that bitcoin can be used as anonymous money in a fully sovereign way. Coinjoin allows for a peaceful, secure, and effective way to reclaim financial privacy. We succeeded.

The day will come when someone will write the code to perfect all the properties of good money. Until then, let us be grateful for what we have accomplished together and be mindful of the challenges ahead.

The post zkSNACKs is Discontinuing its Coinjoin Coordination Service 1st of June appeared first on Wasabi Wallet - Blog.

Effective immediately and until further notice, zkSNACKs is now blocking U.S. citizens and residents from visiting its websites, downloading and using Wasabi Wallet and any related products and services, including APIs and RPC interfaces. 

In light of recent announcements by U.S. authorities,zkSNACKs is now strictly prohibiting U.S. users from using its services. An IP address blocking for U.S. residents is effective on wasabiwallet.io, api.wasabiwallet.io and zksnacks.com.

“U.S.” refers to “United States” and includes the several states of the United States and related territories. If you are a United States Citizen or United States Resident, you are not allowed to visit any sites aforementioned, download Wasabi Wallet or use the Wasabi Wallet coinjoin feature. This includes if you are a U.S. permanent resident or if you are an individual who holds a U.S. passport.

The post zkSNACKs is Now Blocking U.S. Residents and Citizens appeared first on Wasabi Wallet - Blog.

A Fresh New Look 

In this release, Wasabi Wallet has a new look with an even darker “dark mode” highlighted by Wasabi’s signature green color. Commonly used menus and features were made more accessible by moving the coinjoin settings to the coinjoin status bar and adding a visible button in the transaction history to speed up unconfirmed transactions.

In version 2.0.7, privacy warnings were made more convenient by displaying amount differences in BTC and USD when avoiding the creation of change outputs. The wallet password required for spending and recovering funds is now called passphrase and specifies that it cannot be reset. A new sorting option was also added to reorder transactions by date.

Trezor Safe 3 Hardware Device Support

The newest Trezor hardware device with secure element protection, open-source design, and on-device confirmation is now compatible with Wasabi Wallet. Trezor is one of the most popular hardware device manufacturers for bitcoin security products. Wasabi Wallet users can now connect their Trezor Safe 3 and use it privately for cold storage.

Partial Support for Full RBF

As of this release, Wasabi Wallet clients are now detecting Full RBF replacement transactions. Also, the coordinator now replaces payments with low fee rates that double spend coinjoin inputs to defend against Denial of Service attacks. 

Privacy Improvements in Version 2.0.7

Autocoinjoin now only begins after funds are confirmed to prevent extra mining fees from being paid for coins that are already private. Tor version was bumped to 0.4.8.10 from 0.4.8.5.

About Wasabi Wallet

Reclaim your privacy with Wasabi Wallet, a free, open-source Bitcoin wallet with built-in coinjoins. Coinjoins are collaborative bitcoin transactions to enable cash-like privacy features for bitcoin. wasabiwallet.io

The post Introducing Release 2.0.7  appeared first on Wasabi Wallet - Blog.

The RPC is used to communicate with a running Wasabi instance. It provides some options and features which are not available (yet) when using the Graphical User Interface. Since Wasabi version 2.0.6, the RPC can be exposed as an onion service, which enables remote control.

Let’s take a look at how to configure the RPC server, its available methods, the features that are currently only available using the RPC. and finally at a usage example.

Configuration

The RPC server is disabled by default. To use the RPC, it has to be enabled in the Config.json file in the Wasabi data folder by setting JsonRpcServerEnabled to true. 

The Remote Procedure Call (RPC) interface allows anonymous and basic authentication access. The default is anonymous access. To enable basic authentication the JsonRpcUser and JsonRpcPassword should be specified in the Config file, and then the right credentials have to be specified at every request.

It is optional (but recommended) to install the jq command line processor and then use | jq at every request to get a structured output.

Available methods

The current latest Wasabi version (v2.0.6) contains 26 RPC methods:

getstatus, createwallet, recoverwallet, listwallets, loadwallet, listcoins, listunspentcoins, getwalletinfo, getnewaddress, send, build, broadcast, speeduptransaction, canceltransaction, gethistory, getfeerates, listkeys, excludefromcoinjoin, startcoinjoin, payincoinjoin, listpaymentsincoinjoin, cancelpaymentincoinjoin, startcoinjoinsweep, stopcoinjoin, buildunsafetransaction, and stop.

Most of these speak for themselves: createwallet creates a new wallet, listwallets list the available wallets etc.

Features currently only available using the Remote Procedure Call

Some methods offer features that are, at the moment of the writing of this article (Wasabi v2.0.6), only available using the RPC interface, like excludefromcoinjoin, payincoinjoin, startcoinjoinsweep and buildunsafetransaction.

excludefromcoinjoin 

Allows to exclude a coin from participating in coinjoin. The coin will never participate in coinjoin until excludefromcoinjoin is set to false.

payincoinjoin 

Allows to pay to a specific bitcoin address in a coinjoin. This saves fees and block space since incoming funds, outgoing payments, and leftover change can all be made private at once.

startcoinjoinsweep 

Allows to sweep (empty) the wallet by sending the coins to the destination wallet in a coinjoin transaction. The destination wallet needs to be a wallet on the same Wasabi client. It works the same as normal coinjoin, except that the outputs are sent to the destination wallet. Note that this is not a proper coinjoin to other wallet implementation, but supposed to be used to empty a wallet.

buildunsafetransaction

Allows to build a transaction with the mining fee being higher than the sent amount, which is otherwise not possible in Wasabi.

listunspentcoins

Although not really a feature, this RPC allows you to see the addresses and derivation path associated with the wallets’ coins, which is not possible to see using the GUI.

Payincoinjoin

One RPC-only feature worth highlighting is the payincoinjoin. Using this RPC method, the user specifies a destination address and the amount, and then the payment will be done in a coinjoin.

In theory, payments in coinjoins be made to any ScriptPubKey, however the zkSNACKs coordinator currently (March 2024) only accepts P2WPKH and P2TR outputs.

payincoinjoin only registers a payment, so if coinjoin is not running or the amount is lower than the wallet balance, the payment is queued.

This feature is new since the 2.0.6 release. The payincoinjoin works, but there are still some optimizations to be made, like to make the coinjoin coin selection aware of payincoinjoin to select coins based on amounts to fulfill the payment. 

Usage Example

The RPC interface can be used with both the daemon as well as the GUI. However using the GUI while also doing RPC calls is not supported and can make Wasabi crash.For wallet specific calls, the wallet name should be specified in the URL.

To simply start using the RPC:

1. Have the RPC configured
2. Open the terminal and launch the Wasabi daemon: wassabeed
3. Open a second terminal window
4. Call the RPC methods (one can simply copy paste the examples listed in the RPC docs:
5. For example: curl -s --data-binary '{"jsonrpc":"2.0","id":"1","method":"getstatus"}' http://127.0.0.1:37128/ | jq

(| jq should be removed, if it is not installed)

getstatus

Wallet specific call: listunspentcoins

Wallet specific call with a parameter:

For demonstration purposes, we did it like this by manually entering it in the terminal, but the RPC also makes it possible to do things in an automated way.

For more information about the RPC: explanation and examples of each method, troubleshooting and how to expose the RPC Server as an onion service, please check out the RPC docs.

The post How to Use Wasabi Wallet’s RPC Interface  appeared first on Wasabi Wallet - Blog.

The latest integration allows users to protect their bitcoin holdings in cold storage with Jade while using the coinjoin feature from the hot wallet, all from the same Wasabi application. You will have to initialize your Jade with the Blockstream Green software wallet, but once that is done you will be ready to use it with Wasabi. 

Why Blockstream Jade?

Blockstream has a striking track record of state-of-the-art engineering, and Jade proves this once again.

“Blockstream Jade is an easy-to-use, purely open-source hardware wallet that offers advanced security for your Bitcoin and Liquid assets.” – Blockstream

One of the key differences between Jade and other hardware wallets is that the device is fully open-source, it doesn’t have a security element BUT is still resistant to physical attacks. Jade achieves this by introducing a zero-knowledge oracle-enforced PIN protection system. Learn more about this innovative approach to physical security here. 

Get your Jade now for only $64.99 on the Blockstream Store. 

How to Connect Your Blockstream Jade with Wasabi Wallet?

Once you follow these simple steps, you should be able to connect your Jade with Wasabi.

1. First,click ‘Add Wallet’ on Wasabi’s sidebar.
2. Then, click on ‘Connect to hardware wallet‘ when the modal opens.
3. Name your new wallet. Click on ‘Continue’ when done.
4. Connect your Jade to your computer and unlock it with the PIN.
   1. Click on Rescan when your device is ready if needed.
5. Wasabi will detect your Jade. Click on Yes if it’s correct.
6. A success confirmation message will appear. Click on Done.

Your Jade is now ready to be used with Wasabi! 

Hardware Wallets that are Compatible with Wasabi

• BitBox02-BtcOnly1*
• Blockstream Jade
• ColdCard MK1, MK2, MK3, MK4
• Ledger Nano S, S Plus, X
• Trezor Model T

1* The device by default asks for a “Pairing code”, currently, there is no such function in Wasabi.Disable the feature or unlock the device with BitBoxApp or hwi-qt before using it with Wasabi.

More On the Juggernaut Release

Wasabi’s Juggernaut Release contains significant performance and privacy improvements and adds compatibility for two popular open-source hardware devices: Blockstream Jade and BitBox02.

To learn more about the details of this release such as the introduction of the Safety Coinjoin feature, the 11 new RPC calls and the performance and user experience improvements, read the announcement article here. 

Download and verify the new version now.

The post Introducing Support for Blockstream Jade on Wasabi Wallet appeared first on Wasabi Wallet - Blog.

Budapest. February 29th, 2024—Wasabi Wallet has released a new software update with its 2.0.6 version. The Juggernaut release 2.0.6 contains significant performance and privacy improvements and It adds compatibility for two popular open-source hardware devices: Blockstream Jade and BitBox02.

Safety Coinjoin & Time Preference

Sometimes users send bitcoin to their wallet for the first time, coinjoin once, and then sweep their funds in one single transaction into cold storage. While an empty hot wallet is good for security, this behavior can have potential privacy drawbacks. To accommodate this behavior, Wasabi Wallet is releasing a new ‘Safety Coinjoin’ feature which is aimed at protecting user privacy with at least two coinjoin rounds for the first Bitcoin deposit into an empty wallet. This new default feature prevents new users from making coin consolidation mistakes. 

Improvements to the coinjoin time preference setting provide better privacy and smarter fee control for users that wait for the cheapest opportunity to coinjoin.

Blockstream Jade and BitBox Hardware Devices

This new release introduces support for two popular hardware devices: Jade from Blockstream and BitBox02. These hardware integrations allow users to protect their bitcoin holdings in cold storage while using the coinjoin feature from the hot wallet on the same desktop app, bringing convenience, security and privacy to a larger group of users. 

New RPC Calls & Payments In Coinjoin

The RPC server has seen a major improvement with 11 new RPC calls available. Chief among them is payments within coinjoins, a feature not yet available on the desktop app interface. It allows users to save fees and improve privacy by sending coins directly to the final destination in a coinjoin transaction instead of performing each step separately. Other RPC calls include: fee rate for payments, anonscore & coinjoin status in get wallet info, recover wallet, speed up transaction, cancel transaction, load wallet, list wallets, exclude from coinjoin, list payments in coinjoin, cancel payment in coinjoin,start coinjoin sweep and fee overpayment protection overwrite. The RPC server can now be exposed as a Tor onion service.

Speed & Performance

The desktop app launch was significantly improved such that users can now benefit from a tighter delay when starting the wallet on their computer. This performance improvement reduces CPU usage and memory consumption by half. The overall wallet load time was slashed by at least 60%, which is due to transaction processing being much more efficient and transactions being stored in a local database instead of a single text file. Major speed benefits can be enjoyed by users of HDD computers. 

User Experience Improvements

Users can now rename their different wallets directly from the interface in the Wallet Settings. Privacy warnings and suggestions displayed while sending now use unique colors to alert users if they are making a non-private transaction. The wallet creation flow was also cleaned up to make the onboarding easier. Success screens are now closed automatically, saving users extra clicks. Discreet mode has been further expanded to hide suggested address labels at address generation. 

Further Improvements & Bug Fixes 

For businesses and users managing large wallets with lots of activity along with smaller wallets: cross-wallet performance was improved to run distinct wallets in parallel on the same computer. Users running the Wasabi executable can use the –help flag in the console to get options for which arguments to pass. The software was upgraded to Avalonia 11 bringing numerous performance benefits for the GUI. .NET 8 was also a major framework upgrade. Nix flake was configured to improve the backend deployment flow from GitHub for users looking to run their own coordinator. UI memory leaks have been fixed. The Coldcard hardware device edge firmware integration had bug fixes. The PGP key to securely report software vulnerabilities was changed. 

“This juggernaut of a release comes packed with all kinds of performance improvements. The wallet is faster to load, the UI is more responsive, and coins get more privacy for less blockspace. Safety coinjoins are introduced to protect new users from undoing their privacy progress. Thanks to the contributors for putting this one together!” – Max Hillebrand, CEO of zkSNACKs and Wasabi Wallet Contributor 

“Our mission at BitBox is to offer the easiest self custody experience possible. We are excited for this integration with Wasabi wallet, that will allow BitBox users to enhance the privacy of their coins, in a simple way” – Douglas Bakkum, CEO at BitBox

About Wasabi Wallet

Reclaim your privacy with Wasabi Wallet, a free and open source bitcoin wallet with built-in coinjoins. Coinjoins are collaborative bitcoin transactions to enable cash-like privacy features for bitcoin. wasabiwallet.io 
Media contact: [email protected]

The post Juggernaut Release 2.0.6 is Out appeared first on Wasabi Wallet - Blog.

What if you could buy a car directly through Wasabi and have it shipped to you? Now you can.  

The ‘Buy Anything’ Button
The 2.0.5 release of Wasabi Wallet includes a “Buy Anything” button that allows you to BUY ANYTHING (legal).

Just click on the “Buy Anything” button next to the “Send” and “Receive” buttons in your wallet to start a chat conversation with ShopinBit’s professional concierge team. 

After letting them know what you want in good detail, you’ll have to wait a few hours (24-48) for a submission. When all the details have been checked by ShopinBit’s team, they’ll give you an offer.

Your order will be confirmed once you accept it and pay the bitcoin invoice.

If the product is physical, you will need to enter your shipping address details to receive it. The shipping time depends on the product and the shipping destination, but don’t worry, you can track your order with the link provided.

“Your Order Has Been Shipped”

The timing of this release couldn’t be better. The new year is starting and Bitcoin’s price is doing well again, you can order anything you want for yourself and your dear ones directly from your favourite wallet.

Download the latest version (2.0.5) of Wasabi Wallet and start shopping now.

We Have Partnered with ShopinBit

We’d like to thank the Shopinbit team for making this possible through their Premium Concierge Service, which allows you to buy anything and get it delivered anywhere. They’re based in Poland and are Europe’s largest Bitcoin store, but they ship worldwide. 

You have a direct communication channel from your Wasabi Wallet client application to Shopinbit’s servers. zkSNACKs (Wasabi’s development company) can’t see anything exchanged on this channel and doesn’t know anything about your orders. 

To learn more about the ShopinBit company and team, click here.  

What are the Limits and the Fees?

For now, the minimum total order price is USD 1,000. There is no limit per se, but only VIP customers can place orders for more than USD 60,000. VIP customers must have at least one previous shopping experience through ShopinBit’s Concierge service.

Fees might vary depending on the order.

Update Wasabi Wallet and Buy Anything with Bitcoin Now

Other Questions You Might Have (FAQ)

1. Can I really buy anything? 

ShopinBit’s Concierge Service does not provide any kind of drugs, prescription medications, weapons, precious metals, cryptocurrencies, financial instruments, or any type of product that is illegal in Poland. You can buy anything else. 

2. Can I pay my rent or another invoice?

Yes, ShopinBit can pay with almost any payment method supported by Wise, Revolut, the banking system and major credit cards, so services like your rent can be paid. 

3. Why does it take 24-48 hours to get my quote? 

All requests are handled manually by ShopinBit’s team and sometimes need to be reviewed with legal counsel. The following 4 points have to be reviewed: 

 a) That the product/service can be bought from Shopinbit;

 b) ShopinBit is allowed to sell the product to you;

 c) ShopinBit can ship the product to you;

 d) It is all legal to do so.

An offer will be issued only until these 4 points are sorted out. If it’s not possible, you will receive a friendly decline with an explanation of why.

4. How is the bitcoin price calculated at the time of the transaction?

The offer quote is always in fiat (in USD precisely) and the final BTC amount is displayed when the user agrees to buy now. The exchange rate is reserved for 30 minutes.

5. Will I get an invoice? 

Yes, it will be available through a download link.

6. What about duties and taxes? 

It will depend on the source and destination of the product. If it has to cross borders, it might be subject to duties or taxes. If it can be purchased in the same country as it’s being delivered, there will be no duty taxes added to the final price.

7. How long does it take to ship a physical product? A digital product?

There is no general answer to this question for physical products. It depends on where the product is (ShopinBit’s warehouse or third-party warehouse) and how it will be shipped to you. 

For digital products, they are shipped on the same day as payment.

8. What is the data management policy? 

ShopinBit pseudonomizes (a.k.a. turns real personal data into generic gibberish) 30 days after completion of the order. ShopinBit is legally obligated to store invoices (with the shipping address), which are kept offline.

Remember that zkSNACKs is never aware of the data of this service, and you can delete your local data anytime.

9.  How does zkSNACKs make money? 

Orders made through Wasabi include an affiliate code and a fair cut is given to zkSNACKs, similar to standard affiliation programs.

10. Will I get in trouble with tax authorities because of this?

We can’t help you with tax issues, you need to know the laws of your own country. In general, if you haven’t paid taxes, you may get in trouble for not paying the taxes, not for spending your money with ShopinBit’s service.

11. What countries are not allowed?

Iran and North Korea are not allowed. Ukraine and Russia are currently halted due to the ongoing war.

12. Does the service include shipping to remote areas? What shipping service will be used?

ShopinBit ships anywhere, if you can pay for it. The service depends on the country. Their team has experience with difficult shipping conditions.

13. What is the return and reimbursement policy?

After you receive your order, you have a 14-day right of return. This means that if you do not like it, you can send it back (you will have to pay for the shipping).

Cars, boats, yachts, airplanes, jewellery, custom and digital items are non-returnable

If you exercise your right of withdrawal, the USD value will be used to calculate the amount of your returned coins on the day your order arrives back at the warehouse. 

The post Buy Anything with Bitcoin through Wasabi Wallet appeared first on Wasabi Wallet - Blog.