harding

[The proposal below is flawed because it doesn't work for presigned transactions that use BIP68,
such as those proposed for LN anchor outputs or for timelock vault proposals.  It's probably 
flawed in other ways too.  I'm posting this in case it helps anyone else learn from my mistakes.]

On Sun, May 03, 2020 at 12:26:02AM +1000, Anthony Towns via bitcoin-dev wrote:
> [After updating the transaction digest to commit directly to
> scriptPubKey] we'd arguably still be missing:
>
>     [...]
>     what was the height of the coin? (Coin.nHeight)

harding

*Bitcoin Optech [Newsletter #48][] described Jeremy Rubin's OP_CHECKOUTPUTSHASHVERY (COSHV) soft fork proposal. Originally, that content included descriptions of several advanced uses of COSHV, but that material was [removed][] shortly due to publication because of concerns that it was not adequately reviewed and so may have contained errors. Optech initially planned to obtain more reviews and publish the extra content the following week but, by then, the COSHV proposal was withdrawn in favor of a modified proposal with a new name, so the extra content went into limbo. The following section comes from that lost content; it has not been updated since the original COSHV proposal

harding

13:01 <@jnewbery> Hi folks!
13:01 < harding> Hi!
13:01 < dmkathayat> Hello!
13:01 < schmidty> hola
13:01 < amiti> hi!
13:01 < bilthon> hi there
13:01 <@jnewbery> We usually start Bitcoin Core IRC meetings with a 'hi' so it's clear who's at keyboard. Feel free to say hi here!
13:01 < kcalvinalvin> Hi
13:01 < peevsie> hi!
13:02 < emzy> Hi

harding

2018-10-20 19:30 UTC

## Trial 1

Nmap done: 8440 IP addresses (4486 hosts up) scanned in 446.64 seconds

$ grep Ports.*/tcp/ NODE_SCAN_RESULTS.data -c
4486

$ grep Ports.*/open/tcp/ NODE_SCAN_RESULTS.data -c

harding

Price toots

Some people really don't want to hear about the price! But this is other people's favorite topic. If you adhear to the following two rules whenever talking about price, or something related to the price like altcoin prices, we should all be able to continue interacting about our common interests in Bitcoin:

1. Use a Content Warning (the CW in the Mastodon user interface) to allow people to opt-into seeing your price-related information and images. Note that replies to CW-content are also automatically wrapped in the same CW.

harding

Background: future fast Quantum Computers (QCs) are hypothesized to be much faster at solving various forms of the Discrete Log Problem (DLP) than classical computers (e.g. what we use now). Bitcoin uses the DLP in what's called a trapdoor function: a function that's easy to compute one way (a private key generating a public key) but hard to compute the other way (using a public key to recover the original private key). Fast QCs break that trapdoor, hypothetically allowing the operator of the QC to steal the bitcoins from anyone whose public key is publicly known.

harding

#!/bin/bash -eu

DATA=node-count.data

while git checkout HEAD~30
do
  date=$( git log -1 --date=unix | grep ^Date | awk '{ print $2 }' )
  echo -n "$date " >> $DATA

  ## $8 is the 30d uptime; 5..100 shows nodes with uptime >= 5%

harding

Manifest

• gitian-verify/
  • README.md
  • step_1/
    • verify-keys.sh
    • fingerprints.txt
    • signatures/
      • ...
• step_2/

harding

On Mon, Mar 19, 2018 at 10:07:12AM -0700, [redacted] wrote:
> Hi David,
> I'm working on a piece about how the Bitcoin blockchain can accommodate
> arbitrary data, potentially making it illegal in certain countries and
> circumstances. The paper about this can be found here:
>
> https://fc18.ifca.ai/preproceedings/6.pdf
>
> I'm wondering whether you might be available to comment before 1pm PT today.
>

harding

Keybase proof

I hereby claim:

• I am harding on github.
• I am dharding (https://keybase.io/dharding) on keybase.
• I have a public key ASAc0D2AK_qMWWCV97ThMppvd62MCSIIjZN4T2BUtAjS7wo

To claim this, I am signing this object: