The ethical block builder for PulseChain

Every block hides value. We ferret it out.

BlockFerret builds PulseChain blocks the honest way. It digs out the value hidden in each one (arbitrage, protocol spreads, rewarded upkeep) and pays the validator at least 60% of net added MEV after costs, on top of the ordinary reward. Backruns follow their triggering trades, and the builder does not sandwich users.

BlockFerret, a ferret in a hard hat, work vest and tool belt, holding a glowing green block

Live numbers

What BlockFerret added in the last 48 hours

Every figure comes from blocks BlockFerret actually delivered through the Vouch relay, using each block's own accounting: the reward the validator would have earned from a vanilla block of the same public transactions, and the MEV BlockFerret added on top.

Loading live stats…

Extra validator rewards — PLS
Total vanilla rewards — PLS
Total vanilla rewards — PLS
Overall reward multiple —

Totals across all measured blocks in the last 48 hours, including blocks without MEV and payout costs. Median block increase: —. Large wins count toward the overall total.

Blocks delivered

—

through the Vouch relay

Blocks with MEV

—

— of — measured blocks carried added value

Extra paid to validators

— PLS

above the vanilla rewards

MEV added per block

— PLS

on average, above the vanilla reward

Validator reward per block

Hourly averages over the last 48 hours, in PLS. Hours in UTC.

  • Vanilla reward
  • MEV added

Loading live stats…No data available

How we measure

Vanilla reward: for every slot, BlockFerret first builds the ordinary block a validator would get from the public mempool. Its priority fees are the vanilla reward.

MEV added: the actual extra MEV paid to the validator after execution gas, the payout transfer, and reimbursed fees. This includes competition reserves and any historical rebates paid within the reporting window.

Typical block (the headline): half of BlockFerret's blocks raised the validator's reward by more than this, and half by less. The equation above uses one such block's own numbers.

MEV added per block: all the MEV paid to validators in the window, divided by the number of blocks BlockFerret delivered.

You can check every block BlockFerret delivered in the relay's public data API.

For PulseChain wallets

Your transaction. A private path to the block.

Send signed transactions directly to BlockFerret's private pool. Transfers, approvals, swaps, NFTs and contract calls use the same RPC. Your signed transaction stays out of the public mempool before inclusion.

Wallet RPC URL

https://rpc.blockferret.win
Network
PulseChain
Chain ID
369
Currency
PLS

In your wallet's PulseChain network settings, replace the RPC URL above. Keep chain ID 369 and PLS as the currency. No account or API key is required.

Private delivery can take longer

BlockFerret can include your transaction only when an upcoming validator uses the Vouch relay and our block wins its bid. We cannot deliver in every PulseChain block. A higher priority fee can help our bid compete, but cannot guarantee a win or a confirmation time.

Relay reach & current delivery pace

Loading current data…

Relay registrations

—

Vouch registrations, all time

Active chain validators

—

active validators on PulseChain

Registrations / active count

—

a size comparison, not live coverage

BlockFerret delivery pace

—

between deliveries, averaged over 24h

Live counts and the timing guide refresh every minute. Estimates appear only when current data is available.

A wait guide, not a transaction ETA. The delivery average includes quiet periods, losing bids and slots outside the relay. Your transaction may wait longer, miss a winning block, or never be included. “Included” means it landed in a block; chain finality takes additional time.

What these numbers mean

Relay registrations: the Vouch relay's public page reports validators that registered at least once. Some may no longer be active or connected. It does not expose the current active overlap, so dividing registrations by active validators does not establish our chance of winning a slot.

Active chain validators: validators in an active state on the PulseChain beacon chain. Pending and exited validators are excluded. This count is refreshed at least every five minutes.

Delivery pace: 24 hours divided by the number of BlockFerret payloads delivered by the relay in that entire window. It reflects recent results, not a reservation for your transaction, and is hidden when the window cannot be completely checked or has fewer than two deliveries.

