profile
viewpoint

freicoin/freicoin 51

Freicoin integration/staging tree http://freico.in/

freicoin/freicoin-old 27

Bitcoin integration/staging tree

freicoin/freico.in 8

Website files for http://freico.in/

jtimon/freimarkets 7

Freicoin extension for arbitrary assets and trade between them

jtimon/multi-ln-demo 5

Demo for LN payment routing through multiple chains

jtimon/bitcoin 3

Bitcoin Core integration/staging tree

jtimon/preann 3

Parallel Reinforcement Evolutionary Artificial Neural Networks

created repository0i0/0i0-alacritty

created time in 2 hours

pull request commentElementsProject/secp256k1-zkp

WIP: Add MuSig Key Aggregation spec

@jonasnick has explained to me in private that signature aggregation does not work the way I had imagined it to work. signature aggregation requires a (modified) Bellare-Neven signature, which is not the same thing as a Schnorr signature. (In particular jonas pointed out that the scheme I had in mind is broken.)

Thus we can disregard my comments about signature aggregation.

This puts hash-by-key back on the table as an option. IMHO it is an option we should seriously consider.

jonasnick

comment created time in 11 hours

issue commentpjreddie/darknet

Can't open label file. (This can be normal only if you use MSCOCO)

  1. the reason you got this issue is that you miss some txt labels file in the path darknet/data/obj For example, you included 0001.txt in darknet/data/train.txt, but 0001.txt doesn't' exist in the folder darknet/data/obj

  2. why it can be normal in MSCOCO? because COCO 2017 train dataset have 1021 images which have no annotations

  3. how to deal with this issue make sure the txt file in darknet/data/train.txt is equivalent to the folder darknet/data/obj

adilraja

comment created time in 11 hours

push eventbitcoin-core/bitcoin-maintainer-tools

Wladimir J. van der Laan

commit sha 7cdb4afb360226d3eebffb93406e50884355e4cc

doc: Add brief documentation for gitian-verify to README.md

view details

push time in 13 hours

issue commentpjreddie/darknet

Can not make in Linux Mint

Hi, did you manage to solve it? May I know how did you do it? I have got the same issue as you did.

github error

fotmaiden

comment created time in 14 hours

push eventbitcoin-core/bitcoin-maintainer-tools

Wladimir J. van der Laan

commit sha 5a6dceb7f7101a9a1f507d25fbd66c54de3518ec

doc: Add brief documentation for gitian-verify to README.md

view details

push time in 14 hours

fork amiller/saucy-paper

saucy+wrappers+paper

fork in 15 hours

pull request commentbitcoin-core/bitcoin-maintainer-tools

Add gitian-verify script

Be sure to document somewhere that it needs pip install pyyaml. An example incantation with a full path is also useful, so it's clear that you need to point to the gitian.sigs and bitcoin repo.

Documentation is something that still needs to be written. I think it should be in README.md like for the other tools.

I'm not sure why the keys in the gist are different from the branch, but if that problem goes away in future releases then I'm fine with not understanding it :-) When I just tried on v0.21.0, after I downloaded some extra keys into GPG, it complained that sipa, fanquake and yourself are missing from keys.txt.

The keys should no longer be different (this was a temporary issue due to matching only on subkey). The only important thing is that in the metadata, the value between (…) at the end matches the signer name(s) used by the person with that key.

laanwj

comment created time in 18 hours

pull request commentbitcoin-core/bitcoin-maintainer-tools

Add gitian-verify script

Be sure to document somewhere that it needs pip install pyyaml. An example incantation with a full path is also useful, so it's clear that you need to point to the gitian.sigs and bitcoin repo.

I'm not sure why the keys in the gist are different from the branch, but if that problem goes away in future releases then I'm fine with not understanding it :-) When I just tried, after I downloaded some extra keys into GPG, it complained that sipa, fanquake and yourself are missing from keys.txt.

laanwj

comment created time in 19 hours

pull request commentbitcoin-core/bitcoin-maintainer-tools

Add gitian-verify script

Thanks for testing @jonatack !

Pushed some small code improvements (no functional changes):

  • Use Enum for Status
  • Use NamedTuple instead of magic indexing in longer result tuples
  • Use IntFlag for Missing bitfield
  • Add mypy annotations
laanwj

comment created time in 20 hours

push eventbitcoin-core/bitcoin-maintainer-tools

Wladimir J. van der Laan

commit sha 73d1dbd4176fec0312cdb3315b9b8e779785dd1f

Add gitian-verify script Add a script to verify gitian signatures for a version in once glance, independent of the scripts in `gitian-builder` repository.

view details

push time in 20 hours

pull request commentbitcoin-core/bitcoin-maintainer-tools

Add gitian-verify script

Nice!

Quick test at fd17314feca

$ ./gitian-verify.py -r 0.21.0 -d ../gitian.sigs -k ../bitcoin/contrib/gitian-keys/keys.txt
Signer       linux      osx-unsigned  win-unsigned   osx-signed    win-signed   
jonatack       -             -             -           No Key        No Key     

Missing keys
jonatack  82921A4B88FD454B7EB8CE3C796C4100xxxxxxxx  from keys.txt

and using the keys.txt gist above

$ ./gitian-verify.py -r 0.21.0 -d ../gitian.sigs -k keys.txt
Signer       linux      osx-unsigned  win-unsigned   osx-signed    win-signed   
jonatack       -             -             -             OK            OK   

screenshot

Screenshot from 2021-01-15 13-12-55

laanwj

comment created time in 21 hours

pull request commentbitcoin-core/bitcoin-maintainer-tools

Add gitian-verify script

Nice!

Quick test at fd17314feca

$ ./gitian-verify.py -r 0.21.0 -d ../gitian.sigs -k ../bitcoin/contrib/gitian-keys/keys.txt
Signer       linux      osx-unsigned  win-unsigned   osx-signed    win-signed   
jonatack       -             -             -           No Key        No Key     

Missing keys
jonatack  82921A4B88FD454B7EB8CE3C796C4100xxxxxxxx  from keys.txt

and using the keys.txt gist above

$ ./gitian-verify.py -r 0.21.0 -d ../gitian.sigs -k keys.txt
Signer       linux      osx-unsigned  win-unsigned   osx-signed    win-signed   
jonatack       -    
laanwj

comment created time in 21 hours

pull request commentbitcoin-core/bitcoin-maintainer-tools

Add gitian-verify script

Pushed new version:

  • added @fanquake 's workaround for old versions
  • factor out gpg call to a verification interface (could, in the future, potentially add parallelism support for faster checks)
  • keys.txt: look for primary key as well as subkey
  • add "get builds for release" function instead of constant
  • case insensitive sort of signer names

keys.txt can be pruned again a bit after this (the only person in the list with two keys is now emzy who seems to really have two primary keys?)

laanwj

comment created time in a day

push eventbitcoin-core/bitcoin-maintainer-tools

Wladimir J. van der Laan

commit sha fd17314feca69e41b059022dae6f610d968100f7

Add gitian-verify script Add a script to verify gitian signatures for a version in once glance, independent of the scripts in `gitian-builder` repository.

view details

push time in a day

pull request commentbitcoin-core/bitcoin-maintainer-tools

Add gitian-verify script

@fanquake Thanks for testing, and the workaround, will include that.

There's still a few other things I want to address:

  • Be stricter about gpg's output format. It's always the same three lines. The current parsing allows for a bit of "funny business", e.g. if someone through some manages to make it print the "gpg: using" multiple times. Might look into --with-colons as well as supposedly it aids machine parsing.
  • It's kind of unfortunate that this now needs mention of every leaf key used for signing in keys.txt. It would be nice to allow the current abbreviated format of specifying just the parent key, but I'd need to implement a way to get the child keys from gpg.
laanwj

comment created time in a day

issue closedbitcoin-core/bitcoin-maintainer-tools

README.md

External repository for Bitcoin Core related maintenance tools.

github-merge

A small script to automate merging pull-requests securely and sign them with GPG.

For example:

./github-merge.py 1234

(in any git repository) will help you merge pull request #1234 for the configured repository.

What it does:

  • Fetch master and the pull request.
  • Locally construct a merge commit.
  • Show the diff that merge results in.
  • Ask you to verify the resulting source tree (so you can do a make check or whatever).
  • Ask you whether to GPG sign the merge commit.
  • Ask you whether to push the result upstream.

