Welcome to the weekly update on new software design from the Paloma developer community.
REMINDER WARNING:
The New Hatchling Paloma Network of
tumbler
(v1.15.5) and the Pigeon relay module are on v1.12.3 Paloma is just over one year old and its Cosmwasm and EVM contracts are still unaudited and undergoing continuous upgrades on the protocol and its smart contracts. The GRAIN token is available on the Paloma mainnet but is not yet trading on exchanges. Although the flock is flying on the
tumbler
mainnet, it is still subject to the continued development of Paloma’s cross-chain messaging system and the security guarantees offered by the GRAIN token. We expect
tumbler
to experience weekly chain halts and chain restarts for upgrades. We also expect numerous undiscovered bugs and vulnerabilities. No one on this project controls or influences the price of GRAINs. The community will strive to preserve the mainnet state, which includes balances, but considers this mainnet high-risk. Proceed with caution.
This change introduces fundamental changes to the relayer selection process. Live values are now gathered from the metrics module, and individual relayer fees are taken into account.
Going forward, it’s paramount for relayers to make sure they have their fees set and configured for each chain, otherwise they will
not be eligible for relaying anymore
.
The majority of the changes are in
msg_assigner.go
, that’s where most of your attention will be needed. It works by collecting metric and fee data once per block for all validators and ranking them. Then each message during that block will be filtered depending on its requirements, and the top ranking eligible validator will be picked (and removed from the cache). They become eligible again next block. There are still some issues with this algorithm though. At the moment, the logic will prioritize the few top ranking validators only, with little way for the mid tier to rank up. This will need to be revisited in the future for sure. See
palomad tx treasury upsert-relayer-fee --help
for more information!
Fee settings are configured per chain, and stored as float point percentile representations of the total cost of a relayed transaction. For example, a relayer fee of
1.0
entitles the relayer to 100% of the estimated costs for a relayed transaction, whereas a fee setting of
1.15
entitles to a total of 115% of the costs, making a profit of 15%. These funds can later be claimed by directly interfacing with the Paloma bridge on remote chains.
In order to stay eligible for relaying messages, you will need to setup a fee value of at least
1.0
. In order to become profitable, your fee setting needs to be above
1.0
. There are no other limits on which fees you set. The network will automatically choose relayers with lower fees based on the current weight settings as defined by governance (check
palomad q evm chains-infos
for the current relay weights for each chain).
ADDRESS =
FEE = #e.g 1.1
palomad tx treasury upsert-relayer-fee arbitrum-main $FEE --from $ADDRESS --fees 250ugrain --gas auto --yes
palomad tx treasury upsert-relayer-fee base-main $FEE --from $ADDRESS --fees 250ugrain --gas auto --yes
palomad tx treasury upsert-relayer-fee blast-main $FEE --from $ADDRESS --fees 250ugrain --gas auto --yes
palomad tx treasury upsert-relayer-fee bnb-main $FEE --from $ADDRESS --fees 250ugrain --gas auto --yes
palomad tx treasury upsert-relayer-fee eth-main $FEE --from $ADDRESS --fees 250ugrain --gas auto --yes
palomad tx treasury upsert-relayer-fee gnosis-main $FEE --from $ADDRESS --fees 250ugrain --gas auto --yes
palomad tx treasury upsert-relayer-fee matic-main $FEE --from $ADDRESS --fees 250ugrain --gas auto --yes
palomad tx treasury upsert-relayer-fee op-main $FEE --from $ADDRESS --fees 250ugrain --gas auto --yes
A number of fixes to Skyway Bridge functionality included:
Paloma LightNode Sale features for Paloma aim to enable automation of registration of delegator nodes and the automation of fee access for nodes that start without GRAINs. The first feature is to add light node feegrant to governance vote.
Stay up to date and follow the Paloma public repositories and the commits of ongoing upgrades to the Paloma Cosmos-SDK blockchain and the Pigeon relay module here:
A breed of fancy pigeon developed by selective breeding, it has descended from the rock dove as with other types of domesticated pigeons; it is thought to have first been brought into Europe from Tunis, Africa, where the type originated and were first imported into England in the late 19th century.
Source:
This week, we fix the Paloma Skyway Bridge functionality and we add new functionality for the upcoming Paloma LightNode Sale. This new integration of the lightnode sale with Paloma ensures that Paloma LightNodes can leverage Paloma infrastructure for registration and activation.
To follow the project on Github, please star the project:
To participate in the community, please join the Paloma Discord: