Daniel Kraft

For Chimaera, we will need the ability to create name updates that also send coins to certain destination addresses (but unlike name trades, created all by a single user). That...

@JeremyRand (and others): The current behaviour is to actually support **UTF-8 encoded** names and values, as this is what the JSON library (univalue) does. I believe this may be useful...

With #220 and #222, we have now added an object argument to the "write-type" RPCs (`name_new`, `name_firstupdate`, `name_update`). It supports `destAddress` and `sendCoins`. Still open are the encoding fields as...

With #277 merged, all (main) name RPC methods have now an `options` argument. (The ones that don't are `sendtoname`, which is mostly deprecated, and `namerawtransaction`, which can be replaced by...

@JeremyRand I'm fine with that. (However, my own guess would be it is much quicker than one week to do. I think it would not be more than a day...

@yanmaani I think probably the best would be to also add a command-line argument that allows setting the default for `showExpired`, and then flipping that one in most of the...

From my point of view, I think the same code as "name does not exist" is fine, as would be a new error code if you prefer.

You should be able to list all names (not just domains but anything) using `name_scan`. What is the exact command you are using?

Yes. Use a command like this: namecoin-cli name_scan "d/domob" 5 '{"prefix":"d/","nameEncoding":"utf8"}' This will give you the next five `d/` names (i.e. domains), starting from `d/domob` in this case. So what...

With the `prefix` filter, you should not get `id/` names. And if you are unsure about the number, just try calling again passing in the last name you got as...