What implications or other possibilities would arise from P2SH with specific to name operations if any ? I do not mean the transaction specific uses.
Multisignature name operations where more parties could exercise control over a domain name ?

domob wrote:I think we should definitely support P2SH. It is an elegant solution to the problem of specifying "where" to send funds in the case of multisig. Also, it helps with compatibility to Bitcoin.

This is a good argument. I agree with you.
I just listed all available possibilities.

We should support multisignature transactions in the future. And they are supported on the protocol level also without P2SH. - They were some discussions on nothing(multisig directly) vs P2SH vs CHV or OP_EVAL but I know that the mainstream of Bitcoin developers are going with Gavin(and GMaxwell) on...

So, disclaimer: this is just an idea, and I have no idea if it will actually happen. Consider this an informal survey, not a promise. Lately we've had a few new people who are interested in development. Unfortunately bringing them on-board has been kind of ad-hoc, because there's not a great way to...

I do strongly support building on existing GUI's; it's not Namecoin's job to build a general-purpose coin GUI. Fully agree. I also agree that a separate UI, building on top of the RPC interface, would be very cool. There's no reason why the UI should depend on a particular core implementation - it ...

The price depends on demand and supply. Now let's go in detail. It is true that the coins produced will be half so much but the available supply on the market still will grow with half the amount. However as most sellers are miners from merged mining which do not hold their coins so their supply wil...

I'm not sure I follow. It wouldn't be using obvious keys, the proposal is to use user-specified passphrases and/or keys. No one would be using "email" or "telephone" as a key. Taking the example from the Namecoin wiki: $ namecoind name_show "id/khal" { "email": "khal@dot-bit.org", "bitcoin": "1J3EK...