The current approach S2X is taking in deploying their fork is a violation of the second paragraph of the NYA Scaling Agreement

Paragraph 2 of the NYA scaling agreement reads:

We are also committed to the research and development of technical mechanisms to improve signaling(sic) in the bitcoin community, as well as to put in place communication tools, in order to more closely coordinate with ecosystem participants in the design, integration, and deployment of safe solutions that increase bitcoin capacity.

(I added the bold above)

In direct contradiction, however, BTC1 (the S2X codebase) intentionally has created and deployed code that creates a technical mechanism to cloak signalling.

Also in contradiction to the claim of "deployment of safe solutions" the refusal to implement safe two way replay protection, which is an easy thing to do, is actually intentional deployment of an unsafe solution.

Add to that today's news that Jeff Garzik has sought assistance in creating Sybil nodes deployable as docker containers for BTC1 which would send false signals about the quantity of support S2X has and we can see that NYA's second paragraph carries zero weight with its lead (and possibly only) developer.

Add to that the fact that all the miners mined on a separate hard fork of bitcoin that was created simultaneous to the SegWit activation clause, and that all the exchanges listed and traded that alt coin and you have the agreement's first paragraph breached by practically all participants already.

Those that tell you that you are breaking an agreement by not endorsing S2X are the worst kinds of liars. You never signed up to their agreement; and they are the ones breaking the agreement.

(https://medium.com/@DCGco/bitcoin-scaling-agreement-at-consensus-2017-133521fe9a77 for anyone interested in reviewing it.)

submitted by /u/logical
[link] [comments]
Bitcoin

Privacy approach for a light-weight wallet

I am looking for an approach to build a privacy centric lighter weight wallet.
By privacy centric I only mean: network observers should be unable to guess the addresses belongs to the same wallet.
So querying information about addresses should be private.
By light-weight I mean:
1. Do not store hundreds of GB of data (a few is fine).
2. Do not sync for ages. Should be finished within an hour maybe.
The lightest privacy preserving approach I was able to find is pruning, what solves my first criteria, but not the second.
BIP37 is not a good. (See: https://jonasnick.github.io/blog/2015/02/12/privacy-in-bitcoinj/)
Do you guys have suggestions? (Or direct me to a better room to ask this question?)

Recent Questions – Bitcoin Stack Exchange