Very Secure

How To Test gbw-node By Viewing The First Ever Transaction Containing a p2pkh Address

After setting up gbw-node and getting a local trb running, I wanted to do a basic test to make sure that my instance of jfw's wallet software was able to show a balance for an address that had received some bitcoins. Dorion had done a similar exercise, except he scanned up to block 634,000 which took about 24 hours.

Being impatient, I attempted to track the address found in the first non-coinbase txn in history, found in block 170. But I discovered that gbw-node cannot track the receiving address in that transaction, since gbw-node only supports addresses that receive bitcoins via the p2pkh script. The first transaction in bitcoin's history was paid directly to the public key, not the public key's hash.

I believe the first address in the form of a p2pkh script can be found in block 728 in a transaction that sent the address 100 bitcoins.

The corresponding bitcoin address and txn-id are 12higDjoCCNXSA95xZMWUdPvXNmkAduhWv and 6f7cf9580f1c2dfb3c4d5d043cdbb128c640e3f20161245aa7372e9666168516, respectively.

So to quickly test basic functionality of gbw-node, run the following commands:

gbw-node watch firstp2pkh

gbw-node reset
gbw-node scan # Wait for block 728 to pass, then 
gbw-node unspent-outs

You should see:

12higDjoCCNXSA95xZMWUdPvXNmkAduhWv 100.00000000 6f7cf9580f1c2dfb3c4d5d043cdbb128c640e3f20161245aa7372e9666168516 0 #blk 728 tx 1

3 Responses to “How To Test gbw-node By Viewing The First Ever Transaction Containing a p2pkh Address”

  1. Glad to see you got it installed and working, Cheers!

  2. AntonioROb says:

    Here are some interesting transactions that use P2PKH: If P2PK does a good job of locking up bitcoins to a public key, why do we have the more complex P2PKH script? Only Satoshi knows why we started using P2PKH, but the reason probably goes something like this… Satoshi wanted a easier way for people to be able to share their public keys with each other. Satoshi knew that you could make public keys: Safer by adding a checksum to detect errors Shorter by converting the public key to base58 However, the result was still pretty big: Therefore, a solution for getting an even shorter result is to hash the public key first: So there we have a much shorter version of our public key we call it an that we can easily share with other people.

  3. whaack says:


    Interesting spam that got through before I had the spam filter ^, looks like it was able to grab related text from another source and post it here.

Leave a Reply