[

]() ## Preview of Warden Protocol Warden Protocol is a cutting-edge modular L1 blockchain designed for developers to deploy omnichain AI-driven applications. It empowers developers to easily launch secure OApps (Omnichain Applications) that are modularly secure, omnichain interoperable, and chain-abstracted, evolving traditional smart contracts to a new level. **Key Features of Warden Protocol**

1. Modular Security 🔒

- Unlike monolithic systems where a single vulnerability can impact multiple applications, Warden Protocol allows each OApp to define its own security parameters. - This isolation enhances resilience and reduces the risk of widespread vulnerabilities.

2. Omnichain Interoperability 🌐

- Supports seamless interaction across different blockchains, enabling cross-chain transactions, application interactions, and asset exchanges. - This interconnected mesh topology ensures robust and universal connectivity.

3. Chain-Abstraction 🔗

- OApps on Warden Protocol can interact with multiple chains, signing transactions and reading/writing data across different blockchain environments. - This flexibility opens up new use cases and broadens the scope of blockchain applications.

4. Developer-Friendly 👩‍💻

- Allows developers to build OApps using familiar languages and tools. - Provides a high-throughput, low-latency platform with instant finality, reducing development costs and accelerating deployment timelines.

**Advantages of OApps**

1. Secure and Reliable 🛡️

- OApps inherit strong security from the Warden Protocol, leveraging its replicated, permissionless proof-of-stake consensus, fault-tolerant properties, and robust validator set.

2. Scalable and Efficient ⚡

- Developers don’t need to bootstrap new validators, reducing overhead and security budgets. - This makes OApps highly scalable and efficient for high-stakes DeFi applications and more.

3. Innovative and Flexible 🎨

- With modular security, omnichain interoperability, and chain abstraction, OApps offer unprecedented flexibility, enabling developers to stay responsive to new security technologies and user demands.

Warden Protocol is poised to transform the Web3 landscape by providing the infrastructure needed to scale applications securely and efficiently. By unbundling the security stack and offering a modular approach, Warden Protocol is making it easier than ever for developers to create robust, scalable, and innovative blockchain applications.

Website GitHub Twitter Discord Docs

## Available Explorers

___ ## Public Endpoints ```http RPC: {{ RPC }} API: {{ API }} gRPC: {{ GRPC }} peer: {{ ID }}@{{ IP }} ``` ___ ## Prepare #### Update and install packages *This command updates and installs various packages needed for development and system administration. It includes tools for networking, archiving, compiling, version control, and other essential utilities.* ``` sudo apt update && sudo apt upgrade -y && \ sudo apt install curl tar wget clang pkg-config libssl-dev libleveldb-dev jq build-essential bsdmainutils git make ncdu htop screen unzip bc fail2ban htop lz4 -y ```

Details 📚

- **sudo apt update** Updates the package index files from their sources. It retrieves the latest information about available software packages and their dependencies. - **sudo apt upgrade -y** Upgrades all the installed packages on your system to their latest versions. The -y flag automatically confirms the upgrade process without prompting the user for confirmation. - **sudo apt install** Installs one or more software packages. The list of packages to be installed follows this command. - **curl** A command-line tool used to transfer data from or to a server using various protocols (HTTP, HTTPS, FTP, etc.). - **tar** A utility for creating, maintaining, modifying, and extracting files from a tar archive. - **wget** A command-line utility used for downloading files from the web. - **clang** A compiler for the C, C++, and Objective-C programming languages. It is designed to be a replacement for the GCC compiler. - **pkg-config** A helper tool used when compiling applications and libraries. It helps in determining the correct compiler and linker flags that should be used for the compilation. - **libssl-dev** Provides development files for the OpenSSL library, which implements secure communication protocols over the network. - **libleveldb-dev** Development files for the LevelDB library, a fast key-value storage library written at Google that provides an ordered mapping from string keys to string values. - **jq** A lightweight and flexible command-line JSON processor, used for parsing and manipulating JSON data. - **build-essential** A package that includes a list of essential packages for building software, including the GCC compiler, make, and other utilities. - **bsdmainutils** A collection of tools traditionally found in BSD systems, including useful utilities like calendar and col. - **git** A distributed version control system used for tracking changes in source code during software development. - **make** A build automation tool that automatically builds executable programs and libraries from source code by reading files called Makefiles. - **ncdu** A disk usage analyzer with an ncurses interface, useful for finding large files and directories on a filesystem. - **htop** An interactive process viewer for Unix systems, similar to top, but provides a more user-friendly interface. - **screen** A terminal multiplexer that allows you to use multiple terminal sessions within a single window and detach/reattach sessions. - **unzip** A utility for extracting compressed files from .zip archives. - **bc** An arbitrary precision calculator language, which supports interactive execution of statements. - **fail2ban** An intrusion prevention software framework that protects computer servers from brute-force attacks by monitoring log files and banning IPs that show malicious signs. - **lz4** A fast compression algorithm and tool that compresses and decompresses data with very high speed. - **htop** (repeated in the list) An interactive process viewer for Unix systems, similar to top, but provides a more user-friendly interface.

