---
# System prepended metadata

title: Account Naming dApp
tags: [dApp ideas]

---

# Account Naming dApp

### The following question was recently asked in the Provenance slack engineering channel:

*Hi all, I have a quick question I would really appreciate help with -- does anyone know how I can update the accountname for our validator account? our accounting service noticed that there is an accountName field in the API response for the provenance explorer here that is blank, which they were hoping to use that in their API response to clarify which accounts are which. I'm wondering where/how we can set that field for our account?*

The ability to name accounts is an as yet unexercised feature that is a good use case for the creation of a simple dApp to name (i.e. alias) accounts. In order to avoid unrestricted names, a smart contract (SC) is desirable that owns the root of a name (for example, pb which currently exists as a name root in Provenance). A new SC instance would be created for new roots if desired. Adding names to the account is then granted by the SC.

### Proposal

Design a Provenance dApp that adds names to accounts, instantiates new roots, and assesses fees.

### Design Flow

The dApp would consist of the following components and capabilities:

1. Frontend UI:
*     Allow a user to established a new root or use an existing root.
*     Allow a user to name their account using the selected root

2. Smart Contract
*     Instantiate new versions of the SC instance with new root names
*     Update existing instances with new names to apply to provided accounts
*     Assess fees

### Scope of Work

Outside of the work required to create this dApp, Explorer would also need to be updated for service and frontend to account for the possibility of multiple names being applied to a single address.

###### tags: `dApp ideas`