> For the complete documentation index, see [llms.txt](https://docs.rubyscore.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rubyscore.io/how-rubyscore-works/mathematical-model.md).

# Mathematical Model

**RubyScore** transforms a wallet’s on-chain behavior into reputation signals using a **multi-factor model** that includes:

* **Metric normalization** (per chain and over time),
* **Cross-chain aggregation**,
* **Component computation** for **quality / consistency / diversity** (with anti-fraud controls).

### Core signals (non-exhaustive)

* **Amount on balance** — current and averaged balance.
* **Gas spent** — total gas burned.
* **Transactions with unique contracts** — count of distinct contracts; diversification by category (DeFi / NFT / Bridge / DAO).
* **Transactions on different days** — active days.
* **Transactions on different weeks** — weekly distribution of activity.
* **Transactions on different months** — month-over-month activity stability.
* **Transaction volume** — notional volume, normalized per chain/category.
* **Number of transactions** — total count and call typology.

**Additionally considered:**

* **Depth of action sequences** (e.g., bridge → deposit → swap → LP → governance),
* **Economic rationality** (fee/volume ratios, asset retention),
* **Temporal stability** (regularity vs. one-off spikes),
* **Pattern uniqueness** (deviation from mass scripted patterns).

### Scoring approach

RubyScore uses a **proprietary scoring model**: a composition of **weighted, normalized metrics** with **anti-fraud rules**. The output is calibrated to a unified scale and can be tuned for a specific product or ecosystem.

**The final score indicates how closely a wallet’s behavior matches the ideal profile of a valuable audience for a given task or network.**

This approach makes reputation **verifiable, portable, and configurable**—the foundation for trust and fair incentives in Web3.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.rubyscore.io/how-rubyscore-works/mathematical-model.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.