Hello; I provide this data:

https://github.com/eco-stake/validator-registry/blob/master/Pandora/chains.json

that should match with:

https://testnet.restake.app/bitcannadevnet/bcnavaloper153hxvnx24h07aptul43fsuyeq7kgt2erqad6xy

But this is my output when I run the restake app:

[06:59:20.645] ⚛
[06:59:20.729] Failed with error: bitcannadevnet not found in Chain Registry
[06:59:20.730] Autostake failed

And this is the output of the RPC proxy connection at Cosmos Directory:
https://testnet.cosmos.directory/bitcannadevnet
Chain not found

I have multiple bots running but with this repo the newer bots are reading from here and auto compounding at times it shouldn't, is there a way to avoid this?

it looks like my key 'PFC' is in the right place (https://github.com/eco-stake/validator-registry/blob/master/PFC/chains.json#L19), but

[23:15:31.834] Loaded terra
[23:15:31.841] Bot address is terra1dp67gfvhsffyn42k4srsw29wm6d55u9m3evt9d
[23:15:31.841] !! You are not using the preferred derivation path !!
[23:15:31.841] !! You should switch to the correct path unless you have grants. Check the README !!
[23:15:31.841] Not an operator

Many of the crypto community want to support the (generous) IBC Relayers, and a registry of that could offer some value. With the right kind of automation, utilizing the profiles that are already defined here could serve to become a registry of IBC Relayers, with support/tip information. It could also be used as a quality metric for validator selection (in addition to in-chain data, such as governance history and performance.

Help me replace the hardcoded data in this file:
https://github.com/osmosis-labs/docs/blob/main/developing/relaying/relayers.md

Now we read validator icon from keybase.io but we can read from cosmostation registry.
Or they put in this repo.

Hello, we have updated our validator addresses for Planq and Provenance, but in restake.app our profile is still linked to the old ones. Also our profile in Oraichain, which was the one we did create first doesn't show correct contact data or icon.
Can this be fixed?
Thanks

Hello,

We are trying to setup the restake service for Likecoin by adding manually the entry into network.json and the execution looks fine but face an issue as not able to get delegations list.
Log is as below:
[04:10:30.583] Running autostake
[04:10:31.346] Bot balance is 10000000000 nanolike
[04:10:31.347] Finding delegators...
[04:12:10.672] Failed to get delegations: Request failed with status code 524
[04:12:10.672] Checking 0 delegators for grants...

Any suggestion?

Hi, I noticed that the archway network bot is not working correctly, judging by restake.app it doesn't work at any validator

I tried connecting different endpoints, but unfortunately to no avail

Here you can find the logs:
https://github.com/mms-team/logs/blob/main/archway_restake_logs

Unable to clone repo with GitHub desktop as one directory ends with a full stop creating invalid PATH

The directory is CUCK.

Please consider adding a way for validators to verify the validity of their entry.
This would give delegators the certainty that the restake wallets listed in this repository are authentic and controlled by the validator.

The current implementation of restake.app bot does need to query for generic delegation grants (ledger workaround), which do not have a delegation whitelist, potentially allowing the restake wallet to delegate to any validator.
A malicious entity could list restake wallets here and redirect delegators staking rewards to a malicious validator, potentially robbing delegators through commissions.

This scenario might be highly unlikely for mature chains with a high enough delegation floor for validators but chains with accessible active validatorset could face this problem.

My suggestion for a verification method would be to have the validator's initial delegator wallet broadcast a transaction that includes the restake wallet address in the memo and attach the transaction hash to the profile or PR.

Can you merge our PR please?
#3639

We recently submitted a PR for the addition of Sentinel network to our Restaking network resources.
https://github.com/eco-stake/validator-registry/blob/master/ValidatorNode/chains.json

We updated our networks.local.json file to include the new sentinel network

  "sentinel": {
    "enabled": true,
    "prettyName": "Sentinel",
    "restUrl": [
      "http://216.128.136.66:1317"
    ],
    "gasPrice": "0.01udvpn",
    "autostake": {
      "correctSlip44": true,
      "retries": 3,
      "batchPageSize": 100,
      "batchQueries": 25,
      "batchTxs": 50,
      "delegationsTimeout": 20000,
      "queryTimeout": 15000,
      "queryThrottle": 100,
      "gasModifier": 1.1
    }

We ensured that the firewall on our restURL server is allowing traffic to port 1317.

However, when we attempt to npm run dryrun sentinel we receive the following error.

> [email protected] dryrun
> node scripts/dryrun.mjs "sentinel"

[16:17:45.386] ⚛
[16:17:47.073] Loaded Sentinel
[16:17:47.137] Bot address is sent1xgcqw2flkaxffe0s5kctlnelyshe87vh9aaxgs
[16:17:47.137] Not an operator
[16:17:47.137] Autostake finished

The error leads us to believe that the Restake dryrun script is not picking up our recent validator-registry changes.
We've double-checked the normal list of issues

1. indexing enabled
2. minimum gas prices matching our restURL server setting

What else can we check?

NOTE - the other 3 networks we have configured are all running fine. It's just the newly added "sentinel" network that is creating us an issue.

I notice LikeCoin is now support in restake (thought no authz module yet). I would like to know what is the name for the likecoin chain in the chain.json file. Thanks.

Perhaps this is an issue with windows, but we cannot clone due to emoji's being used in the path

Hi guys,

Recently submitted a PR to update the frequency of our restake operator on Teritori, the PR was merged and the front end was updated but looking again today it's showing as daily rather than 10 minutes.

If you could fix we would appreciate, thank you.

Request to merge #841 Please!

We want to change our existing operator address to a new wallet. Is it safe to do it?

Follow Chain Registry lead with JSON schema https://github.com/cosmos/chain-registry/blob/master/chain.schema.json

Setup automatic linting