Reputation Scores

Every node on Magma has two reputation scores, one as a seller and one as a buyer. Each runs from 0 to 100 and is built only from that node's Magma orders over the last 90 days, with recent orders counting most.

Automatic matching favours sellers with higher scores and passes over sellers whose score is too low, so a seller's score directly affects how many orders they get.

What goes into the score

Both scores have two parts:

• Completion: the share of your orders that went through. This matters most.
• Quality: how well the completed orders went. Quality can lower the score, but never by more than a quarter.

Seller score

Buyer score

How the score behaves

• New nodes start in the middle. A node with no orders is neither perfect nor zero, and its first few orders move the score gradually rather than all at once.
• Recent orders count most. An order's weight drops steadily as it ages, so a bad stretch fades within weeks rather than months.
• One bad order is not the end. A failure lowers the score in proportion to how many orders you have; it no longer wipes it out.
• One buyer counts once. However many orders a single buyer places with you, at most one failed order from that buyer counts against you. A buyer placing order after order cannot drag your score down.
• Rejections need a buyer others could serve. A rejection only counts against you once the buyer has completed an order with another seller. Orders you let time out, or fail to open after the buyer paid, always count.
• Missing data is not held against you. If there is nothing to judge a quality part on yet, it is left out rather than scored as zero.

When the buyer's node is the problem

Sometimes a seller cannot complete an order because the buyer's node cannot be reached, or will not accept the channel size. Sellers can say so when they reject an order by passing a cancellation_reason:

A reason that puts the failure on the buyer is only accepted once another seller has reported the same buyer. When it is accepted, the order counts against the buyer instead of you and shows up in your breakdown under excluded. Without that confirmation the order counts as an ordinary rejection, so the reason cannot be used to shield a seller's score from orders they simply chose not to fill. SELLER_UNAVAILABLE always counts as a rejection; it tells the buyer why.

Either way, repeated orders from the same buyer only count once, and rejecting a buyer that no other seller has completed an order with does not count at all. If an unreachable buyer keeps ordering from you, reject each order with UNABLE_TO_CONNECT_TO_NODE rather than letting it time out.

See Sell Liquidity for the reject mutation.

Who sees what

Read your own breakdown from your account's nodes:

query MyReputation {
  user {
    nodes {
      pubkey
      reputation {
        seller {
          score
          completion
          quality
          sample_size
          counts { completed rejected no_response failed_to_open invalid_opening excluded }
          components { key value score sample }
        }
        buyer {
          score
          counts { paid failed_to_pay unreachable }
          components { key value score sample }
        }
      }
    }
  }
}

Each entry in components has a key (for example responseTime), the measured value (a rate from 0 to 1, or a median in seconds), its score from 0 to 1, and the number of orders it is based on.

Improving your score

As a seller:

• Accept or reject new orders quickly. Automating this through the API helps most.
• Only list offers you can fill. Disable an offer or lower its size when your on-chain funds run low instead of rejecting the orders it attracts.
• Open the channel promptly after payment, and keep it open for the full lease.
• Keep your fees within the cap you advertised.
• When a buyer's node is unreachable, reject with UNABLE_TO_CONNECT_TO_NODE rather than letting the order time out.

As a buyer:

• Make sure your node is online and reachable before you buy, and accepts channels of the size you order.
• Pay promptly once the seller accepts.
• Keep the channel open for the full lease.

Next steps

• Sell Liquidity - accept, reject, and open channels.
• Order Lifecycle - every order status and what it means.
• FAQ - common questions.