RanchiMall/electrumx
3
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Prepare 0.10.14

Browse Source
This commit is contained in:
Neil Booth 2017-01-29 08:29:41 +09:00
parent 0202b2210a
commit 4a8cec9988
3 changed files with 17 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
README.rst
View File

@ -135,6 +135,12 @@ version prior to the release of 1.0.
ChangeLog
=========
Version 0.10.14
---------------
* misc cleanups and code changes to prepare for peer discovery in 0.11.0
* add `docs/PEER_DISCOVERY.rst`_
Version 0.10.13
---------------
@ -273,3 +279,4 @@ stability please stick with the 0.9 series.
.. _#102: https://github.com/kyuupichan/electrumx/issues/102
.. _#103: https://github.com/kyuupichan/electrumx/issues/103
.. _docs/HOWTO.rst: https://github.com/kyuupichan/electrumx/blob/master/docs/HOWTO.rst
.. docs/PEER_DISCOVERY.rst: https://github.com/kyuupichan/electrumx/blob/master/docs/PEER_DISCOVERY.rst

18
docs/PEER_DISCOVERY.rst
View File

@ -13,7 +13,7 @@ Peer Database
A persistent store of peers with at least the following information
about a peer so that state persists across server restarts. This
information is required for a response to the *server.peers.subscribe*
information is required for a response to the **server.peers.subscribe**
RPC call:
* host name
@ -42,8 +42,8 @@ to 10 servers that have shown commitment to reliable service.
In ElectrumX this is a per-coin property in `lib/coins.py`.
Response to "server.peers.subscribe" RPC call
---------------------------------------------
Response to server.peers.subscribe RPC call
-------------------------------------------
This RPC call is used by Electrum clients to get a list of peer
servers, in preference to a hard-coded list of peer servers in the
@ -83,8 +83,8 @@ available. It tries to reconnect to each peer once every 24 hours and
drops peers if two weeks have passed since a successful connection.
"server.features" RPC call
--------------------------
server.features RPC call
------------------------
This is a new RPC call that a server can use to advertise what
services and features it offers. It is intended for use by Electrum
@ -123,7 +123,7 @@ Currently ElectrumX understands and returns the following keys:
* **server_version**
A string that identifies the server software. Should be the same as
the response to 'server.version' RPC call. Defaults to "unknown".
the response to **server.version** RPC call.
* **protocol_version**
@ -137,15 +137,15 @@ Currently ElectrumX understands and returns the following keys:
'p' in the IRC real name.
"server.add_peer" RPC call
--------------------------
server.add_peer RPC call
------------------------
This call is intended for a new server to get itself in the connected
set.
It takes a single parameter (named **features** if JSON RPCv2 named
parameters are being used) which contains the same information as the
*server.features* RPC call would return.
**server.features** RPC call would return.
A server receiving a **server.add_peer** call should not replace
existing information about the host(s) given, but instead schedule a

2
server/version.py
View File

@ -1 +1 @@
VERSION = "ElectrumX 0.10.13"
VERSION = "ElectrumX 0.10.14"