> 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/wallet-data.md).

# Wallet data

We index supported blockchains and build a behavioral profile of your wallet based on on-chain events. Core sources include: transactions (EOA↔contract/EOA), cross-chain bridges, staking contracts, DAO governance, DEX/LP pools, and NFT mints/trades.

#### 1.1 Base-level metrics

* **Transaction history**
* **Total gas spent**
* **Daily active activity (DAA)**
* **Unique contracts interacted with**

#### 1.2 Categories of interactions

* **DeFi:** swaps, liquidity add/remove, borrowing/repaying, farming, re-staking.
* **NFT:** mints, buys/sells, participation in collections with verifiable value.
* **Infrastructure/Bridges:** cross-chain transfers, interactions with bridges and messaging protocols.
* **Governance/DAO:** voting, delegation, participation in proposals.

#### 1.3 Action quality & “human-ness”

* **Depth of interactions:** linked action sequences (e.g., bridge → deposit → swap → LP → vote).
* **Temporal consistency:** regularity over time; avoidance of one-off spikes solely for a specific airdrop.
* **Economic rationality:** fee-to-volume ratios, asset retention, completed usage cycles.
* **Pattern uniqueness:** share of actions matching mass “scripted” templates vs. diverse routes.

**Outcome:** a **structured wallet profile** with metrics of activity, quality, and behavioral robustness.


---

# 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/wallet-data.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.