The live data includes timestamps and the validator-count slot. The page hides estimates if its snapshot becomes more than three minutes old.

Your fee

A higher tip helps the validator bid

This RPC does not automatically increase your fees. Choose your priority fee in your wallet's advanced gas settings. A larger tip adds value to the block we can offer the validator, making it more competitive against other builders. There is no separate BlockFerret wallet service fee or required extra payment.

Base fee
Burned by the network.
Priority fee
Forwarded to the winning block's validator through its payout.
Unused gas / fee cap
You pay for gas actually used, not the full gas limit or maximum fee cap.

For EIP-1559 transactions, the effective tip per gas is the smaller of your priority fee cap and your maximum fee cap minus the block's base fee. Allow enough maximum fee to cover both the base fee and your chosen tip.

Gas costs and the ordinary baseline come first. BlockFerret can use verified net MEV to increase its validator bid, then splits the remaining MEV 60% to the validator and 40% to BlockFerret. The same settlement applies to every proposer. Your ordinary priority tip is forwarded separately; it is not split 60/40.

While you wait

Accepted is not yet confirmed

A transaction hash means your submission was accepted. It still needs a valid nonce, sufficient balance, successful execution and space in a winning block. Swaps can also miss their deadline or slippage limit while waiting.

Private submissions expire after 30 minutes. Check the transaction receipt and your wallet nonce before resubmitting an unconfirmed transaction. Your wallet may continue to show “pending” after our queue expires. No on-chain transaction gas is charged if it is never included.

We never automatically release an expired transaction to the public mempool. Choosing another RPC and submitting there can make it public. The current private queue is held in memory, so a service restart can also require resubmission.

Signed writes go only to BlockFerret. Wallet reads and simulations normally use public RPC providers; those providers can see the call data you ask them to simulate. If the public pool is unavailable, a tightly limited Switch read RPC can serve eligible reads. After inclusion, your transaction is public on-chain.

Building an app or tool? Our read-routing guide and example client support direct public reads with automatic proxy fallback. Ordinary wallets keep the standard proxy route; redirects alone cannot guarantee automatic fallback.

External searchers · Permissionless intake

Bring your arb. Submit a private bundle.

Send signed PulseChain trades to BlockFerret without enrollment or an API key. We retain the current block, replay your transactions together, verify payment and can include them in our Vouch relay bid.

You choose the inclusion fee

Your bundle pays a chosen PLS fee through our payment router: 60% to the validator and 40% to BlockFerret. For the eligible Vouch fee depositor, our same-block rebate makes that effectively 80/20. You keep your remaining trade profit and cover your own gas. Ordinary tips go to the validator separately.

Trades must settle atomically and every bundle transaction must succeed. Our final replay preserves existing transaction outcomes, gas coverage and builder earnings.

Sign locally. Track inclusion.

https://rpc.blockferret.win/builders

Use eth_sendBundle with X-Flashbots-Signature. Read live terms for the router address and fresh context for the target block, parent and validator recipient. Bundles contain 1–16 transactions and up to 256 KiB of signed bytes.

Queue acceptance is not guaranteed inclusion. Check status and canonical receipts. Pending bundles stay private; there is no automatic public broadcast or private orderflow feed.

For independent PulseChain builders

Build a better block. Submit it to BlockFerret.

Submit complete PulseChain blocks containing swaps, token and NFT transactions, protocol calls, contract deployments or native transfers. Submission is permissionless: sign with a local authentication wallet, with no enrollment or API key. BlockFerret independently verifies your candidate and can bid with it through the Vouch relay.

The payment rule

Improve both sides of the bid

BlockFerret
Our verified aggregate net earnings must be strictly greater than in our latest own candidate.
Validator
Its verified payment must cover our latest own candidate plus any additional ordinary priority fees.

