A Golang implementation of Paloma Chain, a decentralized, automation network for smart contracts
deployed in the Cosmos, EVM, Solana, and Polkadot networks.
For Crosschain Software engineers that want simultaneous control of mulitiple smart contracts, on any blockchain, Paloma is decentralized and consensus-driven message delivery, fast state awareness, low cost state computation, and powerful attestation system that enables scaleable, crosschain, smart contract execution with any data source.
Table of Contents
Talk to us
We have active, helpful communities on Twitter and Telegram.
Releases
See Release procedure for more information about the release model.
Active Networks
Mainnet
N/A
Testnet Setup Instructions
To get the latest palomad
binary:
wget -O - https://github.com/palomachain/paloma/releases/download/v0.2.4-prealpha/paloma_0.2.4-prealpha_Linux_x86_64.tar.gz | \
sudo tar -C /usr/local/bin -xvzf - palomad
sudo chmod +x /usr/local/bin/palomad
# Required until we figure out cgo
sudo wget -P /usr/lib https://github.com/CosmWasm/wasmvm/raw/main/api/libwasmvm.x86_64.so
Connecting to an existing testnet.
Download and install the latest release of palomad.
Initialize our configuration. This will populate a ~/.paloma/
directory.
MONIKER="$(hostname)"
palomad init "$MONIKER"
Copy the configs of the testnet we wish to connect to
wget -O ~/.paloma/config/genesis.json https://raw.githubusercontent.com/palomachain/testnet/master/paloma-testnet-5/genesis.json
wget -O ~/.paloma/config/addrbook.json https://raw.githubusercontent.com/palomachain/testnet/master/paloma-testnet-5/addrbook.json
Next you can generate a new set of keys to the new machine, or reuse an existing key.
VALIDATOR=<choose a name>
palomad keys add "$VALIDATOR"
# Or if you have a mnemonic already, we can recover the keys with:
palomad keys add "$VALIDATOR" --recover
Get some funds!
ADDRESS="$(palomad keys show "$VALIDATOR" -a)"
JSON=$(jq -n --arg addr "$ADDRESS" '{"denom":"ugrain","address":$addr}') && curl -X POST --header "Content-Type: application/json" --data "$JSON" https://backend.faucet.palomaswap.com/claim
We can verify the new funds have been deposited.
palomad query bank balances --node tcp://testnet.palomaswap.com:26657 "$ADDRESS"
Stake your funds and create our validator.
CHAIN_ID="paloma-testnet-5"
DEFAULT_GAS_AMOUNT="10000000"
VALIDATOR_STAKE_AMOUNT=100000000000ugrain
PUBKEY="$(palomad tendermint show-validator)"
palomad tx staking create-validator \
--fees 10000000000ugrain \
--from="$VALIDATOR" \
--amount="$VALIDATOR_STAKE_AMOUNT" \
--pubkey="$PUBKEY" \
--moniker="$MONIKER" \
--chain-id="$CHAIN_ID" \
--commission-rate="0.1" \
--commission-max-rate="0.2" \
--commission-max-change-rate="0.05" \
--min-self-delegation="100" \
--gas=$DEFAULT_GAS_AMOUNT \
--yes \
-b block
Start it!
palomad start
Running with systemd
First configure the service:
cat << EOT > /etc/systemd/system/palomad.service
[Unit]
Description=Paloma Blockchain
After=network.target
ConditionPathExists=/usr/local/bin/palomad
[Service]
Type=simple
LimitNOFILE=65535
Restart=always
RestartSec=5
WorkingDirectory=~
ExecStartPre=
ExecStart=/usr/local/bin/palomad start
ExecReload=
[Install]
WantedBy=multi-user.target
EOT
Then reload systemd configurations and start the service!
systemctl daemon-reload
service palomad start
# Check that it started successfully.
service palomad status
Uploading a local contract
CONTRACT=<contract.wasm>
VALIDATOR="$(palomad keys list --list-names | head -n1)"
palomad tx wasm store "$CONTRACT" --from "$VALIDATOR" --broadcast-mode block -y --gas auto --fees 3000000000ugrain
Setting up a new private testnet
Download and install the latest release of palomad.
Install jq
, used by the setup script.
apt install jq
Set up the chain validator.
CHAIN_ID=paloma-testnet-5 \
MNEMONIC="$(cat secrets.mn)"
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/palomachain/paloma/master/scripts/setup-volume-testnet.sh)"
We should now see an error free execution steadily increasing chain depth.
palomad start
Others wishing to connect to the new testnet will need your .paloma/config/genesis.json
file,
as well as the main peer designation. We can get the main peer designation with jq
:
jq -r '.body.memo' ~/.paloma/config/gentx/gentx-*.json