Penumbra is a fully shielded zone for the Cosmos ecosystem, allowing anyone to securely transact, stake, swap, or marketmake without broadcasting their personal information to the world.
The primary communication hub is our Discord; click the link to join the discussion there.
The (evolving) protocol spec is rendered at protocol.penumbra.zone.
The (evolving) API documentation is rendered at rustdoc.penumbra.zone.
To participate in our test network, keep reading below.
For instructions on how to set up a node, jump down and read on.
Penumbra Labs runs a test network for the latest version of the Penumbra protocol, and we would be delighted for you to try it out! Per our development plan, we'll be launching (and crashing) lots of testnets, and users should expect data loss at this early stage. Keep in mind that the tokens on the test network have no monetary value whatsoever, and we'll be shutting down the testnet when we reach our next milestone (or before). If (which is to say, when) you encounter bugs or wish for features to exist, we'd love for you to reach out to us on our Discord server.
At the moment the testnet is a single node, and running testnet nodes won't be possible until our next milestone (MVP2), implementing staking and delegation.
To get started with the Penumbra test network, you will first need to download and build the
Penumbra command line light wallet, pcli.
This requires that you install a recent stable version
of the Rust compiler, installation instructions for which you can find
here. Don't forget to reload your shell so that
cargo is available in your $PATH!
On Linux: you may need to install some additional packages in order to build pcli,
depending on your distribution. For a bare-bones Ubuntu installation, you can run:
sudo apt-get install build-essential pkg-config libssl-devOn macOS: you may need to install the command-line developer tools if you have never done so:
xcode-select --installOnce you have installed the above tools, you can clone the repository:
git clone https://github.com/penumbra-zone/penumbraTo build the version of pcli compatible with the current testnet, check out the latest tag for
the current test net:
cd penumbra && git checkout 005-mnemeThen, build the pcli tool using cargo:
cargo build --release --bin pcliBecause you are building a work-in-progress version of the client, you may see compilation warnings, which you can safely ignore.
Hint: When working with pcli, the level of diagnostic information printed is dependent on the RUST_LOG
environment variable. To see progress updates and other logged information while running pcli, we
recommend you set export RUST_LOG=info in your terminal.
On first installation of pcli, you will need to generate a fresh wallet to use with Penumbra. You
should see something like this:
$ cargo run --quiet --release --bin pcli wallet generate
Saving wallet to /home/$USER/.local/share/pcli/penumbra_wallet.json
Saving backup wallet to /home/$USER/.local/share/penumbra-testnet-archive/penumbra-euporie/.../penumbra_wallet.jsonPenumbra's design allows you to create arbitrarily many publicly unlinkable addresses which all
correspond to your own wallet. When you first created your wallet above, pcli created your first
address, labeled Default. When you list your addresses, you should see something like this:
$ cargo run --quiet --release --bin pcli addr list
Index Label Address
0 Default penumbrav0t1...Getting testnet tokens on the Discord in the #testnet-faucet channel
In order to use the testnet, it's first necessary for you to get some testnet tokens. The current
way to do this is to join our Discord and post your address in the #testnet-faucet channel.
We'll send your address some tokens on the testnet for you to send to your friends! :)
Just keep in mind: testnet tokens do not have monetary value, and in order to keep the signal-to-noise ratio high on the server, requests for tokens in other channels will be deleted without response. Please do not DM Penumbra Labs employees asking for testnet tokens; the correct venue is the dedicated channel.
Once you've received your first tokens, you can scan the chain to import them into your local wallet (this may take a few minutes the first time you run it):
cargo run --quiet --release --bin pcli syncIf someone sent you testnet assets, you should be able to see them now by running:
cargo run --quiet --release --bin pcli balanceThis will print a table of assets by balance in each.
Now, for the fun part: sending transactions. If you have someone else's testnet address, you can send them any amount of any asset you have. For example, if I wanted to send 10 penumbra tokens to my friend, I could do that like this (filling in their full address at the end):
cargo run --quiet --release --bin pcli tx send 10penumbra --to penumbrav0t...Notice that asset amounts are typed amounts, specified without a space between the amount (10)
and the asset name (penumbra).
If you have the asset in your wallet to send, then so it shall be done!
Thank you for helping us test the Penumbra network! If you have any feedback, please let us know in
the #testnet-feedback channel on our Discord. We would love to know about bugs, crashes,
confusing error messages, or any of the many other things that inevitably won't quite work yet. Have
fun! :)
The protocol spec is built using mdBook and auto-deployed on
pushes to main. To build it locally:
- Install the requirements:
cargo install mdbook mdbook-katex mdbook-mermaid - To continuously build and serve the documentation:
mdbook serve
This section is for developers, not for running nodes that are part of the public testnet. We won't be ready for multiple testnet nodes until we reach our MVP2 milestone implementing staking and delegation, at which point this will change.
Penumbra has two binaries, the command-line light wallet interface pcli and
the daemon pd. However, the daemon cannot be run alone; it requires both
Tendermint (to handle network communication and drive the consensus state) and
Postgres (to act as a data store).
We use sqlx to interact with the database and do compile-time query checks.
This means that some kinds of development require a local database instance.
For clean checkouts, or changes to the workspace that do not affect the database
queries, running cargo build as usual should work.
However, changes to the database queries or schema require regenerating the
sqlx-data.json file that's checked into git, and this requires a local
Postgres instance and the sqlx command-line tooling.
Install the command-line tooling with:
cargo install sqlx-cli
Running a local postgres instance can be done with:
docker volume create tmp_postgres_data
docker run --name tmp_postgres -e POSTGRES_PASSWORD=postgres -e POSTGRES_USER=postgres -e POSTGRES_DB=penumbra -p 5432:5432 -v tmp_postgres_data:/var/lib/postgresql/data -d postgres
# docker stop tmp_postgres
# docker start tmp_postgres
Managing the database can be done with cargo sqlx:
export DATABASE_URL="postgres://postgres:postgres@localhost:5432/penumbra"
cargo sqlx database create # Creates the database
# cargo sqlx database drop # Drops the database
cargo sqlx migrate run # Updates the database schema
Regenerate the sqlx-data.json file by running the following from inside the pd directory:
cargo sqlx prepare -- --lib
This command checks the queries in the source code against the current database state, so it's important that the database exists and has the current schema (which can be accomplished with the commands above).
Running a local testnet requires creating a genesis.json describing the initial
parameters of the network. This has two parts:
- Tendermint-related data specifying parameters for the consensus engine;
- Penumbra-related data specifying the initial chain state.
First, install Tendermint. Be sure to install v0.35.0, rather
than master.
Next, create the Tendermint config data with
tendermint init validatorThis will create a default genesis file stored in $TMHOME/config (if set, else
~/.tendermint/config) named genesis.json, as well as a validator private key
named priv_validator_key.json.
The Penumbra-related data specifying the initial chain state depends on your local key material, since a testnet with no assets you can control is not particularly useful, so it requires some manual editing.
You'll probably want to generate a new testing wallet with
cargo run --bin pcli -- -w testnet_wallet.json wallet generate
# Example, create whatever addresses you want for testing
cargo run --bin pcli -- -w testnet_wallet.json addr new "Test Address 1"
cargo run --bin pcli -- -w testnet_wallet.json addr new "Test Address 2"
Next, produce a template with
cargo run --bin pd -- create-genesis-template
and copy the output into the genesis.json as the app_state field.
edit it to match the key material you'll be using, which includes:
- changing the validator public keys to match the one Tendermint generated;
- editing the genesis allocations to use your testing addresses, or have other asset types, etc.
You may wish to edit other parts of the testnet config. Example genesis.json
files can be found in the testnets/ directory if you get stuck.
You'll need to create a genesis.json file as described above.
Next, you'll need to set up a Postgres instance. Here is one way:
docker volume create tmp_postgres_data
docker run --name tmp_postgres -e POSTGRES_PASSWORD=postgres -e POSTGRES_USER=postgres -e POSTGRES_DB=penumbra -p 5432:5432 -v tmp_postgres_data:/var/lib/postgresql/data -d postgres
# docker stop tmp_postgres
# docker start tmp_postgresThere are three components to a Penumbra node: the Tendermint instance, the pd
instance, and the Postgres instance.
To create the database, run:
# Edit as appropriate for your Postgres instance
export DATABASE_URL="postgres://postgres:postgres@localhost:5432/penumbra"
cargo sqlx database create
Start the Penumbra instance (you probably want to set RUST_LOG to debug):
cargo run --bin pd start -d "postgres://postgres:postgres@localhost:5432/penumbra"Start the Tendermint node:
tendermint startYou should be running!
To inspect the Postgres state, use:
psql -h localhost -U postgres penumbraIn this database terminal, you can run queries to inspect pd's state.
To stop the node, shut down either pd or tendermint.
Resetting the state requires multiple steps:
- To reset the Tendermint state, use
tendermint unsafe-reset-all. - To reset the Postgres state, use
cargo sqlx database drop. - To reset your wallet state (without deleting keys), use
pcli wallet reset.
You need to do all of these to fully reset the node, and doing only one will result in mysterious errors.
You'll need to create a genesis.json file as described above. This command
will only work if you have loaded genesis state:
docker-compose up --build -dTo load genesis state for a fresh Docker configuration:
NOTE: this will destroy any existing data you have stored in the Docker volumes for pd/postgres/tendermint!
./scripts/docker_compose_freshstart.sh ~/scratch/testnet_build penumbra-thelxinoe testnets/004-thelxinoe/allocations.csv testnets/004-thelxinoe/validators.json 1
# the ~/scratch/testnet_build directory should be the root of the volume mounted
# to the tendermint node containers in docker-compose.yml
#
# the second argument is the name of the testnet chain ID
# the last argument is the # of validators to createThe script will handle generating genesis JSON data (but not editing it).
After running the script, the data directory provided to the script will contain the initial configuration and state of the tendermint nodes.
**You should go in and edit the genesis JSON for node0 (we currently only run one tendermint
node in our testnet: ~/scratch/testnet_build/node0/config/genesis.json)
After configuring the genesis JSON, you can start the testnet:
docker-compose up --build -d
You should have a working setup with all containers running after running the script:
$ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
b7fce1d0ffd9 tendermint/tendermint:latest "docker-entrypoint.s…" 4 minutes ago Up 4 minutes 0.0.0.0:6060->6060/tcp, 0.0.0.0:26656-26657->26656-26657/tcp, 0.0.0.0:27000->26660/tcp tendermint
5a6bd39bb6f7 grafana/grafana:latest "/run.sh" 4 minutes ago Up 4 minutes 0.0.0.0:3000->3000/tcp penumbra-grafana-1
b8f599963ebc penumbra_pd "pd start --host 0.0…" 4 minutes ago Up 4 minutes 0.0.0.0:26658->26658/tcp penumbra
b4f694a238cb postgres:13.0 "docker-entrypoint.s…" 4 minutes ago Up 4 minutes 0.0.0.0:5432->5432/tcp db
9e82aa33b4ff prom/prometheus:latest "/bin/prometheus --c…" 4 minutes ago Up 4 minutes 0.0.0.0:9090->9090/tcp penumbra-prometheus-1On production, you should use the production Docker Compose configuration, which will use the managed database as well as disable various debug build configs used in dev:
docker-compose -f docker-compose.yml -f docker-compose.prod.yml up -d --buildWhen adding new metrics, please following the Prometheus metrics naming
guidelines. Use plurals for consistency. For the
application prefix part of the name, use node for the Penumbra node.