|
Title: Creating (and funding) SPV bitcoind Post by: hivewallet on July 17, 2013, 09:57:14 AM Hi everyone,
We at Hive are interested in co-funding the development of an SPV (Simplified Payment Verification) version of bitcoind. Mike Hearn laid out what changes would be necessary in this bitcoin-development thread: http://sourceforge.net/mailarchive/message.php?msg_id=31175119 He additionally posted some (now broken) code that Satoshi had created to do just that, in 2010: http://pastebin.com/7sHTisSe Are any developers interested in taking this to task, with the aim of getting the whole thing merged into master? Our goal is to further expand the possibilities in Bitcoin wallet development, and especially to grow the now sorely limited SPV selection to at least two solid options. Finally, a call to the lucky Bitcoin wealthy: It would be a delightful to have some public partners in the funding effort. Title: Re: Creating (and funding) SPV bitcoind Post by: ffssixtynine on July 17, 2013, 10:59:04 AM Can I request someone takes on BitcoinSharp as well.
Title: Re: Creating (and funding) SPV bitcoind Post by: hivewallet on July 17, 2013, 03:06:35 PM Can I request someone takes on BitcoinSharp as well. Sounds like a great project, but let's retain this thread for bitcoind SPV exclusively. Title: Re: Creating (and funding) SPV bitcoind Post by: franky1 on July 17, 2013, 03:42:34 PM so hive doesnt have the developers, or the funds..
well thats a great business plan, but atleast they have a business name and a 'we' meaning theres more then one person looking for a salery, while sitting on their hands. Title: Re: Creating (and funding) SPV bitcoind Post by: yaffare on July 17, 2013, 03:46:38 PM Is this really such a good idea right now?
If everybody starts using spv, from where can you download the blocks, if nobody stores the blocks anymore? I guess we should wait, until real block chain pruning is implemented, otherwise the amount of full nodes will go down, which is no good right now. You could end up harming the network more than helping. Title: Re: Creating (and funding) SPV bitcoind Post by: hivewallet on July 18, 2013, 11:16:42 AM so hive doesnt have the developers, or the funds.. well thats a great business plan, but atleast they have a business name and a 'we' meaning theres more then one person looking for a salery, while sitting on their hands. My heart is warmed to see the bitcointalk trolling tradition carrying on so confidently, but in case you actually did misunderstand the nature of the post: We are not seeking funds for ourselves. We are looking for a developer to fund. Bitcoin core development requires skills and knowledge which are, from our perspective at least, quite a specialist matter. We are a team of designers and Objective C developers who would like to remain focused on the things we are good at: interface and user experience. So although we may not be able to meaningfully contribute to the code of Bitcoin's multitudinous depths, we benefit from its enhancement, and so offer funding toward its more flexible future. Title: Re: Creating (and funding) SPV bitcoind Post by: hivewallet on July 18, 2013, 11:24:38 AM Is this really such a good idea right now? If everybody starts using spv, from where can you download the blocks, if nobody stores the blocks anymore? I guess we should wait, until real block chain pruning is implemented, otherwise the amount of full nodes will go down, which is no good right now. You could end up harming the network more than helping. A good question. This is actively being discussed right now on bitcoin-development. See for example Peter Todd's post about an alternative approach with partial UTXO sets: http://permalink.gmane.org/gmane.comp.bitcoin.devel/2520 Title: Re: Creating (and funding) SPV bitcoind Post by: Mike Hearn on July 18, 2013, 01:23:49 PM Most users already aren't becoming full nodes anyway, the abandonment rate on Bitcoin-Qt is pretty high (just compare download numbers with node numbers).
There will be full nodes for as long as there are miners and merchants. I wouldn't worry much. |