<p>The base fee is contained in the ledger and can only be changed by a pseudo-transaction that gets into the consensus set. It's managed by consensus the same way the reserve levels are.</p>

CC BY-SA 3.0
2013-04-26T18:36:31.737Z
"It's managed by consensus the same way the reserve levels are" Details on that process are here: https://ripple.com/wiki/Change_Process
dchapes
CC BY-SA 3.0
2013-04-26T09:05:50.460Z
2013-04-26T09:05:50.460Z
David Schwartz
<p>The <a href="https://ripple.com/wiki/Transaction_Fee" rel="nofollow">Ripple wiki</a> says (emphasis added):</p>

<blockquote>
  <p>If the reference transaction should cost 10 millionths of a ripple, the "base fee" should be set to 10. This is the current value. This makes it very simple to adjust fees to keep them sensible -- <strong>just figure out how many millionths of a Ripple the reference transaction should cost</strong> and set that as the base fee.</p>
</blockquote>

<p>Yes, and how does the system figure out what a reference transaction would cost?</p>

<p>It would be great to know how the transaction fee is determined and how it is adjusted in response to deflation (rising value of XRP or falling supply of the units).</p>

CC BY-SA 3.0
2013-04-26T08:39:22.653Z
Manish, you're flooding a lot of Ripple questions onto here at a higher rate than people can vote on them or answer.  Can I ask why?
eMansipater
CC BY-SA 3.0
2013-04-27T22:40:04.993Z
@eMansipater Yes, sir, you may ask, and I can tell you that I was reading the specs and I posted the questions as they popped into my head. Is that bad form? I could just write down my questions in a text editor and post them at intervals of an hour or two, if that's better. I certainly didn't mean to "flood" anything.
Manish
CC BY-SA 3.0
2013-04-28T18:44:37.970Z
no real problem.  Sometimes flooding a lot of questions is an indicator that someone doesn't quite get how to use Stack Exchange so I was curious where the questions were coming from.  Would you say that the sorts of things you were asking about are missing holes in the existing Ripple documentation, or more just that you were using this as a way to kind of get Ripple into your head?  Generally Stack Exchange works well for individual answers where someone will take the time to give an an-depth answer.  With the rapid fire style you might have better luck on the Ripple forums.
eMansipater
CC BY-SA 3.0
2013-04-28T18:46:52.747Z
(You'll note that although David Schwartz was able to keep up with basic answers he didn't really have time to answer all the questions in depth.)  Stack Exchange shines best when someone can take a few specific questions and answer them so effectively that anyone in the future of the internet would prefer that answer to any other treatment of the question.  When questions are getting fired off too fast, it's hard for the experts to provide that level of detail and quality.  That's all.
eMansipater
CC BY-SA 3.0
2013-04-30T08:57:30.593Z
@eMansipater Frankly, I don't know what you're talking about. If you can point me to one question I posted about Ripple in those few minutes that didn't meet the quality standards of this site, then I'll admit you have a point. If the documentation already contained the answer, then I wouldn't be asking the question. "No real problem." OK, case closed!
Manish
CC BY-SA 3.0
2013-04-30T10:18:48.850Z
"point me to one question"--it's not really about that, more about continually improving the quality of the site.  One weird thing for people to wrap their heads around with Stack Exchange sites is that even an obscure question will often be used by 50 people who later visit, and more than 20,000 people for a really good one.  So the real trick to creating a good Stack Exchange site is working to make questions and answers 20,000 times better than they "need" to be.  That's what people like me are always on about--the 20,000 *other* people who could benefit from an improvement.
eMansipater
CC BY-SA 3.0
2013-05-01T21:28:47.340Z
@eMansipater Thanks, I really appreciate the work you put into the site. I have learnt a lot from it for sure.
Manish
<ripple><ripple-transaction-fees>
With Ripple, how is base fee (transaction fee) calculated?
Manish
# With Ripple, how is base fee (transaction fee) calculated?

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

The [Ripple wiki](https://ripple.com/wiki/Transaction_Fee) says (emphasis added):

> If the reference transaction should cost 10 millionths of a ripple, the "base fee" should be set to 10. This is the current value. This makes it very simple to adjust fees to keep them sensible -- **just figure out how many millionths of a Ripple the reference transaction should cost** and set that as the base fee.

Yes, and how does the system figure out what a reference transaction would cost?

It would be great to know how the transaction fee is determined and how it is adjusted in response to deflation (rising value of XRP or falling supply of the units).

**Tags:** ripple, ripple-transaction-fees

> **Comments:**
> **username_1**: username_0, you're flooding a lot of Ripple questions onto here at a higher rate than people can vote on them or answer.  Can I ask why?  
> **username_0**: @username_1 Yes, sir, you may ask, and I can tell you that I was reading the specs and I posted the questions as they popped into my head. Is that bad form? I could just write down my questions in a text editor and post them at intervals of an hour or two, if that's better. I certainly didn't mean to "flood" anything.  
> **username_1**: no real problem.  Sometimes flooding a lot of questions is an indicator that someone doesn't quite get how to use Stack Exchange so I was curious where the questions were coming from.  Would you say that the sorts of things you were asking about are missing holes in the existing Ripple documentation, or more just that you were using this as a way to kind of get Ripple into your head?  Generally Stack Exchange works well for individual answers where someone will take the time to give an an-depth answer.  With the rapid fire style you might have better luck on the Ripple forums.  
> **username_1**: (You'll note that although username_2 username_2 was able to keep up with basic answers he didn't really have time to answer all the questions in depth.)  Stack Exchange shines best when someone can take a few specific questions and answer them so effectively that anyone in the future of the internet would prefer that answer to any other treatment of the question.  When questions are getting fired off too fast, it's hard for the experts to provide that level of detail and quality.  That's all.  
> **username_0**: @username_1 Frankly, I don't know what you're talking about. If you can point me to one question I posted about Ripple in those few minutes that didn't meet the quality standards of this site, then I'll admit you have a point. If the documentation already contained the answer, then I wouldn't be asking the question. "No real problem." OK, case closed!  
> **username_1**: "point me to one question"--it's not really about that, more about continually improving the quality of the site.  One weird thing for people to wrap their heads around with Stack Exchange sites is that even an obscure question will often be used by 50 people who later visit, and more than 20,000 people for a really good one.  So the real trick to creating a good Stack Exchange site is working to make questions and answers 20,000 times better than they "need" to be.  That's what people like me are always on about--the 20,000 *other* people who could benefit from an improvement.  
> **username_0**: @username_1 Thanks, I really appreciate the work you put into the site. I have learnt a lot from it for sure.  

---

## 1 answers

### Answer by username_2 on 2013-04-26. Score: 2 | Accepted answer

The base fee is contained in the ledger and can only be changed by a pseudo-transaction that gets into the consensus set. It's managed by consensus the same way the reserve levels are.

> **Comments:**
> **username_3**: "It's managed by consensus the same way the reserve levels are" Details on that process are here: https://ripple.com/wiki/Change_Process  

---

