Re: [Bitcoin-development] Proposed alternatives to the 20MB step function

2015-05-18 Thread Rusty Russell
Tier Nolan tier.no...@gmail.com writes:
 On Sat, May 16, 2015 at 1:22 AM, Rusty Russell ru...@rustcorp.com.au
 wrote:
 3) ... or maybe not, if any consumed UTXO was generated before the soft
fork (reducing Tier's perverse incentive).

 The incentive problem can be fixed by excluding UTXOs from blocks before a
 certain count.

 UTXOs in blocks before 375000 don't count.

OK.  Be nice if these were cleaned up, but I guess it's a sunk cost.

 4) How do we measure UTXO size?  There are some constant-ish things in
there (eg. txid as key, height, outnum, amount).  Maybe just add 32
to scriptlen?


 They can be stored as a fixed digest.  That can be any size, depending on
 security requirements.

 Gmaxwell's cost proposal is 3-4 bytes per UTXO change.  It isn't
 4*UXTO.size - 3*UTXO.size

He said utxo_created_size not utxo_created so I assumed scriptlen?

 It is only a small nudge.  With only 10% of the block space to play with it
 can't be massive.

But you made that number up?  The soft cap and hard byte limit are
different beasts, so there's no need for soft cost cap  hard byte
limit.

 This requires that transactions include scriptPubKey information when
 broadcasting them.

Brilliant!  I completely missed that possibility...

 5) Add a CHECKSIG cost.  Naively, since we allow 20,000 CHECKSIGs and
1MB blocks, that implies a cost of 50 bytes per CHECKSIG (but counted
correctly, unlike now).

 This last one implies that the initial cost limit would be 2M, but in
 practice probably somewhere in the middle.

   tx_cost = 50*num-CHECKSIG
 + tx_bytes
 + 4*utxo_created_size
 - 3*utxo_consumed_size

  A 250 byte transaction with 2 inputs and 2 outputs would have an adjusted
  size of 252 bytes.

 Now cost == 352.

 That is to large a cost for a 10% block change.  It could be included in
 the block size hard fork though.

I don't think so.  Again, you're mixing units.

 I think have one combined cost for
 transactions is good.  It means much fewer spread out transaction checks.
 The code for the cost formula would be in one place.

Agreed!  Unfortunately there'll always be 2, because we really do want a
hard byte limit: it's total tx bytes which brings most concerns about
centralization.  But ideally it'll be so rarely hit that it can be ~
ignored (and certainly not optimized for).

Cheers,
Rusty.

--
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
___
Bitcoin-development mailing list
Bitcoin-development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-development


[Bitcoin-development] Open Bitcoin Privacy Project Spring 2015 Report

2015-05-18 Thread Justus Ranvier
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

We're produced the first in what we hope to be a long series of
reviews of Bitcoin wallet privacy features, available here:

http://www.openbitcoinprivacyproject.org/2015/05/spring-2015-wallet-privacy-rating-report/

https://github.com/OpenBitcoinPrivacyProject/wallet-ratings/raw/master/2015-1/OBPP%20Bitcoin%20Wallet%20Privacy%20Rating%20Report%20-%20Spring%202015.pdf

Specifically from the readers of this list, we are very interested in
feedback regarding our privacy threat model and the rating criteria we
derive from it.

Threat model:
https://github.com/OpenBitcoinPrivacyProject/wallet-ratings/blob/master/2015-1/threat%20model.wiki

Please send any suggestions or corrections via a GitHub issue to the
wallet-ratings repository so that we can incorporate it into future
reports.

- -- 
Justus Ranvier
Open Bitcoin Privacy Project
http://www.openbitcoinprivacyproject.org/
jus...@openbitcoinprivacyproject.org
E7AD 8215 8497 3673 6D9E 61C4 2A5F DA70 EAD9 E623
-BEGIN PGP SIGNATURE-

