f(x)Core Mainnet Validator Bugs/Fixes & Technical Support

Aritz_Bahamonde · October 2, 2022, 1:25pm

put more than 50th

and you are lucky because look FX_Paper Validator…DONT KNOW WHY…

Aghanims · November 21, 2022, 1:40pm

Hi all,

I am new here and trying for function X validator, I am technical trained but not in blockchain, will post here if there is any issues

Aghanims · November 23, 2022, 4:41am

Successfully create my first validator by following the gitbook instructions!
https://starscan.io/fxcore/tx/6DE9A86D8F2F26276FB9346CDD9F4C6FC532D00DE308B56D05B40B8555F136E9

Welcome to stake

Edit: Is there an issue on the explorer? as I cant see my validator there

Superbit123 · November 23, 2022, 8:49am

Welcome to the fx party.

Check under inactive perhaps. You will need to have staked more than the 50th validator to be classified as active.

FxWorldValidator · November 23, 2022, 1:37pm

Hi Aghanism
Please join also the validator group in telegram if you havent yet.

Aghanims · November 24, 2022, 2:27am

How can I join the group?

Aritz_Bahamonde · November 24, 2022, 3:22pm

SCENE · December 9, 2022, 9:00am

Hi Aghanims, to be on the active list of validators, the total amount of delegated tokens in your validator must be within the Top 50.

ByteXSylvia · December 13, 2022, 10:18am

Hello when i make this i get this error :fxcored keys parse $(cat .fxcore/config/priv_validator_key.json| jq -r '.address') Error: decoding bech32 failed: invalid separator index 39 Usage: fxcored keys parse [address or name] [flags] Thanks in advance

ByteXSylvia · December 13, 2022, 11:59am

and when i make this i get this ~# fxcored tendermint show-validator
{“@type”:“/cosmos.crypto.ed25519.PubKey”,“key”:“xxKMArCG0hhgLTjc35rtvqh4mA1g+tjehdhSVLxxisI=”} i get this @lancelai

ByteXSylvia · December 13, 2022, 12:07pm

i have problem on this place in the youtube video LIVE SESSION: Function X Public Validator Setup training - YouTube

lancelai · December 14, 2022, 1:42am

Are u setting up a new validator?

That’s to do some verification and probably the format changed.

I suggest you to ignore that and just compare with below 2 command:

curl -s 127.0.0.1:26657/status | jq '.result.validator_info.pub_key'

cat .fxcore/config/priv_validator_key.json| jq .pub_key

ByteXSylvia · December 14, 2022, 5:58am

yes i will add a new Validator.

fxcored tx staking create-validator \
  --chain-id=fxcore \
  --gas="auto" \
  --gas-adjustment=1.2 \
  --gas-prices="4000000000000FX" \
  --from=byte \
  --ledger \
  --amount=105000000000000000000FX \
  --pubkey="xxKMArCG0hhgLTjc35rtvqh4mA1g+tjehdhSVLxxisI=" \
  --commission-rate="0.05" \
  --commission-max-rate="0.5" \
  --commission-max-change-rate="0.01" \
  --min-self-delegation="100000000000000000000" \
  --moniker="ByteX" \
  --website="https://twitter.com/Byte_Produce" \
  --details="My Personal Validator. Anyone who knows me knows that I will do my best. For those who don't know me: I want FunctionX to make the world a better place. I'm 100% committed to making it happen. Kind regards, Sylvia" \
  --keyring-backend file

I get this error :

Default sign-mode 'direct' not supported by Ledger, using sign-mode 'amino-json'.
Error: invalid character 'x' looking for beginning of value
Usage:
  fxcored tx staking create-validator [flags]

Or what do I need to add to --pubkey=$(fxcored tendermint show-validator) \

Best regards Sylvia

lancelai · December 14, 2022, 6:17am

have you tried $(fxcored tendermint show-validator) ?

ByteXSylvia · December 14, 2022, 6:27am

yes than i get

fxcored tx staking create-validator \
>   --chain-id=fxcore \
>   --gas="auto" \
>   --gas-adjustment=1.2 \
>   --gas-prices="4000000000000FX" \
>   --from=byte \
>   --ledger \
>   --amount=105000000000000000000FX \
>   --pubkey=$(fxcored tendermint show-validator) \
>   --commission-rate="0.05" \
>   --commission-max-rate="0.5" \
>   --commission-max-change-rate="0.01" \
>   --min-self-delegation="100000000000000000000" \
>   --moniker="ByteX" \
>   --website="https://twitter.com/Byte_Produce" \
>   --details="My Personal Validator. Anyone who knows me knows that I will do my best. For those who don't know me: I want FunctionX to make the world a better place. I'm 100% committed to making it happen. Kind regards, Sylvia" \
>   --keyring-backend file
Enter keyring passphrase:
Default sign-mode 'direct' not supported by Ledger, using sign-mode 'amino-json'.
Error: invalid character 'o' looking for beginning of value
Usage:
  fxcored tx staking create-validator [flags]

