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

Merge branch 'release-0.7.1'

Browse Source
This commit is contained in:
Neil Booth 2016-11-20 22:03:28 +09:00
commit e2e41c3663
4 changed files with 8 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
README.rst
View File

@ -84,7 +84,7 @@ I believe all of the following play a part::
- aggressive caching and batching of DB writes - aggressive caching and batching of DB writes
- more compact and efficient representation of UTXOs, address index, - more compact and efficient representation of UTXOs, address index,
and history. Electrum-Server stores full transaction hash and and history. Electrum Server stores full transaction hash and
height for each UTXO, and does the same in its pruned history. In height for each UTXO, and does the same in its pruned history. In
contrast ElectrumX just stores the transaction number in the linear contrast ElectrumX just stores the transaction number in the linear
history of transactions. For at least another 5 years this history of transactions. For at least another 5 years this

5
docs/RELEASE-NOTES
View File

@ -1,3 +1,8 @@
version 0.7.1
-------------
- fixes an unqualified use of RPCError
version 0.7 version 0.7
----------- -----------

2
server/protocol.py
View File

@ -492,7 +492,7 @@ class Session(JSONRPC):
try: try:
return await getattr(self.daemon, method)(*args) return await getattr(self.daemon, method)(*args)
except DaemonError as e: except DaemonError as e:
raise RPCError('daemon error: {}'.format(e)) raise self.RPCError('daemon error: {}'.format(e))
def tx_hash_from_param(self, param): def tx_hash_from_param(self, param):
'''Raise an RPCError if the parameter is not a valid transaction '''Raise an RPCError if the parameter is not a valid transaction

2
server/version.py
View File

@ -1 +1 @@
VERSION = "ElectrumX 0.7" VERSION = "ElectrumX 0.7.1"