status-im
/
keycard-certify
mirror of https://github.com/status-im/keycard-certify.git
2
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
Tool for certifying Keycard production
13 Commits 1 Branch 2 Tags 1.2 MiB
TypeScript 44.2%
Python 23.7%
HTML 12.5%
CSS 12.1%
Groovy 7.5%
Go to file
Michele Balistreri ed72777991
Merge pull request #2 from status-im/add-ci-builds 
ci: add Jenkinsfile and shell.nix for builds
 		2023-08-11 11:07:01 +02:00
build added icon 2022-11-18 01:50:09 +01:00
ci ci: add Jenkinsfile and shell.nix for builds 2023-08-11 10:40:55 +02:00
css added icon 2022-11-18 01:50:09 +01:00
img added icon 2022-11-18 01:50:09 +01:00
layouts initial commit 2022-11-16 21:28:43 +01:00
src updated electron 2023-08-04 11:43:46 +02:00
.gitignore initial commit 2022-11-16 21:28:43 +01:00
LICENSE initial commit 2022-11-16 21:28:43 +01:00
README.md ci: add Jenkinsfile and shell.nix for builds 2023-08-11 10:40:55 +02:00
index.html lot identifier update 2023-06-19 16:59:09 +02:00
package-lock.json updated electron 2023-08-04 11:43:46 +02:00
package.json ci: add Jenkinsfile and shell.nix for builds 2023-08-11 10:40:55 +02:00
tsconfig.json ci: add Jenkinsfile and shell.nix for builds 2023-08-11 10:40:55 +02:00

README.md

Keycard Certify

To create certificates you should first fill in the form, specifying lot number, the quantity of cards for which you need to create a certificate, destination path for the certificates file and choose the output encryption PGP key. You also need a Keycard to sign the certificates. Path m/43'/60'/1581'/2'/0 will be used to sign.

Continuous Integration

The CI builds can be found in Jenkins under keycard-certify.

The releasejob builds the app for Linux, MacOS, and Windows, then publishes all artifacts to a GitHub release based on version set inpackage.json`.