Fund a native payment to the BlockFerret wallet below and a final payment to the template's validator recipient. Replay includes gas and account spending; moving our own funds around cannot count as a fee. Ordinary transaction tips go to the validator.

0x3Ec102407BffeABB8a494deeAeEFAc74Be4f5ea1

No fixed commission or upfront deposit is required. The residual 60/40 split on our own added MEV does not automatically apply to your entire profit. Among eligible evaluated candidates, validator payment ranks first, then BlockFerret net earnings; exact ties keep the current choice.

Public endpoints

Get context. Sign. Submit.

GET · Current public template

https://rpc.blockferret.win/v1/builder-context

POST · Signed builder JSON-RPC

https://rpc.blockferret.win/builders

Use blockferret_sendCandidateBlock to submit a complete Capella execution payload. Use blockferret_getSubmissionStatus with the same signing identity to check its state.

Authentication uses X-Flashbots-Signature: personal-sign the UTF-8 hex string of the exact request body's Keccak-256 hash. Your authentication wallet can be unfunded; payment transactions need their own funds and signatures. Keep all private keys on your machine.

  1. Fetch fresh context. Require templateAvailable: true and genericBuilderTransactions: true. Context provides the public transactions, block attributes, validator recipient and current baseline payment. HTTP 503 or a false template flag means no template is available for that duty.
  2. Construct and replay locally. Add any transactions supported by PulseChain, while retaining the supplied public transactions in order with unchanged outcomes. Keep the required block attributes, fee recipient and withdrawals. Include funded payments to BlockFerret and the validator, then build the full payload with accurate roots, gas used and block hash.
  3. Sign the exact request. Submit params: [{slot, proposerPubkey, executionPayload}]. The slot is a decimal JSON number; the payload uses Capella hex quantities. Our independent replay must pass the current execution limits and both payment checks.
  4. Track the actual block. A submission ID means queue acceptance. It does not guarantee selection, a winning relay bid or inclusion. Check owner-only status, then the exact block hash and receipts on-chain. Rebuild when the parent or baseline changes.

The example uses Node.js 20+ and ethers 6. Builder requests have separate capacity from wallet intake: 60 requests/minute per signing address, 600/minute shared across builder submission and context, two concurrent requests, and 16 complete-block queue slots. Requests are capped at 8 MiB and blocks at 10,000 transactions. Back off on 429 or 503.

Templates exist during eligible relay duty windows. Queue entries expire after at most two minutes, but duty deadlines or parent changes can invalidate a block much sooner. The queue is currently held in memory. We do not automatically broadcast submitted transactions publicly or provide private wallet bytes to other builders.

How it works

From mempool to your fee recipient in one slot

  1. Sniff

    BlockFerret watches PulseChain's public mempool and accepts signed wallet transactions through its private RPC. Private submissions are kept with BlockFerret until inclusion, without being broadcast to the public mempool.

  2. Dig

    For each upcoming block it digs for value: price gaps between exchanges, imbalances left by large trades, protocol spreads and rewarded upkeep.

  3. Inspect

    Every candidate block gets a full safety inspection: it's executed exactly before it's offered.

  4. Deliver

    The block is bid through the Vouch relay. A winning MEV block pays the ordinary baseline plus the competition reserve and the validator's share of the remaining net MEV, inside the same block.

What it digs for

Value that's already in the block

BlockFerret doesn't make money by getting in anyone's way. It digs out value that is already there (price gaps, spreads and protocol rewards) and shares most of it with the validator.

Cross-DEX arbitrage

When a token trades at different prices on different PulseChain exchanges, BlockFerret closes the gap, pulling prices back in line for everyone.

Backruns

Large swaps move prices. BlockFerret rebalances them in the same block, strictly after the user's trade has executed at the price they signed for.

Protocol spreads

Some protocols let anyone mint at a fixed rate. When the market pays more, BlockFerret mints and sells in one step, turning the spread into block value.

Protocol upkeep

