-
Notifications
You must be signed in to change notification settings - Fork 3
/
Copy pathgetFAQ.tsx
1315 lines (1287 loc) · 91 KB
/
getFAQ.tsx
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
import React from "react";
import { UrlObject } from "url";
interface IGetFAQ {
LinkComponent: React.ComponentType<{
href: string | UrlObject;
children: React.ReactNode;
style?: React.CSSProperties;
}>;
siteMap: { EXTERNAL: { DOCS: { INDEX: string } } };
}
export const getFAQ = ({ LinkComponent, siteMap }: IGetFAQ) => {
const DocsLink: React.FC = () => (
<LinkComponent
href={siteMap.EXTERNAL.DOCS.INDEX}
style={{ textDecoration: "underline" }}
>
documentation
</LinkComponent>
);
const BOBA = {
what: `RPC in Boba Network enables seamless interaction with the Layer 2 solution, allowing developers to query data and execute transactions efficiently.`,
why: `Boba Network utilizes RPC to provide external access to its Layer 2 solution, enabling developers to integrate Boba into their Web3 projects effortlessly.`,
how: (
<>
Using Boba Network RPC involves sending requests to a Boba node through
an RPC API. dRPC offers efficient and reliable Boba ETH RPC and Boba BNB
RPC endpoints for seamless communication with the Boba Network,
empowering developers to build scalable and secure Web3 applications.
Learn more from dRPC‘s {DocsLink}.
</>
),
};
const FAQ_BY_NETWORK = {
"gelato-orbit-anytrust": {
what: `Gelato Orbit Anytrust RPC refers to the protocol used for interfacing with the Gelato blockchain network. It allows external applications to communicate with Gelato, facilitating various operations such as querying data and executing transactions.`,
why: `Gelato Orbit Anytrust RPC offers fast, secure, and scalable access to Gelato's blockchain network. It enables developers to build efficient and reliable Web3 applications while leveraging Gelato's innovative features and capabilities.`,
how: (
<>
Using Gelato Orbit Anytrust RPC involves connecting to a Gelato node
through an RPC API. Developers can send requests to the Gelato network
using various tools and programming libraries. dRPC provides
accessible Gelato Gelato Orbit Anytrust RPC endpoints, ensuring
seamless integration and data interaction for developers and users.
Learn more from dRPC‘s {DocsLink}.
</>
),
},
"gelato-op-celestia": {
what: `RPC in Gelato OP Celestia refers to the protocol used for interacting with the Celestia blockchain network. It enables external applications to communicate with the network, facilitating data retrieval and transaction processing.`,
why: `Gelato OP Celestia utilizes RPC to provide external access to its blockchain network. This enables applications to interact with the network, query data, and perform transactions, supporting the development and adoption of decentralized applications.`,
how: (
<>
Using Gelato OP Celestia RPC involves connecting to a Celestia node
through an RPC API. dRPC offers Gelato OP Celestia RPC endpoints,
providing reliable data access and integration for Web3 applications,
supporting scalability and innovation in the decentralized ecosystem.
Learn more from dRPC‘s {DocsLink}.
</>
),
},
dymension: {
what: `RPC in Dymension facilitates interaction with the Dymension blockchain network, allowing external applications to communicate with RollApps and access decentralized data efficiently.`,
why: `Dymension employs RPC to provide external access to its modular blockchain network, enabling seamless communication between applications and RollApps for scalable decentralized solutions.`,
how: (
<>
Using Dymension RPC involves connecting to a Dymension node through an
RPC API. dRPC offers reliable Dymension RPC endpoints, ensuring smooth
integration and access to decentralized data for Web3 applications.
Learn more from dRPC‘s {DocsLink}.
</>
),
},
playnance: {
what: `RPC in Playnance facilitates communication between external applications and the Playnance Web3 ecosystem. It allows for efficient data retrieval and interaction, enhancing the functionality of Playnance's platforms.`,
why: `Playnance utilizes RPC to provide external access to its Web3 iGaming platforms. It enables seamless interaction with player accounts, game data, and financial transactions, enhancing the user experience and platform functionality.`,
how: (
<>
To leverage Playnance RPC, developers can connect to dRPC's RPC
endpoints using various tools and programming libraries. This allows
for efficient communication with the Playnance Web3 ecosystem,
facilitating integration with gaming platforms and financial services.
Learn more from dRPC‘s {DocsLink}.
</>
),
},
near: {
what: `RPC in NEAR refers to Remote Procedure Call, a protocol used for interacting with the NEAR blockchain. It enables external applications to communicate with the network, facilitating data retrieval and transaction processing.`,
why: `NEAR utilizes RPC to provide external access to its high-performant blockchain network. It enables developers and users to interact with NEAR's ecosystem, facilitating operations such as querying data, submitting transactions, and interacting with smart contracts.`,
how: (
<>
To use NEAR RPC, developers can send requests to a NEAR node through
an RPC API. dRPC offers NEAR RPC endpoints for seamless communication
with the NEAR blockchain, ensuring reliability and efficiency in data
interaction and integration. Learn more from dRPC‘s {DocsLink}.
</>
),
},
polygon: {
what: "RPC in Polygon stands for Remote Procedure Call, a protocol enabling external applications to interact with the Polygon network. It's essential for requesting data and performing transactions efficiently on Polygon's blockchain.",
why: `Polygon leverages RPC to facilitate external access and interaction with its Layer-2 network. This allows for operations like data queries, transaction processing, and smart contract interactions, supporting the overall scalability and efficiency of the network.`,
},
arbitrum: {
what: "RPC in Arbitrum refers to the Remote Procedure Call protocol used for interacting with the Arbitrum Layer-2 network. It allows external applications to communicate with the Arbitrum blockchain, enabling data requests and transaction processing.",
why: `Arbitrum uses RPC to offer efficient, external connectivity to its Layer-2 network. This enables streamlined interactions with smart contracts and facilitates operations like querying data and processing transactions, enhancing the scalability and accessibility of the Arbitrum network.`,
},
solana: {
what: `RPC in Solana is a protocol used for interfacing with the Solana blockchain. It allows external applications to communicate with the network, making it possible to query data, submit transactions, and interact with smart contracts efficiently.`,
why: `Solana employs RPC to provide external access to its high-speed blockchain network. It facilitates a range of operations including querying blockchain information, executing transactions, and smart contract interactions, essential for developers and users in the Solana ecosystem.`,
},
ethereum: {
what: `RPC in Ethereum, which stands for Remote Procedure Call, is a communication protocol used for interacting with the Ethereum blockchain. It allows external applications to request data from, and perform actions on, the Ethereum network, typically using the JSON-RPC format.`,
why: `Ethereum uses RPC to facilitate external access to its blockchain. It enables applications to perform operations like querying blockchain data, sending transactions, and interacting with smart contracts, without running a full node. This approach promotes decentralization and accessibility of the Ethereum network.`,
},
optimism: {
what: `RPC in Optimism is a protocol that enables direct communication with the Optimism Layer 2 network, allowing users and applications to interact with the blockchain more efficiently, especially for executing transactions and querying data.`,
why: `RPC is crucial in Optimism as it facilitates smoother and more efficient interactions with the Ethereum blockchain. It allows for the execution of smart contracts and transactions at a significantly reduced cost and higher speed, enhancing the overall scalability of Ethereum.`,
how: (
<>
To use Optimism RPC, connect to an Optimism node via RPC API calls.
These calls can be made through programming libraries or tools
designed for blockchain connectivity. dRPC offers accessible Optimism
RPC endpoints to ensure seamless communication with the Optimism
network for developers and users. Learn more from dRPC‘s{" "}
{DocsLink}.
</>
),
},
zksync: {
what: `RPC in zkSync is a protocol that enables direct interaction with the zkSync layer 2 network. It allows for efficient communication with the Ethereum blockchain, providing faster and more cost-effective transactions.`,
why: `zkSync uses RPC to streamline external access to its layer 2 scaling solution, facilitating smoother and more efficient interactions with Ethereum-based applications and services.`,
},
base: {
what: `Base RPC refers to the fundamental Remote Procedure Call infrastructure that facilitates core interactions with blockchain networks. It is crucial for executing basic blockchain operations, including data retrieval and transaction processing.`,
why: `Base uses RPC to offer efficient, external connectivity to its Layer-2 network. This enables streamlined interactions with smart contracts and facilitates operations like querying data and processing transactions, enhancing the scalability and accessibility of the Base network.`,
},
bitcoin: {
what: `Bitcoin RPC is a protocol enabling external applications to interact with the Bitcoin network. It allows for querying blockchain data, executing transactions, and managing wallets, enhancing the functionality and accessibility of Bitcoin.`,
why: `RPC is crucial in Bitcoin for providing a standardized way for external software to communicate with the Bitcoin network, facilitating a wide range of operations essential for users and developers within the Bitcoin ecosystem.`,
how: (
<>
To use Bitcoin RPC, you can connect through dRPC's endpoints to
the Bitcoin network. This connection enables efficient management of
Bitcoin transactions and access to blockchain data, making it a
valuable tool for developers and blockchain enthusiasts. Learn more
from dRPC's {DocsLink}.
</>
),
},
fantom: {
what: `RPC in Fantom refers to the Remote Procedure Call protocol, which allows for direct communication with the Fantom blockchain. It enables external applications to interact seamlessly with the network, facilitating data queries, transactions, and smart contract operations.`,
why: `Fantom utilizes RPC to enhance its network accessibility and functionality. This protocol allows for efficient interaction with the blockchain, making it ideal for a range of applications from decentralized finance to general data retrieval.`,
how: (
<>
To use Fantom RPC, you can connect to a Fantom node via RPC API. This
involves sending structured requests, usually in JSON-RPC format. dRPC
offers reliable Fantom RPC endpoints, simplifying the process for
users and developers to interact with the Fantom network effectively.
Learn more from dRPC‘s {DocsLink}.
</>
),
},
cronos: {
what: `RPC in Cronos is a protocol enabling external applications to interact with the Cronos blockchain. It allows for querying blockchain data, executing transactions, and managing smart contracts, vital for streamlined network operations.`,
why: `Cronos utilizes RPC to facilitate easy access to its blockchain, ensuring developers and applications can seamlessly connect, query, and transact on the network. This approach enhances the usability and efficiency of the Cronos ecosystem.`,
how: (
<>
To use Cronos RPC, connect to a Cronos node via RPC API. These
connections can be made through various programming libraries and
tools, allowing for smooth communication with the Cronos blockchain.
dRPC provides reliable Cronos RPC endpoints, optimizing your
blockchain interactions. Learn more from dRPC‘s {DocsLink}.
</>
),
},
bsc: {
what: `RPC in BNB refers to the protocol used for interacting with the Binance Smart Chain. It enables applications to connect to the blockchain, facilitating transactions and smart contract operations efficiently.`,
why: `RPC plays a crucial role in BNB by enabling seamless interaction with the Binance Smart Chain. It allows for efficient and secure communication, essential for developers and businesses leveraging the blockchain's capabilities.`,
how: (
<>
To connect to BNB using RPC, utilize dRPC‘s BNB RPC endpoints.
These endpoints enable direct and reliable communication with the
Binance Smart Chain, ensuring high-speed transactions and access to
blockchain services. Learn more from dRPC‘s {DocsLink}.
</>
),
},
avalanche: {
what: `RPC in Avalanche refers to the Remote Procedure Call protocol, facilitating interaction with the Avalanche network. It allows external applications to communicate with Avalanche for data queries, transaction execution, and smart contract operations.`,
why: `Avalanche employs RPC to enhance its accessibility and functionality, allowing for streamlined interaction with its high-speed blockchain. It is essential for efficient DApp development, data retrieval, and transaction processing on the Avalanche platform.`,
how: `To utilize Avalanche RPC, connect to an Avalanche node via an RPC API.
This involves sending formatted requests using tools or programming
libraries, which dRPC provides to ensure seamless and reliable access to
Avalanche's capabilities.`,
},
gnosis: {
what: `RPC in Gnosis stands for Remote Procedure Call, a protocol enabling interaction with the Gnosis blockchain. It allows for querying data and executing transactions in the Gnosis ecosystem, facilitating efficient and reliable blockchain operations.`,
why: `RPC plays a vital role in Gnosis by enabling external applications to interact with its blockchain. It simplifies the process of accessing blockchain data and executing smart contracts, thereby enhancing the utility and accessibility of the Gnosis platform.`,
how: (
<>
To use Gnosis RPC, connect to a Gnosis node via RPC API. This
connection can be established using tools like dRPC‘s endpoints,
offering a streamlined and secure way to interact with the Gnosis
blockchain for various applications. Learn more from dRPC‘s{" "}
{DocsLink}.
</>
),
},
starknet: {
what: `RPC in Starknet facilitates interaction with its ZK-Rollup technology, enabling applications to communicate with the Starknet network. It supports various operations like querying data, processing transactions, and interacting with smart contracts.`,
why: `Starknet employs RPC to ensure smooth access and functionality for its decentralized network. This protocol is key to managing complex computations and transactions on Starknet, enhancing its scalability and user accessibility.`,
how: (
<>
To use Starknet RPC, developers connect to Starknet nodes using RPC
API calls. These calls can be made through different tools and
programming libraries, with dRPC providing reliable endpoints for
efficient Starknet network communication. Learn more from dRPC‘s{" "}
{DocsLink}.
</>
),
},
moonbeam: {
what: `RPC in Moonbeam facilitates interaction with the Moonbeam network, allowing applications to communicate effectively with this Ethereum-compatible blockchain on Polkadot for diverse operational needs.`,
why: `Moonbeam RPC is crucial for developers seeking to leverage Moonbeam's Ethereum compatibility and Polkadot's scalability, offering a bridge for efficient and secure blockchain interactions.`,
how: (
<>
To connect to Moonbeam RPC, utilize dRPC‘s endpoints, which
provide a reliable and easy-to-use interface for interacting with
Moonbeam’s network, ensuring smooth and secure operations. Learn more
from dRPC‘s {DocsLink}.
</>
),
},
"polygon-zkevm": {
what: `Polygon zkEVM RPC refers to the Remote Procedure Call interface for Polygon's zkEVM, a Layer 2 solution blending ZK-Rollups with Ethereum's EVM. It facilitates efficient, secure interactions between applications and the Polygon network.`,
why: ` Utilizing Polygon zkEVM RPC offers enhanced scalability and reduced transaction costs for Ethereum-based dApps. It is ideal for developers seeking to leverage Ethereum's ecosystem with the added efficiency of Polygon's zkEVM technology.`,
how: (
<>
Connecting to Polygon zkEVM RPC is done via dRPC‘s endpoints,
enabling developers to interact with the Polygon network through a
robust and user-friendly interface, suitable for a wide range of
decentralized applications. Learn more from dRPC‘s {DocsLink}.
</>
),
},
klaytn: {
what: `Kaia RPC enables seamless interactions with the Kaia blockchain, allowing external applications to access and transact on its network efficiently.`,
why: `Kaia RPC is the key to leveraging Kaia's high throughput and low latency for robust blockchain applications, making it ideal for enterprise solutions.`,
how: (
<>
Accessing Kaia RPC is simple with dRPC‘s endpoints, offering a
straightforward way for applications to engage with Kaia’s blockchain
technology. Learn more from dRPC‘s {DocsLink}.
</>
),
},
aurora: {
what: `Pioneered as an EVM on the NEAR Protocol, Aurora RPC is a protocol enabling efficient interaction with the Aurora blockchain, ensuring developers can leverage its high-throughput, scalable environment with ease.`,
why: `Aurora's use of RPC is integral for its operation as an Ethereum-compatible platform. It enables seamless application interactions, ensuring developers can utilize Aurora's advanced features like its fast transaction finalization and scalability.`,
how: (
<>
Accessing Aurora RPC involves connecting to the Aurora network using
RPC endpoints. dRPC provides these endpoints, ensuring efficient
communication with Aurora for operations like data requests and smart
contract interactions. Learn more from dRPC‘s {DocsLink}.
</>
),
},
linea: {
what: `RPC in Linea stands for Remote Procedure Call, a protocol allowing for seamless interaction with the Linea network. It supports both existing Ethereum applications and the development of new, more efficient solutions.`,
why: `Linea uses RPC to ensure developers can easily access its network, fostering an environment where applications can scale beyond the limitations of Ethereum Mainnet. This accessibility is crucial for the evolution and expansion of blockchain applications.`,
how: (
<>
To utilize Linea RPC, developers connect through RPC endpoints to
interact with the Linea network. dRPC offers these endpoints, enabling
straightforward, secure, and fast communication for deploying and
managing applications. Learn more from dRPC‘s {DocsLink}.
</>
),
},
"arbitrum-nova": {
what: `Arbitrum Nova RPC is a set of interfaces for interacting with the Arbitrum Nova chain, designed to facilitate ultra-low fee transactions and efficient data handling through its unique AnyTrust model. dRPC provides seamless access to these endpoints, enhancing blockchain connectivity.`,
why: `Choosing Arbitrum Nova for RPC operations means benefiting from its groundbreaking approach to minimizing transaction fees while ensuring high data availability and security. dRPC's Arbitrum Nova RPC endpoints are tailored to support this, offering a competitive edge in blockchain development.`,
how: (
<>
Connecting to Arbitrum Nova RPC involves utilizing dRPC‘s
specialized endpoints, which enable direct communication with the Nova
network. This connection facilitates various operations, from querying
blockchain data to executing transactions, all with the advantage of
Arbitrum Nova's low-cost structure. Learn more from dRPC‘s{" "}
{DocsLink}.
</>
),
},
harmony: {
what: `RPC in Harmony allows developers to interact with the Harmony blockchain, enabling the execution of smart contracts, transactions, and data queries through a straightforward API interface.`,
why: `Harmony uses RPC to ensure developers and applications can easily access its blockchain, fostering an environment where building and integration on Harmony are seamless and efficient.`,
how: (
<>
To utilize Harmony RPC, connect via dRPC‘s endpoints. This
grants reliable and fast access to Harmony‘s network,
simplifying operations like smart contract interaction and transaction
processing. Learn more from dRPC‘s {DocsLink}.
</>
),
},
kava: {
what: `RPC in Kava facilitates communication between external applications and the Kava blockchain, allowing for data queries, transaction submission, and smart contract interaction with ease.`,
why: `Kava RPC is essential for developers looking to leverage Kava’s unique blend of Cosmos’s interoperability and Ethereum's extensive developer ecosystem, providing a streamlined interface for robust dApp development.`,
how: (
<>
Accessing Kava RPC is straightforward with dRPC‘s endpoints,
offering developers a reliable and efficient way to connect to the
Kava network for querying data, executing transactions, and more.
Learn more from dRPC‘s {DocsLink}.
</>
),
},
celo: {
what: `RPC in Celo stands for Remote Procedure Call, a protocol that allows external applications to interact with the Celo blockchain, enabling users to perform secure and efficient financial transactions directly from their mobile devices.`,
why: `Celo utilizes RPC to enhance its mobile-first blockchain's accessibility, allowing for straightforward financial operations. This ensures that developers can build user-friendly applications on the Celo network, promoting financial inclusion on a global scale.`,
how: (
<>
To use Celo RPC, developers connect to the Celo network via RPC
endpoints provided by services like dRPC. These endpoints facilitate
communication with the blockchain, allowing for transactions, wallet
interactions, and access to blockchain data, all geared towards mobile
efficiency. Learn more from dRPC‘s {DocsLink}.
</>
),
},
opbnb: {
what: `RPC in opBNB stands for Remote Procedure Call, a protocol enabling external applications to interact with the opBNB blockchain. It allows for efficient data querying, transaction submission, and smart contract operations, making it indispensable for developers building on opBNB.`,
why: `opBNB uses RPC to facilitate seamless communication between external applications and its blockchain, ensuring developers can easily access blockchain data, submit transactions, and interact with smart contracts. This accessibility is crucial for the scalability and functionality of applications within the opBNB ecosystem.`,
how: (
<>
To use opBNB RPC, developers need to connect to an opBNB node through
RPC API calls. These calls can be made using various tools or
libraries tailored to blockchain development. dRPC offers reliable and
scalable opBNB RPC endpoints, simplifying the process for developers
to connect and interact with the opBNB blockchain. Learn more from
dRPC‘s {DocsLink}.
</>
),
},
mantle: {
what: `RPC in Mantle facilitates interaction with the Mantle Network, allowing applications to query data, execute transactions, and interact with smart contracts efficiently through a set of standardized protocols.`,
why: `Mantle utilizes RPC to ensure developers can easily access its EVM-compatible technology stack, enabling fast, secure, and scalable solutions for Ethereum scaling and beyond.`,
how: (
<>
To use Mantle RPC, connect with a Mantle node via dRPC's provided
endpoints. This connection enables you to interact with the Mantle
Network using simple API calls for data retrieval, transaction
submissions, and more. Learn more from dRPC‘s {DocsLink}.
</>
),
},
metis: {
what: `RPC in Metis, standing for Remote Procedure Call, is a critical communication protocol that enables external applications to interact with the Metis Layer 2 network. It allows for efficient querying of blockchain data, transaction submissions, and smart contract deployments.`,
why: `Metis RPC is vital for accessing the enhanced capabilities of the Metis Layer 2 Rollup platform, including improved transaction speeds, reduced costs, and increased scalability. It supports developers in building more efficient and effective Web3 applications on Metis.`,
how: (
<>
To use Metis RPC, developers can connect to dRPC's Metis RPC
endpoints, offering reliable and scalable access to the Metis network.
This connection enables the seamless execution of smart contracts and
transactions, ensuring a high-performance foundation for Web3
projects. Learn more from dRPC‘s {DocsLink}.
</>
),
},
filecoin: {
what: `RPC in Filecoin refers to the Remote Procedure Call protocol used for interacting with the Filecoin network. It enables external applications to communicate with the network, facilitating operations such as querying storage data and submitting storage and retrieval deals.`,
why: `Filecoin utilizes RPC to provide external access to its decentralized storage network. RPC allows applications to interact with the network efficiently, enabling storage providers and clients to access and manage storage deals seamlessly.`,
how: (
<>
Using Filecoin RPC involves sending requests to a Filecoin node
through an RPC API. These requests can be made using various tools and
programming libraries. dRPC provides accessible Filecoin RPC endpoints
for efficient and reliable communication with the Filecoin network.
Learn more from dRPC‘s {DocsLink}.
</>
),
},
fuse: {
what: `RPC in Fuse refers to Remote Procedure Call, a protocol for communication between a client and a server. In the context of Fuse, RPC allows external applications to interact with the Fuse blockchain, facilitating actions such as querying data and executing transactions.`,
why: `Fuse utilizes RPC to enable external access to its blockchain network. This allows developers to build decentralized applications (dApps) and integrate with the Fuse ecosystem efficiently, promoting innovation and adoption in decentralized finance (DeFi) and other Web3 projects.`,
how: (
<>
To use Fuse RPC, developers can send RPC requests to a Fuse node using
the appropriate API. These requests enable interaction with the Fuse
blockchain, including querying data and executing transactions. dRPC
offers reliable and scalable Fuse RPC endpoints, facilitating seamless
integration with Fuse-powered applications. Learn more from
dRPC‘s {DocsLink}.
</>
),
},
taiko: {
what: `RPC in Taiko refers to Remote Procedure Call, a protocol used for communication with the Taiko blockchain network. It enables external applications to request data and perform actions on the Taiko network.`,
why: `Taiko utilizes RPC to provide external access to its blockchain network, allowing developers to interact with smart contracts, query blockchain data, and execute transactions efficiently.`,
how: (
<>
To use Taiko RPC, connect to a Taiko node using RPC API calls. These
calls can be made through various tools or programming libraries. dRPC
offers reliable and decentralized Taiko RPC endpoints for seamless
communication with the Taiko blockchain. Learn more from dRPC‘s{" "}
{DocsLink}.
</>
),
},
astar: {
what: `RPC in Astar zkEVM refers to Remote Procedure Call, a protocol used for communication between client applications and the zkEVM network. It enables querying blockchain data and executing transactions securely and efficiently.`,
why: `Astar zkEVM utilizes RPC to provide external access to its blockchain network. RPC facilitates interaction with smart contracts, querying blockchain data, and submitting transactions, enabling developers to build scalable and privacy-preserving applications on the zkEVM platform.`,
how: (
<>
To use Astar zkEVM RPC, developers can send RPC requests to Astar
zkEVM nodes, either directly or through a service like dRPC. These
requests enable actions such as querying blockchain data and executing
transactions securely and efficiently. Learn more from dRPC‘s{" "}
{DocsLink}.
</>
),
},
berachain: {
what: `RPC in Berachain enables external applications to communicate with the Berachain blockchain, facilitating data retrieval and interaction with smart contracts.`,
why: `Berachain utilizes RPC to offer external access to its blockchain network, allowing for efficient communication and interaction with decentralized applications.`,
how: (
<>
To use Berachain RPC, developers can send requests to a Berachain node
through an RPC API. dRPC provides reliable Berachain RPC endpoints,
ensuring seamless integration with the Berachain blockchain. Learn
more from dRPC‘s {DocsLink}.
</>
),
},
haqq: {
what: `RPC in HAQQ is a communication protocol used for interacting with the HAQQ blockchain. It facilitates external access to the network, allowing for data retrieval, transaction processing, and smart contract interactions.`,
why: `HAQQ utilizes RPC to enable external applications to communicate with its blockchain network. This promotes interoperability and accessibility, facilitating various blockchain functionalities within the HAQQ ecosystem.`,
how: (
<>
To use HAQQ RPC, developers connect to HAQQ nodes using RPC API calls.
These calls can be made through programming libraries or tools,
enabling seamless integration with HAQQ's blockchain network.
dRPC provides efficient HAQQ RPC endpoints for reliable communication
and data interaction. Learn more from dRPC‘s {DocsLink}.
</>
),
},
"immutable-zkevm": {
what: `RPC in Immutable zkEVM is a protocol used for interfacing with the zkEVM-based blockchain. It enables external applications to communicate with the network, facilitating various operations such as querying data and executing transactions efficiently.`,
why: `Immutable zkEVM utilizes RPC to enable external access to its zkEVM-based blockchain network. This allows developers and users to interact with the network, query blockchain data, and execute transactions, promoting decentralization and accessibility.`,
how: (
<>
To use Immutable zkEVM RPC, you can connect to an Immutable zkEVM node
using an RPC API. These requests can be made using various tools and
programming libraries. dRPC offers reliable and scalable Immutable
zkEVM RPC endpoints, ensuring seamless integration with Web3 projects.
Learn more from dRPC‘s {DocsLink}.
</>
),
},
manta: {
what: `RPC in Manta Network is a protocol used to interact with the Manta Network blockchain. It allows external applications to communicate with the network, facilitating various operations such as querying data and interacting with smart contracts.`,
why: `Manta Network utilizes RPC to enable external access to its privacy-focused blockchain network. RPC facilitates efficient communication with the Manta Network, allowing developers and users to interact with decentralized applications and conduct transactions securely.`,
how: (
<>
Using Manta Network RPC involves sending requests to a Manta Network
node through an RPC API. These requests can be made using various
tools and programming libraries. dRPC offers accessible Manta Network
RPC endpoints, ensuring efficient and reliable communication with the
Manta Network blockchain. Learn more from dRPC‘s {DocsLink}.
</>
),
},
okt: {
what: `RPC in OKT Chain, or Remote Procedure Call, is a protocol used for communication between applications and the OKT Chain blockchain. It enables external access to the blockchain, allowing for tasks such as querying data and executing transactions.`,
why: `OKT Chain utilizes RPC to provide external access to its blockchain, enabling interaction with decentralized applications and smart contracts. RPC facilitates the seamless transfer of data and commands between applications and the OKT Chain network.`,
how: (
<>
To use OKT Chain RPC, developers connect to an OKT Chain node through
an RPC API. This allows for tasks such as querying blockchain data and
executing transactions. dRPC offers efficient OKT Chain RPC endpoints
for smooth communication with the OKT Chain network. Learn more from
dRPC‘s {DocsLink}.
</>
),
},
vara: {
what: `RPC in Vara Network is a protocol used for interfacing with the Vara Network blockchain. It allows external applications to communicate with the network, making it possible to query data, submit transactions, and interact with smart contracts efficiently.`,
why: `Vara Network employs RPC to provide external access to its blockchain network. It facilitates a range of operations including querying blockchain information, executing transactions, and smart contract interactions, essential for developers and users in the Vara Network ecosystem.`,
how: (
<>
Using Vara Network RPC involves sending requests to a Vara Network
node through an RPC API. These requests can be made using various
tools and programming libraries. dRPC provides accessible Vara Network
RPC endpoints for efficient and reliable communication with the Vara
Network blockchain. Learn more from dRPC‘s {DocsLink}.
</>
),
},
scroll: {
what: `RPC in Scroll refers to the Remote Procedure Call protocol used for communication with the Scroll blockchain. It enables external applications to interact with the Scroll network, facilitating data retrieval and transaction processing.`,
why: `Scroll utilizes RPC to provide external access to its blockchain network, allowing applications to communicate with the Scroll network efficiently. This promotes seamless integration and interaction with Scroll-based decentralized applications.`,
how: (
<>
To use Scroll RPC, developers can send JSON-RPC formatted requests to
a Scroll node using tools or programming libraries. dRPC offers
convenient and reliable Scroll RPC endpoints for streamlined
communication with the Scroll blockchain. Learn more from dRPC‘s{" "}
{DocsLink}.
</>
),
},
lisk: {
what: `RPC in Lisk is a protocol used for interfacing with the Lisk blockchain. It enables external applications to communicate with the network, facilitating operations such as querying data, submitting transactions, and interacting with smart contracts.`,
why: `Lisk utilizes RPC to provide external access to its blockchain network. This enables developers and users to interact with the Lisk blockchain, execute transactions, and deploy smart contracts, fostering innovation and decentralized applications within the Lisk ecosystem.`,
how: (
<>
To use Lisk RPC, developers can send requests to a Lisk node using RPC
API calls. These requests can be made using various programming
languages and tools. dRPC offers scalable Lisk RPC endpoints, ensuring
reliable and efficient communication with the Lisk blockchain network.
Learn more from dRPC‘s {DocsLink}.
</>
),
},
blast: {
what: `RPC in Blast refers to the Remote Procedure Call protocol used for interacting with the Blast blockchain. It enables external applications to communicate with the Blast network, facilitating data queries and transaction processing.`,
why: `Blast utilizes RPC to provide external access to its blockchain network. This enables developers and users to interact with Blast, facilitating operations such as querying data, executing transactions, and accessing smart contracts.`,
how: (
<>
To use Blast RPC, developers can send RPC requests to a Blast node
using JSON-RPC formatted calls. These requests can be made using
various tools and libraries, allowing seamless integration with the
Blast blockchain. dRPC offers efficient and reliable Blast RPC
endpoints for developers looking to interact with Blast's
blockchain. Learn more from dRPC‘s {DocsLink}.
</>
),
},
evmos: {
what: `RPC in Evmos, known as Remote Procedure Call, enables communication with the Evmos blockchain. It allows external applications to interact with the network, facilitating tasks such as querying data and executing transactions.`,
why: `Evmos utilizes RPC to provide external access to its blockchain network. This enables developers and users to communicate with the network efficiently, supporting functions like accessing blockchain data and executing transactions.`,
how: (
<>
To use Evmos RPC, developers can send RPC requests to an Evmos node
using dRPC APIs. These requests can be made using various programming
languages or tools. dRPC offers Evmos RPC endpoints for seamless
integration and interaction with the Evmos blockchain. Learn more from
dRPC‘s {DocsLink}.
</>
),
},
heco: {
what: `RPC in Heco, short for Remote Procedure Call, facilitates communication with the Heco blockchain. It enables external applications to interact with the network, making it possible to retrieve data and execute transactions.`,
why: `Heco utilizes RPC to offer external access to its blockchain network. This allows applications to interact with smart contracts, retrieve blockchain data, and perform various operations without running a full node, promoting decentralization and accessibility.`,
how: (
<>
To use Heco RPC, developers can connect to a Heco node through RPC API
calls. dRPC provides dedicated Heco RPC endpoints for seamless
integration, enabling efficient communication with the Heco
blockchain. Learn more from dRPC‘s {DocsLink}.
</>
),
},
mode: {
what: `RPC in Mode is a protocol used for interacting with the Mode blockchain. It facilitates communication between external applications and the Mode network, allowing for data retrieval, transaction processing, and smart contract interactions.`,
why: `Mode utilizes RPC to provide external access to its blockchain network, enabling developers to build and scale applications on the Mode platform. It supports various operations such as querying data, executing transactions, and interacting with smart contracts, crucial for developers and users in the Mode ecosystem.`,
how: (
<>
Using Mode RPC involves sending requests to a Mode node through an RPC
API. These requests can be made using various tools and programming
libraries. dRPC offers reliable and efficient Mode RPC APIs, ensuring
seamless communication with the Mode blockchain for developers and
users. Learn more from dRPC‘s {DocsLink}.
</>
),
},
moonriver: {
what: `RPC in Moonriver allows external applications to communicate with the Moonriver blockchain, facilitating data retrieval, transaction processing, and smart contract interactions.`,
why: `Moonriver utilizes RPC to provide external access to its blockchain network, enabling developers and users to interact with the Moonriver ecosystem efficiently.`,
how: (
<>
To use Moonriver RPC, developers can send requests to a Moonriver node
through an RPC API. dRPC offers reliable and efficient Moonriver RPC
APIs, simplifying blockchain integration and data interaction for
developers. Learn more from dRPC‘s {DocsLink}.
</>
),
},
"neon-evm": {
what: `RPC in Neon EVM enables seamless communication between applications and the Neon EVM blockchain. It facilitates data retrieval, transaction processing, and smart contract interactions, enhancing the scalability and accessibility of Ethereum dApps on Solana.`,
why: `Neon EVM utilizes RPC to offer efficient access to its blockchain network. This allows developers to interact with Ethereum dApps on Solana, tapping into the benefits of Solana's high-performance ecosystem while leveraging familiar Ethereum tools and infrastructure.`,
how: (
<>
Using Neon EVM RPC involves connecting to a Neon EVM node through an
RPC API. This allows for seamless integration of Ethereum dApps on
Solana, enabling developers to harness the power of Solana's
vibrant ecosystem with ease. dRPC provides reliable Neon EVM RPC
endpoints for efficient and scalable blockchain connectivity. Learn
more from dRPC‘s {DocsLink}.
</>
),
},
ronin: {
what: `RPC in Ronin is a protocol used for interacting with the Ronin blockchain. It facilitates communication between external applications and the blockchain, enabling actions such as querying data and executing transactions efficiently.`,
why: `RPC in Ronin is a protocol used for interacting with the Ronin blockchain. It facilitates communication between external applications and the blockchain, enabling actions such as querying data and executing transactions efficiently.`,
how: (
<>
To use Ronin RPC, developers can connect to the Ronin blockchain
through RPC API calls. These calls enable access to blockchain data
and execution of transactions. With dRPC's reliable Ronin RPC
endpoints, integrating Ronin into your Web3 projects is fast, secure,
and scalable. Learn more from dRPC‘s {DocsLink}.
</>
),
},
telos: {
what: `RPC in Telos refers to the Remote Procedure Call protocol used for interacting with the Telos blockchain. It enables external applications to communicate with the network, facilitating data retrieval, transaction processing, and smart contract interactions.`,
why: `Telos utilizes RPC to provide external access to its high-speed and scalable blockchain network. It enables developers and users to interact with the Telos blockchain efficiently, supporting a wide range of operations essential for decentralized applications and blockchain projects.`,
how: (
<>
To use Telos RPC, developers can connect to a Telos node using RPC API
calls. These calls can be made through various tools and programming
libraries. dRPC offers reliable and efficient Telos RPC endpoints,
ensuring seamless communication with the Telos blockchain for your
Web3 projects. Learn more from dRPC‘s {DocsLink}.
</>
),
},
thundercore: {
what: `RPC in Thundercore facilitates seamless communication with the Thundercore blockchain. It enables external applications to interact with Thundercore's network, allowing for data queries, transaction submissions, and smart contract interactions.`,
why: `Thundercore utilizes RPC to provide external access to its blockchain infrastructure. By offering RPC endpoints, Thundercore enables developers to integrate their applications with the Thundercore network efficiently, enhancing interoperability and functionality.`,
how: (
<>
To use Thundercore RPC, developers can send requests to a Thundercore
node through an RPC API. These requests can be made using various
tools and libraries, ensuring seamless communication with the
Thundercore blockchain. dRPC offers Thundercore RPC endpoints,
facilitating smooth integration and data interaction for developers.
Learn more from dRPC‘s {DocsLink}.
</>
),
},
"zeta-chain": {
what: `RPC in ZetaChain facilitates communication with the ZetaChain blockchain, allowing external applications to interact with the network, query data, and execute transactions efficiently.`,
why: `ZetaChain utilizes RPC to provide external access to its foundational blockchain network, enabling seamless communication with other blockchains and supporting a fluid, multi-chain crypto ecosystem.`,
how: (
<>
To use ZetaChain RPC, developers connect to a ZetaChain node through
RPC API calls. These calls enable actions such as querying blockchain
data and executing transactions, fostering integration and data
interoperability within the ZetaChain ecosystem. Learn more from
dRPC‘s {DocsLink}.
</>
),
},
zora: {
what: `RPC in Zora refers to the Remote Procedure Call protocol used for interacting with the Zora Network blockchain. It allows external applications to communicate with the Zora Network, enabling data requests and transaction processing.`,
why: `Zora utilizes RPC to offer efficient, external connectivity to its Layer-2 network. This enables streamlined interactions with NFTs and facilitates operations like querying data and processing transactions, enhancing the scalability and accessibility of the Zora Network. `,
how: (
<>
To use Zora RPC, connect to a Zora Network node using RPC API calls.
These calls can be made through various tools or programming
libraries. dRPC provides easy-to-use Zora RPC endpoints for this
purpose, ensuring smooth communication with the Zora Network. Learn
more from dRPC‘s {DocsLink}.
</>
),
},
bittorrent: {
what: `RPC in Bittorrent enables seamless interaction with the Bittorrent-Chain, allowing external applications to access blockchain data and execute transactions efficiently.`,
why: `Bittorrent utilizes RPC to provide external connectivity to its blockchain network, facilitating operations such as querying data and interacting with smart contracts, essential for decentralized application development.`,
how: (
<>
To leverage Bittorrent RPC, developers can send requests to a
Bittorrent node via RPC API calls. dRPC offers user-friendly
Bittorrent RPC endpoints, ensuring smooth communication with the
Bittorrent-Chain for seamless blockchain integration. Learn more from
dRPC‘s {DocsLink}.
</>
),
},
"boba-ethereum": BOBA,
"boba-bnb": BOBA,
core: {
what: `RPC in Core allows external applications to interact with the Core blockchain, facilitating tasks such as data retrieval, transaction submission, and smart contract interactions efficiently.`,
why: `Core utilizes RPC to provide developers and users with external access to its blockchain network, enabling seamless integration and interaction with Core's decentralized ecosystem.`,
how: (
<>
To utilize Core Network RPC, developers can send requests to a Core
node through an RPC API. These requests can be made using various
tools and programming libraries. dRPC offers reliable and efficient
Core Network RPC endpoints, ensuring smooth communication with the
Core blockchain. Learn more from dRPC‘s {DocsLink}.
</>
),
},
axelar: {
what: `RPC in Axelar facilitates cross-chain communication, allowing external applications to interact with the Axelar blockchain and access its interoperable infrastructure for secure message passing and transactions across multiple networks.`,
why: `Axelar utilizes RPC to provide seamless access to its cross-chain infrastructure, enabling decentralized applications (dApps) to securely communicate and transfer assets across various blockchain networks, enhancing interoperability.`,
how: (
<>
To use Axelar RPC, developers connect to an Axelar node through RPC
API calls. These calls allow actions such as querying blockchain data,
initiating cross-chain transfers, and executing multi-chain
transactions, empowering dApps to integrate seamlessly with Axelar's
interoperability services.
</>
),
},
bob: {
what: `RPC in GoBob allows external applications to interact with the GoBob blockchain, facilitating data queries and transaction execution on its scalable, Ethereum-compatible infrastructure.`,
why: `GoBob uses RPC to provide developers with access to its blockchain, enabling efficient communication and interaction with the network, which is optimized for decentralized applications and cross-chain interoperability.`,
how: (
<>
To use GoBob RPC, developers connect to a GoBob node via RPC API
calls. These calls enable querying of blockchain data, execution of
transactions, and interaction with smart contracts, fostering
integration with GoBob's Ethereum-compatible ecosystem.
</>
),
},
"cosmos-hub": {
what: `RPC in Cosmos facilitates communication with the Cosmos Hub, enabling external applications to interact with the network, query data, and execute transactions.`,
why: `Cosmos uses RPC to provide access to its interoperable blockchain ecosystem, supporting communication and transactions between blockchains in the Cosmos network.`,
how: (
<>
To use Cosmos RPC, you need to send JSON-RPC formatted requests to a
Cosmos node, either your own or via a service provider. These requests
can be made using tools like cURL or programming libraries in various
languages. The node processes the requests and returns data or
confirms transactions.
</>
),
},
"eth-beacon-chain": {
what: `RPC in Beacon Chain facilitates interaction with the Ethereum 2.0 consensus layer, allowing users to query validator data, chain state, and execute staking-related transactions.`,
why: `Beacon Chain RPC provides external access to the Ethereum 2.0 network, enabling users and validators to interact with the network’s proof-of-stake consensus mechanism.`,
how: (
<>
To use Beacon Chain RPC, you need to send JSON-RPC formatted requests
to a Beacon Chain node, either your own or through a service. These
requests can be executed using tools like cURL or libraries in various
programming languages. The node processes these requests and provides
the necessary data or transaction confirmation.
</>
),
},
fraxtal: {
what: `RPC in Fraxtal allows applications to interact with the Fraxtal protocol, enabling stablecoin transactions, data queries, and governance functions.`,
why: `Fraxtal utilizes RPC to provide external access to its decentralized stablecoin ecosystem, allowing seamless stablecoin minting, redeeming, and participation in governance.`,
how: (
<>
To use Frax RPC, you need to send JSON-RPC formatted requests to a
Fraxtal node, either your own or via a service provider. These
requests can be made using tools like cURL or libraries in various
programming languages. The node processes the requests and returns
data or confirms transactions.
</>
),
},
gameswift: {
what: `RPC in GameSwift enables interaction with its blockchain gaming ecosystem, allowing external applications to query data and execute in-game transactions.`,
why: `GameSwift uses RPC to provide developers with access to its gaming ecosystem, facilitating communication between games and its blockchain infrastructure.`,
how: (
<>
To use GameSwift RPC, you need to send JSON-RPC formatted requests to
a GameSwift node, either your own or via a service provider. These
requests can be executed using tools like cURL or libraries in various
languages. The node processes these requests and returns data or
confirms in-game actions.
</>
),
},
goat: {
what: `RPC in Goat Network allows communication with the Goat blockchain, enabling external applications to query data and execute transactions efficiently.`,
why: `Goat Network utilizes RPC to provide external access to its blockchain, supporting various decentralized applications and ecosystem use cases.`,
how: (
<>
To use Goat RPC, you need to send JSON-RPC formatted requests to a
Goat Network node, either your own or via a service provider. You can
make these requests using tools like cURL or programming libraries.
The node processes these requests and returns the necessary
information or confirms transactions.
</>
),
},
kroma: {
what: `RPC in Kroma facilitates interaction with its Ethereum Layer 2 solution, allowing external applications to interact with the network, query data, and execute transactions.`,
why: `Kroma uses RPC to enable access to its Layer 2 network, providing faster and more cost-effective transactions while maintaining Ethereum compatibility.`,
how: (
<>
To use Kroma RPC, you need to send JSON-RPC formatted requests to a
Kroma node, either your own or via a service provider. These requests
can be made using tools like cURL or programming libraries. The node
processes the requests and returns data or transaction confirmations.
</>
),
},
kusama: {
what: `RPC in Kusama facilitates interaction with the Kusama network, allowing external applications to query data and execute transactions on its experimental, scalable blockchain platform.`,
why: `Kusama utilizes RPC to provide external access to its network, enabling experimentation with governance, staking, and parachain functionality in a real-world environment.`,
how: (
<>
To use Kusama RPC, you need to send JSON-RPC formatted requests to a
Kusama node, either your own or via a service provider. These requests
can be made using tools like cURL or programming libraries. The node
processes these requests and returns data or confirms transactions.
</>
),
},
metall2: {
what: `RPC in Metall2 facilitates communication with the Metall2 blockchain, allowing external applications to query data and execute transactions.`,
why: `Metall2 utilizes RPC to provide seamless access to its network, enabling interaction with its secure, scalable blockchain for decentralized applications.`,
how: (
<>
To use Metall2 RPC, you need to send JSON-RPC formatted requests to a
Metall2 node, either your own or via a service provider. These
requests can be made using tools like cURL or programming libraries.
The node processes the requests and returns data or confirms actions.
</>
),
},
neutron: {
what: `RPC in Neutron facilitates interaction with the Neutron blockchain, enabling external applications to query data and execute transactions within its ecosystem.`,
why: `Neutron utilizes RPC to provide access to its scalable and interoperable blockchain network, designed to support decentralized applications and cross-chain functionality.`,
how: (
<>
To use Neutron RPC, you need to send JSON-RPC formatted requests to a
Neutron node, either your own or via a service provider. These
requests can be executed using tools like cURL or programming
libraries in various languages. The node processes these requests and
returns the desired data or confirms transactions.
</>
),
},
"open-campus-codex": {
what: `RPC in Open Campus enables interaction with its blockchain-based educational ecosystem, allowing external applications to query data and execute transactions related to decentralized learning.`,
why: `Open Campus utilizes RPC to provide external access to its blockchain platform, supporting decentralized learning applications and educational content monetization.`,
how: (
<>
To use Open Campus RPC, you need to send JSON-RPC formatted requests
to a node, either your own or via a service provider. These requests
can be executed using tools like cURL or programming libraries in
various languages. The node processes the requests and provides data
or confirms transactions.
</>
),
},
osmosis: {
what: `RPC in Osmosis facilitates interaction with the decentralized exchange (DEX) and DeFi ecosystem, allowing external applications to query data and execute trades and liquidity operations.`,
why: `Osmosis uses RPC to provide external access to its DEX platform, enabling decentralized trading, liquidity provision, and governance activities within the Cosmos ecosystem.`,
how: (
<>
To use Osmosis RPC, you need to send JSON-RPC formatted requests to an
Osmosis node, either your own or via a service provider. These
requests can be made using tools like cURL or programming libraries.
The node processes the requests and returns data or transaction
confirmations.
</>
),
},
polkadot: {
what: `RPC in Polkadot allows communication with its scalable, multi-chain network, enabling external applications to interact with parachains, query data, and execute transactions.`,
why: `Polkadot utilizes RPC to provide external access to its relay chain and parachain infrastructure, supporting cross-chain functionality and decentralized applications.`,
how: (
<>
To use Polkadot RPC, you need to send JSON-RPC formatted requests to a
Polkadot node, either your own or through a service provider. These
requests can be made using tools like cURL or programming libraries.
The node processes the requests and returns data or confirms
transactions.
</>
),
},
"polygon-blackberry": {
what: `RPC in ThirdWeb's Polygon Blackberry enables developers to interact with the Polygon network, facilitating queries and transaction execution on its Ethereum Layer 2 scaling solution.`,
why: `Polygon Blackberry uses RPC to provide developers with access to Polygon's fast and low-cost infrastructure, supporting decentralized applications with Ethereum compatibility.`,
how: (
<>
To use Polygon Blackberry RPC, you need to send JSON-RPC formatted
requests to a Polygon node, either your own or through thirdweb’s
services. These requests can be executed using tools like cURL or
programming libraries. The node processes the requests and returns the
desired data or confirms actions.
</>
),
},
"re.al": {
what: `RPC in Re.al allows external applications to interact with its blockchain platform, enabling transactions and data queries within its real estate ecosystem.`,
why: `Re.al uses RPC to provide access to its blockchain, facilitating real estate tokenization, transactions, and governance within a decentralized property ecosystem.`,
how: (
<>
To use Re.al RPC, you need to send JSON-RPC formatted requests to a
Re.al node, either your own or via a service provider. These requests
can be made using tools like cURL or programming libraries in various
languages. The node processes these requests and provides data or
confirms transactions.
</>
),
},
rootstock: {
what: `RPC in Rootstock enables interaction with its Bitcoin-backed smart contract platform, allowing external applications to query blockchain data and execute decentralized transactions.`,
why: `Rootstock utilizes RPC to provide developers with access to its smart contract ecosystem, which combines Bitcoin's security with Ethereum-compatible decentralized applications.`,
how: (
<>
To use Rootstock RPC, you need to send JSON-RPC formatted requests to
a Rootstock node, either your own or through a service provider. These
requests can be executed using tools like cURL or libraries in various
programming languages. The node processes the requests and returns
data or confirms actions.
</>
),
},
tron: {
what: `RPC in Tron enables interaction with its high-performance blockchain, allowing external applications to query data, execute transactions, and interact with decentralized applications (dApps).`,
why: `Tron uses RPC to provide external access to its scalable network, supporting dApp development, transactions, and digital asset management.`,
how: (
<>
To use Tron RPC, you need to send JSON-RPC formatted requests to a
Tron node, either your own or through a service provider. These
requests can be made using tools like cURL or libraries in various
programming languages. The node processes the requests and provides
data or transaction confirmations.
</>
),
},
zircuit: {
what: `RPC in Zircuit allows external applications to interact with its blockchain ecosystem, facilitating data queries and transaction execution within its decentralized platform.`,
why: `Zircuit utilizes RPC to provide access to its network, supporting decentralized applications, asset management, and cross-chain interoperability.`,
how: (
<>
To use Zircuit RPC, you need to send JSON-RPC formatted requests to a
Zircuit node, either your own or via a service provider. These
requests can be executed using tools like cURL or libraries in various
programming languages. The node processes the requests and returns
data or confirms actions.
</>
),
},
wemix: {
what: `RPC in Wemix enables interaction with its blockchain platform for gaming, allowing external applications to query data, execute transactions, and manage digital assets.`,
why: `Wemix uses RPC to provide access to its gaming-focused blockchain, supporting decentralized games and token-based economies.`,
how: (
<>
To use Wemix RPC, you need to send JSON-RPC formatted requests to a
Wemix node, either your own or through a service provider. These
requests can be executed using tools like cURL or programming
libraries in various languages. The node processes the requests and
returns data or transaction confirmations.
</>
),
},
alephzero: {
what: `RPC in Aleph Zero allows external applications to interact with its blockchain, enabling data queries, transaction execution, and decentralized application development.`,
why: `Aleph Zero uses RPC to provide access to its high-performance, privacy-focused network, supporting fast and secure transactions for various use cases.`,
how: (
<>
To use Aleph Zero RPC, you need to send JSON-RPC formatted requests to
an Aleph Zero node, either your own or via a service provider. These
requests can be made using tools like cURL or libraries in various
programming languages. The node processes these requests and returns
data or transaction confirmations.
</>
),
},
"arb-blueberry": {
what: `RPC in Arbitrum Blueberry allows external applications to interact with the Layer 2 network, enabling efficient Ethereum-compatible transactions and data queries.`,
why: `Arbitrum Blueberry utilizes RPC to provide access to its fast and cost-effective Layer 2 solution, supporting decentralized applications with Ethereum compatibility.`,
how: (
<>
To use Arbitrum Blueberry RPC, you need to send JSON-RPC formatted
requests to an Arbitrum node, either your own or through a service
provider such as Sequence. These requests can be executed using tools
like cURL or programming libraries in various languages. The node
processes the requests and provides the necessary data or confirms
actions.
</>
),
},
everclear: {
what: `RPC in Everclear facilitates interaction with its blockchain network, allowing external applications to query data and execute decentralized transactions.`,
why: `Everclear uses RPC to provide access to its decentralized platform, enabling seamless interaction with its secure and scalable blockchain ecosystem.`,
how: (
<>
To use Everclear RPC, you need to send JSON-RPC formatted requests to
an Everclear node, either your own or via a service provider. These
requests can be executed using tools like cURL or programming
libraries. The node processes the requests and returns data or
transaction confirmations.
</>
),
},
"opcelestia-raspberry": {
what: `RPC in Opcelestia Raspberry enables external applications to interact with the Opcelestia blockchain, facilitating data queries and transaction execution.`,