___ #### Installing Go v1.22.1 *This command downloads and installs {{ BIN_GO_VERSION }}. It sets up the Go environment by updating the PATH variable and verifies the installation.* ``` cd $HOME && \ wget "https://golang.org/dl/go{{ GO_VERSION::1.22.1 }}.linux-amd64.tar.gz" && \ sudo rm -rf /usr/local/go && \ sudo tar -C /usr/local -xzf "go{{ GO_VERSION }}.linux-amd64.tar.gz" && \ rm "go{{ GO_VERSION }}.linux-amd64.tar.gz" && \ echo "export PATH=$PATH:/usr/local/go/bin:$HOME/go/bin" >> $HOME/.bash_profile && \ source $HOME/.bash_profile && \ go version ``` ___ ## Installing {{ CHAIN_NAME }} binary *This command installs the {{ CHAIN_NAME }} binary, offering two methods: building from source or downloading a prebuilt binary.*

```shell
git clone {{ GIT_REPO }} {{ CHAIN_NAME }} 
cd {{ CHAIN_NAME }} 
git checkout v{{ VERSION }} 
make install
{{ BIN }} version --long | grep -e version -e commit
# version: {{ VERSION }}
# commit: {{ COMMIT }}```

```bash
wget {{ BIN_URL }}
chmod +x {{ BIN }}
mkdir -p $HOME/go/bin
mv {{ BIN }} $HOME/go/bin
{{ BIN }} version --long | grep -e version -e commit
# version: {{ VERSION }}
# commit: {{ COMMIT }}```

