Jeremy Rand

The raw transaction API is an obvious way to solve this, but doing so for name registrations is blocked by #181 (specifically the issues that `name_new` and `name_firstupdate` outputs can't...

> The raw transaction API is an obvious way to solve this, but doing so for name registrations is blocked by #181 (specifically the issues that name_new and name_firstupdate outputs...

Relevant: https://github.com/namecoin/namecoin-core/issues/463 would allow us to do this without calling the raw transaction API from Qt code.

> We now have a JSON `options` argument, so we could implement this. However, I don't think it should really be Namecoin Core's job to validate anything here. That would...

> there are features that are only really available in the UI already, e.g. coin control. (Which may be a bad example as it has code in the core codebase...

Okay, segregating namespace-aware RPC methods into their own source code file seems like a reasonable compromise. Running `help send` yields this example: ~~~ Create a transaction that should confirm the...

I've reproduced this. Namecoin Core 0.15.99-name-tab-beta2, self-compiled (with Gitian), on Qubes 3.2 / Fedora 26. No obvious errors show up in `debug.log`, but I do notice the following at the...

According to `debug.log`, Namecoin Core was launched at `2018-02-26 00:52:55`. So it took about 4 minutes for the freeze to happen on my end.

The bug doesn't seem to be dependent on whether the chain is still syncing, since I just fully synced with 0.15.99-name-tab-beta1, then relaunched 0.15.99-name-tab-beta2, and it froze after about 6...

I think this doesn't affect current master, but since master doesn't have feature parity with Brandon's beta yet, I'll leave this open.