Skip to content
master
Go to file
Code

Latest commit

 

Git stats

Files

Permalink
Failed to load latest commit information.
Type
Name
Latest commit message
Commit time
 
 
 
 
cmd
 
 
 
 
 
 
 
 
src
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

README.md

mdl logo

MDL Talent Hub Token / TH / Token Hour / Talent Hour Wallet

Build Status GoDoc Go Report Card

MDL is a token used in MDL Talent Hub platform. It's based on Skycoin's code base.

MDL & SKY improvements are far too many to be addressed here. Please read MDL website, MDL blog and Skycoin Blog instead.

MDL, following Skycoin's concepts, was designed to be what Bitcoin would look like if it were built from scratch, to remedy the rough edges in the Bitcoin design.

  • no duplicate coin-base outputs
  • enforced checks for hash collisions
  • simple deterministic wallets
  • no transaction malleability
  • no signature malleability
  • removal of the scripting language
  • CoinJoin and normal transactions are indistinguishable
  • elimination of edge-cases that prevent independent node implementations
  • <=10 second transaction times
  • elimination of the need for mining to achieve blockchain consensus

Links

Table of Contents

Changelog

CHANGELOG.md

Installation

MDL supports go1.10+.

Go 1.10+ Installation and Setup

Golang 1.10+ Installation/Setup

Go get MDL

go get github.com/MDLlife/MDL/...

This will download github.com/MDLlife/MDL to $GOPATH/src/github.com/MDLlife/MDL.

You can also clone the repo directly with git clone https://github.com/MDLlife/MDL, but it must be cloned to this path: $GOPATH/src/github.com/MDLlife/MDL.

Run MDL from the command line

cd $GOPATH/src/github.com/MDLlife/MDL
make run

Show MDL node options

cd $GOPATH/src/github.com/MDLlife/MDL
make run-help

Run MDL with options

Example:

cd $GOPATH/src/github.com/MDLlife/MDL
make ARGS="--launch-browser=false -data-dir=/custom/path" run

Docker image

$ docker volume create mdl-data
$ docker volume create mdl-wallet
$ docker run -ti --rm \
    -v mdl-data:/data \
    -v mdl-wallet:/wallet \
    -p 6000:6000 \
    -p 6420:6420 \
    -p 6430:6430 \
    mdl/mdl

Access the dashboard: http://localhost:6420.

Access the API: http://localhost:6420/version. This is the quickest way to start using MDL using Docker.

$ docker volume create mdl-data
$ docker volume create mdl-wallet
$ docker run -ti --rm \
    -v mdl-data:/data \
    -v mdl-wallet:/wallet \
    -p 6000:6000 \
    -p 6420:6420 \
    -p 6430:6430 \
    mdl/mdl

This image has a mdl user for the mdl daemon to run, with UID and GID 10000. When you mount the volumes, the container will change their owner, so you must be aware that if you are mounting an existing host folder any content you have there will be own by 10000.

The container will run with some default options, but you can change them by just appending flags at the end of the docker run command. The following example will show you the available options.

docker run --rm mdl/mdl -help

Access the dashboard: http://localhost:6420.

Access the API: http://localhost:6420/version.

Building your own images

Building your own images. There is a Dockerfile in docker/images/mainnet that you can use to build your own image. By default it will build your working copy, but if you pass the MDL_VERSION build argument to the docker build command, it will checkout to the branch, a tag or a commit you specify on that variable.

Development image

The MDLlife/MDLdev-cli docker image is provided in order to make easy to start developing MDL. It comes with the compiler, linters, debugger and the vim editor among other tools.

$ git clone https://github.com/MDLlife/MDL
$ cd mdl
$ MDL_VERSION=v0.23.0
$ docker build -f docker/images/mainnet/Dockerfile \
  --build-arg=MDL_VERSION=$MDL_VERSION \
  -t mdl:$MDL_VERSION .

or just

$ docker build -f docker/images/mainnet/Dockerfile \
  --build-arg=MDL_VERSION=v0.23.0 \
  -t mdl:v0.23.0 .

The MDLlife/MDLdev-dind docker image comes with docker installed and all tools available on MDLlife/MDLdev-cli:develop docker image.

Also, the MDLlife/MDLdev-vscode docker image is provided to facilitate the setup of the development process with Visual Studio Code and useful tools included in MDLlife/MDLdev-cli.

API Documentation

