# Fastbuy DB

> Work with the BSC meme-token swap database (Four.meme, Flap and OpenFour) through the fastbuy-db MCP server. Use it when asked about tokens, swaps, wallets, volumes, pools or indexer state; when writing SQL against this database; or when the tables four_tokens, flap_tokens, openfour_tokens, four_curve_swaps, flap_curve_swaps, openfour_curve_swaps, four_dex_swaps, flap_dex_swaps, openfour_dex_swaps, dex_pools, indexer_state come up.

- Skill: `alxlemesh/fastbuy-db` (Agent Skill, multi-file: 4 files)
- Install (CLI): `npx skillmds@latest add alxlemesh/fastbuy-db`
- Raw SKILL.md: https://api.skillmd.com/api/skills/alxlemesh/fastbuy-db/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Data & Analytics
- Author: alxlemesh (https://skillmd.com/u/alxlemesh)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/alxlemesh/fastbuy-db

---


# The fastbuy swap database

An index of BSC meme-token swaps. Six swap streams, each in its own table:

|                | Four.meme          | Flap               | OpenFour               |
| -------------- | ------------------ | ------------------ | ---------------------- |
| bonding curve  | `four_curve_swaps` | `flap_curve_swaps` | `openfour_curve_swaps` |
| DEX afterwards | `four_dex_swaps`   | `flap_dex_swaps`   | `openfour_dex_swaps`   |

Tokens live in `four_tokens`, `flap_tokens` and `openfour_tokens`. The indexer writes them;
everyone else reads. Through this MCP server the access is read-only: any write is rejected
by the database role itself.

## Ask the server before trusting this file

This skill is a **copy**, pinned to the version in its `plugin.json`, and the database moves
with the indexer: a migration lands over there and every word below can be a release behind
without saying so. So start by fetching the current text from the server:

- **`get_guide`** — the schema reference and the ready-made queries as the server holds them
  right now. One call, and it is exactly the material in `references/` but never stale.
- **`describe_table`** — the columns, types and indexes of one table from the live catalog;
  righter than any prose, including the guide's.
- The server's own instructions arrive on connect and say the same in three lines.

Where the server and this file disagree, **the server is right**. What follows is the
offline summary: enough to write a sane query before the first call, not the source of
truth.

## Four things people trip over

**1. Addresses and hashes are `BYTEA`, not text.**

```sql
-- to search: the index will be used
WHERE token = addr('0xbb4cdb…')
-- to display
SELECT hex(token) AS token
```

Or read the `<table>_hex` views — the same columns with addresses as strings:
`four_tokens_hex`, `flap_curve_swaps_hex`, and so on. `WHERE token = '0x…'` without
`addr()` will not work: the types do not match.

**2. Amounts are `NUMERIC(78,0)` in wei and arrive as strings.**

That is a `uint256`: 78 digits, which do not fit into a double. In code wrap them in
`BigInt`, never in `Number`. Dividing by `10^decimals` must use the precision of the
specific quote: every known one has 18, `XAUt` has 6. Never assume eighteen for a quote
you do not recognise.

**3. A wallet is matched against three fields at once.**

`maker` is who received the tokens, `tx_from` is who signed the transaction, `tx_to` is
who it was addressed to. A purchase made through the trader's own contract never lands in
`maker`, because the contract receives the tokens. So:

```sql
WHERE maker = addr($1) OR tx_from = addr($1) OR tx_to = addr($1)
```

All three fields are indexed. The `get_txs_by_maker` tool does this for you.

**4. OpenFour is a protocol of its own, not a flavour of Four.meme.**

Its table shares the prefix and nothing else: the supply is `max_supply` (not
`total_supply`), the lifecycle is a numeric `phase` from the contract's enum — 0 `Created`,
1 `Trading`, 2 `MigratePending`, 3 `Migrated`, 4 `Terminal`, 5 `SoldOut`, and the enum gets
extended — instead of a `status` word, and the quote is always a real ERC20, never the zero
address. `get_tokens` takes `phase` for it and `status` for the other two; in SQL, joining
an OpenFour swap to `four_tokens` finds nothing.

## The server's tools

Start with a ready-made query and reach for `execute_sql` when it is not enough.

| Tool               | When                                                              |
| ------------------ | ----------------------------------------------------------------- |
| `get_guide`        | First: the current schema reference and recipes from the server   |
| `get_swaps`        | Swaps under any filter: token, wallet, side, quote, pool, period  |
| `get_txs_by_maker` | Every swap of an address — `maker`, `tx_from` and `tx_to` at once |
| `get_tokens`       | Find a token by symbol, name, address, creator, status or phase   |
| `get_token`        | Token card: fields, pools, trade counters, volumes per quote      |
| `get_wallet`       | Wallet summary: trades, volumes, favourite tokens                 |
| `top_traders`      | Who traded the most over a period                                 |
| `list_tables`      | What the database holds and how much it weighs                    |
| `describe_table`   | Columns, types, indexes and foreign keys of one table             |
| `execute_sql`      | An arbitrary `SELECT` when no ready-made tool fits                |
| `indexer_status`   | How far the indexer got and whether it fell behind                |

## Do not

- **Treat an empty answer as an error.** Tokens launched before the indexer started are not
  in the database, and neither are their swaps. Before blaming the query, check
  `indexer_status`: the period you asked about may simply not be indexed.
- **Add up volumes across different quotes.** BNB, USDT and a tokenized stock are different
  units; they can only be summed one quote at a time.
- **Turn amounts into `Number`.** The precision is lost silently.
- **Search by `tx_hash` expecting an index.** The hash indexes were dropped (migration
  `0004`): such a search is a full table scan. Bound it by a period or a block range.
- **Trust `reltuples` as an exact count.** `list_tables` and `indexer_status` report the
  planner's estimate; for an exact number use `COUNT(*)` or the `count` parameter of
  `get_swaps`.

## Further reading

Both files are mirrored by `get_guide`, which serves the server's copy of them — reach for
the tool when the server is connected, and for these when it is not.

- [references/schema.md](references/schema.md) — every table, column, type and index, what
  each field means and what its `NULL` means.
- [references/recipes.md](references/recipes.md) — ready-made queries: wallet swaps, token
  volumes, fresh launches, indexer health.