+
## What is Lava? π
Lava is the first modular data access layer for blockchains. It introduces [`specs`](/spec): a modular primitive that lets contributors permissionlessly add support for new chains and data services to the base protocol. RPC is the first service supported by the protocol but we are soon bringing further choice by integrating with indexing and API partners, such as Subsquid.
diff --git a/docs/intro/explorers.md b/docs/intro/explorers.md
index 2cbe97c0..625ecc4b 100644
--- a/docs/intro/explorers.md
+++ b/docs/intro/explorers.md
@@ -7,12 +7,16 @@ title: π Explorers
-## Official Explorer β
+
+
+## β Official Explorer {#official-explorer}
Our **official block explorer** is brought to you by Nodes.Guru:
https://lava.explorers.guru/
+
+
## Community Block Explorers π§πΎβπ€βπ§πΎ
- β¨[BCCNodes](https://explorer.bccnodes.com/lava-T/)
- β¨[Kjnodes](https://explorer.kjnodes.com/lava-testnet)
@@ -23,6 +27,11 @@ https://lava.explorers.guru/
- β¨[Stake Village](https://exp.stakevillage.net/Lava-testnet)
- β¨[STAKEME](https://lava.exploreme.pro)
+
## Community Public RPC Explorer π΅πΌ
One of our community members is providing an experimental service to see all exposed providers on the network:
-https://services.kjnodes.com/testnet/lava/public-rpc/
+> https://services.kjnodes.com/testnet/lava/public-rpc/
+
+## Lava SDK Block Explorer π
+One of our team members has developed an [`allblocks`](/all-blocks-app) application which gets the latest block from Lava supported chains and reports latency information:
+> https://allblocks.vercel.app
diff --git a/docs/intro/faq.md b/docs/intro/faq.md
index cf9d94ee..f756c8b0 100644
--- a/docs/intro/faq.md
+++ b/docs/intro/faq.md
@@ -13,14 +13,13 @@ There is an additional channel called #FAQ on our Discord. If you need further h
-## Dictionary π
+## Nodes, Validators and Providers β« {#nodes-validators-providers}
-### Keyring
-The keyring holds the private/public keypairs used to interact with a node. For instance, a validator key needs to be set up before running the blockchain node, so that blocks can be correctly signed. The private key can be stored in different locations, called "backends", such as a file or the operating system's own key storage. ([learn more here](https://docs.cosmos.network/main/run-node/keyring.html))
+### π‘ What is a specification and what does it let me do? {#specs}
+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.
-## Nodes, Validators and Providers β«
-### I have problems running the install scripts. {#install-troubleshooting}
+### π‘ I have problems running the install scripts. {#install-troubleshooting}
Troubleshooting:
@@ -40,39 +39,35 @@ Troubleshooting:
1. Make sure your account is funded from Lava side before you try to stake as a validator
## Providers π₯οΈ
-### How can I update/edit my provider information?
+
+### π‘ How can I update/edit my provider information? {#provider-info}
To update your provider information on chain, send the `provider-stake` 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
+### π‘ I get `ERR_stake_provider_endpoints: invalid provider endpoints` error when trying to stake as a provider {#staking-error}
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 unboding period for providers?
+### π‘ Is there an unbonding period for providers? {#unbonding-period}
Yes, it's currently configured to 21 days.
-### How can I see my current provider state (incl. unbonding)?
+### π‘ How can I see my current provider state (incl. unbonding)? {#provider-state}
You can use the following query: `lavad q pairing providers `
-### When running my provider process `lavad server` I get the following error `provider endpoint mismatch`
+### π‘ When running my provider process `lavad server` I get the following error `provider endpoint mismatch` {#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
+### π‘ Using Lava with Other RPC Clients {#using-lava-with-other-rpcs}
Lava easily integrates with other RPC clients.
1. **Gateway** - Simply create an account on the gateway, and replace your client's RPC URL with the appopriate one. Get started [immediately](/gateway-getting-started)!
2. **SDK** - You can also use the SDK library integrations to integrate with [viem](/viem), [cosmjs](/cosmjs), [web3.js](/web3js), or [ethers.js](/ethersjs5).
-
-
-### I'm already using another SDK.
+### π‘ I'm already using another SDK. {#using-lava-with-other-sdks}
No problem, Lava offers integrations to existing popular libraries [here](/sdk-integrations).
-
-### How to change the RPC url which Cosmjs uses?
+### π‘ How to change the RPC url which Cosmjs uses? {#changing-cosmjs-url}
If you want a native integration to use seamlessly, please check out the new Lava integration for [CosmJS](/cosmjs)!
Alternatively, please check out the cosmolava-client created by one of our community members: [MELLIFERA-Labs/cosmolava-client](https://github.com/MELLIFERA-Labs/cosmolava-client)
diff --git a/docs/intro/intro.md b/docs/intro/intro.md
index 1378ae74..7dd149ab 100644
--- a/docs/intro/intro.md
+++ b/docs/intro/intro.md
@@ -18,9 +18,9 @@ Welcome testers! Thank you for joining the testnet. If you find errors in our do
## Overview π
-Web3 is only as strong as its weakest link. Today, due to complexities and lack of incentives to run your own node, apps rely on costly centralized services, unreliable public RPC endpoints, and self-hosted services. Lava is here to fix it. Access Lava, Access Web3.
+Today, RPC & data infrastructure is not up to par for scaling Ethereum, its rollups and all other blockchains. Lavaβs novel architecture aims to offer developers fast, reliable and accurate access to any chain. RPC is the first service on Lava, but we will be expanding to subgraphs, oracles and more.
-Lava is built as an application-specific L1 PoS Blockchain, based on [CosmosSDK](https://tendermint.com/sdk/). We are building the most reliable, modular, and extensible network, which ensures high network performance and secure blockchain access for all web3 APIs.
+Lava is built as an application-specific L1 PoS Blockchain, based on CosmosSDK. The protocol introduces a primitive called βspecsβ. Specs are modules defining APIs in JSON-format, which can then be served by the network of providers to meet demand. We envision a modular economy for data infrastructure for web3 and beyond.
Lava documentation is intended to be the definitive reference for all technical aspects of Lava Protocol. For other information about Lava Network, please visit our [blog](https://www.lavanet.xyz/blog?utm_source=intro-page&utm_medium=docs) or review our new [research](https://community.lavanet.xyz/c/research/9?utm_source=intro-page&utm_medium=docs)!
@@ -29,7 +29,7 @@ Lava documentation is intended to be the definitive reference for all technical
[](/chains)
-[](/access-intro)
+[](/developer)
[](/validator)
diff --git a/docs/intro/key-terms.md b/docs/intro/key-terms.md
index 669a9e59..5d2ba107 100644
--- a/docs/intro/key-terms.md
+++ b/docs/intro/key-terms.md
@@ -9,7 +9,7 @@ title: π Key Terms
Lava Network
- A marketplace for blockchain data, driven by open-source software and protocols, aiming for data accessibility and availability.
+ A marketplace for blockchain data, driven by open-source software and protocols, aiming for modular peer-to-peer data accessibility and availability.
@@ -19,7 +19,7 @@ title: π Key Terms
Token (LAVA)
- LAVA is the native digital asset of the Lava Network, central to its economic model.
+ LAVA is the native digital asset of the Lava Network, central to its economic model. It serves multiple purposes within the network, including as a means to pay for gas fees required for transactions, a governance token allowing holders to participate in network decisions, and as rewards distributed to validators, providers, and contributors.
@@ -27,6 +27,11 @@ title: π Key Terms
The decentralized decision-making process in Lava Network, where token holders have control over key aspects.
+
+ Specifications
+ Modular blueprints for Lava's multichain and multi-API support, defining chain and method requirements, costs, and verifications. Specs are the minimum module necessary for Lava API support.
+
+
## π° Subscriptions and Plans
@@ -88,7 +93,7 @@ title: π Key Terms
SDK
- A JavaScript-based tool that simplifies the process of sending data relays to providers, offering compatibility with various development environments.
+ A JavaScript/TypeScript package that simplifies the process of sending data relays to providers, offering compatibility with various development environments.
@@ -108,6 +113,10 @@ title: π Key Terms
A web application providing insights into the Lava protocol, including data on relays, Compute Unit (CU) usage, provider statistics, and more.
+
+ Server Kit
+
+
## ποΈ Badges, Pairing, and Rewards
@@ -123,4 +132,32 @@ title: π Key Terms
Rewards
In LAVA tokens, these incentivize honest participation in the Lava Network, distributed to validators, providers, and contributors for their contributions and services.
+
+
+## Accounts & Wallets
+
+
+Keyring
+The keyring holds the private/public keypairs used to interact with a node. For instance, a validator key needs to be set up before running the blockchain node, so that blocks can be correctly signed. The private key can be stored in different locations, called "backends", such as a file or the operating system's own key storage. (learn more here)
+
+
+
+Keypair
+
+A keypair in the context of the Lava Network consists of two essential components: a public key and a private key. This cryptographic pair is crucial for securing accounts and authorizing transactions within the Lava ecosystem.
+
+
+
+Public Key
+A public key is a cryptographic key that is openly shared and used for various purposes, including encrypting data, verifying digital signatures, and establishing secure communication within the Lava Network. It is one half of a key pair, with the other half being the private key. Public keys are essential for securing Lava assets, verifying transactions, and ensuring data integrity.
+
+Example Key: `lava@16g2y9l2zj5yrwcftd6lrwepnhjnl0f2gd70tjg`
+
+
+
+
+Private Key
+In the Lava Network, a private key is a highly confidential and secret cryptographic key that forms a key pair with a corresponding public key. The private key is used for critical tasks such as decrypting data, signing transactions, and providing access to Lava assets and sensitive information. It should be securely stored and never shared publicly, as it grants full control and ownership over cryptographic assets and secure communications.
+
+Example Key: (`64 character hexadecimal string`)
\ No newline at end of file
diff --git a/docs/specs/add-spec.md b/docs/intro/specs/add-spec.md
similarity index 98%
rename from docs/specs/add-spec.md
rename to docs/intro/specs/add-spec.md
index 4778bcca..bb0f107e 100644
--- a/docs/specs/add-spec.md
+++ b/docs/intro/specs/add-spec.md
@@ -1,6 +1,6 @@
---
slug: /add-spec
-title: New Spec
+title: Adding Specifications π§
---
# Adding a Specification to Lava
diff --git a/docs/specs/spec-reference.md b/docs/intro/specs/spec-reference.md
similarity index 99%
rename from docs/specs/spec-reference.md
rename to docs/intro/specs/spec-reference.md
index b7ec0047..781aeba9 100644
--- a/docs/specs/spec-reference.md
+++ b/docs/intro/specs/spec-reference.md
@@ -1,6 +1,6 @@
---
slug: /spec-reference
-title: Reference
+title: Reference Guide π
---
# Spec Reference Guide
diff --git a/docs/specs/spec.md b/docs/intro/specs/spec.md
similarity index 99%
rename from docs/specs/spec.md
rename to docs/intro/specs/spec.md
index 27f02127..d8f998c7 100644
--- a/docs/specs/spec.md
+++ b/docs/intro/specs/spec.md
@@ -143,7 +143,7 @@ The following is a snippet of the `debug` add-on for our `ETH1` spec:
### Extensions γ°οΈ
-`"extensions"` allow for the adjustment or enhancement of existing methods and APIs within a spec for special use cases. They provide the means to tweak, optimize, or expand current functions based on the needs of a subset of consumers who require more functionality from specified method calls. This allows for alternative functionalities to be outlined inside a spec, giving both providers and consumers flexibility to
+`"extensions"` allow for the adjustment or enhancement of existing methods and APIs within a spec for special use cases. They provide the means to tweak, optimize, or expand current functions based on the needs of a subset of consumers who require more functionality from specified method calls. This allows for alternative functionalities to be outlined inside a spec, giving both providers and consumers flexibility to serve / request special functions.
Example
diff --git a/docs/lava-blockchain/wallet.mdx b/docs/lava-blockchain/wallet.mdx
index 3ca6ebf4..273cf7f6 100644
--- a/docs/lava-blockchain/wallet.mdx
+++ b/docs/lava-blockchain/wallet.mdx
@@ -195,7 +195,7 @@ This section is intended for advanced users.
The CLI wallet provides various backends, including support for hardware wallets.
## Account Preparation using CLI {#account}
-Choose your preferred keyring backend ([FAQ: what is a keyring](/faq#keyring)).
+Choose your preferred keyring backend... ([What is a keyring?](/key-terms#accounts--wallets)).
```bash
lavad config keyring-backend [os|file|kwallet|pass|test|memory]
```
diff --git a/docs/provider/improve-QoS-and-jailing.md b/docs/provider/improve-QoS-and-jailing.md
deleted file mode 100644
index b21a3018..00000000
--- a/docs/provider/improve-QoS-and-jailing.md
+++ /dev/null
@@ -1,180 +0,0 @@
----
-slug: /provider-QoS
-title: Improve QoS and jailing
----
-
-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
-# How To improve your rewards
-
- After staking on chain, providers serve consumers and get cryptographic proofs of relay service. these proofs are sent on chain to accumulate CUs that lead to token rewards. these rewards are mostly affected by 3 factors:
- * Passable Quality of Service - directly affect rewards in a given session
- * Excellence Quality of Service - affect provider selection both within a pairing and in the pairing probabilities
- * Jail - prevents a provider from giving service for a period of time
-
-# improving Passable Quality of Service
-Passable Quality of Service is scored separately in each relay session. lower scores mean lower rewards up to half the accumulated CU can be reduced for bad service.
-Passable QoS metrics can be viewed both in the info explorer and prometheus metrics
-Passable QoS is binary, either it's good or bad there is no in-between. scores in the range `0-1` are a result of averaging that binary score across relays.
-
-## metrics
-Passable Quality of score divides into 3 metrics:
-* Availability
-* Sync/ Freshness of data
-* Latency
-## Availability
-score `0 or 1` per relay, averaged across relays to give a range `0-1`. 0 is given for a failed relay.
-lower availability score can be the result of failed relays by one of the following:
-
-### causes
-* time out - the provider does not respond in the maximum allowed time, and the consumer gives up
-```
-can be checked in the provider logs, requests that time out are also identified by the provider and terminated
-```
-* unsupported chain - the provider runs with disabled chains
-```
-can be checked in the provider initialization logs and on the request logs, also on the prometheus metrics for disabled chains
-```
-* errors - any lava error, whether unscyned epoch in the provider, wrong wallet, misconfigured url
-```
-can be checked in the provider logs, and prometheus metrics for disabled chains
-```
-### how to improve
-find the cause of the error, and take the necessary actions to resolve them
-* add more endpoints
-```
-lava supports setting more than one endpoint, and consumers know to loadbalance in case one is down, by setting several endpoints (with several services) providers can avoid downtime
-```
-
-## Latency
-score `0 or 1` per relay, averaged across relays to give a range `0-1`. 0 is given for a relay that took above half the timeout.
-lower latency score can be the result of slow responses, and can be identified by turning on debug logs in the provider to see the latency or checking prometheus.
-
-### How To Improve
-* activate lavap cache
-```
-caching can boost up performance and latency at the expense of some memory, if you didn't set a valid cache configuration it would reduce latency scores
-```
-* set the provider service in proximity to the node
-```
-a provider service that is located in the same server or vpc as the node will provide the best latency, while a provider that has to go through TLS and connect to a different location will have increased latency
-```
-* set the correct geolocation
-```
-lava matches consumers and providers based on geolocation, if your services do not cover several locations with several nodes, it is recommended to set geolocations that are in proximity to your provider service and node.
-if you misconfigure geolocations that are far from your node's location, your latency scores will be lower
-```
-* reduce server load or improve the machine
-```
-servers that receive too much usage to the machine capabilities will respond slower, it is recommended to monitor CPU, networking and memory usage
-```
-* add more endpoints
-```
-lava supports setting more than one endpoint, and consumers know to pick the closest one, by setting more endpoints latency scores will be lower
-```
-
-## Sync/freshness
-score `0 or 1` per relay, averaged across relays to give a range `0-1`. 0 is given for a relay that has a latest block proof that is older than the spec allowed block lag for QoS sync.
-
-### how to identify
-the freshness proofs are updated by the provider service in a GET_BLOCKNUM request, and then returned together with consumer relay responses.
-it is possible to turn on debug logs and see the blocks advancing.
-the latest block is exported in prometheus, and also uploaded on chain.
-you can compare the latest block on your provider to other providers, a useful way to do this is filter provider_latest_block_report and compare your results to others
-```bash
-lavap test events 2000 --event lava_provider_latest_block_report --node https://public-rpc-testnet2.lavanet.xyz:443/
-```
-
-### How To Improve
-* provider state is not updating fast enough
-```
-make sure GET_BLOCKNUM requests do not fail, common problems are throttling, or a url misconfiguration
-```
-* latest block is too old
-```
-some nodes can lose sync and return stale data, it is imperative to monitor these cases and fix them, making sure the node is synced
-```
-
-# improving Excellence Quality of Service
-calculated very similarly to Passable QoS, Excellence QoS provides a range of scores that are time weighted to take the latest information
-all the actions mentioned here to improve passable QoS affect excellence
-
-## metrics
-Excellence Quality of score divides into 3 metrics:
-* Availability - score in the range `0-1`
-* Sync/ Freshness of data - how much time behind other providers are we, lower is better, 0 means your sync is the best in the pairing
-* Latency - how many benchmark ticks passed during a relay in average (time taken / benchamrk time). lower is better
-
-# How to fix getting jailed
-lava protocol removes providers that are providing inferior service. the mechanism is detached from QoS measurements.
-in order to be jailed a provider needs to avoid the following
-* have the staked endpoint not respond to connections
-* have disabled chains in the staked endpoint
-* have too many consecutive errors with a large group of consumers
-* have a non TLS connection or an exired certificate
-* block headers or origins
-* miss on getting rewards
-
-## how jailing happens
-lava's blockchain jails a provider if:
-* there are enough other providers in the spec
-* the provider is not frozen (if you freeze for maintenance you will not get jailed)
-* the provider is active for at least 8 epochs
-* in the last 8 epohs the provider got less sum of rewards than reports sum in the last 2 epochs
-
-## identify getting jailed
-if your provider got jailed it will immediately upon the next epoch stop receiving requests.
-
-it is possible to monitor this event via info webpage or the following command:
-when being reported before getting jailed:
-```bash
-lavap test events 2000 --event lava_provider_reported --node https://public-rpc-testnet2.lavanet.xyz:443/
-```
-a group of reports can lead to being jailed.
-
-when the blockchain's criteria for jail are met:
-```bash
-lavap test events 2000 --event lava_provider_jailed --node https://public-rpc-testnet2.lavanet.xyz:443/
-```
-
-## resuming service
-since version 0.27.0, providers that are jailed can resume service by unfreezing.
-it is planned to have a cooldown period on unfreezing, if repeated jails are activated in a short period
-```bash
-lavad tx pairing unfreeze --help
-```
-
-## understanding the jail reason
-jail reports contain additional info on the report reason and they can be either due to:
-* disconnections - provider did not respond to connection attempts
-* errors - provider's responses were a sequence of consecutive errors
-in addition the reports contain an exact time tag, so the provider can check the events
-```bash
-lavap test events 2000 --event lava_provider_reported --node https://public-rpc-testnet2.lavanet.xyz:443/
-```
-
-### disconnections
-these mean the provider's endpoint did not respond and can be due to the following problems
-* TLS certificate outdated or not set
-* misconfiguration proxying the requests to the provider service
-* provider service not running
-* wrong endpoint in the stake entry on chain: can be fixed by running
-```bash
-lavad tx pairing modify-provider ${CHAIN} --endpoints "${ENDPOINTS}" --geolocation ${GEOLOCATION} --from ${WALLET}
-```
-** make sure the url in the endpoint is the provider grpc listening address and not your node url **
-
-** Disconnection problems can be identified by running the test command **
-```bash
-lavap test rpcprovider ${PUBLIC_ADDRESS}
-```
-
-### errors
-these mean the provider service connection was solid but all relays turned to be errors, might be caused by the following:
-* disabled chain - the provider doesnt have access to the node, or a verification does not pass, and the chain is disabled
-* unexpected errors
-* timeouts
-
-** errors can be identified by looking at the provider service logs, it is recommended to run with debug if repeatedly getting jailed **
-
diff --git a/docusaurus.config.js b/docusaurus.config.js
index f69a3662..6bff4abc 100644
--- a/docusaurus.config.js
+++ b/docusaurus.config.js
@@ -133,7 +133,7 @@ const config = {
{
label: "Web3 APIs β‘οΈ",
position: "left",
- to: "access-intro",
+ to: "developer",
},
{
label: "Lava Protocol π",
diff --git a/sidebars.js b/sidebars.js
index e2d03dff..12d73e6d 100644
--- a/sidebars.js
+++ b/sidebars.js
@@ -16,6 +16,20 @@ const sidebars = {
'intro/about',
'intro/explorers',
'intro/key-terms',
+ {
+ type: 'category',
+ label: 'ποΈ Specifications',
+ collapsible: true,
+ collapsed: true,
+ link: {
+ type: 'doc',
+ id: 'intro/specs/spec'
+ },
+ items: [
+ 'intro/specs/add-spec',
+ 'intro/specs/spec-reference'
+ ]
+ },
'intro/faq'
]
},
@@ -231,7 +245,7 @@ const sidebars = {
label: 'Developers π»',
link: {
type: 'doc',
- id: 'developers/developer-intro'
+ id: 'developer/developer'
},
collapsible: true,
collapsed: true,
@@ -243,10 +257,10 @@ const sidebars = {
collapsed: true,
link: {
type: 'doc',
- id: 'developers/gateway/gateway-access'
+ id: 'developer/gateway/gateway-access'
},
items: [
- 'developers/gateway/gateway-getting-started',
+ 'developer/gateway/gateway-getting-started',
]
},
{
@@ -256,7 +270,7 @@ const sidebars = {
collapsed: true,
link: {
type: 'doc',
- id: 'developers/server-kit/access-server-kit'
+ id: 'developer/server-kit/access-server-kit'
},
items: []
},
@@ -267,12 +281,12 @@ const sidebars = {
collapsed: true,
link: {
type: 'doc',
- id: 'developers/sdk/access-sdk'
+ id: 'developer/sdk/access-sdk'
},
items: [
- 'developers/sdk/sdk-getting-started',
- 'developers/sdk/sdk-backend',
- 'developers/sdk/sdk-frontend',
+ 'developer/sdk/sdk-getting-started',
+ 'developer/sdk/sdk-backend',
+ 'developer/sdk/sdk-frontend',
{
type: 'category',
label: 'Examples π‘',
@@ -282,9 +296,10 @@ const sidebars = {
type: 'generated-index'
},
items: [
- 'developers/sdk/examples/sdk-multichain-example',
- 'developers/sdk/examples/lava-sdk-gallery',
- 'developers/sdk/examples/lava-bazaar',
+ 'developer/sdk/examples/sdk-multichain-example',
+ 'developer/sdk/examples/lava-sdk-gallery',
+ 'developer/sdk/examples/lava-bazaar',
+ 'developer/sdk/examples/all-blocks-app'
]
},
]
@@ -296,30 +311,29 @@ const sidebars = {
collapsed: true,
link: {
type: 'doc',
- id: 'developers/integrations/sdk-integrations'
+ id: 'developer/integrations/sdk-integrations'
},
items: [
- 'developers/integrations/cosmjs',
- 'developers/integrations/ethersjs5',
- 'developers/integrations/ethersjs6',
- 'developers/integrations/viem',
- 'developers/integrations/web3js'
+ 'developer/integrations/cosmjs',
+ 'developer/integrations/ethersjs5',
+ 'developer/integrations/ethersjs6',
+ 'developer/integrations/viem',
+ 'developer/integrations/web3js'
]
},
- {
- type: 'category',
- label: 'ποΈ Specifications',
- collapsible: true,
- collapsed: true,
- link: {
- type: 'doc',
- id: 'specs/spec'
- },
- items: [
- 'specs/add-spec',
- 'specs/spec-reference'
- ]
- },
+ {
+ type: 'category',
+ label: 'π« Endpoints',
+ collapsible: true,
+ collapsed: true,
+ link: {
+ type: 'doc',
+ id: 'developer/endpoints/iprpc'
+ },
+ items: [
+ 'developer/endpoints/public-rpc',
+ 'developer/endpoints/iprpc']
+ }
]
},
{
@@ -399,19 +413,6 @@ const sidebars = {
'lava-blockchain/badge-server'
]
},
- {
- type: 'category',
- label: 'Get RPC / Web3 APIs β‘οΈ',
- collapsible: true,
- collapsed: true,
- link: {
- type: 'doc',
- id: 'access-intro'
- },
- items: [
- 'public-rpc',
- ],
- },
`tutorials`,
{
type: 'link',
diff --git a/static/img/chains/near_call.webm b/static/img/chains/near_call.webm
new file mode 100644
index 00000000..75655b9e
Binary files /dev/null and b/static/img/chains/near_call.webm differ
diff --git a/static/img/tutorial/sdk/demo_app/all_blocks_ui.png b/static/img/tutorial/sdk/demo_app/all_blocks_ui.png
new file mode 100644
index 00000000..9f953d84
Binary files /dev/null and b/static/img/tutorial/sdk/demo_app/all_blocks_ui.png differ