REST API

REST API.

JSON-RPC 2.0 API

Deprecated, avoid using this

JSON-RPC 2.0 README.

MDL command line interface

CLI command API.

Integrating MDL with your application

MDL Integration Documentation

Contributing a node to the network

Add your node's ip:port to the peers.txt file. This file will be periodically uploaded to https://res.mdl.wtf/blockchain/peers.txt and used to seed client with peers.

Note: Do not add MDLwire nodes to peers.txt. Only add MDL nodes with high uptime and a static IP address (such as a MDL node hosted on a VPS).

Creating a new coin

See the newcoin tool README

Running with a custom coin hour burn factor

The coin hour burn factor is the denominator in the ratio of coinhours that must be burned by a transaction. For example, a burn factor of 2 means 1/2 of hours must be burned. A burn factor of 10 means 1/10 of coin hours must be burned.

The coin hour burn factor can be configured with a USER_BURN_FACTOR envvar. It cannot be configured through the command line.

USER_BURN_FACTOR=999 ./run-client.sh

This burn factor applies to user-created transactions.

To control the burn factor in other scenarios, use -burn-factor-unconfirmed and -burn-factor-create-block.

Running with a custom max transaction size

USER_MAX_TXN_SIZE=1024 ./run-client.sh

This maximum transaction size applies to user-created transactions.

To control the transaction size in other scenarios, use -max-txn-size-unconfirmed and -max-txn-size-create-block.

To control the max block size, use -max-block-size.

Transaction and block size are measured in bytes.

Running with a custom max decimal places

USER_MAX_DECIMALS=4 ./run-client.sh

This maximum transaction size applies to user-created transactions.

To control the maximum decimals in other scenarios, use -max-decimals-unconfirmed and -max-decimals-create-block.

Creating a new coin

See the newcoin tool README

Running with a custom coin hour burn factor

The coin hour burn factor is the denominator in the ratio of coinhours that must be burned by a transaction. For example, a burn factor of 2 means 1/2 of hours must be burned. A burn factor of 10 means 1/10 of coin hours must be burned.

The coin hour burn factor can be configured with a USER_BURN_FACTOR envvar. It cannot be configured through the command line.

$ USER_BURN_FACTOR=999 ./run-client.sh

This burn factor applies to user-created transactions.

To control the burn factor in other scenarios, use -burn-factor-unconfirmed and -burn-factor-create-block.

Running with a custom max transaction size

$ USER_MAX_TXN_SIZE=1024 ./run-client.sh

This maximum transaction size applies to user-created transactions.

To control the transaction size in other scenarios, use -max-txn-size-unconfirmed and -max-txn-size-create-block.

To control the max block size, use -max-block-size.

Transaction and block size are measured in bytes.

Running with a custom max decimal places

$ USER_MAX_DECIMALS=4 ./run-client.sh

This maximum transaction size applies to user-created transactions.

To control the maximum decimals in other scenarios, use -max-decimals-unconfirmed and -max-decimals-create-block.

URI Specification

MDL URIs obey the same rules as specified in Bitcoin's BIP21. They use the same fields, except with the addition of an optional hours parameter, specifying the coin hours.

Example MDL URIs:

  • mdl:2hYbwYudg34AjkJJCRVRcMeqSWHUixjkfwY
  • mdl:2hYbwYudg34AjkJJCRVRcMeqSWHUixjkfwY?amount=123.456&hours=70
  • mdl:2hYbwYudg34AjkJJCRVRcMeqSWHUixjkfwY?amount=123.456&hours=70&label=friend&message=Birthday%20Gift

Additonally, if no mdl: prefix is present when parsing, the string may be treated as an address:

  • 2hYbwYudg34AjkJJCRVRcMeqSWHUixjkfwY

However, do not use this URI in QR codes displayed to the user, because the address can't be disambiguated from other Skyfiber coins.

Wire protocol user agent

Wire protocol user agent description

Additonally, if no mdl: prefix is present when parsing, the string may be treated as an address:

  • 2hYbwYudg34AjkJJCRVRcMeqSWHUixjkfwY

However, do not use this URI in QR codes displayed to the user, because the address can't be disambiguated from other Skyfiber coins.

Wire protocol user agent

Wire protocol user agent description

Development

We have two branches: master and develop.

develop is the default branch and will have the latest code.

master will always be equal to the current stable release on the website, and should correspond with the latest release tag.

