Peter Todd

I recommend following the Bitcoin Core guidelines: http://www.mail-archive.com/[email protected]/msg05467.html There's also a handy script to sign/merge GitHub pull-reqs in the Bitcoin Core repo: https://github.com/bitcoin/bitcoin/blob/master/contrib/devtools/github-merge.py Timestamping your git commits is the new...

All the cool kids have them.

addinvoice --private doesn't add hop hints if no amount is provided

1

### Background `lncli addinvoice --private` returns an invoice without hop hints; if an amount is provided the `--private` option works as expected. ### Your environment * lnd version 0.15.0-beta commit=v0.15.0-beta...

Change `ots upgrade` to only accept one file at a time

1

Multiple files confuses the logic, and unlike `stamp` - where a merkle tree is created over all files - there isn't a natural efficiency gain from upgrading multiple files at...

Fix incorrect usage of "aggregator" when we mean "calendar"

1

Building on #59, this pull-req changes the stamp subcommand and git wrapper to use the terminology "aggregator" rather than "calendar" to refer to the servers that aggregate digests into per-second...

@haraldschilly opened https://github.com/opentimestamps/python-opentimestamps/issues/31 in the wrong repo, so opening an issue here to track it.

Basically, rather than the current wrapper.sh uglyness, command line arguments should be replaced with a .gitconfig section for `[ots]`. Similar to how git-annex works.

Slightly faster, but more importantly, gives feedback sooner if the timestamp will fail due to it not yet being confirmed.

``` $ ./ots upgrade requirements.txt.ots release-notes.md.ots TODO.md.ots README.md.ots LICENSE.ots Success! Timestamp complete Calendar https://alice.btc.calendar.opentimestamps.org: Pending confirmation in Bitcoin blockchain Failed! Timestamp not complete ``` Quite at release-notes.md.ots when the other...

E.g. it'd be cool if you got a display of how many more blocks needed to be mined for the tx to fully confirm.