Cannot sync bor with new heimdalld

My heimdalld compiled by tag v.0.2.7 and fully synched
“latest_block_height”: “8628622”,
“latest_block_time”: “2022-03-15T13:52:10.898416246Z”,
“catching_up”: false

when i started bor v0.2.14-tmp-span-hotfix i got this:

INFO [03-15|13:51:06.852] Retrying again in 5 seconds for next Heimdall span path=bor/span/4054
INFO [03-15|13:51:07.493] Retrying again in 5 seconds for next Heimdall span path=bor/span/4054
INFO [03-15|13:51:11.854] Retrying again in 5 seconds for next Heimdall span path=bor/span/4054
INFO [03-15|13:51:12.494] Retrying again in 5 seconds for next Heimdall span path=bor/span/4054
INFO [03-15|13:51:16.856] Retrying again in 5 seconds for next Heimdall span path=bor/span/4054
INFO [03-15|13:51:17.496] Retrying again in 5 seconds for next Heimdall span path=bor/span/4054

bor command:

bor --datadir $DATA_DIR
–port 30304
–http --http.addr ‘0.0.0.0’
–http.vhosts ‘
–http.corsdomain '

–http.port 8545
–rpc.txfeecap 0
–ws --ws.port 8546 --ws.addr 0.0.0.0 --ws.origins ‘*’
–ipcpath $DATA_DIR/bor.ipc
–http.api ‘eth,net,web3,txpool’
–syncmode ‘fast’
–networkid ‘137’
–miner.gaslimit ‘20000000’
–miner.gastarget ‘20000000’
–txpool.nolocals
–txpool.accountslots ‘128’
–txpool.globalslots ‘20000’
–txpool.lifetime ‘0h16m0s’
–cache 16384
–maxpeers 200
–maxpendpeers 1000000
–metrics
–bootnodes “enode://0cb82b395094ee4a2915e9714894627de9ed8498fb881cec6db7c65e8b9a5bd7f2f25cc84e71e89d0947e51c76e85d0847de848c7782b13c0255247a6758178c@44.232.55.71:30303,enode://88116f4295f5a31538ae409e4d44ad40d22e44ee9342869e7d68bdec55b0f83c1530355ce8b41fbec0928a7d75a5745d528450d30aec92066ab6ba1ee351d710@159.203.9.164:30303,enode://3178257cd1e1ab8f95eeb7cc45e28b6047a0432b2f9412cff1db9bb31426eac30edeb81fedc30b7cd3059f0902b5350f75d1b376d2c632e1b375af0553813e6f@35.221.13.28:30303,enode://16d9a28eadbd247a09ff53b7b1f22231f6deaf10b86d4b23924023aea49bfdd51465b36d79d29be46a5497a96151a1a1ea448f8a8666266284e004306b2afb6e@35.199.4.13:30303,enode://ef271e1c28382daa6ac2d1006dd1924356cfd843dbe88a7397d53396e0741ca1a8da0a113913dee52d9071f0ad8d39e3ce87aa81ebc190776432ee7ddc9d9470@35.230.116.151:30303”

1 Like

How i can make it work? Which versions should i use?

1 Like

Works after update of ~/.heimdalld/config/genesis.json to latest version from GitHub - maticnetwork/launch: Matic network mainnet v1 launch

git clone GitHub - maticnetwork/launch: Matic network mainnet v1 launch
cp -f launch//sentry/sentry/heimdalld/genesis.json ~/.heimdalld/config/genesis.json

1 Like