Modules

  • api - REST API interface
  • cipher - cryptographic library (key generation, addresses, hashes)
  • cipher/base58 - Base58 encoding
  • cipher/encoder - reflect-based deterministic runtime binary encoder
  • cipher/encrypt - at-rest data encryption (chacha20poly1305+scrypt)
  • cipher/go-bip39 - BIP-39 seed generation
  • cli - CLI library
  • coin - blockchain data structures (blocks, transactions, unspent outputs)
  • daemon - top-level application manager, combining all components (networking, database, wallets)
  • daemon/gnet - networking library
  • daemon/pex - peer management
  • params - configurable transaction verification parameters
  • readable - JSON-encodable representations of internal structures
  • mdl - core application initialization and configuration
  • testutil - testing utility methods
  • transaction - methods for creating transactions
  • util - miscellaneous utilities
  • visor - top-level blockchain database layer
  • visor/blockdb - low-level blockchain database layer
  • visor/historydb - low-level blockchain database layer for historical blockchain metadata
  • wallet - wallet file management

Client libraries

MDL implements client libraries which export core functionality for usage from other programming languages. Read the corresponding README file for further details.

For further details run make docs to generate documetation and read the corresponding README and API references.

It is also possible to build client libraries for other programming languages using SWIG.

Running Tests

$ make test

Running Integration Tests

There are integration tests for the CLI and HTTP API interfaces. They have two run modes, "stable" and "live".

The stable integration tests will use a mdl daemon whose blockchain is synced to a specific point and has networking disabled so that the internal state does not change.

The live integration tests should be run against a synced or syncing node with networking enabled.

Stable Integration Tests

$ make integration-test-stable

or

$ ./ci-scripts/integration-test-stable.sh -v -w

The -w option, run wallet integrations tests.

The -v option, show verbose logs.

Live Integration Tests

The live integration tests run against a live runnning mdl node, so before running the test, we need to start a mdl node: The live integration tests run against a live runnning mdl node, so before running the test, we need to start a mdl node:

./run-daemon.sh
$ ./run-daemon.sh

After the MDL node is up, run the following command to start the live tests:

make integration-test-live
$ make integration-test-live

The above command will run all tests except the wallet-related tests. To run wallet tests, we need to manually specify a wallet file, and it must have at least 2 coins and 256 coinhours, it also must have been loaded by the node.

We can specify the wallet by setting two environment variables: WALLET_DIR and WALLET_NAME. The WALLET_DIR represents the absolute path of the wallet directory, and WALLET_NAME represents the wallet file name.

Note: WALLET_DIR is only used by the CLI integration tests. The GUI integration tests use the node's configured wallet directory, which can be controlled with -wallet-dir when running the node.

If the wallet is encrypted, also set WALLET_PASSWORD.

export WALLET_DIR="$HOME/.mdl/wallets"
export WALLET_NAME="$valid_wallet_filename"
export WALLET_PASSWORD="$wallet_password"
/run-client.sh -launch-browser=false -enable-all-api-sets -enable-api-sets=DEPRECATED_WALLET_SPEND
$ export WALLET_DIR="$HOME/.mdl/wallets"
$ export WALLET_NAME="$valid_wallet_filename"
$ export WALLET_PASSWORD="$wallet_password"
$ ./run-client.sh -launch-browser=false -enable-all-api-sets

Then run the tests with the following command:

make integration-test-live-wallet

There are two other live integration test modes for CSRF disabled and networking disabled.

To run the CSRF disabled tests:

./run-daemon.sh -disable-csrf
make integration-test-live-disable-csrf
$ make integration-test-live-wallet

There are two other live integration test modes for CSRF disabled and networking disabled.

To run the CSRF disabled tests:

$ ./run-daemon.sh -disable-csrf

To run the networking disabled tests, which requires a live wallet:

./run-client.sh -disable-networking -launch-browser=false
export WALLET_DIR="$HOME/.mdl/wallets"
export WALLET_NAME="$valid_wallet_filename"
export WALLET_PASSWORD="$wallet_password"
make integration-test-live-disable-networking
$ make integration-test-live-disable-csrf

To run the networking disabled tests, which requires a live wallet:

$ ./run-client.sh -disable-networking -launch-browser=false
$ export WALLET_DIR="$HOME/.mdl/wallets"
$ export WALLET_NAME="$valid_wallet_filename"
$ export WALLET_PASSWORD="$wallet_password"
$ make integration-test-live-disable-networking

