inersha 2017-01-19 00:47:49
Where does the difficulty come from?
inersha 2017-01-19 00:48:06
Is it worked out by dividing the maximum target by the current target?
Lauda 2017-01-19 00:49:01
https://en.bitcoin.it/wiki/Difficulty
piqure 2017-01-19 00:49:02
^^^ WARNING: any URL may lead directly or indirectly to COIN-STEALING MALWARE! ^^^
inersha 2017-01-19 00:57:33
Lauda: Thanks, so everything comes from the changing `bits` values in block headers?
inersha 2017-01-19 00:58:15
...and the difficulty value doesn't actually control anything... it's just a way of representing the change from one target to another?
Lauda 2017-01-19 00:58:19
Huh what is 'everything comes'?
inersha 2017-01-19 00:58:44
'everything comes' = the target and difficulty
Lauda 2017-01-19 00:58:58
No, that's not right.
inersha 2017-01-19 00:59:04
i.e. The changing `bits` value is the source of the difficulty value.
cannon-c 2017-01-19 01:00:52
I am looking to including SSSS (Shamirs Secret Sharing Scheme) into bitcoin core
inersha 2017-01-19 01:00:53
Lauda: Can you explain? Is the difficulty worked out from the target, or is the target worked out from the difficulty?
cannon-c 2017-01-19 01:01:12
nvm.... didnt mean to interrupt, will finish my question later
Lauda 2017-01-19 01:02:20
Difficulty is a representation of the target. The smaller the target, the higher the difficulty and vice versa. That's what I'd say.
Lauda 2017-01-19 01:02:37
"Difficulty is a measure of how difficult it is to find a hash below a given target."
inersha 2017-01-19 01:04:41
Okay, thanks. For some reason I thought the difficulty was a stored value that _controlled_ the target, but the target adjustments do not seem to actually use it.
Lauda 2017-01-19 01:05:07
No, that's not it
inersha 2017-01-19 01:06:57
Lauda: Am I mistaken?
Lauda 2017-01-19 01:07:24
Yes. Someone else can explain why, I got to run.
cannon-c 2017-01-19 01:18:01
I am looking to including SSSS (Shamirs Secret Sharing Scheme) into bitcoin core.
cannon-c 2017-01-19 01:18:42
So I can back up my xpriv or regular priv key into fragmented backups
cannon-c 2017-01-19 01:19:07
which would require pre-defined threshold to re-assemble. For usecase of secure distributed wallet backups
cannon-c 2017-01-19 01:19:34
or for family to recover funds if something happens. Before I do this, does bitcoin core already have fragmented backups feature?
haakonn 2017-01-19 01:26:40
cannon-c: there's no such feature in bitcoin core, but i've seen external tools for it
cannon-c 2017-01-19 01:27:01
Anyone else find useful to have ssss included with core?
cannon-c 2017-01-19 01:27:09
Im doing it just for personal use,
cannon-c 2017-01-19 01:27:18
but guess could do a commit if it works out well
haakonn 2017-01-19 01:27:24
notably i've seen https://github.com/blockstack/secret-sharing - not played with it
piqure 2017-01-19 01:27:25
^^^ WARNING: any URL may lead directly or indirectly to COIN-STEALING MALWARE! ^^^
haakonn 2017-01-19 01:28:02
it seems like a good match for bitcoin in general, but maybe you could achieve the same thing using multisig
cannon-c 2017-01-19 01:28:24
multisig currently has ~80 bits security without segwit
cannon-c 2017-01-19 01:28:36
I am looking to have the priv key itself fragmented
cannon-c 2017-01-19 01:30:57
for greater security
cannon-c 2017-01-19 01:31:19
by using standard P2PKH address
haakonn 2017-01-19 01:31:45
yeah, too bad about multisig security