___ #### Initialization *This command initializes the node with a given moniker (node name) and chain ID, then sets the client configuration to use the specified chain ID and a test keyring backend.* ``` {{ BIN }} init {{ MONIKER::NODE_NAME }} --chain-id {{ CHAIN_ID }} && \ {{ BIN }} config set client chain-id {{ CHAIN_ID }} && \ {{ BIN }} config set client keyring-backend test ``` ___ #### Download genesis *The genesis file is essential for starting the blockchain. It contains the initial state of the blockchain and is typically downloaded from the official hosting site or a trusted mirror. Our genesis file is uploaded from a fully-synced node, but it is always recommended to verify its contents.* ``` wget {{ GENESIS_URL }} -O $HOME/{{ NODE_HOME }}/config/genesis.json ``` ___ #### Download addrbook *An addrbook.json file helps your node connect to other peers in the network. If you experience peering issues, using a good addrbook.json can solve the problem.* ``` wget {{ ADDRBOOK_URL }} -O $HOME/{{ NODE_HOME }}/config/addrbook.json ``` ___ ## Configuration #### Change ports (Optional) *This script changes the ports used by various services in the config.toml and app.toml files based on your node number. It also sets an environment variable for the node's local address. This step is optional and can help avoid port conflicts.* ``` . <(wget -qO- https://raw.githubusercontent.com/romanv1812/NodeTools/main/helpfulScripts/change_ports.sh) {{ NODE-NUMBER::1 }} {{ NODE_HOME }} {{ BIN }} config set client node $NODE ``` ___ #### Web Services (Optional) *This optional step allows you to configure web services for your node. You can open the RPC address, enable or disable API, gRPC, gRPC-Web, and JSON-RPC services, and set the minimum gas prices.* ``` sed -i.bak -e "/^\[rpc\]/,/^laddr =/s|laddr = \"tcp://127\.0\.0\.1:|laddr = \"tcp://{{ RPC-OPEN::127.0.0.1 }}:|" $HOME/{{ NODE_HOME }}/config/config.toml sed -i.bak -e "/^\[api\]/,/^enable/s|^enable *=.*|enable = '{{ API-ENABLE::false }}'|" $HOME/{{ NODE_HOME }}/config/app.toml sed -i.bak -e "/^\[grpc\]/,/^enable/s|^enable *=.*|enable = '{{ gRPC-ENABLE::false }}'|" $HOME/{{ NODE_HOME }}/config/app.toml sed -i.bak -e "/^\[grpc-web\]/,/^enable/s|^enable *=.*|enable = '{{ gRPC-WEB-ENABLE::false }}'|" $HOME/{{ NODE_HOME }}/config/app.toml sed -i.bak -e "/^\[json-rpc\]/,/^enable/s|^enable *=.*|enable = '{{ JSON-RPC-ENABLE::false }}'|" $HOME/{{ NODE_HOME }}/config/app.toml sed -i.bak -e "s|^minimum-gas-prices *=.*|minimum-gas-prices = '{{ GAS-PRICE::0.001 }}{{ TOKEN }}'|" $HOME/{{ NODE_HOME }}/config/app.toml ``` ___ #### Pruning (Optional) *This optional step allows you to configure pruning settings for your node. You can enable or disable the indexer, set custom pruning options, and define intervals for pruning and snapshots to optimize disk space usage.* ``` sed -i.bak -e "s/^indexer *=.*/indexer = \"{{ INDEXER-ENABLE::null }}\"/" $HOME/{{ NODE_HOME }}/config/config.toml sed -i.bak -e "s/^pruning *=.*/pruning = \"{{ PRUNING::custom }}\"/" $HOME/{{ NODE_HOME }}/config/app.toml sed -i.bak -e "s/^pruning-keep-recent *=.*/pruning-keep-recent = \"{{ PRUNING-KEEP-RECENT::100 }}\"/" $HOME/{{ NODE_HOME }}/config/app.toml sed -i.bak -e "s/^pruning-keep-every *=.*/pruning-keep-every = \"{{ PRUNING-KEEP-EVERY::0 }}\"/" $HOME/{{ NODE_HOME }}/config/app.toml sed -i.bak -e "s/^pruning-interval *=.*/pruning-interval = \"{{ PRUNING-INTERVAL::17 }}\"/" $HOME/{{ NODE_HOME }}/config/app.toml sed -i.bak -e "s/^snapshot-interval *=.*/snapshot-interval = \"{{ SNAPSHOT-INTERVAL::100 }}\"/" $HOME/{{ NODE_HOME }}/config/app.toml ``` ___ #### Create a service file *Create a service file to manage the node with systemd.* ``` sudo tee /etc/systemd/system/{{ BIN }}.service > /dev/null <

```bash
sudo systemctl stop {{ BIN }}
cp $HOME/{{ NODE_HOME }}/data/priv_validator_state.json $HOME/{{ NODE_HOME }}/priv_validator_state.json.backup
rm -rf $HOME/{{ NODE_HOME }}//data 
curl {{ SNAPSHOT_URL }} | lz4 -dc - | tar -xf - -C $HOME/{{ NODE_HOME }}
mv $HOME/{{ NODE_HOME }}/priv_validator_state.json.backup $HOME/{{ NODE_HOME }}/data/priv_validator_state.json
sudo systemctl restart {{ BIN }} && sudo journalctl -u {{ BIN }} -f```

