Bitcoin protocol and software changes as JSON
Bitcoin protocol and software changes as JSON: Bitcoin Core merges and releases, BIP updates, Lightning spec and implementation changes. Each item has status (proposal, merged, released, activated), layer (consensus, policy, p2p, wallet), why it matters, what has not happened yet, and primary source links.
Answeringour last check, 2026-10-10
1 of 1checks answered this week
538 msmedian answer time
$0.01listed price per call
$0.01price it asked us
Paid test badge: not yet. The checks above are free: we call the tool without paying and read the payment request it sends back. The Verified badge needs paid calls whose answers match the promised output, and nobody can buy a badge.
Endpoint
GET https://btc-radar.vercel.app/bitcoin/technical-updates
| Category | Market data |
|---|---|
| Provider host | btc-radar.vercel.app |
| Networks | eip155:8453, eip155:84532 |
| Payment schemes | exact |
| Self-reported calls, 30 days | 3 from 3 payers (the provider's figure, not ours) |
Our checks, last 30 days
| Day | Result | HTTP | Asked | Time |
|---|---|---|---|---|
| 2026-10-10 | valid payment request | 402 | $0.01 | 538 ms |
Example input (from the provider)
{
"method": "GET",
"queryParams": {},
"type": "http"
}
Promised output schema (from the provider)
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {
"input": {
"additionalProperties": false,
"properties": {
"method": {
"enum": [
"GET"
],
"type": "string"
},
"queryParams": {
"properties": {},
"type": "object"
},
"type": {
"const": "http",
"type": "string"
}
},
"required": [
"type",
"method"
],
"type": "object"
},
"output": {
"properties": {
"example": {
"type": "object"
},
"type": {
"type": "string"
}
},
"required": [
"type"
],
"type": "object"
}
},
"required": [
"input"
],
"type": "object"
}