Repository navigation
[Bug]: lavap crashes on startup for NEART provider #2282
Description
Is there an existing issue for this?
- I have searched the existing issues
What happened?
We have a very simple config for the NEART spec:
metrics-listen-address: ":9201"
endpoints:
- api-interface: jsonrpc
chain-id: NEART
network-address:
address: "127.0.0.1:1500"
disable-tls: true
node-urls:
- url: "http://10.0.1.1:3030"and are observing a crash directly when lavap starts, before even making a network request:
Apr 29 14:49:08.154133884 INF Process Started
Apr 29 14:49:08.189602363 INF RPCProvider started
Apr 29 14:49:08.189793369 INF read config file successfully expected_config_name=/var/lib/lavanet/config/neart.yml
Apr 29 14:49:08.189898011 INF Running with chain-id:lava-mainnet-1
Apr 29 14:49:08.189962643 INF Setting gas for tx Factory gas-adjustment=3 gas-prices=0.00002ulava
Apr 29 14:49:08 INF setting log level loglevel=info
Apr 29 14:49:08 INF lavap Binary Version: 6.0.0
Apr 29 14:49:08 INF Connected to cache service address=unix:/run/lavanet-cache/cache.sock
Apr 29 14:49:08 INF cache service connected address=unix:/run/lavanet-cache/cache.sock cacheLatestBlockEnabled=false
Apr 29 14:49:08 INF prometheus endpoint listening Listen Address=:9201
Apr 29 14:49:09 INF Lava Spec found on chain SpecId=LAV1
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x48 pc=0x26297b6]
goroutine 1 [running]:
github.com/lavanet/lava/v5/protocol/statetracker.NewStateTracker({_, _}, {{0x3925cd0, 0xc000721b00}, {0x390c040, 0xc001146a40}, {0x38f8230, 0x53b6b80}, 0x0, 0x0, ...}, ...)
github.com/lavanet/lava/v5/protocol/statetracker/state_tracker.go:286 +0x4f6
github.com/lavanet/lava/v5/protocol/statetracker.NewProviderStateTracker({_, _}, {{0x3925cd0, 0xc000721b00}, {0x390c040, 0xc001146a40}, {0x38f8230, 0x53b6b80}, 0x0, 0x0, ...}, ...)
github.com/lavanet/lava/v5/protocol/statetracker/provider_state_tracker.go:38 +0x205
github.com/lavanet/lava/v5/protocol/rpcprovider.(*RPCProvider).Start(0xc00157f180, 0xc001426c70)
github.com/lavanet/lava/v5/protocol/rpcprovider/rpcprovider.go:263 +0xa38
github.com/lavanet/lava/v5/protocol/rpcprovider.CreateRPCProviderCobraCommand.func3(0xc001251508, {0xc000e8cb40, 0x1, 0x12})
github.com/lavanet/lava/v5/protocol/rpcprovider/rpcprovider.go:1267 +0x265e
github.com/spf13/cobra.(*Command).execute(0xc001251508, {0xc000e8ca20, 0x12, 0x12})
github.com/spf13/cobra@v1.8.0/command.go:983 +0xaaa
github.com/spf13/cobra.(*Command).ExecuteC(0xc00137b508)
github.com/spf13/cobra@v1.8.0/command.go:1115 +0x3ff
github.com/spf13/cobra.(*Command).Execute(...)
github.com/spf13/cobra@v
5B6D
1.8.0/command.go:1039
github.com/spf13/cobra.(*Command).ExecuteContext(...)
github.com/spf13/cobra@v1.8.0/command.go:1032
github.com/cosmos/cosmos-sdk/server/cmd.Execute(0xc00137b508, {0x0, 0x0}, {0xc0010d1578, 0x16})
github.com/cosmos/cosmos-sdk@v0.47.13/server/cmd/execute.go:33 +0x16e
main.main()
github.com/lavanet/lava/v5/cmd/lavap/main.go:84 +0x50e
We can run lavap for other specs, including NEAR (mainnet) just fine.
Lava Version
lavap 6.0.0
How to reproduce?
No response
Activity
wigan-ludgate commentedon Apr 29, 2026
Quite competently,
erris not handled when creating the chain tracker – cfstate_tracker.go:285