JSON-RPC: fix error code for non-existing finalized block

src/schemas/block.json

@@ -126,7 +126,7 @@
 		"title": "Block tag",
 		"type": "string",
 		"enum": ["earliest", "finalized", "safe", "unsafe", "pending", "latest"],
-		"description": "`latest`: **DEPRECATED** Currently an alias for `unsafe`, will be removed at some point in the future; `earliest`: The lowest numbered block the client has available; `finalized`: The most recent crypto-economically secure block, cannot be re-orged outside of manual intervention driven by community coordination; `safe`: The most recent block that is safe from re-orgs under honest majority and certain synchronicity assumptions; `unsafe`: The most recent block in the canonical chain observed by the client, this block can be re-orged out of the canonical chain; `pending`: A sample next block built by the client on top of `unsafe` and containing the set of transactions usually taken from local mempool. Before the merge transition is finalized, any call querying over `finalized` or `safe` block MUST be responded with `-32100: Unknown block` error"
+		"description": "`latest`: **DEPRECATED** Currently an alias for `unsafe`, will be removed at some point in the future; `earliest`: The lowest numbered block the client has available; `finalized`: The most recent crypto-economically secure block, cannot be re-orged outside of manual intervention driven by community coordination; `safe`: The most recent block that is safe from re-orgs under honest majority and certain synchronicity assumptions; `unsafe`: The most recent block in the canonical chain observed by the client, this block can be re-orged out of the canonical chain; `pending`: A sample next block built by the client on top of `unsafe` and containing the set of transactions usually taken from local mempool. Before the merge transition is finalized, any call querying over `finalized` or `safe` block MUST be responded with `-32099: Unknown block` error"
 	},
 	"BlockNumberOrTag": {
 		"title": "Block number or tag",