The Oxen Network has transitioned to the Session Network. More information here.
It is no longer possible to register new ONS mappings. It is possible to update ONS mappings if you still hold OXEN.
Once the new Session Name Service (SNS) launches, it will be possible to create new usernames mapped to Account IDs on Session. ONS mappings will also be migrated to the new SNS.
The following steps can be used to register and update ONS mappings in the CLI wallet. Note that you can access a detailed description of each command within the app, using “help <command_name>”.
Purchasing an Oxen Name System record
Purchasing an ONS record in the CLI wallet uses the ons_buy_mapping command. All arguments for the ons_buy_mapping command are optional except for the <name> and <value> that the name maps to.
Example: Buy an ONS record that maps ‘KeeJef’ to a Session ID: 053 … 254. The wallet buying the mapping is the owner of the record, but specifies a backup owner who will also be authorised to update the record:
Example: Buy an ONS record that maps ‘KeeJef’ to a Session ID: 053…254. You buy on behalf of another wallet T6UD8...ppir and specify another backup wallet:
Updating an Oxen Name System record: Wallet executing update is owner of record
Updating an ONS record in the CLI wallet uses the ons_update_mapping command. All arguments for the ons_update_mapping command are optional except the name of the record to update, and at least one field of the record to update (owner, backup_owner, or value). The [signature] argument is for deferring updates to the record, and is explained in detail in the next section.
Example: Updating the owner of the record (essentially transferring ownership — after changing ownership, you will no longer be authorised to update the record):
Note: At this time you can only update Session ID mappings, you cannot yet add a wallet address mapping to your name — this will require additional changes which will be implemented at a later date.
Example: Update all fields of the mapping.
Updating an Oxen Name System Record: Wallet executing is not owner of record)
In this scenario, you have an ONS record that you wish to update, and you’re able to coordinate with the wallet owning the record. The wallet that owns the record can execute this command to generate a signature.