Wallets & apps

Connect your wallet

Set up the BlockFerret private RPC in MetaMask, Rabby, or another PulseChain wallet.

2 min read

Network settings#

Open your wallet’s PulseChain network settings and replace the RPC URL with the endpoint below. Keep the chain ID and currency unchanged.

RPC URL

https://rpc.blockferret.win

Wallet field	Value
Network name	PulseChain
RPC URL	`https://rpc.blockferret.win`
Chain ID	`369`
Currency symbol	`PLS`

MetaMask#

Open Settings → Networks and select PulseChain.
Edit the RPC URL to https://rpc.blockferret.win.
Check that the chain ID is 369, then save and select that network.
Use your usual dApp or wallet transaction flow. The wallet signs locally.

The exact menu wording varies by wallet version. If PulseChain has not been added yet, use the same values when adding a custom network.

Rabby and other wallets#

Choose PulseChain in the wallet’s custom RPC or network settings and set the same URL. Normal reads use the server proxy, so a wallet does not need to recover from a failed redirect. No account or API key is required.

Supported transactions#

Transfers, approvals, swaps, token and NFT actions, protocol calls, and contract creation can be submitted, subject to validation, supported chain transaction formats, available funds, and successful execution.

BlockFerret accepts already signed transactions through eth_sendRawTransaction. It does not hold your wallet keys or sign transactions for you.

Fees and waiting#

A higher priority tip can make our block more competitive, but cannot guarantee a winning bid or an inclusion time. Review the privacy and inclusion guide before relying on a time-sensitive swap.

A simple connectivity check#

Shell

curl https://rpc.blockferret.win \
  -H "Content-Type: application/json" \
  --data '{"jsonrpc":"2.0","id":1,"method":"eth_chainId","params":[]}'

A successful chain-ID response contains "result": "0x171", the hexadecimal representation of 369. This checks RPC connectivity, not future transaction inclusion.