Some of the documentation (e.g. for RPC commands) uses d/myname, some of it uses myname, some of it uses d/abc, and some of it uses d/domob.
It would be nice to standardize this. Just using myname without the d/ is confusing, but otherwise I don't have a strong opinion. I would suggest d/example, however it's squatted. d/namecoin might work. We could also use a specific namespace, like ex/domain, although this has some risk of confusion.
In upstream, there is a const std::string array EXAMPLE_ADDRESS with some (invalid) bech32 addresses. That is a good model of how to do it.
Of these, I personally prefer d/namecoin or d/domob, but ACK on using a const std::string for this; we can bikeshed about which example name to use after it's factored out.
Some of the documentation (e.g. for RPC commands) uses
d/myname
, some of it usesmyname
, some of it usesd/abc
, and some of it usesd/domob
.It would be nice to standardize this. Just using
myname
without thed/
is confusing, but otherwise I don't have a strong opinion. I would suggestd/example
, however it's squatted.d/namecoin
might work. We could also use a specific namespace, likeex/domain
, although this has some risk of confusion.In upstream, there is a
const std::string
arrayEXAMPLE_ADDRESS
with some (invalid) bech32 addresses. That is a good model of how to do it.