Debugging Integration Tests

Run specific test case:

It's annoying and a waste of time to run all tests to see if the test we real care is working correctly. There's an option: -r, which can be used to run specific test case. For example: if we only want to test TestStableAddressBalance and see the result, we can run:

$ ./ci-scripts/integration-test-stable.sh -v -r TestStableAddressBalance

Update golden files in integration testdata

Golden files are expected data responses from the CLI or HTTP API saved to disk. When the tests are run, their output is compared to the golden files.

To update golden files, use the provided make command:

$ make update-golden-files

We can also update a specific test case's golden file with the -r option. For example:

$ ./ci-scripts/integration-test-stable.sh -v -u -r TestStableAddressBalance

Test coverage

Coverage is automatically generated for make test and integration tests run against a stable node. This includes integration test coverage. The coverage output files are placed in coverage/.

To merge coverage from all tests into a single HTML file for viewing:

$ make check
$ make merge-coverage

Then open coverage/all-coverage.html in the browser.

Test coverage for the live node

Some tests can only be run with a live node, for example wallet spending tests. To generate coverage for this, build and run the mdl node in test mode before running the live integration tests.

In one shell:

$ make run-integration-test-live-cover

In another shell:

$ make integration-test-live

After the tests have run, CTRL-C to exit the process from the first shell. A coverage file will be generated at coverage/mdl-live.coverage.out.

Merge the coverage with make merge-coverage then open the coverage/all-coverage.html file to view it, or generate the HTML coverage in isolation with go tool cover -html

Test coverage

Coverage is automatically generated for make test and integration tests run against a stable node. This includes integration test coverage. The coverage output files are placed in coverage/.

To merge coverage from all tests into a single HTML file for viewing:

make check
make merge-coverage

Then open coverage/all-coverage.html in the browser.

Test coverage for the live node

Some tests can only be run with a live node, for example wallet spending tests. To generate coverage for this, build and run the mdl node in test mode before running the live integration tests.

In one shell:

make run-integration-test-live-cover

In another shell:

make integration-test-live

After the tests have run, CTRL-C to exit the process from the first shell. A coverage file will be generated at coverage/mdl-live.coverage.out.

Merge the coverage with make merge-coverage then open the coverage/all-coverage.html file to view it, or generate the HTML coverage in isolation with go tool cover -html

Formatting

All .go source files should be formatted goimports. You can do this with:

$ make format

Code Linting

Install prerequisites:

$ make install-linters

Run linters:

$ make lint

Profiling

A full CPU profile of the program from start to finish can be obtained by running the node with the -profile-cpu flag. Once the node terminates, a profile file is written to -profile-cpu-file (defaults to cpu.prof). This profile can be analyzed with

$ go tool pprof cpu.prof

The HTTP interface for obtaining more profiling data or obtaining data while running can be enabled with -http-prof. The HTTP profiling interface can be controlling with -http-prof-host and listens on localhost:6060 by default.

See https://golang.org/pkg/net/http/pprof/ for guidance on using the HTTP profiler.

Some useful examples include:

go tool pprof http://localhost:6060/debug/pprof/profile?seconds=10
go tool pprof http://localhost:6060/debug/pprof/heap

A web page interface is provided by http/pprof at http://localhost:6060/debug/pprof/.

Fuzzing

Fuzz tests are run with go-fuzz. Follow the instructions on the go-fuzz page to install it.

Fuzz tests are written for the following packages:

base58

To fuzz the cipher/base58 package,

make fuzz-base58

encoder

To fuzz the cipher/encoder package,

make fuzz-encoder

Dependencies

Rules

Dependencies must not require cgo. This means dependencies cannot be wrappers around C libraries. Requiring cgo breaks cross compilation and interferes with repeatable (deterministic) builds.

Critical cryptographic dependencies used by code in package cipher are archived inside the cipher folder, rather than in the vendor folder. This prevents a user of the cipher package from accidentally using a different version of the cipher dependencies than were developed, which could have catastrophic but hidden problems.

Management

The HTTP interface for obtaining more profiling data or obtaining data while running can be enabled with -http-prof. The HTTP profiling interface can be controlled with -http-prof-host and listens on localhost:6060 by default.

See https://golang.org/pkg/net/http/pprof/ for guidance on using the HTTP profiler.

