Skip to content

Commit

Permalink
Updates from attempt at purchaing OUI and devAddr slab
Browse files Browse the repository at this point in the history
  • Loading branch information
deasydoesit authored and jthiller committed Jan 11, 2024
1 parent b3ae95f commit aa9621f
Show file tree
Hide file tree
Showing 2 changed files with 59 additions and 34 deletions.
66 changes: 38 additions & 28 deletions docs/network-iot/run-an-lns/buy-an-oui.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -47,16 +47,38 @@ As an alternate to purchasing a devAddr slab, it is also an option to
and use it in a [roaming](/iot/lorawan-roaming) configuration. An OUI and data credits are required
in either scenario.

Before purchasing an OUI and devAddr Slab, you will need to do the following:
Before purchasing an OUI and devAddr slab, you will need to create the following:

- Generate an owner key pair
- Generate a delegate key pair
- Make sure you have a Helium Wallet
- Helium wallet
- OUI owner key pair
- OUI delegate key pair

You can follow the guide to [create a Helium Wallet](/wallets/helium-wallet-app). Let's now generate
the key pairs.
The steps provided below outline how to create a Helium wallet and OUI owner and delegate key pairs.

### Install The Config Service CLI
### 1. Create Helium Wallet in Solana Format

To create a Helium wallet, you can follow the guide for [creating a new Helium Account](/wallets/helium-wallet-app).

In doing so, a Helium wallet will be generated with key pairs in the native Solana format.

### 2. Convert Solana Formatted Public Key to Legacy Helium Format

The OUI configuration process currently leverages public keys in a format from the legacy Helium L1
blockchain. To convert a Solana public key into the legacy format, use the conversion tool below.

In using the tool, simply paste your Helium wallet public key in the Solana format into the top
"Enter Helium or Solana Wallet Address" field and copy the result from the "Helium Address" field.

**This value will be the Helium wallet public key in the legacy format required for purchasing an
OUI**.

import { DisplayLegacyWallet } from '@theme/DisplayLegacyWallet'

<div className="screensnippet-wrapper">
<DisplayLegacyWallet />
</div>

### 3. Install The Config Service CLI

The [Helium Config Service CLI](https://github.com/helium/helium-config-service-cli) will be used to
generate the key pairs used for the OUI. Run the following commands to pull & build the config
Expand Down Expand Up @@ -103,17 +125,16 @@ automatically be available to your command line.
sudo cp target/release/helium-config-service-cli /usr/local/bin/
```

### Generate OUI Keys
### 4. Generate OUI Keys

Generate the key pairs you'll be using to authenticate your interactions with the config service.
These keys are implemented such that only you can create/modify/delete routes.

After this step you will have at least two keys:

- **Delegate Key Pair**: The delegate key is actively used to create and manage routes. In case it
is ever compromised, it can be updated using the owner key.
Note that an OUI can have multiple delegate key pairs. Guidance on how to manage delegate key
pairs can be found in the [advanced configuration](/iot/run-an-lns/advanced-configuration).
is ever compromised, it can be updated using the owner key. Note that an OUI can have multiple
delegate key pairs. Guidance on how to manage delegate key pairs can be found in the [advanced configuration](/iot/run-an-lns/advanced-configuration).

- **Owner Key Pair**: The owner key is irreplaceable and should be kept safe, secure, and private at
all times. If lost or compromised, you could lose your OUI. The owner key pair is used for
Expand Down Expand Up @@ -150,28 +171,17 @@ helium-config-service-cli env info --keypair <key file name>.bin
}
```

The .bin files should be kept safe and never shared. The public key of these key pairs is the only
The `.bin` files should be kept safe and never shared. The public key of these key pairs is the only
part that should be shared.

### Helium Wallet Address

The OUI configuration process currently leverages public keys in a format from the Helium L1
blockchain. To convert a Solana address into this legacy format, use the conversion tool below.

import { DisplayLegacyWallet } from '@theme/DisplayLegacyWallet'

<div className="screensnippet-wrapper">
<DisplayLegacyWallet />
</div>

### Submit For Purchasing
### 5. Submit For Purchasing

Direct purchase of OUIs and devAddrs are not currently avaliable on-chain. Send an email to
Direct purchase of OUIs and devAddrs are not currently available on-chain. Send an email to
[[email protected]](mailto:[email protected]) containing the following information.

- The public key of your owner key pair
- The public key of your delegate key pair
- The Helium wallet address
- The Helium wallet address (`Step 2` above)
- The public key of your owner key pair (`Step 4` above)
- The public key of your delegate key pair (`Step 4` above)
- The number of devAddrs you want

Once you receive your OUI, the next step is to fund it. There are several options in the
Expand Down
27 changes: 21 additions & 6 deletions docs/wallets/helium-wallet-app.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -67,13 +67,28 @@ See Hotspot manufacturer apps for features like:
/>

Accounts created with the Helium Wallet app are generated with a 24-word seed phrase. These 24 words
in the correct order are the **ONLY** way to access the account and can never be recovered if lost.
**They should never be shared**. Whoever has them is considered the owner of all Tokens, Hotspots,
or NFTs in the account. Anyone asking for them is guaranteed to be a scammer.
in the correct order are the **ONLY** way to access the account and can **NEVER** be recovered if
lost. Whoever has the 24-word seed phrase controls the wallet, meaning that they are considered the
owner of all Tokens, Hotspots, or NFTs in the account.

**Taking and storing screenshots of the seed words is not recommended, as it is not a** secure way
to store them. Screenshots and photos stored or backed up in the cloud can easily be hacked and
funds stolen.
Accordingly, it is **IMPERATIVE** that the 24-word seed phrase be stored in a **SECURE MANNER** and
**NEVER BE SHARED**. Taking and storing screenshots of the seed words is **NOT RECOMMENDED**, as it
is not a secure way to store them. Screenshots and photos stored or backed up in the cloud can
easily be **HACKED** leading to funds being **STOLEN**.

The point cannot be emphasized enough:

**Securely store and never share your 24-word seed phrase**.

**Securely store and never share your 24-word seed phrase**.

**Securely store and never share your 24-word seed phrase**.

Anyone asking for your 24-word seed phrase is **GUARANTEED TO BE A SCAMMER**. If you fail to keep
your 24-word seed phrase secure or if you share your 24-word seed phrase with anybody, all of your
Tokens, Hotspots, or NFTs will be **STOLEN** and will never be able to be recovered!

**SECURELY STORE AND NEVER SHARE YOUR 24-WORD SEED PHRASE!**

### Importing An Existing Account

Expand Down

0 comments on commit aa9621f

Please sign in to comment.