The Crypt

Live Deployemnt

The state of The Crypt as of its last mainnet deployment is in the prod branch.

main branch has since added the Seeker Soul minter chapter, which never made it to mainnet.

main branch also contains the latest user docs whoich did not make it prod.

Local development environment

Git LFS:

Please ensure you have git lfs set up on your machine, you will need to download the files and then run the git lfs install command.

https://git-lfs.github.com/

The Crypt is made up of a number of services. The main client is the "frontend", the API server is the "relay" and an EVM compatible chain is required for contract interactions are the main components.

You will need to install nvm and npm to get started

https://github.com/nvm-sh/nvm#install--update-script (Make sure to read their readme)

If you are running this for the first time, please go into the loot-dungeon/frontend folder and run the following command:

npm install

To provision the services locally for local development run:

docker-compose --profile=dev up --build

The first build will take a while, but it should be quick after that.

The following services will be provisioned:

• ethereum (localhost:8545
• relay (localhost:3080)
• frontend (localhost:3005)
• devtool (localhost:3000)
• relicassets (localhost:8080)

Configuring metamask for local dev

You will need to add a new network to your browser wallet. The details to add are:

Name    : localhost (or whatever you want)
RPC     : http://localhost:8545
ChainID : 31337

You can then import one or more of the following test accounts for interacting:

Deployer account

The deployer account is used by hardhat to deploy the contracts, and can execute the owner-only functions on contracts.

0xD173aeD60711bDF4AE1bDbA6ec59aACd0ecBb028
6335c92c05660f35b36148bbfb2105a68dd40275ebf16eff9524d487fb5d57a8

Relay account

The relay account is used by the relay for signing meta-transactions, and can execute relay-only contract functions.

0xDeee4887A6f90c1F08Be2151A3aa23D05bA4C545
095a37ef5b5d87db7fe50551725cb64804c8c554868d3d729c0dd17f0e664c87

Test account 1

Test account 1 is available for use to simulate users.

0x4208a6518500E980ED44Da94ea31b85c85ec4568
8451fe83595a88521cac265c1356568ab84c2b5d81654f36ea309be28ded5a0d

Test account 2

Test account 2 is available for use to simulate users.

0x9Be7ecc6643AD6a9621E96b2CFa37a48AfFfbBF3
c23d69dca6cf8207c53e350cf1ce19807c0a4aee4bee0417fdae8bb0341f482e

More accounts

You can find more account details dumped in the output when the evm node starts up.

Useful commands for local dev

If you ever need to rebuild the application images, add --build flag:

docker-compose --profile=dev up --build

To only run the local EVM chain (listening on port 8545), omit the profile:

docker-compose up

Destroy local chain state ready to deploy with a clean slate:

docker-compose down -v

Hop inside a running chain container to poke around use docker exec:

docker exec -it loot-dungeon_hardhat_1 /bin/sh

Destroy all your docker images to free up space:

docker rmi -f $(docker images -q)