```
SNAP_RPC="{{ RPC }}:443"
sudo systemctl stop {{ BIN }}

cp $HOME/{{ NODE_HOME }}/data/priv_validator_state.json $HOME/{{ NODE_HOME }}/priv_validator_state.json.backup
{{ BIN }} tendermint unsafe-reset-all --home $HOME/{{ NODE_HOME }} --keep-addr-book 

peers="{{ ID }}@{{ IP }}"
sed -i.bak -e "s/^persistent_peers *=.*/persistent_peers = \"$peers\"/" $HOME/{{ NODE_HOME }}/config/config.toml 

LATEST_HEIGHT=$(curl -s $SNAP_RPC/block | jq -r .result.block.header.height);
BLOCK_HEIGHT=$((LATEST_HEIGHT - 1000));
TRUST_HASH=$(curl -s "$SNAP_RPC/block?height=$BLOCK_HEIGHT" | jq -r .result.block_id.hash) 

echo $LATEST_HEIGHT $BLOCK_HEIGHT $TRUST_HASH && sleep 2 

sed -i.bak -E "s|^(enable[[:space:]]+=[[:space:]]+).*$|\1true| ;
s|^(rpc_servers[[:space:]]+=[[:space:]]+).*$|\1\"$SNAP_RPC,$SNAP_RPC\"| ;
s|^(trust_height[[:space:]]+=[[:space:]]+).*$|\1$BLOCK_HEIGHT| ;
s|^(trust_hash[[:space:]]+=[[:space:]]+).*$|\1\"$TRUST_HASH\"| ;
s|^(seeds[[:space:]]+=[[:space:]]+).*$|\1\"\"|" $HOME/{{ NODE_HOME }}/config/config.toml

mv $HOME/{{ NODE_HOME }}/priv_validator_state.json.backup $HOME/{{ NODE_HOME }}/data/priv_validator_state.json

sudo systemctl restart {{ BIN }} && sudo journalctl -u {{ BIN }} -f```

___ ## Upgrade Node ``` cd {{ CHAIN_NAME }} git pull git checkout tags/{{ APP_VERSION::v0.1.0}} -b {{ APP_VERSION }} make install sudo systemctl restart {{ BIN }} && sudo journalctl -u {{ BIN }} -f ``` ___ ## Delete Node ``` sudo systemctl stop {{ BIN }} sudo systemctl disable {{ BIN }} sudo rm -rf /etc/systemd/system/{{ BIN }}.service sudo rm $(which {{ BIN }}) sudo rm -rf $HOME/{{ NODE_HOME }} ``` ## Key management

```
# This command generates a new wallet with a unique keypair.
# Use this to create a secure, brand-new wallet for transactions.
{{ BIN }} keys add {{ WALLET::wallet }}```

```
# This command restores a wallet using a mnemonic phrase.
# Ideal for accessing a previously created wallet on a new device.
{{ BIN }} keys add {{ WALLET::wallet }} --recover
```

```
# This command removes a wallet from the node's key management system.
# Ensure you have backed up the key before deleting, as this action is irreversible.
{{ BIN }} keys delete {{ WALLET::wallet }}
```

```
# This command lists all the wallets managed by the node.
# Useful for getting an overview of all available wallets and their statuses.
{{ BIN }} keys list
```

```
# This command exports the wallet's private key to a file.
# Use this to backup your wallet's key securely.
{{ BIN }} keys export {{ WALLET::wallet }} > {{ WALLET }}.backup
```

```
# This command imports a wallet key from a backup file.
# Essential for restoring wallet access from a previously exported key file.
{{ BIN }} keys import {{ WALLET::wallet }}  {{ WALLET }}.backup```

___ ## Validator management

```
cat < $HOME/validator.json
{
    "pubkey": "{{ BIN }} tendermint show-validator",
    "amount": "1000000{{ TOKEN }}",
    "moniker": "{{ MONIKER::VALIDATOR_NAME }}",
    "identity": "{{ IDENTITY:: }}",
    "website": "{{ WEBSITE:: }}",
    "security": "{{ EMAIL:: }}",
    "details": "{{ DETAILS:: }}",
    "commission-rate": "{{ COMISSION-RATE::0.1 }}",
    "commission-max-rate": "{{ MAX-RATE::0.2 }}",
    "commission-max-change-rate": "{{ CHANGE-RATE::0.01 }}",
    "min-self-delegation": "1"
}
EOF
{{ BIN }}  tx staking create-validator validator.json \
    --from {{ WALLET::wallet }} \
    --chain-id {{ CHAIN_ID }} \
	--gas auto --fees 32000000000000{{ TOKEN }}  -y```