iQIcBAEBAgAGBQJVWhBvAAoJECpf2nDq2eYj3JEP/jw/Xkgq4yZRE4FK8a8kPBqn
3ULyS74KtNyPDdpTK0bdH7//0d1ep+LvNpIkFhWCJ/WQ7T/Ft3iQl1HJvXGC0ZzM
XKd7ptXLpBrKElARAORgUlFPOeKzOrOyP4uvvGAMZ+CXEnKeyxDzK+WzfYnWyDEU
Q4XQ/ndwPqbZm9Nb+GeF186TXcA/KqcQEuOIw7/jFGHfFT6QBKVz1SraVrgdcMky
8KKYOsYJt8lTUjVN1INmLFoRZ0cGUd+IFKweSCibyAu9TdvVQfQSPfSnfZtDLk6X
g1oPYaxX6r9+/1zm2v5ISk97nKrvNslPjeQbuW3vWlROSxGZ9lV+MVNvkqm1jSpF
ip0Il+VJb8hhh9LRJV6euhLQyR+xnLIVJvslJt883rhKIBi3M/OipMuhipIeAbnV
0WQmnpQ9ZgagPoFRxGp86Cz7PWTfj7zllB3yk/M3tA8e64VQFhEnoyJO8hPqfEQh
wPZP3UQ+K3PM/2oe4W5ZkfkqD6tIzGTQeMkGFeCvTsMmsW9+Ml8j4YTwKA0z5vr5
IebJ51Vpaq1noVEl46q8utpLp1wATI8SG5sBwSaR4/REUGkSWjSCeZeLcK8WzdEa
SaZ8t5Rqr1AcwtD6n9rVvYoF26285120jM/YX8XgMldWi0RXrlWD4B4lA1i7eVfZ
hINSIR+QsJsw7yq7Ox3/
=NMNo
-END PGP SIGNATURE-


0xEAD9E623.asc
Description: application/pgp-keys
--
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y___
Bitcoin-development mailing list
Bitcoin-development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-development


Re: [Bitcoin-development] Open Bitcoin Privacy Project Spring 2015 Report

2015-05-18 Thread Justus Ranvier
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Replying to the list because this is a common question.

We rated as many wallets as we could based on the amount of manpower
we had available to perform the ratings.

We will be holding a recruiting drive shortly to solicit additional
volunteers so that we can cover more wallet for the next round of ratings.


On 05/18/2015 11:40 PM, Eric Lombrozo wrote:
 mSIGNA is notably absent from the report despite having some of the
 most advanced security and privacy features and having been on the
 bitcoin.org site longer than some of the other wallets reviewed.
 
 Is there some process to get reviewed I missed? Please add us to
 the report.

- -- 
Justus Ranvier
Open Bitcoin Privacy Project
http://www.openbitcoinprivacyproject.org/
jus...@openbitcoinprivacyproject.org
E7AD 8215 8497 3673 6D9E 61C4 2A5F DA70 EAD9 E623
-BEGIN PGP SIGNATURE-

iQIcBAEBAgAGBQJVWmA1AAoJECpf2nDq2eYjXGgP/2CpIYpG49WKAfG/PXmu1zFV
+zzU/7PCz+0ez0mGCz5l3QMc9TCDs6KDx0sPHZngwwLio3C4JMpu+zfnw6gngw/G
6NNtmDZ9xWgWx3kQyBLWBCM/K63rLE1QYJqiIc7QaDuDTk5w0upwkFxLejWeem1j
Z8Zy6ycHNNHE19o5pIYViWaRXojMD70fBFSoU9sAyvnOup7b5Cj4PLx7mbMbaegV
gCHd7zd88AH0f2ilFiVMQJBKf03KzYjarRVrAyvAb/8VLiYMRC8SS3y2tzM+qRKl
ZADAp8FiQ6GOFRssNg+x7tc3DX2ngBljLLKM90kPLR2cvwp8VHi0I0biqM8n2M17
CMjZVRNvXitNnKFc42nk51HsZR5LkDK3Rf9I1E3fBVKJ5feEbDi3tlEg9PCWD2xM
PmSRzXoUBAjpr9xL2kBzlE4aTYZCmmMxAMF1mcSYujdNzQ2IN0gD1urJtCwZ8zZ1
LL2cPimS3GTWEpoQQ/Fu+0NDwiPditDGt+DN16Mi5uioPvaumHMIV6u9ZNdD9ZEv
UTGW8C2Hj+ENzqhpdhlV5YfYUnKo6/ukw+xxTXRxbbLGxA6iRrVnPzsYTZoF0Vrt
T4IsdzPIg5yeF5IQKEV1lLyx+gOIvmDF1RZE36NY8bGn2zusFzUGxiqWa6yw0hfw
l4ytd8pfhIvTkuz1o9aQ
=kWhU
-END PGP SIGNATURE-


0xEAD9E623.asc
Description: application/pgp-keys
--
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y___
Bitcoin-development mailing list
Bitcoin-development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-development