Account activity
Direct requests by initiating account. Select an account to focus the evidence.
An account may serve many users. These IDs do not count independently operated applications.
Chain Signatures research
Activity, account mix and economic evidence for NEAR.
Loading saved evidence…
Activity snapshot
11 November 2026 UTC · indexed parent-transaction cohort · blocks 223,988,378–224,135,609
—Direct signing requests
—Initiating account IDs
—Signer-touching parent transactions
—Top-three account share
Loading interpretation…
Observed signing requests establish use of the service. The available periods do not establish a lasting adoption trend.
Signing requests are not destination settlements. Full-workflow economics and independent operator identities are not measured.
Counting rules and coverage
One request = one distinct retained receipt containing an exact sign FunctionCall, filtered to v1.signer during collection. Responses, internal completion and other methods are excluded.
Parent inclusion defines the cohort. Descendant receipts may fall outside the day. Older normalized records retain creation timestamps, not execution timestamps, and omit raw receivers and outcomes. Provider completeness has not been independently established against a full node.
Full method and corrections ↗Historical comparison
Matched parent cohorts · 00:00–01:00 UTC on 10 and 11 November 2026. Two hours do not establish a lasting trend.
Loading comparison evidence…
Accounts & receipts
Filter the selected cohort. Counts use all matching requests; the table shows the first 20 receipt rows.
| Initiating account | Receipt creation (UTC) | Receipt / parent transaction |
|---|
All account counts and excluded methods
Archives and offline reproduction
npm test npm run independent-audit npm run build npm run serve
Reproduction verifies retained evidence and calculations. Network recollection is separate. It does not independently prove index completeness.
Recorded build output
Evidence interpretation
Signals to investigate next
The full-day cohort and the two selected hours are different populations. These are research interpretations and investigation signals, not forecasts or a buy/sell recommendation.
Direct-stage fees and sensitivity assumptions
All scenario requests count; operator independence is unknown. Assumes constant sampled fees and protocol rules. Excludes parent transactions, responses, cleanup, other contracts and destination fees. This is not a forecast, service revenue or token price model. Intents fees and buybacks are separate.
80 measured fee outcomes ↗Further thesis boundaries
More persuasive adoption evidence would include repeated complete-day cohorts over several weeks, independently identified unrelated app operators, linked destination outcomes and complete NEAR workflow fees. Declining account concentration alone would not prove broader adoption.
Utility depends on signing-service security and availability. Outbound signing does not independently verify inbound chain state. This research does not establish superiority over other systems or a token price implication.