Some useful examples include:

$ go tool pprof http://localhost:6060/debug/pprof/profile?seconds=10
$ go tool pprof http://localhost:6060/debug/pprof/heap

A web page interface is provided by http/pprof at http://localhost:6060/debug/pprof/.

Fuzzing

Fuzz tests are run with go-fuzz. Follow the instructions on the go-fuzz page to install it.

Fuzz tests are written for the following packages:

base58

To fuzz the cipher/base58 package,

$ make fuzz-base58

encoder

To fuzz the cipher/encoder package,

$ make fuzz-encoder

Dependencies

Rules

Dependencies must not require cgo. This means dependencies cannot be wrappers around C libraries. Requiring cgo breaks cross compilation and interferes with repeatable (deterministic) builds.

Critical cryptographic dependencies used by code in package cipher are archived inside the cipher folder, rather than in the vendor folder. This prevents a user of the cipher package from accidentally using a different version of the cipher dependencies than were developed, which could have catastrophic but hidden problems.

Management

Dependencies are managed with dep.

To install dep for development:

go get -u github.com/golang/dep/cmd/dep
$ go get -u github.com/golang/dep/cmd/dep

dep vendors all dependencies into the repo.

If you change the dependencies, you should update them as needed with dep ensure.

Use dep help for instructions on vendoring a specific version of a dependency, or updating them.

When updating or initializing, dep will find the latest version of a dependency that will compile.

Examples:

Initialize all dependencies:

$ dep init

Update all dependencies:

$ dep ensure -update -v

Add a single dependency (latest version):

$ dep ensure github.com/foo/bar

Add a single dependency (more specific version), or downgrade an existing dependency:

$ dep ensure github.com/foo/bar@tag

Configuration Modes

There are 4 configuration modes in which you can run a mdl node:

  • Development Desktop Daemon
  • Server Daemon
  • Electron Desktop Client
  • Standalone Desktop Client

Development Desktop Client Mode

This mode is configured via run-client.sh

$ ./run-client.sh

Server Daemon Mode

The default settings for a mdl node are chosen for Server Daemon, which is typically run from source. This mode is usually preferred to be run with security options, though -disable-csrf is normal for server daemon mode, it is left enabled by default.

$ ./run-daemon.sh

To disable CSRF:

$ ./run-daemon.sh -disable-csrf

Electron Desktop Client Mode

This mode configures itself via electron-main.js

Standalone Desktop Client Mode

This mode is configured by compiling with STANDALONE_CLIENT build tag. The configuration is handled in cmd/mdl/mdl.go

Wallet GUI Development

The compiled wallet source should be checked in to the repo, so that others do not need to install node to run the software.

Instructions for doing this:

Wallet GUI Development README

Translations

You can find information about how to work with translation files in the Translations README.

Releases

Update the version

  1. If the master branch has commits that are not in develop (e.g. due to a hotfix applied to master), merge master into develop
  2. Make sure the translations are up to date. See the i18n README for instructions on how to update translations and how to check if they are up to date.
  3. Compile the src/gui/static/dist/ to make sure that it is up to date (see Wallet GUI Development README)
  4. Update version strings to the new version in the following files: electron/package-lock.json, electron/package.json, electron/mdl/current-mdl.json, src/cli/cli.go, src/gui/static/src/current-mdl.json, src/cli/integration/testdata/status*.golden, template/coin.template, README.md files .
  5. If changes require a new database verification on the next upgrade, update src/mdl/mdl.go's DBVerifyCheckpointVersion value
  6. Update CHANGELOG.md: move the "unreleased" changes to the version and add the date
  7. Update files in https://github.com/mdl/repo-info/tree/master/repos/mdl/remote for images MDLlife/MDL, MDLlife/MDLdev-cli, and MDLlife/MDLdev-vscode, adding a new file for the new version and adjusting any configuration text that may have changed
  8. Merge these changes to develop
  9. Follow the steps in pre-release testing
  10. Make a PR merging develop into master
  11. Review the PR and merge it
  12. Tag the master branch with the version number. Version tags start with v, e.g. v0.20.0. Sign the tag. If you have your GPG key in github, creating a release on the Github website will automatically tag the release. It can be tagged from the command line with git tag -as v0.20.0 $COMMIT_ID, but Github will not recognize it as a "release".
  13. Make sure that the client runs properly from the master branch
  14. Release builds are created and uploaded by travis. To do it manually, checkout the master branch and follow the create release builds instructions.