Best regards Sylvia

ByteXSylvia · December 14, 2022, 6:58am

I think the Problem is with --pubkey=$(fxcored tendermint show-validator)

fxcored tendermint show-validator
{"@type":"/cosmos.crypto.ed25519.PubKey","key":"xxKMArCG0hhgLTjc35rtvqh4mA1g+tjehdhSVLxxisI="}

I try this too

fxcored tx staking create-validator \
>   --chain-id=fxcore \
>   --gas="auto" \
>   --gas-adjustment=1.2 \
>   --gas-prices="4000000000000FX" \
>   --from=byte \
>   --ledger \
>   --amount=105000000000000000000FX \
>   --pubkey="@type":"/cosmos.crypto.ed25519.PubKey","key":"xxKMArCG0hhgLTjc35rtvqh4mA1g+tjehdhSVLxxisI=" \
>   --commission-rate="0.05" \
>   --commission-max-rate="0.5" \
>   --commission-max-change-rate="0.01" \
>   --min-self-delegation="100000000000000000000" \
>   --moniker="ByteX" \
>   --website="https://twitter.com/Byte_Produce" \
>   --details="My Personal Validator. Anyone who knows me knows that I will do my best. For those who don't know me: I want FunctionX to make the world a better place. I'm 100% committed to making it happen. Kind regards, Sylvia" \
>   --keyring-backend file
Enter keyring passphrase:
Default sign-mode 'direct' not supported by Ledger, using sign-mode 'amino-json'.
Error: invalid character '@' looking for beginning of value

Where i get the real Pubkey for the Validator?

fxcored status
NodeInfo:
  channels: "40202122233038606100"
  id: 2e60e9b2a687b75d8d1858d81c161cee6a261560
  listen_addr: tcp://0.0.0.0:26656
  moniker: your-moniker
  network: fxcore
  other:
    rpc_address: tcp://0.0.0.0:26657
    tx_index: "on"
  protocol_version:
    app: 0
    block: 11
    p2p: 8
  version: release/v2.4.x-fc080689c410d58a32f41bb98d215e39f4e6774a
SyncInfo:
  catching_up: false
  earliest_app_hash: DC5DE2C98B911DDA8A534B06506AD2564089E0045CE95C842AE21AEEA62CF055
  earliest_block_hash: FCCB9080E7A0B03BE634E4AFB8EC89EF3AE6AF4107E402116E61D35D9749EA18
  earliest_block_height: "7640001"
  earliest_block_time: "2022-11-25T01:46:37.688900169Z"
  latest_app_hash: 20A2629DC4D6B89788CC8D2AE2B86DAAA441924184141EB8AB91D8AB33C4A2D9
  latest_block_hash: DEF52C76C56B379FAE1FFCEF9B319CCFDB3A3490CB06AEF868BE3DAC843C5C52
  latest_block_height: "7921136"
  latest_block_time: "2022-12-14T05:30:08.146525377Z"
ValidatorInfo:
  Address: 58D7227B62E2DC93C36E032D19D1B52315ABEA33
  PubKey:
    key: xxKMArCG0hhgLTjc35rtvqh4mA1g+tjehdhSVLxxisI=
  VotingPower: 0

best regards Sylvia

lancelai · December 15, 2022, 1:44am

Using the pubkey is fine. This is the new pubkey format for cosmos based
Could you try with single quote instead:
'{"@type":"/cosmos.crypto.ed25519.PubKey","key":"xxKMArCG0hhgLTjc35rtvqh4mA1g+tjehdhSVLxxisI="}'

otherwise it could be other cause

ByteXSylvia · December 15, 2022, 5:11am

Many thanks this work for me Function X StarScan

Best regards Sylvia

CryptoKid · March 1, 2023, 4:33pm

Hello,

I’m trying to setup a validator, I downloaded the daily database snapshot, also built the binary (also tried with the one from GitHub), I get an error like this:

panic: can’t get node C9893711CA969BABF9646D869ADC3C27A49C830A7D36EECA75A0747224BC562E: leveldb: closed

Ideas of what could be the solution?

FrenchXCore · March 1, 2023, 5:17pm

@CryptoKid : Still need help ? Contact me over Telegram @FrenchXCore !!