Electrum Personal Server beta release

Electrum Personal Server is an implementation of the Electrum wallet server protocol that allows users to point their Electrum wallet at their own full node. It is compatible resource-saving features like pruning, blocksonly and disabled txindex. It is much less resource-intensive than other Electrum servers because it only stores the user's own addresses, instead of every address that was ever used. As such it makes tradeoffs, namely losing Electrum's "instant on" feature.

Full node wallets are important in bitcoin because they are an big part of what makes the system be trustless. No longer do people have to trust a financial institution like a bank or paypal, they can run software on their own computers. If bitcoin is digital gold, then a full node wallet is your own personal goldsmith who checks for you that received payments are genuine. You wouldn't accept large amounts of cash or gold coins without checking they are actually genuine, the same applies for bitcoin.

Full node wallets are also important for privacy. Using Electrum under default configuration requires it to send all your bitcoin addresses to some server. That server can then easily spy on you. Full node wallets like Electrum Personal Server would download the entire blockchain and scan it for the user's own addresses, and therefore don't reveal to anyone else which bitcoin addresses they are interested in.

Right now using Electrum Personal Server is the easiest way to use a hardware wallet backed by your own full node. It is very lightweight, being a small python script that barely uses any CPU or RAM; much less than the full node it's connected to. Hopefully Electrum Personal Server can be part of the solution in putting full node wallets into the hands of as many people as possible.

The project is now in beta release: https://github.com/chris-belcher/electrum-personal-server

It now has all the essential features to make it practical for use; Merkle proofs, deterministic wallets, bech32 addresses, SSL, Core's multi-wallet support. Along with the features that were in the alpha release of tracking new transactions, confirmations, block headers, importing addresses.

Further Reading:

submitted by /u/belcher_
[link] [comments]
Bitcoin – The Currency of the Internet

If you are running unpruned node consider running an Electrum server to support BIP148 (reddit.com)

Hi All! If you happen to be running unpruned node please consider running an Electrum server to support BIP148. This will ensure BIP148 has light client support post fork if there happens to be two chains. Electrum server requires additional 20GB on top of 120GB required by Bitcoin Core. It will take 1-2 days to sync on a HDD, probably faster on SSD. You will also need an open port for the light client to connect. If you are running Linux instructions are here:…


where do i place auth in a AJAX RPC server call

Getting a 401 on my AJAX ‘getinfo’ request to Coin rpc api I am running this script on chrome with cors security turned off

$  .ajax({   url: "http://" +  username + ":" + password +    "@",   type: 'POST',   contenType: 'application/json',   cache:false,   dataType:"json",   data: encodedData,   timeout: 15000  })  .done(function(msg){   alert(msg);   console.log(msg)  });  var encodedData = JSON.stringify ( {    "jsonrpc": "2.0",    "method": "getinfo",   "params": "",   "id": 1  } );  

this curl script hits the server and returns all info fine..

   curl --user username:password -d "{\"jsonrpc\": \"1.0\", \    "id\": 1, \"method\": \"getinfo\", \"params\": [] }" -i -X POST -H     "Content-Type: application/json" 



i have hidden the pass for this post and know for sure where username and password are written has the correct details Thanks for any help it would be much appreciated. leave bitcoin address for tips from me for anyone who unblocks me 🙂

Recent Questions – Bitcoin Stack Exchange