If there are problems discovered after merging to master, start over, and increment the 3rd version number. For example, v0.20.0 becomes v0.20.1, for minor fixes.

Pre-release testing

Performs these actions before releasing:

  • make check
  • make integration-test-live
  • make integration-test-live-disable-networking (requires node run with -disable-networking)
  • make integration-test-live-disable-csrf (requires node run with -disable-csrf)
  • make intergration-test-live-wallet (see live integration tests) both with an unencrypted and encrypted wallet
  • go run cmd/cli/cli.go checkdb against a fully synced database
  • go run cmd/cli/cli.go checkDBDecoding against a fully synced database
  • On all OSes, make sure that the client runs properly from the command line (./run-client.sh and ./run-daemon.sh)
  • Build the releases and make sure that the Electron client runs properly on Windows, Linux and macOS.
    • Use a clean data directory with no wallets or database to sync from scratch and verify the wallet setup wizard.
    • Load a test wallet with nonzero balance from seed to confirm wallet loading works
    • Send coins to another wallet to confirm spending works
    • Restart the client, confirm that it reloads properly
  • For both the Android and iOS mobile wallets, configure the node url to be https://staging.node.mdl.net and test all operations to ensure it will work with the new node version.

Creating release builds

Create Release builds.

Release signing

Releases are signed with this PGP key:

0x5801631BD27C7874

The fingerprint for this key is:

pub   ed25519 2017-09-01 [SC] [expires: 2023-03-18]
      10A7 22B7 6F2F FE7B D238  0222 5801 631B D27C 7874
uid                      GZ-C MDL <token@protonmail.com>
sub   cv25519 2017-09-01 [E] [expires: 2023-03-18]

Keybase.io account: https://keybase.io/gzc

Follow the Tor Project's instructions for verifying signatures.

If you can't or don't want to import the keys from a keyserver, the signing key is available in the repo: gz-c.asc.

Releases and their signatures can be found on the releases page.

Instructions for generating a PGP key, publishing it, signing the tags and binaries: https://gist.github.com/gz-c/de3f9c43343b2f1a27c640fe529b067c

Responsible Disclosure

Security flaws in mdl source or infrastructure can be sent to security@mdl.net. Bounties are available for accepted critical bug reports.

PGP Key for signing:

-----BEGIN PGP PUBLIC KEY BLOCK-----

mDMEWaj46RYJKwYBBAHaRw8BAQdApB44Kgde4Kiax3M9Ta+QbzKQQPoUHYP51fhN
1XTSbRi0I0daLUMgU0tZQ09JTiA8dG9rZW5AcHJvdG9ubWFpbC5jb20+iJYEExYK
AD4CGwMFCwkIBwIGFQgJCgsCBBYCAwECHgECF4AWIQQQpyK3by/+e9I4AiJYAWMb
0nx4dAUCWq/TNwUJCmzbzgAKCRBYAWMb0nx4dKzqAP4tKJIk1vV2bO60nYdEuFB8
FAgb5ITlkj9PyoXcunETVAEAhigo4miyE/nmE9JT3Q/ZAB40YXS6w3hWSl3YOF1P
VQq4OARZqPjpEgorBgEEAZdVAQUBAQdAa8NkEMxo0dr2x9PlNjTZ6/gGwhaf5OEG
t2sLnPtYxlcDAQgHiH4EGBYKACYCGwwWIQQQpyK3by/+e9I4AiJYAWMb0nx4dAUC
Wq/TTQUJCmzb5AAKCRBYAWMb0nx4dFPAAQD7otGsKbV70UopH+Xdq0CDTzWRbaGw
FAoZLIZRcFv8zwD/Z3i9NjKJ8+LS5oc8rn8yNx8xRS+8iXKQq55bDmz7Igw=
=5fwW
-----END PGP PUBLIC KEY BLOCK-----

Key ID: 0x5801631BD27C7874

The fingerprint for this key is:

pub   ed25519 2017-09-01 [SC] [expires: 2023-03-18]
      10A7 22B7 6F2F FE7B D238  0222 5801 631B D27C 7874
uid                      GZ-C MDL <token@protonmail.com>
sub   cv25519 2017-09-01 [E] [expires: 2023-03-18]

Keybase.io account: https://keybase.io/gzc

You can’t perform that action at this time.