Daniel Kraft

@wangchun: Would you support such a fork and if so, how much advance notice do you need? I'm currently thinking of something like three months. Would that be sufficient? (We...

Contacted Slush through their contact form, BTC.com and ViaBTC through their support email addresses. @JeremyRand - I'm not on Twitter, could you perhaps take care of pointing the BTC.top CEO...

Thanks @YihaoPeng for the quick reply - that sounds great! I've not yet set a fork height in the code, so for now, there's no need to update. I'll coordinate...

@JeremyRand - sounds good. There is plenty of time before this would actually go live (three months at least), so there is also no particular hurry. We've had some P2SH...

Slush gave their support by email. I've not yet heard from ViaBTC. @JeremyRand, did you try to contact BTC.top via Twitter yet?

In https://github.com/namecoin/meta/issues/51, we decided that we should go for Segwit with Bitcoin's block weight at least initially (and then see how the situation evolves and consider lowering the weight limit...

Yes, it is only those. Ok cool! Then I suggest this as the next steps: As soon as Bitcoin releases the final 0.18.0, I will set the soft fork for...

Proposed activation is in #302. Please take a look and give feedback there (especially if you do not agree with the proposed activation heights).

Version [0.18.0](https://github.com/namecoin/namecoin-core/releases/tag/nc0.18.0) has just been released with a scheduled segwit activation. @YihaoPeng, @wangchun and everyone else, please make sure to update timely.

That proposal sounds good to me. Having JSON objects is very nice. I think that the basic commands should still be usable "easily" from the command-line (e. g., `name_show d/domob`...