blocktivity-tx

A Blocktivity daily-transaction endpoint for the BitShares blockchain.

A scheduled GitHub Actions job queries the public BitShares Kibana/Elasticsearch cluster (https://kibana.bitshares.dev, index bitshares-*) for the last 24 hours of signed transactions and publishes the result as a static JSON file via GitHub Pages.

Endpoint

GitHub Pages serves the gh-pages branch (Settings → Pages → Deploy from a branch → gh-pages / root):

https://<owner>.github.io/blocktivity-tx/tx-daily.json

This URL is what goes into Blocktivity's txEndpoint field.

Payload

{
  "transactions": 32237,
  "period_start": "2026-10-14T22:30:00Z",
  "period_end":   "2026-10-15T22:30:00Z",
  "updated_at":   "2026-10-15T22:31:10Z",
  "chain": "BitShares",
  "chain_id": "mainnet",
  "period": "24h",
  "from_block": 115230156,
  "to_block": 115258879,
  "transaction_definition": "Successful user-submitted transactions; virtual/system operations (e.g. fill_order, asset_settle_cancel) excluded.",
  "failed_transactions_included": false,
  "system_transactions_included": false
}

Count semantics

• The index stores one document per (operation × impacted account), so counting documents overcounts and cardinality aggregations are only approximate. Distinct transactions are therefore enumerated exactly with a paginated composite aggregation over block_data.trx_id.keyword (~5 pages of 10k, ~2 s total), counting signed transactions, not operations (~32k vs ~113k per day).
• operation_history.is_virtual: false excludes chain-generated virtual operations (e.g. fill_order, asset_settle_cancel).
• BitShares activity is predominantly DEX order operations rather than plain value transfers; "transactions" here means the signed transactions a user broadcasts, of any operation type.

Publication model

main holds only code. Each run writes docs/tx-daily.json on the runner and force-pushes the contents of docs/ as a single commit to the gh-pages branch, so:

• main history stays clean and reviewable,
• the published branch always has exactly one commit,
• GitHub Pages serves the latest payload.

Because every run pushes a commit, the repository is never inactive for the 60 days that would auto-disable the schedule (see below).

Keeping the schedule alive

GitHub disables scheduled workflows in public repositories after 60 days without commits, not after 60 days without scheduled activity (see the GitHub docs). This workflow pushes a refreshed gh-pages commit every hour, so the 60-day clock is reset continuously and the schedule runs indefinitely. If it ever stops, re-enable it once in the Actions tab.

Blocktivity submission notes

Field	Value
name	BitShares
symbol	BTS
website	https://bitshares.org
txDefinition.window	rolling-24h
txDefinition.successful	included
txDefinition.failed	excluded
txDefinition.system	excluded
txDefinition.internal	excluded
txDefinition.batched	individually
txDefinition.rollup	n-a
idCg	bitshares
idCmc	463

The submitter (the named organisation that stands behind the data) and the authenticity proof are separate from this endpoint and must be arranged by the submitting organisation.

Local run

npm run tx        # writes docs/tx-daily.json (not committed; ignored)

Optional env overrides: KIBANA_URL, KIBANA_INDEX.

License

MIT — see LICENSE.