VETIVER-9.0.1 silently ignores rpc.modules when configured as a list of
{name,version,enabled} objects. Switch to canonical OBJECT format from
rskj's expected.conf:
modules = { eth { version = "1.0", enabled = "true" } ... }
Without this, the RPC server starts but no modules are registered, so
eth_blockNumber returns method-not-found and show-status flags as 'error'
even though the chain itself imports blocks fine.
Also added 'hosts = []' under rpc.providers.web.http (LIST per
expected.conf, was missing). Same fix applied to bamboo testnet config.
Note: this only resolves mainnet. Bamboo still needs DB recreate due to
unrelated 'Invalid block header size: 22' corruption.
37 lines
991 B
Plaintext
37 lines
991 B
Plaintext
blockchain.config.name = "main"
|
|
|
|
database.dir = /var/lib/rsk/database/mainnet
|
|
|
|
peer.port = 3234
|
|
|
|
rpc {
|
|
providers = {
|
|
web = {
|
|
cors = "*"
|
|
http = {
|
|
enabled = true
|
|
bind_address = "0.0.0.0"
|
|
hosts = []
|
|
port = 8545
|
|
}
|
|
ws = {
|
|
enabled = true
|
|
bind_address = "0.0.0.0"
|
|
port = 8546
|
|
}
|
|
}
|
|
}
|
|
|
|
modules = {
|
|
eth { version = "1.0", enabled = "true" }
|
|
net { version = "1.0", enabled = "true" }
|
|
rpc { version = "1.0", enabled = "true" }
|
|
web3 { version = "1.0", enabled = "true" }
|
|
evm { version = "1.0", enabled = "true" }
|
|
sco { version = "1.0", enabled = "true" }
|
|
txpool { version = "1.0", enabled = "true" }
|
|
debug { version = "1.0", enabled = "true" }
|
|
personal { version = "1.0", enabled = "true" }
|
|
}
|
|
}
|