<p>The original idea of the field was to keep a hash of the contents of your wallet that you could update in the Ripple ledger. Your wallet would also contain any prior hashes of earlier versions of the wallet that you couldn't confirm had already been replaced in the ledger. </p>

<p>That way, a malicious (or negligent) wallet provider couldn't serve you an old/obsolete version of your wallet. You just retrieve your <code>WalletLocator</code> from the network and if that isn't either the hash of your wallet or a prior hash stored in your wallet, you know you have a newer wallet out there somewhere. This would also catch the case where you store your wallet in more than one place and retrieve it from the "wrong" place.</p>

<p>Since the field was added, a different wallet model was used. But the field is still in the server and Ripple network in case anyone wants to use it.</p>

CC BY-SA 3.0
2014-02-04T20:18:23.777Z
2014-02-04T20:18:23.777Z
David Schwartz
<p><a href="https://ripple.com/wiki/Transaction_Format#AccountSet_.283.29" rel="nofollow">https://ripple.com/wiki/Transaction_Format#AccountSet_.283.29</a> defines  a field "WalletLocator" (256 bits) in Ripple's AccountSet transaction. That means that the field belongs to an account, and the owner of the account can set this field to whatever value they want. </p>

<p>Currently, it's not yet implemented in the <a href="https://github.com/ripple/ripple-lib/blob/develop/src/js/ripple/transaction.js#L460" rel="nofollow">client code</a> but in the <a href="https://github.com/ripple/rippled/blob/d22b25c030fe2f3d98e3ecd95763cbd0d2d166af/src/ripple_app/tx/AccountSetTransactor.cpp#L200" rel="nofollow">server code</a>. I'm not able to make sense of the name "WalletLocator", and the code doesn't provide an explanation either.</p>

<p>What's the purpose of the field?</p>

<ripple>
What's the purpose of the WalletLocator field in Ripple accounts?
real-or-random
# What's the purpose of the WalletLocator field in Ripple accounts?

(Asked by: username_0 on 2014-02-04)

<https://ripple.com/wiki/Transaction_Format#AccountSet_.283.29> defines a field "WalletLocator" (256 bits) in Ripple's AccountSet transaction. That means that the field belongs to an account, and the owner of the account can set this field to whatever value they want.

Currently, it's not yet implemented in the [client code](https://github.com/ripple/ripple-lib/blob/develop/src/js/ripple/transaction.js#L460) but in the [server code](https://github.com/ripple/rippled/blob/d22b25c030fe2f3d98e3ecd95763cbd0d2d166af/src/ripple_app/tx/AccountSetTransactor.cpp#L200). I'm not able to make sense of the name "WalletLocator", and the code doesn't provide an explanation either.

What's the purpose of the field?

**Tags:** ripple


---

## 1 answers

### Answer by username_1 on 2014-02-04. Score: 2 | Accepted answer

The original idea of the field was to keep a hash of the contents of your wallet that you could update in the Ripple ledger. Your wallet would also contain any prior hashes of earlier versions of the wallet that you couldn't confirm had already been replaced in the ledger.

That way, a malicious (or negligent) wallet provider couldn't serve you an old/obsolete version of your wallet. You just retrieve your `WalletLocator` from the network and if that isn't either the hash of your wallet or a prior hash stored in your wallet, you know you have a newer wallet out there somewhere. This would also catch the case where you store your wallet in more than one place and retrieve it from the "wrong" place.

Since the field was added, a different wallet model was used. But the field is still in the server and Ripple network in case anyone wants to use it.


---