Many protocols reward anyone who performs routine maintenance: keeper triggers, liquidations of under-collateralized positions, redemptions. BlockFerret watches for them and steps in when they pay.

Strategies run through dedicated executor contracts and are re-proven against every block. We don't publish the blueprints.

Ethics

The Ferret Code

Six rules enforced through block construction, full execution replay and payment checks.

  1. No sandwiches

    Backruns execute after their triggering trades. BlockFerret does not sandwich users.

  2. Verified execution

    Every block is replayed and verified before submission.

  3. Validators first

    Every MEV bid preserves the full vanilla baseline. Any ordinary fee displaced to make room is reimbursed before MEV is shared.

  4. Compete within earned MEV

    All gas and the ordinary baseline are covered first. A competition reserve can raise the validator bid using verified net MEV. The remainder is split 60/40 for every proposer. Bids remain within verified funding and cannot spend treasury PLS.

  5. Fail closed

    If anything is uncertain, whether a simulation, a price or a receipt, BlockFerret falls back to an ordinary block. Guesswork never reaches the relay.

  6. Every block on the record

    Each block carries a proof of its strategy and accounting, and every candidate is written to a hash-chained audit log tied to the policy that approved it.

BlockFerret will

  • Close price gaps between PulseChain exchanges
  • Rebalance prices after trades, in the same block
  • Capture protocol mint-and-sell spreads
  • Perform rewarded, permissionless protocol upkeep
  • Capture verified arbitrage and reimburse lost ordinary priority fees before sharing the surplus

BlockFerret will never

  • Place a backrun before its triggering trade
  • Sandwich a trade
  • Alter a user's signed transaction parameters
  • Censor anyone for who they are: not by address, not by app, not by token
  • Share private signed transactions with other builders or broadcast them publicly
  • Reorganize or rewrite past blocks

For validators

Put BlockFerret to work for your validator

BlockFerret delivers its blocks through the Vouch relay. Run Vouch's PulseChain build of mev-boost next to your beacon node and your validator receives BlockFerret's bids, alongside every other builder on the relay, whenever it proposes.

Vouch relay URL for mev-boost

https://0xa6b974cbc17ce9c37b5f9796e167455d22882f2ca662c19379b0b9c476b1fbe745c19006444b653f9fb8409ffda9a450@boost-relay.vouch.run
  1. Run Vouch's mev-boost sidecar

    Stock mev-boost releases don't work on PulseChain, so use Vouch's build (the pulse branch). The Docker setup comes with the Vouch relay already configured and listens on port 18550.

    # Docker quickstart
    mkdir -p mev-boost && cd mev-boost && \
    curl -fsSLO https://raw.githubusercontent.com/Vouchrun/mev-boost/pulse/ops/docker-compose.yml && \
    curl -fsSLO https://raw.githubusercontent.com/Vouchrun/mev-boost/pulse/ops/mev-boost-config.example.yaml && \
    docker compose up -d
  2. Point your clients at mev-boost

    # beacon node
    --http-mev-relay=http://127.0.0.1:18550
    
    # validator client
    --enable-builder
    --suggested-gas-limit=45000000
    --suggested-fee-recipient=0xYourFeeRecipient

    Set the gas limit. Both PulseChain clients default to 30M gas while the network runs at about 45M, so without the flag every mev-boost block leaves about a third of its space unused. Start the sidecar first, then restart the beacon node and the validator client, ideally when no proposal is due.

  3. Propose as usual

    Your validator registers its fee recipient with the relay. When it proposes, the relay offers the best bid, and BlockFerret's payment arrives at your fee recipient in the block itself. If the relay is ever unavailable, your client falls back to a local block. You can't end up worse off.

    The setup guide shows how to confirm your registration and your first delivered block. The Docker setup skips bids under 2,000 PLS; those slots are built locally.

FAQ

Questions wallets & validators ask

Can another builder submit a block without enrollment?

