On Thu, Jul 18, 2013 at 06:46:16PM +0200, Wendell wrote:
> Heh, will do. If you have less confidence in your programming skills perhaps
> its best if you write documentation and we bring in someone else to do the
> heavy lifting? Maybe Eric Lombrozo would be interested in this, for example...
I
Heh, will do. If you have less confidence in your programming skills perhaps
its best if you write documentation and we bring in someone else to do the
heavy lifting? Maybe Eric Lombrozo would be interested in this, for example...
-wendell
grabhive.com | twitter.com/grabhive
On Jul 18, 2013, a
On Wed, Jul 17, 2013 at 03:37:41PM +0200, Wendell wrote:
> Peter,
>
> This sounds like a _very_ good idea for a desktop client, and probably
> acceptable to users so long as we take available disk space into
> consideration, and only ever use a fraction of it.
>
> Will you implement this?
I've
On Thu, Jul 18, 2013 at 07:13:53AM -0400, Peter Todd wrote:
> Note that with OP_DEPTH we can remove the small chance of the payee
> vanishing and putting the funds in limbo:
>
> OP_DEPTH OP_LESSTHAN
> IF 2 PK1 PK2 CHECKMULTISIG
> ELSE PK1 CHECKSIG
> ENDIF
>
> Though that shows ho
On Thu, Jul 18, 2013 at 08:53:55AM -0400, Jeff Garzik wrote:
> On Thu, Jul 18, 2013 at 7:13 AM, Peter Todd wrote:
> > Note that with OP_DEPTH we can remove the small chance of the payee
> > vanishing and putting the funds in limbo:
>
> What are the costs, benefits, and risks associated with scrip
> SPV clients behaving normally are highly abusive: they use up maximum
> node resources with minimum cost to themselves.
>
This must be a new use of the word "abuse" I haven't come across before :)
At any rate, some of these assumptions are incorrect. Botnets of
compromised web servers are quite
On Thu, Jul 18, 2013 at 08:13:08AM -0400, Peter Todd wrote:
> A more sophisticated approach would be possible if there existed a
> version of H() with a computational trap-door - that is if there existed
> H'(s, i)=H(i) where H' had significantly faster running time than H(),
> but required knowled
Hi Bazyli,
Just did a fresh build based on git (Xcode) - had one issue: the paillier and
account tests were missing - please comment them out in tests/CMakeLists.txt,
then coinexplorer should build nicely.
Note I did a git push as well, so you need to do a git pull first.
/Michael
Hi Bazyli,
I actually do my main development on Mac OSX, so it surprises me to hear - I
build Xcode projects with libcoin daily on Mac OSX and linux, on Windows it is
agreeable more of a fight to build. QT is really not needed, I kept it there
for BitcoinQT, that was once part of the tree too,
On Thu, Jul 18, 2013 at 7:13 AM, Peter Todd wrote:
> Note that with OP_DEPTH we can remove the small chance of the payee
> vanishing and putting the funds in limbo:
What are the costs, benefits, and risks associated with scripts no
longer being stateless, as OP_DEPTH would seem to introduce?
--
On Wed, Jul 17, 2013 at 02:29:26PM +0200, Mike Hearn wrote:
> Partial UTXO sets is a neat idea. Unfortunately my intuition is that many
> SPV wallets only remain open for <1 minute at a time because the user wants
> to see they received money, or to send it. It'd be neat to get some
> telemetry fro
Hi!
I should introduce myself. I am the BitcoinKit developer. If you can call that
way a dude that wrapped up already existing code for Mac developers easier to
understand and use :-)
I'm replying mostly because libcoin is something that I would like to have a
closer look at.
Problems I've enc
On Fri, Apr 19, 2013 at 06:48:11PM -0700, Jeremy Spilman wrote:
> 0. User and AP negotiate how much to escrow, who pays the fees, and how
> far in the future nLockTime will be set (how long user’s funds will be tied
> if AP doesn’t close the channel)
>
> 1. User creates an unsigned TX1 with 1 or
> The 90 minutes is not - the blockchain has grown quite a lot since last
> year, and as for the 3.5 speed, I havn't tested it since Pieter's
> ultraprune - libcoin also has something similar to ultraprune, done
> directly in the sqlite database backend, but I should run a head to head
> again - co
14 matches
Mail list logo
