44cf9b054b
* updated tutorials with archive + stub * removed out of date faq pages * added binary build instructions section * removed clients from docs * added clients to devportal * moved nym-vs-others to docs from devportal * removed ood quickstart stuff * tweaked integration options page * summary changes for new structure * moved sdk to devportal * removed sdk from docs * changed summary file for new structure * added intro client overview page * added wallet gif * fixed now broken links * removed old comm pages * added references to newer apps (oreowallet + zcash demo) * updated darkfi irc socks5 * fixed broken link --------- Co-authored-by: mfahampshire <mfahampshire@pm.me>
17 lines
741 B
Markdown
17 lines
741 B
Markdown
# Addressing System
|
|
|
|
When a Nym client is initalised, it generates and stores its own public/private keypair locally. When the client starts, it automatically connects to the Nym network and finds out what Nym infrastructure exists. It then chooses and connects to a specific Gateway node via websocket.
|
|
|
|
All apps in the Nym network therefore have an address, in the format:
|
|
|
|
```
|
|
user-identity-key.user-encryption-key@gateway-identity-key
|
|
```
|
|
|
|
Which in practice, looks something like this:
|
|
|
|
```
|
|
DguTcdkWWtDyUFLvQxRdcA8qZhardhE1ZXy1YCC7Zfmq.Dxreouj5RhQqMb3ZaAxgXFdGkmfbDKwk457FdeHGKmQQ@4kjgWmFU1tcGAZYRZR57yFuVAexjLbJ5M7jvo3X5Hkcf
|
|
```
|
|
|
|
This is obviously not very user-friendly and the moment, and will be developed on in the coming months. |