Who is guarding NEAR?

GET https://api.fastnear.com/v1/account/{account}/staking        # which pools the account uses
POST https://rpc.mainnet.fastnear.com  query call_function
     {pool}.get_account({"account_id": account})                 # staked, unstaked, can it be withdrawn
     {pool}.get_reward_fee_fraction()                             # the fee right now
The verdict joins that with the pool's last 30 days of uptime from this site's data (pipeline/analyze.py).

-- Every epoch boundary on NEAR mainnet, found from the token supply alone.
--
-- NEAR mints staking rewards once per epoch, in the epoch's first block. Every other block only
-- burns fees. So the first block of an epoch is exactly a block whose total supply is higher than
-- the block before it. That block's parent hash is the id the protocol gives to the epoch after
-- next, which is what the `validators` RPC method takes.
--
-- Scans block_height, block_timestamp, prev_block_hash and total_supply: about 15 GB for all history.
-- Narrow @from_date / @to_date to scan less. Always filtered on block_date.
WITH blocks AS (
  SELECT
    block_date,
    block_height,
    block_timestamp,
    prev_block_hash,
    total_supply,
    LAG(total_supply) OVER (PARTITION BY block_date ORDER BY block_height) AS supply_before
  FROM `bigquery-public-data.crypto_near_mainnet_us.blocks`
  WHERE block_date BETWEEN @from_date AND @to_date
),
day_end AS (
  SELECT block_date, MAX_BY(total_supply, block_height) AS closing_supply
  FROM `bigquery-public-data.crypto_near_mainnet_us.blocks`
  WHERE block_date BETWEEN DATE_SUB(@from_date, INTERVAL 1 DAY) AND @to_date
  GROUP BY block_date
)
SELECT
  b.block_height                                             AS epoch_start_height,
  b.block_timestamp                                          AS epoch_start_timestamp_ns,
  b.prev_block_hash                                          AS last_block_hash_of_previous_epoch,
  b.total_supply / 1e24                                      AS supply_after_mint_near,
  COALESCE(b.supply_before, d.closing_supply) / 1e24         AS supply_before_mint_near,
  (b.total_supply - COALESCE(b.supply_before, d.closing_supply)) / 1e24 AS minted_near
FROM blocks AS b
LEFT JOIN day_end AS d
  ON d.block_date = DATE_SUB(b.block_date, INTERVAL 1 DAY)
WHERE b.total_supply - COALESCE(b.supply_before, d.closing_supply) > 100e24
ORDER BY b.block_height

POST https://rpc.mainnet.fastnear.com   {"method": "validators", "params": {"epoch_id": "<id>"}}
One call per epoch, 4,410 epochs since 29 March 2021. Staked = sum of current_validators[].stake.
Supply at each epoch comes from sql/01_epoch_boundaries.sql. Code: pipeline/fetch_chain.py, pipeline/analyze.py

For each of 660 staking pools, at block 224,048,464:
  {pool}.get_reward_fee_fraction()
  {pool}.get_accounts({"from_index": i, "limit": 500})     # every delegator: staked, unstaked, can_withdraw
A pool is private when its fee is 100% and one account holds at least 95% of it.
The line is those pools' stake in each epoch's validator set, divided by total stake.
Code: pipeline/fetch_pools.py, pipeline/analyze.py (census)

From the census above: for each validator, the stake held by
  meta-pool.near, linear-protocol.near and lst.rhealab.near
compared with the validator's total and with the lowest stake in the active set (the entry bar).
Operators: pools that report the same owner account, plus the name families in data/static/operators.csv.

For each epoch: reward per staked NEAR at full uptime
    = 90% x (NEAR minted for the epoch, adjusted for validators that were offline) / total stake
A pool earns that times its uptime factor: 0 below 90% uptime, full at 99%, a straight line between.
A delegator keeps (1 - fee). Compounded over the 102 epochs of the last 30 days and annualized.
Checked against the chain: see "Does the model match?" in METHOD.md. Code: pipeline/metrics.py

Same validator sets as chart 02, one point per day.
Leaving now: sum of unstaked_balance where can_withdraw is false, across every pool in the census.
Accounts adding stake or unstaking in a day: sql/03_staking_pool_usage.sql on the NEAR BigQuery dataset, 8 November 2026 and 9 November 2026.
Active accounts: sql/02_network_daily.sql, median of the last 30 days.

{pool}.get_owner_id()                                 # the account that controls the pool
GET https://api2.near.social/v1/accounts/{owner}     # has_profile, name, followers, posts