# Ledger, xBOMB Collateral workaround

A few of our users have experienced problems when trying to deposit xBOMB as collateral into our [busm.money](https://busm.money/) protocol when using a Ledger device.

Please follow the steps below to manually fix this problem! (Until a long term fix has been applied).

* Head to [this link](https://bscscan.com/address/0x66a5224a941bc56dccdaf6c37f29f3e4bcb8f9eb).
* Select "**Contract**".

![](/files/BDaH8kFnk9mPMaYf0sSr)

* Select "**Write Contract**".

![](/files/hRAp0BJ0nLRMtK9gwjGO)

* Click "**Connect to Web3**". (*Connect with your Ledger).*

![](/files/kJxjLOxjgsRFAYS5iooI)

* Once connected, scroll down to section "**10. SetMasterContractApproval**".
* Enter the following information;
* user - **enter your Ledger address here**
* masterContract - **0x070430D1C765623C46C66c06A8164bB29705fF7F**
* approved - **true**
* v - **0**
* r - **0x**
* s - **0x**

![](/files/XsIcOmFAVolBg912VnCp)

* After you have filled in the information correctly, click "**Write**" and confirm the MetaMask transaction.

Once these steps have been completed, you can head back over to [busm.money](https://busm.money/) and deposit your xBOMB as collateral, problem solved!


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.bomb.money/protocol/ledger-xbomb-collateral-workaround.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.