diff options
| author | Wladimir J. van der Laan <laanwj@gmail.com> | 2019-06-08 16:44:45 +0200 |
|---|---|---|
| committer | Wladimir J. van der Laan <laanwj@gmail.com> | 2019-06-08 16:45:06 +0200 |
| commit | 70d77fff3a8d54d2f0e347f7d93d7b11eb18597d (patch) | |
| tree | 2d1b249bb7355f5a78a7a16cbc0ea1c573c19703 /src/rpc/blockchain.cpp | |
| parent | 5d2ccf0ce9ca1571c650a69319fb9c1e0b626ecb (diff) | |
| parent | 8081927c33299e82498a85ac773c9f162e69ecaf (diff) | |
| download | bitcoin-70d77fff3a8d54d2f0e347f7d93d7b11eb18597d.tar.xz | |
Merge #16162: scripts: add key for Michael Ford (fanquake) to trusted keys list
8081927c33299e82498a85ac773c9f162e69ecaf scripts: add key for fanquake to trusted keys list (fanquake)
Pull request description:
Adding my key to the [trusted keys list](https://github.com/bitcoin/bitcoin/blob/master/contrib/verify-commits/trusted-keys) to join the maintainer group. I'll gain merge access and will continue with all triage/repo management work. I'll be focusing primarily on build system development with some guidance from theuni.
Some maintainer related discussion from the Core Dev meetup in Amsterdam is available [here](http://diyhpl.us/wiki/transcripts/bitcoin-core-dev-tech/2019-06-06-maintainers/).
ACKs for commit 808192:
MarcoFalke:
ACK 8081927c33299e82498a85ac773c9f162e69ecaf
laanwj:
ACK, this matches the key I have 8081927c33299e82498a85ac773c9f162e69ecaf:
meshcollider:
ACK, this matches the key I have from the CoreDev New York 2018 keysigning party https://github.com/bitcoin/bitcoin/pull/16162/commits/8081927c33299e82498a85ac773c9f162e69ecaf
IlyasRidhuan:
ACK. 8081927c33299e82498a85ac773c9f162e69ecaf matches the key I have.
Tree-SHA512: 63c390f5ede316263def2f9a897a1046d4ae58e4ea758f379164c6c5afce4928e2c9463fbcac004742838fd4ac1e48679e7a2a0f9095fd134a900f9064584056
Diffstat (limited to 'src/rpc/blockchain.cpp')
0 files changed, 0 insertions, 0 deletions