QUAY · Fee review

Priority-fee and tip configuration review

We read your public transaction signatures and compare your current priority-fee and tip settings against what those transactions actually paid and landed at.

You receive one written page within 48 hours of a complete brief. This is a recommendation, nothing more: we do not change your config, your wallet, or your transactions.

What you send

All of this is public data. Send nothing that is not already visible on chain or in a block explorer.

  • Up to 200 transaction signatures — Just signatures. Never a private key, never a seed phrase, never an RPC URL with a token in it.
  • Your current priority-fee setting
  • Your current tip setting
  • Which venue or aggregator you route through

We will not ask for, display, or accept an API key, an RPC URL containing a token, or a private key.

What you get back

One page, delivered within 48 hours of a complete brief:

  • The percentile your current setting actually lands at
  • The percentile to target, with the reasoning shown
  • When to raise, and the specific condition that should trigger it
  • Where you are overpaying, with the wasted amount per landed tx
  • What we could not determine from the signatures, named explicitly

If an input cannot be read from a signature, the report says UNKNOWN — not a guess.

What we cannot tell you from signatures alone

Signatures show what was submitted and what landed on chain. They do not show everything about your operation. At minimum, we cannot see:

  • Your fills — whether a landed transaction achieved the trade outcome you wanted
  • Your strategy — intent, sizing logic, or timing rules behind each send
  • Your RPC latency — how long your node or provider took to propagate the transaction
  • Why a specific transaction failed if the failure is not recorded on chain (simulation rejections, dropped packets, client-side aborts)

Anything that cannot be derived from the signatures you send is marked UNKNOWN in the report. We do not infer or fill gaps.

Example layout — not a real client report

Fee review · one-page output (redacted shape)

Sample scope
[venue name] · [N signatures reviewed]
Settings as submitted
Priority: [your value] · Tip: [your value]
Current setting — landed percentile
[percentile band + short note]
Recommended target percentile
[target band + reasoning inline]
When to raise
[specific condition that should trigger a raise — e.g. queue depth, failure class, time window]
Overpaying
[venue or route] · [wasted amount per landed tx, where measurable]
Could not determine (UNKNOWN)
[each gap named — e.g. fill outcome, RPC latency, off-chain failure reason]

Price and intake

$199

Once · In English · PayPal or invoice on reply

Pay with PayPal here and send your brief with the PayPal transaction ID, or send the brief first and pay on the invoice we send when we confirm it. No form on this page collects anything.

This is a written recommendation based on public chain data. We do not touch your config, your wallet, or your transactions. Following the recommendation may not improve your landing rate or lower your cost, and we do not promise that it will. We make no claim about earnings, returns or savings.

Refunds

If you want your money back, you get it.

No form, no reason, no time limit, no exceptions. Mail support@elghaly.dev and say you want a refund.

This covers everything QUAY sells — the fee review, Land reports, proof cards, Node Watch. Before we start, after we deliver, either way.

Paid with PayPal here, or through the shop checkout — back to the same card or PayPal account, 5–10 business days. A PayPal payment can also be disputed through PayPal.

Wallet — back to the address it came from, same asset, same network, within 3 business days, minus the network fee. Send from an address you control; we cannot refund an exchange deposit address.

We would rather return money than keep money someone does not want us to have.

Where we are