This means that there are no potential race conditions (where a pull request gets updated while you're reviewing it, but before you click merge), and when using GPG signatures, that even a compromised GitHub couldn't mess with the sources.

Setup

Configuring the github-merge tool for the bitcoin repository is done in the following way:

git config githubmerge.repository bitcoin/bitcoin
git config githubmerge.testcmd "make -j4 check" (adapt to whatever you want to use for testing)
git config --global user.signingkey mykeyid

If you want to use HTTPS instead of SSH for accessing GitHub, you need set the host additionally:

git config githubmerge.host "https://github.com"  (default is "git@github.com", which implies SSH)

Authentication (optional)

The API request limit for unauthenticated requests is quite low, but the limit for authenticated requests is much higher. If you start running into rate limiting errors it can be useful to set an authentication token so that the script can authenticate requests.

  • First, go to Personal access tokens.
  • Click 'Generate new token'.
  • Fill in an arbitrary token description. No further privileges are needed.
  • Click the Generate token button at the bottom of the form.
  • Copy the generated token (should be a hexadecimal string)

Then do:

git config --global user.ghtoken "pasted token"

Create and verify timestamps of merge commits

To create or verify timestamps on the merge commits, install the OpenTimestamps client via pip3 install opentimestamps-client. Then, download the gpg wrapper ots-git-gpg-wrapper.sh and set it as git's gpg.program. See the ots git integration documentation for further details.

update-translations

Run this script from the root of a repository to update all translations from Transifex. It will do the following automatically:

  • Fetch all translations
  • Post-process them into valid and committable format
  • Add missing translations to the build system (TODO)

clang-format

A script to format cpp source code according to the .clang-format file in the bitcoin repo. This should only be applied to new files or files which are currently not actively developed on. Also, git subtrees are not subject to formatting.

Note: The script is currently untested and unmaintained, but kept for archival reasons, in case it is planned to be used some day.

build-for-compare

Build for binary comparison.

See build-for-compare.py --help for more information.

Builds from current directory, which is assumed to be a git clone of the bitcoin repository.

DO NOT RUN this with the nocopy=1 flag set on working tree if you have any local additions, it will nuke all non-repository files, multiple times over. By leaving nocopy off (default) the git tree is copied to a temporary directory and all operations are performed there.

Example:

git clone https://github.com/bitcoin/bitcoin.git bitcoin-compare
cd bitcoin-compare
../bitcoin-maintainer-tools/build-for-compare.py 4731cab 2f71490
sha256sum /tmp/compare/bitcoind.*.stripped
git diff -W --word-diff /tmp/compare/4731cab /tmp/compare/2f71490

backport

Script to backport pull requests in order of merge, to minimize number of conflicts. Pull ids are listed in to_backport.txt or given on the command line.

Requires pip3 install gitpython or similar.

unittest-statistics

unittest-statistics.py can be used to print a table of the slowest 20 unit tests.

Usage:

unittest-statistics.py </path/to/test_bitcoin> [<subtest>]

For example:

unittest-statistics.py src/test/test_bitcoin wallet_tests

treehash512

This script will show the SHA512 tree has for a certain commit, or HEAD by default.

Usage:

treehash512.py [<commithash>]

This should match the Tree-SHA512 commit metadata field added by github-merge.

signoff

This is an utility to manually add a treehash to the HEAD commit and then gpg-sign it. This is useful when there is the need to manually add a commit.

Usage:

signoff.py

(no command line arguments)

When there is already a treehash on the HEAD commit, it is compared against what is computed. If this matches, it continues. If the treehash mismatches an error is thrown. If there is no treehash it adds the "Tree-SHA512:" header with the computed hash to the commit message.

After making sure the treehash is correct it verifies whether the commit is signed. If so it just displays the signature, if not, it is signed.

subtree updates

Bitcoin Core comes with several subtrees (c.f. https://github.com/bitcoin/bitcoin/tree/master/test/lint#git-subtree-checksh) To update the subtree, make sure to fetch the remote of the subtree. Then a simple call should pull in and squash the changes:

git subtree pull --prefix src/${prefix} ${remote_repo} ${ref} --squash

For setting up a subtree, refer to git help subtree.

check-dnsseeds

Sanity-check the DNS seeds used by Bitcoin Core.

Usage:

check-dnsseeds.py

Example output:

* Mainnet
OK   seed.bitcoin.sipa.be (40 results)
OK   dnsseed.bluematt.me (33 results)
FAIL dnsseed.bitcoin.dashjr.org
OK   seed.bitcoinstats.com (50 results)
OK   seed.bitcoin.jonasschnelli.ch (38 results)
OK   seed.btc.petertodd.org (23 results)
OK   seed.bitcoin.sprovoost.nl (35 results)
OK   dnsseed.emzy.de (41 results)

* Testnet
OK   testnet-seed.bitcoin.jonasschnelli.ch (36 results)
OK   seed.tbtc.petertodd.org (38 results)
OK   testnet-seed.bluematt.me (5 results)

fastcopy-chaindata

Fast local copy of Bitcoin Core blockchain state.

fastcopy-chaindata.py ~/.bitcoin /path/to/temp/datadir

This utility hardlinks all but the last block data file (rev and blk), and hardlinks all .ldb files to the destination. The last data files as well as the other leveldb data files (such as the log) are copied.

This relies on the fact that block files (except the last) and ldb files are read-only once they are written.

Warning: Hardlinking only works within a filesystem, and may not work for all filesystems.

transifex-migrate-resource

Copy a transifex resource to another.

Run the script providing the slug of the project and the slug of the old and new resource. The new resource should already have been created, but be otherwise empty. It should be based on the exact same source translation.

Example: Old resource slug: 'old' New resource slug: 'new'

python transifex-migrate-resource.py project old new

After running the command you will be asked for your Transifex username and password.

list-pulls

Script to parse git commit list, extract github issues to create a changelog in text and json format.

Run this in the root directory of the repository.

This requires an up-to-date checkout of https://github.com/zw/bitcoin-gh-meta.git in the parent directory, or environment variable GHMETA.

It takes a range of commits and a .json file of PRs to exclude, for example if these are already backported in a minor release. This can be the pulls.json generated from a previous release.

Example usage:

../maintainer-tools/list-pulls.py v0.18.0 0.19 relnot/pulls-exclude.json > relnot/pulls.md

The output of this script is a first draft based on rough heuristics, and likely needs to be extensively manually edited before ending up in the release notes.

make-tag

Make a new release tag, performing a few checks.

Usage: make-tag.py <tag>.

closed time in a day

hellomalaysia

issue openedbitcoin-core/bitcoin-maintainer-tools

README.md

External repository for Bitcoin Core related maintenance tools.

github-merge

A small script to automate merging pull-requests securely and sign them with GPG.

For example:

./github-merge.py 1234

(in any git repository) will help you merge pull request #1234 for the configured repository.

What it does:

  • Fetch master and the pull request.
  • Locally construct a merge commit.
  • Show the diff that merge results in.
  • Ask you to verify the resulting source tree (so you can do a make check or whatever).
  • Ask you whether to GPG sign the merge commit.
  • Ask you whether to push the result upstream.

This means that there are no potential race conditions (where a pull request gets updated while you're reviewing it, but before you click merge), and when using GPG signatures, that even a compromised GitHub couldn't mess with the sources.

Setup

Configuring the github-merge tool for the bitcoin repository is done in the following way:

git config githubmerge.repository bitcoin/bitcoin
git config githubmerge.testcmd "make -j4 check" (adapt to whatever you want to use for testing)
git config --global user.signingkey mykeyid

If you want to use HTTPS instead of SSH for accessing GitHub, you need set the host additionally:

git config githubmerge.host "https://github.com"  (default is "git@github.com", which implies SSH)

Authentication (optional)

The API request limit for unauthenticated requests is quite low, but the limit for authenticated requests is much higher. If you start running into rate limiting errors it can be useful to set an authentication token so that the script can authenticate requests.

  • First, go to Personal access tokens.
  • Click 'Generate new token'.
  • Fill in an arbitrary token description. No further privileges are needed.
  • Click the Generate token button at the bottom of the form.
  • Copy the generated token (should be a hexadecimal string)

Then do:

git config --global user.ghtoken "pasted token"

Create and verify timestamps of merge commits

To create or verify timestamps on the merge commits, install the OpenTimestamps client via pip3 install opentimestamps-client. Then, download the gpg wrapper ots-git-gpg-wrapper.sh and set it as git's gpg.program. See the ots git integration documentation for further details.

update-translations

Run this script from the root of a repository to update all translations from Transifex. It will do the following automatically:

  • Fetch all translations
  • Post-process them into valid and committable format
  • Add missing translations to the build system (TODO)

clang-format

A script to format cpp source code according to the .clang-format file in the bitcoin repo. This should only be applied to new files or files which are currently not actively developed on. Also, git subtrees are not subject to formatting.

Note: The script is currently untested and unmaintained, but kept for archival reasons, in case it is planned to be used some day.

build-for-compare

Build for binary comparison.

See build-for-compare.py --help for more information.

Builds from current directory, which is assumed to be a git clone of the bitcoin repository.

DO NOT RUN this with the nocopy=1 flag set on working tree if you have any local additions, it will nuke all non-repository files, multiple times over. By leaving nocopy off (default) the git tree is copied to a temporary directory and all operations are performed there.

Example:

git clone https://github.com/bitcoin/bitcoin.git bitcoin-compare
cd bitcoin-compare
../bitcoin-maintainer-tools/build-for-compare.py 4731cab 2f71490
sha256sum /tmp/compare/bitcoind.*.stripped
git diff -W --word-diff /tmp/compare/4731cab /tmp/compare/2f71490

backport

Script to backport pull requests in order of merge, to minimize number of conflicts. Pull ids are listed in to_backport.txt or given on the command line.

Requires pip3 install gitpython or similar.

unittest-statistics

unittest-statistics.py can be used to print a table of the slowest 20 unit tests.

Usage:

unittest-statistics.py </path/to/test_bitcoin> [<subtest>]

For example:

unittest-statistics.py src/test/test_bitcoin wallet_tests

treehash512

This script will show the SHA512 tree has for a certain commit, or HEAD by default.

Usage:

treehash512.py [<commithash>]

This should match the Tree-SHA512 commit metadata field added by github-merge.

signoff

This is an utility to manually add a treehash to the HEAD commit and then gpg-sign it. This is useful when there is the need to manually add a commit.

Usage:

signoff.py

(no command line arguments)

When there is already a treehash on the HEAD commit, it is compared against what is computed. If this matches, it continues. If the treehash mismatches an error is thrown. If there is no treehash it adds the "Tree-SHA512:" header with the computed hash to the commit message.

After making sure the treehash is correct it verifies whether the commit is signed. If so it just displays the signature, if not, it is signed.

subtree updates

Bitcoin Core comes with several subtrees (c.f. https://github.com/bitcoin/bitcoin/tree/master/test/lint#git-subtree-checksh) To update the subtree, make sure to fetch the remote of the subtree. Then a simple call should pull in and squash the changes:

git subtree pull --prefix src/${prefix} ${remote_repo} ${ref} --squash

For setting up a subtree, refer to git help subtree.

check-dnsseeds

Sanity-check the DNS seeds used by Bitcoin Core.

Usage:

check-dnsseeds.py

Example output:

* Mainnet
OK   seed.bitcoin.sipa.be (40 results)
OK   dnsseed.bluematt.me (33 results)
FAIL dnsseed.bitcoin.dashjr.org
OK   seed.bitcoinstats.com (50 results)
OK   seed.bitcoin.jonasschnelli.ch (38 results)
OK   seed.btc.petertodd.org (23 results)
OK   seed.bitcoin.sprovoost.nl (35 results)
OK   dnsseed.emzy.de (41 results)

* Testnet
OK   testnet-seed.bitcoin.jonasschnelli.ch (36 results)
OK   seed.tbtc.petertodd.org (38 results)
OK   testnet-seed.bluematt.me (5 results)

fastcopy-chaindata

Fast local copy of Bitcoin Core blockchain state.

fastcopy-chaindata.py ~/.bitcoin /path/to/temp/datadir

This utility hardlinks all but the last block data file (rev and blk), and hardlinks all .ldb files to the destination. The last data files as well as the other leveldb data files (such as the log) are copied.

This relies on the fact that block files (except the last) and ldb files are read-only once they are written.

Warning: Hardlinking only works within a filesystem, and may not work for all filesystems.

transifex-migrate-resource

Copy a transifex resource to another.

Run the script providing the slug of the project and the slug of the old and new resource. The new resource should already have been created, but be otherwise empty. It should be based on the exact same source translation.

Example: Old resource slug: 'old' New resource slug: 'new'

python transifex-migrate-resource.py project old new

After running the command you will be asked for your Transifex username and password.

list-pulls

Script to parse git commit list, extract github issues to create a changelog in text and json format.

Run this in the root directory of the repository.

This requires an up-to-date checkout of https://github.com/zw/bitcoin-gh-meta.git in the parent directory, or environment variable GHMETA.

It takes a range of commits and a .json file of PRs to exclude, for example if these are already backported in a minor release. This can be the pulls.json generated from a previous release.

Example usage:

../maintainer-tools/list-pulls.py v0.18.0 0.19 relnot/pulls-exclude.json > relnot/pulls.md

The output of this script is a first draft based on rough heuristics, and likely needs to be extensively manually edited before ending up in the release notes.

make-tag

Make a new release tag, performing a few checks.

Usage: make-tag.py <tag>.

created time in a day

pull request commentbitcoin-core/bitcoin-maintainer-tools

Add gitian-verify script

Nice! Concept ACK.

Gave this a test run. Added some additional keys here: https://gist.github.com/fanquake/763634cc1d0758b05ac471e4f507699b. This gets you back through to 0.18.0.

I noticed that when I try and verify for 0.13.0 - 0.16.0, the script would error out:

./gitian-verify.py -r 0.16.0 -d ~/gitian-building/gitian.sigs -k ~/Downloads/keys.txt
....
  File "/Users/michael/.pyenv/versions/3.9.0/lib/python3.9/site-packages/yaml/constructor.py", line 100, in construct_object
    data = constructor(self, node)
  File "/Users/michael/.pyenv/versions/3.9.0/lib/python3.9/site-packages/yaml/constructor.py", line 427, in construct_undefined
    raise ConstructorError(None, None,
yaml.constructor.ConstructorError: could not determine a constructor for the tag '!omap'
  in "/Users/michael/gitian-building/gitian.sigs/0.16.0-linux/kallewoof/bitcoin-linux-0.16-build.assert", line 1, column 5

Turns out some of those asserts contain invalid yaml (!omap instead of !!omap). There are a couple upstream issues about this, including https://github.com/ruby/psych/issues/241 & some discussion here: https://github.com/etotheipi/BitcoinArmory/pull/306. The suggested work around seems to fix the issue:

diff --git a/gitian-verify.py b/gitian-verify.py
index 2bb5f60..5c0e8c8 100755
--- a/gitian-verify.py
+++ b/gitian-verify.py
@@ -9,6 +9,9 @@ import re
 import subprocess
 import yaml
 
+# workaround legacy issue where some yaml may contain !omap instead of !!omap
+yaml.add_constructor("!omap", yaml.constructor.SafeConstructor.construct_yaml_omap, Loader=yaml.SafeLoader)
+
 class Status:
     '''Verification status enumeration.'''
     OK = 0                 # Full match

Up to you whether it's worth including to fix verification of older builds.

laanwj

comment created time in a day

push eventbitcoin-core/bitcoin-maintainer-tools

Wladimir J. van der Laan

commit sha 3082005152ad489825cbbb648f766fbbeefa7c57

Add gitian-verify script Add a script to verify gitian signatures for a version in once glance, independent of the scripts in `gitian-builder` repository.

view details

push time in a day

push eventbitcoin-core/bitcoin-maintainer-tools

Wladimir J. van der Laan

commit sha 12dfa044a5aa8b633e4633b25bd9660dab10f241

Add gitian-verify script Add a script to verify gitian signatures for a version in once glance, independent of the scripts in `gitian-builder` repository.

view details

push time in a day

PR opened bitcoin-core/bitcoin-maintainer-tools

Add gitian-verify script

Add a script to verify gitian signatures for a version in one glance, independent of the Ruby scripts in gitian-builder repository.

Example (./gitian-verify.py -r 0.21.0rc5 -d ../gitian.sigs -k keys.txt):

screenshot_gitianverify

This needs a slightly different keys.txt from that on the branch (the key IDs must match exactly the signing keys, the aliases in parenthesis are important); see this gist https://gist.github.com/laanwj/8368525bba4d89488dd5a0418884d91d

It supports these options:

usage: gitian-verify.py [-h] [--verbose] [--release RELEASE] [--directory DIRECTORY] [--keys KEYS] [--verify-program VERIFY_PROGRAM] [--compare-to COMPARE_TO]

Verify gitian signatures

optional arguments:
  -h, --help            show this help message and exit
  --verbose, -v         Be more verbose
  --release RELEASE, -r RELEASE
                        Release name
  --directory DIRECTORY, -d DIRECTORY
                        Signatures directory
  --keys KEYS, -k KEYS  Keys file
  --verify-program VERIFY_PROGRAM, -p VERIFY_PROGRAM
                        Specify verification program to use (default is gpg)
  --compare-to COMPARE_TO, -c COMPARE_TO
                        Compare other manifests to SIGNER's, if not given pick first
+242 -0

0 comment

1 changed file

pr created time in a day

create barnchbitcoin-core/bitcoin-maintainer-tools

branch : 2021-01-gitian-verify

created branch time in a day

pull request commentElementsProject/secp256k1-zkp

WIP: Add MuSig Key Aggregation spec

P.S. I hate little endian formats. Also isn't 32-bytes too much?

My mistake, should have been 4 bytes. Changed spec and C code to encode index with MSB first.

jonasnick

comment created time in 2 days

PR merged ElementsProject/secp256k1-zkp

Add contrib/sync-upstream.sh script to automate syncing PRs

Based on @apoelstra's original script but adapted to work with github-cli instead of "hub".

+112 -0

8 comments

2 changed files

jonasnick

pr closed time in 2 days

push eventElementsProject/secp256k1-zkp

Jonas Nick

commit sha 7eeacd7725fa8c895c2f58850b151e66199137cf

Add contrib/sync-upstream.sh script to automate merging upstream PRs

view details

Jonas Nick

commit sha ed69ea79b429beae4260917e08fe60317d38ee8d

Merge #98: Add contrib/sync-upstream.sh script to automate syncing PRs 7eeacd7725fa8c895c2f58850b151e66199137cf Add contrib/sync-upstream.sh script to automate merging upstream PRs (Jonas Nick) Pull request description: ACKs for top commit: real-or-random: ACK 7eeacd7725fa8c895c2f58850b151e66199137cf The code looks fine. I haven't tested this script but it's not the end of the world if the script has a bug. Tree-SHA512: d2e0128980538f4e1f20ce3709d1464e82e2d0d89e6faafa157f627cea2919cc3d2a578daf73b93624fa61ecb74891b547d303471afb4f865130b7cd094cd0d0

view details

push time in 2 days

pull request commentElementsProject/secp256k1-zkp

Add contrib/sync-upstream.sh script to automate syncing PRs

ACK 7eeacd7725fa8c895c2f58850b151e66199137cf The code looks fine. I haven't tested this script but it's not the end of the world if the script has a bug.

https://github.com/ElementsProject/secp256k1-zkp/compare/7eeacd7725fa8c895c2f58850b151e66199137cf..8295d64396a8560453180b87851f37a3113a72d2

jonasnick

comment created time in 2 days

issue commentpjreddie/darknet

Demo needs OpenCV for webcam images.

je rencontre la meme dificulté avec yolov3

pareil ! as tu resolut ?

ccs1605

comment created time in 2 days

issue commentpjreddie/darknet

Demo needs OpenCV for webcam images.

make

GPU=0 CUDNN=0 OPENCV=1 OPENMP=0 DEBUG=0

./darknet detector demo cfg/coco.data cfg/yolov3.cfg yolov3.weights dubai.mp4 Demo needs OpenCV for webcam images. still not working for me

ccs1605

comment created time in 2 days

more