Why the Same Place Can Produce a Different SeedAddress Phrase
Learn why a place name is not a permanent recovery input, how coordinates affect SeedAddress derivation, and what to record for reproducible recovery.
The same place name can produce a different SeedAddress phrase later because the phrase is derived from coordinates, not from the words you typed into the search box. A search result can resolve to another place, a mapping provider can update its data, or the selected place can receive different coordinates. If the coordinates, password, language or word length change, the deterministic result can change too. Because the v1 method uses a geohash at precision 9, two nearby coordinates in the same geohash cell can still produce the same phrase; crossing a cell boundary can change it. Keep an independent offline backup instead of relying on a future search for the same name.
A place name is not the derivation input
SeedAddress first uses address search to let you select a place. The application sends the selected place ID to its map provider and requests the place's latitude and longitude. Google's Geocoding API documentation describes geocoding as converting a place or address into geographic coordinates and a Place ID. The visible label is therefore a convenient description; the coordinates returned for the selected result are what enter the derivation flow.
This distinction matters when a search has several similar results. A street, building, park or business can have nearby entries with similar names. Selecting a different suggestion can return a different Place ID and a different point even when the text looks almost identical. Record the complete selected address and coordinates after choosing the result, rather than relying on memory of the search phrase. The current interface does not offer a field for pasting old coordinates, so this record documents and compares the original inputs; it does not guarantee that the UI can reproduce them later.
Why coordinates can change over time
Geographic data is maintained by a provider. Places can move, addresses can be corrected, boundaries can be mapped differently, and a provider can improve its geocoding result. Google says that Place IDs may change over time and that the same place or location can have multiple different Place IDs. A Place ID helps identify a result across Google Maps Platform APIs, but it is not a permanent promise that a future lookup will return the same coordinates.
This does not mean that every repeated search will change. It means that a place name, result or Place ID should not be treated as a cryptographic backup. A future lookup may return the same latitude and longitude, but recovery depends on the exact values used when the phrase was created. Google's geocoding best practices also distinguish complete address geocoding from ambiguous place searches, which is another reason to keep the selected result precise.
What SeedAddress derives from the selected inputs
In the browser, SeedAddress derives a mnemonic from four inputs: the selected latitude and longitude, a password, the word length and the language. The current v1 method hashes the password, combines it with a geohash of the coordinates and derives bytes for a BIP39-compatible word list. The password and mnemonic stay in transient browser memory during this step; they are not sent to the map service.
Changing any of these values changes the output:
- Selecting a nearby result can change the latitude or longitude and can change the result.
- A provider update can return a different coordinate for the same visible place and can change the result.
- A different password can produce a different derivation.
- Changing the language can select another word list and change the result.
- Choosing 12, 15, 18, 21 or 24 words can change the result length and derived bytes.
The BIP39 specification defines how entropy and a checksum are represented as mnemonic words. It does not turn a place name into a stable secret or recover the coordinates that were used previously. A valid-looking phrase cannot tell you which map result, password or language produced it.
What to record for recovery
If you choose to use SeedAddress as a deterministic recovery tool, keep a private record of the inputs needed to reproduce the result:
- The complete selected place label and the latitude and longitude returned at creation time.
- The word length and language selected in the generator.
- A safe, independent way to preserve the password without exposing it to connected services.
- An offline backup of the resulting phrase, stored separately from the device or account it protects.
Do not put a real password or phrase in this article, a test form, a screenshot, a cloud note or a website. A map address is public information, but the password and mnemonic are secrets. Keep enough context to distinguish a SeedAddress password from a wallet's optional BIP39 passphrase; they serve different roles. The BIP39 passphrase guide explains that difference.
The independent phrase backup is the important fallback. If the provider later returns another point, the old coordinates are missing, or the password is lost, searching for the same visible place may not reproduce the original result. The current UI cannot restore by pasting a previous coordinate pair, so a saved coordinate record is evidence for comparison rather than a recovery guarantee. The recovery guide describes the inputs required by the existing v1 flow.
What a longer phrase does not fix
SeedAddress does not add random entropy during its deterministic derivation. A 24-word output is therefore not guaranteed to provide 256-bit security merely because it has 24 words. The public address is not a secret, and the five-character minimum is retained for legacy compatibility; it is not a recommendation for a new password.
Use a wallet's secure random generation when you need a fresh wallet seed with new entropy. If you use SeedAddress for a reproducible result, test the recovery procedure with harmless inputs before relying on it and preserve the exact inputs and an independent offline copy. Never infer the old phrase by trying nearby coordinates or by entering words into an online checker.
If the result no longer matches
Stop before moving funds. Compare the recorded latitude and longitude, password process, language and word length with the original record. Confirm that the same locale and word list are selected, and check whether you selected the same place result rather than merely typing the same name. If you have an independent phrase backup, use the wallet's documented recovery process instead of guessing which coordinates changed.
The practical rule is simple: treat a place name as a search aid and the exact coordinates as a recovery input. Keeping both an independent backup and a precise input record makes the deterministic trade-off visible before it becomes a recovery surprise.