maybe make it so bitcoin.conf settings can be edited with in the app
instead of external editor, and make it easier to enable rpc server mode...
--
Rapidly troubleshoot problems before they affect your business. Most IT
o
Amazingly thorough, Peter. Thanks so much!
-wendell
hivewallet.com | twitter.com/hivewallet | pgp: B7179FA88C498718
On Dec 19, 2013, at 8:17 AM, Peter Todd wrote:
> Here's my draft. I don't claim this to be "official", but I think this
> should represent the consensus we've come to at the DarkW
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello fellow bitcoin developers. Included below is the first draft of
a BIP for a new Merkle-compressed data structure. The need for this
data structure arose out of the misnamed "Ultimate blockchain
compression" project, but it has since been recogniz
How does signing the commit message itself help at all since it just signs
the commit message, not the content of the commit. You could commit some
code then I. Then I squash my commits into yours and use your commit
message. You could also include the previous commit hash in your commit
message.
On Thu, Dec 19, 2013 at 04:04:17PM -, Amir Taaki wrote:
Looks like for this to actually go to the email lists they need to be in
the To: field.
> About signing each commit, Linus advises against it:
>
> http://git.661346.n2.nabble.com/GPG-signing-for-git-commit-td2582986.html
>
> "Btw, ther
Hey Peter -
I think this is a super list. A couple of thoughts:
a) In the section on multi-sig and multi-factor, I think we can split these
apart. Multi-factor user authentication is very valuable and not the same
as multi-factor signing, which is a second level of complexity. The
multi-facto
On 19 December 2013 16:04, Amir Taaki wrote:
> About signing each commit, Linus advises against it:
>
> http://git.661346.n2.nabble.com/GPG-signing-for-git-commit-td2582986.html
Yeah, it makes no sense after reading it. Nice catch.
However, his recommendation for signing tags with `git tag -s`
On 19 December 2013 13:17, Peter Todd wrote:
> ** Fees
>
> Wallets MUST give users the ability to set the fee per KB they are
> willing to pay for their transactions. Wallets SHOULD allow users to
> change that fee after the fact via transction replacement.
Can you add a part about SHOULD/MUST
Here's my draft. I don't claim this to be "official", but I think this
should represent the consensus we've come to at the DarkWallet
Hackathon; I'm writing it up as an email in part to preserve a record of
that consensus.
* General Principles
We believe in decentralization, user-defined privacy
9 matches
Mail list logo
