please don't do the rest submittx at all if its only bin, if it won't take hex it will be massively less used, and we'll just have more code to hang around and bloat the codebase; while people will continue to eschew bitcoin core and use some web api that actually gives an interface people expect. :-/
Probably easiest to just specify the format to whatever the default is, and have `-json` or whatever on bitcoin-tx though
I feel like most users might do something along the lines of 'bitcoin-tx ... | curl 'http://somepopularnode.com/tx' --data-raw -H "Content-Type:application/octet-stream"
there were no changes to bitcoin-cli in 0.11.1, right?
https://bitcoin.org/en/download <- suggest that the "over 20GB" part toward the bottom should probably be updated to "over 50GB", or point to some resource that tracks blockchain size for future-proofness, to avoid giving misleading info.
You need the `bitcoin` repo (specifically the contrib/gitian-descriptors and depends dirs), your fork of the `gitian.sigs` repo so you can add to it, and the `devrandom/gitian-builder` repo.
PRab: "bitcoin-builder" isn't a thing
I cloned gitian-builder, but never bitcoin-builder.
hm, set up a twitterbot to tweet bitcoin-announce mailing list titles with links to full email body? :)
would prefer to keep non-tech discussion of my post on #bitcoin. if there are tech corrections, by all means, post here
guys, sorry for instigating this discussion thread. clearly this was the kind of thing happening on #bitcoin-dev that brought about the change to using this channel instead. can we go back to pull requests and releases?
most of the children have moved out of /r/bitcoin anyway
i'm not sure there are any useful public venues for bitcoin related matters any more. i'd say post announcements on a read-only mailing list, say, bitcoin-core-announce, and let responsible people stay on top of announcements about software they run that handles their money.