A Golang implementation of Paloma Chain, a decentralized, automation network for smart contracts deployed in the Cosmos, EVM, Solana, and Polkadot networks.
Paloma is the fastest, secure crosschain communications blockchain. For Crosschain Software engineers who want simultaneous control of multiple, cross-chain-deployed, smart contracts, Paloma is decentralized and consensus-driven message delivery. Paloma is fast state awareness, low cost state computation, and a powerful attestation system. Polama blockchain enables scalable, crosschain, smart contract execution with any data source.
We have active, helpful communities on Twitter and Telegram.
- Bengali README
- Chinese README
- Indonesian README
- Japanese README
- Persian README
- Polish README
- Portuguese README
- Romanian README
- Russian README
- Spanish README
- Thai README
- Turkish README
- Ukrainian README
- Vietnamese README
See Release procedure for more information about the release model.
- Testnet
paloma-testnet-16(May 23, 2024) - Mainnet
tumbler(April 22, 2024)
Some have seen errors with GLIBC version differences with the downloaded binaries. This is caused by a difference in the libraries of the host that built the binary and the host running the binary.
If you experience these errors, please pull down the code and build it, rather than downloading the prebuilt binary
The current required version of libwasm is 2.1.3. If you're upgrading from a prior version it is recommended to remove the cache to avoid errors. If you're already have palomad running, you will need to stop it before doing these steps.
wget https://github.com/CosmWasm/wasmvm/releases/download/v2.1.3/libwasmvm.x86_64.so
sudo mv libwasmvm.x86_64.so /usr/lib/
rm -r ~/.paloma/data/wasm/cache
wget -O - https://github.com/palomachain/paloma/releases/download/v2.3.2/paloma_Linux_x86_64.tar.gz | \
sudo tar -C /usr/local/bin -xvzf - palomad
sudo chmod +x /usr/local/bin/palomadgit clone https://github.com/palomachain/paloma.git
cd paloma
git checkout v2.3.2
make build
sudo mv ./build/palomad /usr/local/bin/palomadIf you're upgrading to the most recent version, you will need to stop palomad before copying the new binary into place.
Download and install the latest release of palomad.
Initialize our configuration. This will populate a ~/.paloma/ directory.
MONIKER="$(hostname)"
palomad init "$MONIKER"
#for testnet
CHAIN_ID="paloma-testnet-16"
#for mainnet
CHAIN_ID="tumbler"
Copy the configs of the network we wish to connect to
Testnet:
wget -O ~/.paloma/config/genesis.json https://raw.githubusercontent.com/palomachain/testnet/master/paloma-testnet-16/genesis.json
wget -O ~/.paloma/config/addrbook.json https://raw.githubusercontent.com/palomachain/testnet/master/paloma-testnet-16/addrbook.jsonMainnet:
wget -O ~/.paloma/config/genesis.json https://raw.githubusercontent.com/palomachain/mainnet/master/tumbler/genesis.json
wget -O ~/.paloma/config/addrbook.json https://raw.githubusercontent.com/palomachain/mainnet/master/tumbler/addrbook.jsonNext 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" --recoverHead over to https://faucet.palomaswap.com/ and get some funds!
We can verify the new funds have been deposited.
palomad query bank balances --node "https://testnet.palomaswap.com:443" "$ADDRESS"And start the node!
palomad startIf desired we can stake our funds and create a validator.
MONIKER="$(hostname)"
VALIDATOR="$(palomad keys list --list-names | head -n1)"
STAKE_AMOUNT=1000000ugrain
PUBKEY="$(palomad tendermint show-validator)"
palomad tx staking create-validator \
--fees=1000000ugrain \
--from="$VALIDATOR" \
--amount="$STAKE_AMOUNT" \
--pubkey="$PUBKEY" \
--moniker="$MONIKER" \
--website="https://www.example.com" \
--details="<enter a description>" \
--chain-id=$CHAIN_ID \
--commission-rate="0.1" \
--commission-max-rate="0.2" \
--commission-max-change-rate="0.05" \
--min-self-delegation="100" \
--yes \
--broadcast-mode=blockYou may receive an error account sequence mismatch, you will need to wait until your local paloma
catches up with the rest of the chain.
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
Environment=PIGEON_HEALTHCHECK_PORT=5757
ExecReload=
[Install]
WantedBy=multi-user.target
EOTThen reload systemd configurations and start the service!
service palomad start
# Check that it's running successfully:
service palomad status
# Or watch the logs:
journalctl -u palomad.service -fCONTRACT=<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