<p>This was created specifically to resolve a problem Bitstamp was having. Though there is absolutely no reason to send XRP to Bitstamp, people were constantly doing that. Bitsamp had to either steal the XRP or refund it. Obviously, they wanted to refund it. But this would drain their hot wallet of XRP.</p>

<p>To resolve this, we're in the process of adding the flag you mentioned, "lsfDisallowXRP". If the flag is set, the client will not let you send XRP to the account that has set it. Bitstamp would then set this flag.</p>

<p>Bitstamp can still put XRP in the account to fund its transactions by simply ignoring the flag. We may also add a way to override the flag in the client, possibly by putting a special marker at the end of the address or possibly with a button.</p>

CC BY-SA 3.0
2013-04-27T22:34:22.157Z
By the way, I think the reason people are sending XRP to Bitstamp is that they think they can sell it there. I did it myself, and it bounced. Then I realized that Bitstamp only has a "Buy Ripples" option, no option to sell.
Manish
CC BY-SA 3.0
2013-05-06T19:17:39.133Z
Send them to me instead.
Vinnie Falco
CC BY-SA 3.0
2013-04-26T09:13:33.850Z
2013-04-26T09:13:33.850Z
David Schwartz
<p>In the spec for the <a href="https://ripple.com/wiki/Ledger_Format" rel="nofollow">ledger format</a>, there's a flag called "lsfDisallowXRP" in the account root entry. It says: "Indicates that this account does not want to receive XRP." But why wouldn't an account want to receive XRP, given that it's necessary for doing any transactions?</p>

<protocol><ripple>
With Ripple, what is lsfDisallowXRP?
Manish
# With Ripple, what is lsfDisallowXRP?

(Asked by: username_0 on 2013-04-26)

In the spec for the [ledger format](https://ripple.com/wiki/Ledger_Format), there's a flag called "lsfDisallowXRP" in the account root entry. It says: "Indicates that this account does not want to receive XRP." But why wouldn't an account want to receive XRP, given that it's necessary for doing any transactions?

**Tags:** protocol, ripple


---

## 1 answers

### Answer by username_1 on 2013-04-26. Score: 3 | Accepted answer

This was created specifically to resolve a problem Bitstamp was having. Though there is absolutely no reason to send XRP to Bitstamp, people were constantly doing that. Bitsamp had to either steal the XRP or refund it. Obviously, they wanted to refund it. But this would drain their hot wallet of XRP.

To resolve this, we're in the process of adding the flag you mentioned, "lsfDisallowXRP". If the flag is set, the client will not let you send XRP to the account that has set it. Bitstamp would then set this flag.

Bitstamp can still put XRP in the account to fund its transactions by simply ignoring the flag. We may also add a way to override the flag in the client, possibly by putting a special marker at the end of the address or possibly with a button.

> **Comments:**
> **username_0**: By the way, I think the reason people are sending XRP to Bitstamp is that they think they can sell it there. I did it myself, and it bounced. Then I realized that Bitstamp only has a "Buy Ripples" option, no option to sell.  
> **username_2**: Send them to me instead.  

---

