FAQs
There is an additional channel called #FAQ on our Discord. If you need further help hop on to our support channels there.
Nodes, Validators and Providers β«β
π‘ What is a specification and what does it let me do?β
A specification (βspecβ) is a module which you can add to Lava, extending the range of data services the network of providers can serve. RPC specs are the first to be added to Lava, and we will offer subgraph specs soon.
π‘ I have problems running the install scripts.β
Troubleshooting:
lavad
command not found- Try running
source ~/.profile
- Try running
- The node is stuck on βWaiting for node to catch upβ
- This process might take some time based on your internet connection, compute capabilities and the height of the latest block on the network
- Please allow 5-20 minutes for this procedure to catch up with the latest block in the network
- curl or unzip commands are not found
sudo apt update && sudo apt install curl unzip -y
- sudo command not found
apt install sudo -y
- When running
stake_validator
you get the erroraccount lava@XYZ not found: key not found
- Make sure your account is funded from Lava side before you try to stake as a validator
Providers π₯οΈβ
π‘ What is QoS (Passable Quality-of-Service)?β
This score for providers per relay is based on the metrics of latency, sync, and availability. There are two different types of QoS:
π‘ How can you improve your provider's QoS?β
Providers are rated based on response time, availability and freshness. It is also important to maintain high performance on your nodes and to have powerful servers. For more details, see RSCH-1000
π‘ How can I check the provider's performance?β
You can check all providers on Lava Info. For your own provider, you can configure Prometheus using the metrics-listening-address
flag.
You can also track your own performance using the CLI: lavad test rpcprovider...
.
π‘ How do I earn Magma points with a provider?β
At the moment, providers are not connected to Magma and you cannot earn any points. However, you can already test the performance of providers, evaluate your CU, QoS...
π‘ What is the difference between a provider who uses Lavavisor and one who does not?β
There is no difference. LavaVisor updates the binary automatically. Without it you have to do it manually. LavaVisor is based on Cosmovisor
π‘ The tokens used for providers and validators are different?β
No, there is only one token - LAVA
. It is used as a governance token, as gas fees required for transactions, for rewards distributed to validators/providers, etc.
Lava uses dualstaking, when staking a provider, a validator is also specified.
π‘ How does slashing work for providers?β
Slashing has not yet been implemented for providers. It is planned to only be for fraudulent activity. A freeze feature has been implemented for service providers to avoid downtime or poor QoS. Documentation is available for jailing.
Here are some basic facts about jailing:
- providers claim CUs serviced via relay payments;
- each relay payment has an unreponsive providers list (provider1's claim might report providers 2,3 for example), these reports are signed by the consumer as well as the CU used;
- every epoch (15m) the chain checks unresponsiveness claims, against the CU serviced over the last 5 epochs;
- if the ratio of complaints per relay is greater than the ratio of service claimed (if you want the full equation lmk) if more than 0.5 AND the number of providers available in the specification is greater than 5 per geolocation, then the provider is jailed and gets all its funds back after 25 hours.
π‘ How much do providers earn now?β
Providers earn fees in the form of lava tokens from consumers for servicing requests. Accordingly, testnet providers are currently earning lava tokens on the testnet. Remember that Testnet tokens have no value!
π‘ How quickly do new providers receive relay requests?β
It can take up to 15m to get relays again.
π‘ Is it ok to use the same wallet address between node and provider?β
Yes, you can, it's allowed.
π‘ What is Incentivized Public RPC (ipRPC)?β
These are incentivized programs where providers earn for servicing specific chains. Chains reward node operators for joining Lava and serving infrastructure in their native token. The following ipRPCs are currently supported:
π‘ Who can join the Incentivized Public RPC?β
Anyone can join the ipRPC. It requires setting up a provider for the appropriate service. Then sign up to receive lava testnet tokens using the appropriate forms:
π‘ How can I update/edit my provider information?β
To update your provider information on chain, send the lavad tx pairing modify-provider...
transaction with the updated information and an additional stake of minimum 1 ulava.
π‘ I get ERR_stake_provider_endpoints: invalid provider endpoints
error when trying to stake as a providerβ
In your stake-provider transaction you need to specify all required provider endpoints based on the chain you are staking on. For example to provide for cosmos chains you need both tendermint-rpc and rest as follows: "IP:port,tendermintrpc,1 IP:port,rest,1"
.
π‘ Is there an unbonding period for providers?β
Yes, it's currently configured to 21 days.
π‘ How can I see my current provider state (incl. unbonding)?β
You can use the following query: lavad q pairing providers <CHAIN_ID>
π‘ When running my provider process lavad server
I get the following error provider endpoint mismatch
β
This error means that you have used different geolocations when using the provider-stake
transaction and when running lavad server
, please ensure they match and the problem should be resolved.
Developer β¨οΈβ
π‘ Using Lava with Other RPC Clientsβ
Lava easily integrates with other RPC clients.
- Gateway - Simply create an account on the gateway, and replace your client's RPC URL with the appopriate one. Get started immediately!
- SDK - You can also use the SDK library integrations to integrate with viem, cosmjs, web3.js, or ethers.js.
π‘ I'm already using another SDK.β
No problem, Lava offers integrations to existing popular libraries here.
π‘ How to change the RPC url which Cosmjs uses?β
If you want a native integration to use seamlessly, please check out the new Lava integration for CosmJS! Alternatively, please check out the cosmolava-client created by one of our community members: MELLIFERA-Labs/cosmolava-client
If you just want to switch the RPC URL you can do so using the HttpEndpoint interface on stargate or cosmwasm-stargate. Be sure you've grabbed the TendermintRPC endpoint from Lava or you may encounter errors.