BlockRazor
English
繁体中文English
English
繁体中文English
  • Introduction
  • Supported Blockchain
  • Use Cases
    • Wallet
    • DEX
    • Trading Bot
    • Searcher
    • Algorithmic Trading
  • Scutum(MEV Protect RPC)
    • New to MEV
    • Exclusive for Project
    • General for Wallet User
    • Searcher
      • Authentication
      • Subscribe Bundle
      • Send Bundle
  • Builder
    • BSC
      • Send Bundle
      • Send PrivateTransaction
      • Call Bundle
  • High-performance Network Service
    • Authentication
    • BSC
      • Proto
      • Subscribe NewTxs
      • Subscribe NewBlocks
      • Send RawTx
      • Send RawTxBatch
      • Full Node Synchronization
  • Privacy Statement
Powered by GitBook
On this page
  • Why Choose Scutum RPC?
  • How to Use Scutum RPC
  • FAQ
  1. Use Cases

Wallet

PreviousUse CasesNextDEX

Last updated 1 day ago

Speed, security, and cost are the key elements of the swap transaction experience.

The RPC serves as the starting point and a critical node in the process from transaction submission to transaction inclusion. Wallets tend to build high-performance RPC nodes or purchase services from RPC providers (such as Alchemy and Infura), which can enhance transaction speed to some extent but often overlook security and cost.

An RPC that is responsible for the user transaction experience can meet user needs in terms of speed, security, and cost simultaneously. For more details, please refer to Analysis of Swap Transaction Elements.

Why Choose Scutum RPC?

Scutum RPC provides a privacy channel for transactions, blocking potential MEV attacks at the source.

Based on a globally distributed network, Scutum can receive transactions from clients with extremely low latency and then forward these transactions to geographically nearby Builders, which achieves end-to-end low-latency forwarding at the network level and improves the transaction inclusion rate.

The chart data shows that transactions submitted to Scutum have a probability of being included in the next block as high as 95%, and 100% probability being included in the next 2 blocks, which significantly surpasses that of competitors.

Scutum RPC nodes are deployed globally in a distributed manner, adhering to the principles of multi-active and multi-cloud, ensuring long-term fault-free operation of the system.

Scutum RPC offers free RPC services to Wallets, with no rate limits on the API, reducing the costs associated with building or purchasing RPC nodes. Additionally, Scutum RPC supports transaction revert protection, free transaction cancellation and real time refund, further lowering traders' transaction costs to a large extent.

How to Use Scutum RPC

Scutum will generate a dedicated RPC URL for Wallet projects registered with BlockRazor. The dedicated RPC supports same JSON RPC methods as other Public RPC, requiring no re-integration, with integration time not exceeding 10 minutes. The specific steps are as follows:

  1. Register for BlockRazor

  2. Login to the portal of BlockRazor

  3. Go to the RPC module to view your dedicated RPC (currently supporting Ethereum and BSC). You can visualize and configure RPC parameters with one click, and then copy the RPC URL.

  4. Go to the wallet project, locate the chain's RPC configuration file, and replace the default endpoint with the Scutum dedicated RPC URL.

  5. Update and publish the wallet project(optional).

  6. Log in to the portal of BlockRazor to check the refund and transactions.

FAQ

Does Scutum support other JSON RPC methods besides sendRawTransaction?

  • Yes, Scutum supports all native JSON RPC methods, such as getAccountBalance, getTransactionByHash.

Currently, on which chains does Scutum provide services?

  • Currently, Scutum supports Ethereum and BSC.

Does Scutum RPC impose rate limits on JSON RPC methods, including sendRawTransaction?

  • Scutum RPC has no rate limits and does not require token validation, allowing for direct integration.

The benchmark client sends transactions to Scutum RPC, A RPC, and B RPC, recording the difference between the latest block number at the time of sending the transaction and the block number in which the transaction is included. A smaller difference indicates a faster on-chain speed.