Merge pull request #35 from mDuo13/gh-pages

merge footer fix & wallet_propose wording
This commit is contained in:
Rome Reginelli
2014-08-29 11:49:12 -07:00
2 changed files with 2 additions and 2 deletions

View File

@@ -142,7 +142,7 @@ mixpanel.init("132d42885e094171f34467fc54da6fab");
<div class="col-md-2">
<ul class="footer_links middleware">
<li><a href="https://github.com/ripple/gatewayd">Gatewayd</a>
<li><a href="gatewayd.html">Gatewayd</a>
<li><a href="ripple-rest.html">Ripple REST</a>
<li><a href="https://github.com/ripple/ripple-lib">Ripple Lib</a>
</ul>

View File

@@ -1049,7 +1049,7 @@ Each transaction object includes the following fields, depending on whether it w
Use the `wallet_propose` method to generate the keys needed for a new account. The account created this way will only become officially included in the Ripple network when it receives a transaction that provides enough XRP to meet the account reserve. (The `wallet_propose` command does not affect the global network. Technically, it is not strictly necessary for creating a new account: you could generate keys some other way, but that is not recommended.)
*The `wallet_propose` request is an admin command that cannot be run by unpriviledged users!*
*The `wallet_propose` request is an admin command that cannot be run by unpriviledged users!* (Since admin commands are not transmitted over the outside network this command is protected against people sniffing the network for account secrets.)
#### Request Format ####