> The API implementation is not what is centralizing, nor is full indexation
> non-scalable. The centralization is in not running the API from a node under
> your own control. This is of course implied by the comment, “without the need
> for syncing”. In other words it is the deployment cost of
Awesome, thanks for the information. I will work on it and keep it in mind.
On Wed, Aug 29, 2018, 11:57 PM Jonas Schnelli wrote:
>
> > The API implementation is not what is centralizing, nor is full
> indexation non-scalable. The centralization is in not running the API from
> a node under your
You have created a straw man.
And light clients working against the P2P network (anonymous nodes) implies
they are not fully validating, so you are contradicting yourself.
e
> On Aug 29, 2018, at 11:27, Jonas Schnelli wrote:
>
>
>> The API implementation is not what is centralizing, nor is f
Thanks! That is what my main point is.
On Wed, Aug 29, 2018, 8:10 PM Eric Voskuil wrote:
> The API implementation is not what is centralizing, nor is full indexation
> non-scalable. The centralization is in not running the API from a node
> under your own control. This is of course implied by th
The API implementation is not what is centralizing, nor is full indexation
non-scalable. The centralization is in not running the API from a node under
your own control. This is of course implied by the comment, “without the need
for syncing”. In other words it is the deployment cost of the node
Note:
This spec cannot be used directly with a shamir scheme to produce
single-round threshold multisigs, because shares of point R would need to
be broadcast to share participants in order to produce valid single
signatures.
(R, s) schemes can still be used "online", if share participants publis
Thanks, I'll check it out.
On Wed, Aug 29, 2018, 12:06 AM Jonas Schnelli wrote:
> Hi
>
> To give a critical viewpoint on a such API:
>
> Such APIs usually result in central validation, meaning that users trust
> API services rather the validating their own data. It break some of the
> fundamenta
It's cool but
- there's a lot of online steps.
- it's not a threshold system
Using a shamir scheme solves this and isn't subject to birthday attacks:
https://medium.com/@simulx/an-m-of-n-bitcoin-multisig-scheme-e7860ab34e7f
On Mon, Aug 13, 2018 at 7:08 AM nakagat via bitcoin-dev <
bitcoin-dev
Rather than restricting every timestamp (or just the 2016*N+1
timestamps) to >= 1+ the previous timestamp as recorded on the
blockchain, the difficulty calculation could have the same restriction
but only in how the timestamps are used. I don't know about backwards
compatibility. Either way, this
Hi
To give a critical viewpoint on a such API:
Such APIs usually result in central validation, meaning that users trust API
services rather the validating their own data. It break some of the fundamental
properties of Bitcoin (avoid trusted third parties).
Systems or applications depending on a
10 matches
Mail list logo
