I created a draft BIP detailing a way to add auxiliary headers to Bitcoin
in a bandwidth efficient way. The overhead per auxiliary header is only
around 104 bytes per header. This is much smaller than would be required
by embedding the hash of the header in the coinbase of the block.
It is a sof
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I host charts of my node's system metrics at
http://statoshi.info/#/dashboard/db/system-metrics
Note that the CPU spikes are abnormal as I'm making automated RPC calls to
query the UTXO set.
My node's bandwidth usage chart can be found at
http://s
>
> I am familiar with the Princeton threshold signature but I was under the
> impression a single key needed to be generated on a single device then
> split and distributed.
>
> Does this scheme work the same way?
>
No, it doesn't. Neither device ever sees as master private key.
--
Thanks Mike I'll have to read that threshold signature paper.
I am familiar with the Princeton threshold signature but I was under the
impression a single key needed to be generated on a single device then
split and distributed.
Does this scheme work the same way?
I would have concerns about gen
On 8 November 2014 16:28, Daniel F wrote:
> > But I'd like to know what storage, RAM and bandwidth resources are
> > needed. I guess that the problem is not the CPU.
>
> Hi Francis,
>
> Here are some rough guidelines for you, based on the statistics from my
> node:
>
> disk usage: about 30GB cur
Yes. I think one of the next things we need is a library that produces nice
and attractive PDFs of "wallet certificates" so it's easy to print out a
paper backup.
But the whole field of secure key escrow needs more research. Banking gives
people the very nice property that you can lose literally e
Overall, super duper awesome. :) Tweeted this post.
I do have a concern about 2-of-2 arrangements. To me, this screams
"twice as fragile" if not done properly; and I've seen a few naive
implementations in the field that seemed quite fragile.
2FA/2-of-2 does solve the common problem of single d
Here is a summary of current developments in the space of decentralised
2-factor Bitcoin wallets. I figured some people here might find it
interesting.
There has been very nice progress in the last month or two. Decentralised
2FA wallets run on a desktop/laptop and have a (currently always Android
> But I'd like to know what storage, RAM and bandwidth resources are
> needed. I guess that the problem is not the CPU.
Hi Francis,
Here are some rough guidelines for you, based on the statistics from my
node:
disk usage: about 30GB currently for the blockchain data. It'll only
keep growing fro
9 matches
Mail list logo
