Bitcoin Forum
December 14, 2017, 02:23:31 PM *
News: Latest stable version of Bitcoin Core: 0.15.1  [Torrent].
 
   Home   Help Search Donate Login Register  
Pages: [1]
  Print  
Author Topic: Looking for developers to get involved with BitWasp  (Read 316 times)
fbueller
Sr. Member
****
Offline Offline

Activity: 412


View Profile
May 28, 2014, 12:04:53 PM
 #1

Hi folks,

As some of you know, BitWasp was rewritten last August, and some great progress has been made in this time. We now support multisig transactions, have a whole heap of features, but really I can only take this so far by myself! I am looking for people who would be interested in writing some code for us, and getting involved in maintaining the project.

I am looking to talk to PHP (CodeIgniter), javascript, and UI developers who can help me take this further. At present, the order process is quite cumbersome, and I'm not sure most buyers would be able to manage it. Certainly, people who've never used Bitcoin are at an even bigger disadvantage.

So, I'm looking for people who can help me with some of the following:
 - A general utility, with the exact same functionality as https://coinb.in/multisig, with some compatibility issues ironed out.

 - Bitcore. It has everything we need to make the system pretty elegant - keys for multisig addresses shouldn't need to leave the browser, or come from their bitcoin client, because they realistically won't need to use them again. So, JS derivation of a seed, and signing a multisig-spend transaction in the browser before sending back would really streamline the process, and mean that peoples interaction with their client software is minimized.
 - Bitcore+1 : BIP32 for seeds!

 - Multisig in general. Myself and some others are currently looking at a protocol for requesting signatures for a transaction, in an aside to signing in the browser with JS. It would largely mirror (or may be an extension of) the PaymentProtocol, and should give a systematic way to gather signatures for a multisig transaction by scanning a QR. If hardware wallets were able to support PaymentProtocol, then they should also be able to support our protocol. Essentially, we're just looking at an analogous SignatureRequest message, and finding a suitable way to encode the redeemScript.
This last one will take forever, but is just one of the things we're working on.

There are plenty of other technologies we could use to make Bitwasp brilliant. I'm imagining a time when people won't see multisig mentioned once throughout the site, users shouldn't need to be told that funds are secured by X, when they just assume they're secure anyway.

Anyway, I'd love to talk to you if you have ideas or feedback, or maybe want to get involved.

Bitwasp Developer.
Pages: [1]
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!