standardize "history too large" error code

Author: SomberNight

docs/protocol-changes.rst

@@ -239,6 +239,7 @@ Changes
     which aims to provide some clarity re whether the server supports optional features.
   * :func:`server.ping` can now also be sent as an unrequested notification, by both the client
     and the server. The request/response signature also changed.
+  * Standardize "history too large" error code for `blockchain.scriptpubkey.*` methods.
 
 New methods
 -----------

docs/protocol-methods.rst

@@ -329,6 +329,10 @@ Return the confirmed and unconfirmed history of a :ref:`scriptPubKey <scriptpubk
   See :func:`blockchain.scriptpubkey.get_mempool` for how mempool
   transactions are returned.
 
+  If the history of the spk is too long (busy address, touched by thousands of txs),
+  and so the server refuses to serve it, it SHOULD send a JSON-RPC error with integer code `10_001`
+  to communicate this to the client.
+
 **Result Examples**
 
 ::
@@ -507,6 +511,10 @@ Subscribe to a :ref:`scriptPubKey <scriptpubkeys>`.
     .. function:: blockchain.scriptpubkey.subscribe(scripthash, status)
        :noindex:
 
+  If the history of the spk is too long (busy address, touched by thousands of txs),
+  and so the server refuses to serve it, it SHOULD send a JSON-RPC error with integer code `10_001`
+  to communicate this to the client.
+
 blockchain.scriptpubkey.unsubscribe
 ===================================