```
{{ BIN }} tx staking edit-validator \
--moniker "{{ MONIKER::VALIDATOR_NAME }}" \
--identity "{{ IDENTITY:: }}" \
--website "{{ WEBSITE:: }}" \
--details "{{ DETAILS:: }}" \
--from {{ WALLET::wallet }} \
--commission-rate {{ COMISSION-RATE::0.1 }} \
--chain-id {{ CHAIN_ID }} \
--gas auto \
--fees 32000000000000{{ TOKEN }} \
-y```

```
# Retrieves comprehensive information regarding the validator.
# This command is utilized to fetch details about the current validator, including its address, public key, and associated data.
{{ BIN }} q staking validator $({{ BIN }} keys show {{ WALLET::wallet }} --bech val -a) 
```

```
# Fetches information about the validator's signing behavior.
# This command extracts details concerning the signing behavior associated with the current validator, including missed block counts and other security-related parameters.
{{ BIN }} q slashing signing-info $({{ BIN }} tendermint show-validator) 
```

```
# Retrieves parameters pertinent to slashing.
# This command extracts the current parameters governing slashing, such as threshold values for penalties and punishment durations.
{{ BIN }} q slashing params 
```

```
# Validates the status of your key.
# This command compares the public key of your validator with the key associated with your node to ensure that the key is in an up-to-date state.
[[ $({{ BIN }} q staking validator $({{ BIN }} keys show {{ WALLET::wallet }}  --bech val -a) -oj | jq -r .consensus_pubkey.key) == $({{ BIN }} status | jq -r .ValidatorInfo.PubKey.value) ]]
echo -e "Your key status is ok" || echo -e "Your key status is error"
```

```
# Retrieves information about validator penalties.
# This command fetches details about current penalties imposed on the validator, including information about blocks where signatures were missed.
{{ BIN }} q slashing signing-info $({{ BIN }} tendermint show-validator) 
```

```
# Obtains details of the active set of validators.
# This command retrieves information about all validators currently in the active set, their current statuses, and other associated parameters.
{{ BIN }} q staking validators -o json --limit=1000 \
| jq '.validators[] | select(.status=="BOND_STATUS_BONDED")' \
| jq -r '.tokens + " - " + .description.moniker' \
| sort -gr | nl
```

```
# Obtains details of the inactive set of validators.
# This command fetches information about all validators currently in the inactive set, their current statuses, and other associated parameters.
{{ BIN }} q staking validators -o json --limit=1000 \
| jq '.validators[] | select(.status=="BOND_STATUS_UNBONDED")' \
| jq -r '.tokens + " - " + .description.moniker' \
| sort -gr | nl
```

## Onchain

```
# Withdraw all accumulated rewards from your account.
# This command retrieves and withdraws all rewards earned from staking.
{{ BIN }} tx distribution withdraw-all-rewards --from {{ WALLET }} --chain-id {{ CHAIN_ID }}  --gas auto fees 32000000000000{{ TOKEN }} -y
```

```
# Withdraw rewards and commission earned from your validator.
# Use this command to claim both validator rewards and commission earnings.
{{ BIN }} tx distribution withdraw-rewards {{ VALOPER }} --from {{ WALLET }} --commission --chain-id {{ CHAIN_ID }} --gas auto 32000000000000{{ TOKEN }} -y 
```

```
# Check the balance of your account.
# This command displays the current balance of your account.
{{ BIN }} query bank balances {{ WALLET_ADDRESS::$WALLET_ADDRESS }}
```

```
# Delegate tokens from your account to yourself as a validator.
# This command allows you to stake tokens on your own validator node.
{{ BIN }} tx staking delegate $({{ BIN }} keys show {{ WALLET }} --bech val -a) {{ AMOUNT::1000000 }}{{ TOKEN }} --from {{ WALLET }} --chain-id {{ CHAIN_ID }}  --gas auto --fees 32000000000000{{ TOKEN }} -y 
```

```
# Delegate tokens to another validator.
# Use this command to stake tokens on a validator other than yourself.
```

```
# Redelegate tokens from one validator to another.
# This command allows you to switch your stake from one validator to another.
```

```
# Unbond tokens from staking.
# Use this command to initiate the unbonding process for your staked tokens.
```

```
# Transfer funds to another account.
# This command allows you to send tokens to another account on the network.
```