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 ?
Search found 541 matches
- Sun Dec 14, 2014 12:51 pm
- Forum: Project direction
- Topic: P2SH addresses
- Replies: 12
- Views: 13991
- Tue Dec 09, 2014 9:04 pm
- Forum: Project direction
- Topic: P2SH addresses
- Replies: 12
- Views: 13991
Re: P2SH addresses
This is a good argument. I agree with you.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.
I just listed all available possibilities.
- Tue Dec 09, 2014 3:41 pm
- Forum: Project direction
- Topic: P2SH addresses
- Replies: 12
- Views: 13991
Re: P2SH addresses
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...
- Sat Dec 06, 2014 1:45 pm
- Forum: General Discussion
- Topic: Regular Public Developer IRC meetings?
- Replies: 1
- Views: 3933
Re: Regular Public Developer IRC meetings?
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...
- Fri Nov 28, 2014 2:00 pm
- Forum: Tools, GUI & other softwares
- Topic: Brainstorming: GUI for the rebased client
- Replies: 25
- Views: 111605
Re: Brainstorming: GUI for the rebased client
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 ...
- Fri Nov 28, 2014 1:28 pm
- Forum: General Discussion
- Topic: Block Reward Halving Upcoming
- Replies: 7
- Views: 10689
Re: Block Reward Halving Upcoming
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...
- Fri Nov 28, 2014 1:07 pm
- Forum: General Discussion
- Topic: Forum Moderation Policy (Rules)
- Replies: 19
- Views: 112002
Re: Forum Moderation Policy (Rules)
The rules sounds reasonable,
- Sun Nov 23, 2014 7:42 pm
- Forum: Tools, GUI & other softwares
- Topic: Try out DjsWallet with Namecoin support
- Replies: 3
- Views: 45460
Re: Try out DjsWallet with Namecoin support
Please try my new Javascript browser wallet based on bitcoinjs-lib with support for Namecoin. Currently in Alpha stage. Ignore cert warning for now. Thanks. https://djswallet.com Thanks for implementing Namecoin. Some observations: - creating additional Bitcoin/Namecoin receiving addresses they wil...
- Thu Nov 20, 2014 3:45 pm
- Forum: Project direction
- Topic: Encryption Spec Requirements
- Replies: 9
- Views: 10964
Re: Encryption Spec Requirements
Roughly what I was thinking of was: { "enc": "fch843fhjdfgh29rjdcdfvifjer8esjcfvre9r" "bitcoin": "1J3EKMfboca3SESWGrQKESsG1MA9yK6vN4", "namecoin": "N2pGWAh65TWpWmEFrFssRQkQubbczJSKi9" } Where for some secret decryption key, "fch843fhjdfgh29rjdcdfvifjer8esjcfvre9r" decrypts to: {"email": "khal@dot-b...
- Wed Nov 19, 2014 11:12 am
- Forum: Project direction
- Topic: Encryption Spec Requirements
- Replies: 9
- Views: 10964
Re: Encryption Spec Requirements
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...