Built with :

• pnpm
• Vite
• VueJS
• Vuetify
• Vuex
• Cypress

We plan to refactor a lot of things in the next release. (Vue3 / Vite / Vuetify 3 / Pinia etc.)

This project contains the sources files for the CasperHolders website.

The CasperHolders Software doesn't make any external request to any services.

Except to the Casper Network itself.

The CasperHolders Software doesn't store/share any personal data with anybody.

The software doesn't read your private key, and your private key is not saved/shared with anybody.

The software doesn't read your smart contract, and your smart contract is not saved/shared with anybody.

If you don't have pnpm you can use this documentation : https://pnpm.io/installation

pnpm install
pnpm dev

In order to run correctly the tests locally create a file name .env.local with the following content :

VITE_APP_FAKE_KEY="<TestnetPrivateKeyWithoutPem>"
VITE_APP_FAKE_VALIDATOR_KEY="<TestnetValidatorPrivateKeyWithoutPem>"
VITE_APP_FAKE_MULTISIG_KEY="<TestnetMultiSigPrivateKeyWithoutPem>"
VITE_APP_FAKE_SECOND_MULTISIG_KEY="<TestnetSecondMultisigPrivateKeyWithoutPem>"
VITE_APP_E2E=true

The first env variable will enable you to test all users interactions (Transfer / Stake / Unstake)
The second env variable will enable you to test all validators operations (Add & Withdraw bid)
The third env variable will be a main test multisig account. The fourth env variable will be an authorized key for the multisig account. The last one will tell the app to run in E2E mode and will bypass the casper signer to use a local signer with the fake keys provided.
Check the globalPlugin.js to see how it works.
Only the positive path for sending smart contract is not tested. See issue #10

pnpm vite --port 8080
pnpm test:e2e

Will use the .env.testnet file

pnpm build-testnet

Will use the .env.testnet file

pnpm build-mainnet

Use the correct value for the mode argument to build either for testnet or mainnet .env file

docker build --build-arg mode=(testnet|mainnet) . 

Use the correct folder for either testnet or mainnet config.

kubectl apply -f kubernetes/(testnet|mainnet)/

The CasperHolders application(s) contains actually 4 main parts :

Contains all the UI for the CasperHolders website (This repo)

The website interact directly with a Casper Node that's why we don't need a proper api.

The connection to a Casper node is done directly with a nginx reverse proxy.

The nginx reverse proxy configuration is not open source as this simple to do for any sysadmin and is part of the commercial* part of the website.

Contains almost all the CasperHolders logic. Link

Parse the whole blockchain into a database.

This is used to retrieve users operations and calculate the APY faster on the API. Link

Link

Only contains 5 endpoints to generate and consume prometheus metrics from operations that are done on the CasperHolders Website and also retrieve validator metadata and the APY on the network.

This API is useless if you don't need / want metrics.

The frontend can work flawlessly without the API.

It will not impact any feature (Except the metrics graph on the front page) on the website.

You may get some errors in the javascript console by not providing the API url.

Maybe in the future this API will contain more features.

(* Every component hosted on casperholders.io is Open Source and every component hosted on casperholders.com is Closed Source)