jgarzik

diff --git a/configure.ac b/configure.ac
index a9156c3..50509d6 100644
--- a/configure.ac
+++ b/configure.ac
@@ -1,6 +1,6 @@
 dnl require autoconf 2.60 (AS_ECHO/AS_ECHO_N)
 AC_PREREQ([2.60])
-define(_CLIENT_VERSION_MAJOR, 0)
+define(_CLIENT_VERSION_MAJOR, 1)
 define(_CLIENT_VERSION_MINOR, 14)

jgarzik

Keybase proof

I hereby claim:

• I am jgarzik on github.
• I am jgarzik (https://keybase.io/jgarzik) on keybase.
• I have a public key whose fingerprint is AF8B E07C 7049 F3A2 6B23 9D53 25B3 0832 0178 2B2F

To claim this, I am signing this object:

jgarzik

Verifying that +jgarzik is my openname (Bitcoin username). https://onename.io/jgarzik

jgarzik

#include <sys/types.h>
#include <sys/stat.h>
#include <stdio.h>
#include <stdlib.h>
#include <string.h>
#include <fcntl.h>
#include <time.h>
#include <stdint.h>
#include <stdbool.h>
#include <unistd.h>

jgarzik

This protocol describes a simple payment channel protocol, such as the one presented in https://en.bitcoin.it/wiki/Contracts#Example_7:_Rapidly-adjusted_.28micro.29payments_to_a_pre-determined_party

JSON-RPC methods shown here may be sent via HTTPS or stratum protocol. It is easily adaptable to protocol buffers or another favored marshalling method.

Open channel

Client requests a public key. Server responds with a public key (K2). K2, converted to a bitcoin address, forms the unique identifier for this payment channel. Each public key returned must be unique.

jgarzik

(1) request payment information, required for auction creation.  for zero
    creation fees, price is 0, and "txout" is not required.

{
        id: 1,
        method: "auction.prepare",
        params: [
                {
                // auction creator's address/identity
                userid: "mkzfa27nZdHvwTZ6CitKmxroHrPbuvQQ4y",

jgarzik

DRAFT IN PROGESS - DO NOT CIRCULATE

Technical note

The Challenges of Packaging Bitcoin Software

Introduction

Bitcoin technology is complex. Under the hood of the decentralized virtual currency lies a novel form of decentralized, distributed database. It is critical for users, system adminstrators and packaging engineers to understand bitcoin's database consistency model, which is radically different from familiar database consistency models (MySQL, Berkeley DB, Amazon Dynamo, or Google's GPS-based doohickey).

jgarzik

hello test test.

test test test my home page test test test.

test test

jgarzik

This is a review of "Quantitative Analysis of the Full Bitcoin Transaction Graph" by Dorit Ron and Adi Shamir.

There are some incorrect details and analyses that warrant attention.

Oct. 31 UPDATE

The authors have introduced several revisions to their paper, available at the same URL as before.

The criticism below may be outdated in part or in full.

jgarzik

diff --git a/bitcoin/serialize.py b/bitcoin/serialize.py
index 6d7fc6d..13a3afd 100644
--- a/bitcoin/serialize.py
+++ b/bitcoin/serialize.py
@@ -7,6 +7,7 @@
 #
 
 import struct
+import hashlib
 from Crypto.Hash import SHA256, RIPEMD160