Yes. Any signing address can submit a complete PulseChain block containing swaps, token or NFT transactions, protocol calls, contract deployments and native transfers. Retain the supplied public transactions in order with unchanged outcomes and use the current block attributes. Independent replay must verify strictly higher BlockFerret net earnings, sufficient validator payment including added priority fees, and protected state and balances. See the builder guide above for endpoints and an example client.

Does submitting a candidate guarantee that it will be used?

No. Acceptance only puts the candidate in a bounded queue. It must pass independent replay and payment checks against the latest own candidate, be selected, and win a relay opportunity before its exact block can be included. Parent changes and duty deadlines can make it stale. Check submission status and then its block hash and receipts on-chain; we do not automatically broadcast its transactions to the public mempool.

How do I use the BlockFerret private RPC?

Set your wallet's PulseChain RPC URL to https://rpc.blockferret.win, with chain ID 369 and currency PLS. Transfers, approvals, swaps, NFT transactions, contract calls and contract creation are supported, subject to validation and successful execution. No account or API key is required.

Will a higher fee guarantee fast confirmation?

No. A higher priority tip increases the validator value of our block, but BlockFerret must have a relay opportunity and win the bid. The live delivery average is a timing guide, not a promised confirmation time. Your transaction may wait longer or expire without inclusion; private submissions expire after 30 minutes.

Does BlockFerret take 40% of my priority fee?

No. Ordinary priority tips are forwarded to the winning block's validator through its payout. Base fees are burned, and there is no separate BlockFerret wallet service fee. A competition reserve can use verified net added MEV to increase the bid; the remaining MEV is split 60% to the validator and 40% to BlockFerret. Your ordinary priority tip is separate.

What happens if my private transaction is not included?

A transaction hash confirms acceptance, not inclusion. The private submission expires after 30 minutes and is never automatically broadcast publicly. Check its receipt and your wallet nonce before resubmitting an unconfirmed transaction; your wallet may still show it as pending after expiry. You pay no on-chain transaction gas if it was never included.

Does BlockFerret cost my validator anything?

There is no separate validator service fee. Every MEV bid covers gas and preserves the ordinary baseline before allocating a competition reserve and sharing the remainder. BlockFerret's retention comes only from added MEV. An ordinary block without MEV can pay slightly less than its priority-fee total because of the final payout transfer's gas cost.

How is the increase calculated?

The headline is the overall increase across delivered blocks with comparable accounting in the last 48 hours: (total paid to validators − total vanilla rewards) ÷ total vanilla rewards × 100%. Each vanilla reward is the ordinary baseline built from that slot's public mempool. Blocks without MEV and payout costs are included. This weights the increase by ordinary reward, rather than averaging per-block percentages. The median block increase is shown separately and can be near zero even when a few large wins add substantial PLS. These figures count validator payments, excluding the builder's retained earnings.

What happens when another builder wins my slot?

Nothing changes for you. The relay simply gives you the highest bid. BlockFerret only earns when its block is the one you sign.

Does BlockFerret sandwich trades?

No. BlockFerret does not sandwich trades. Backruns execute after their triggering transactions.

Do I need to change my fee recipient or keys?

No. You keep your own fee recipient and keys. BlockFerret pays you with a transfer inside the block it built, and the relay verifies the bid before it ever reaches you.

Which mev-boost do I need?

Vouch's PulseChain build: the pulse branch of Vouchrun/mev-boost, also published as the Docker image ghcr.io/vouchrun/mev-boost:pulse. Stock flashbots releases don't support PulseChain. Its setup guide covers Docker, the client flags (including the 45M gas limit) and how to check that everything is working.

Who runs the relay?

The relay is operated by Vouch. It's a standard mev-boost relay that any PulseChain validator can connect to, and its public page shows live stats and every delivered block.

Ready to put a ferret on the job?

Run Vouch's mev-boost with the Vouch relay and BlockFerret starts bidding for your blocks.

Put BlockFerret to work