[ANNOUNCE] Electrum - Lightweight Bitcoin Client

[ThomasV]

Is it somehow possible to use the paying (sending) address itself as change address?

not with the gui, but you can specify the change address with the command line.

What if i freeze the change address, where does the change go then?

freeze has no effect on receiving

[1714201798]

1714201798

[1714201798]

1714201798

[bitcats]

Ok, thanks!

May be the option to set the change addr will be added to the gui in near future 

[Xenland]

How do I help contribute to documentation is their a page I can be referred to??

https://en.bitcoin.it/wiki/Electrum

Thats more like "How to use electrum" I was under the assumption we were talking about how to help develop with eletrum kind of docs...

[Lumpy]

Maybe now that there is an expert mode setting, various features from the command line could be added to the GUI?

Import/export keys would be nice, selecting change addresses, etc.

[Michael_S]

Hello Thomas and all,

I have written some documentation based on my understanding, from the viewpoint of a user with some basic technical understanding but without too deep background, i.e. from my standpoint :-)  (hope this is somewhat representative).

I think this material can be used both for the Wiki (I do not know how to best put it into the Electrum Wiki - it is quite a lot of text and I did not want to "spam" the wiki page with it), and also for some "help" text in the client itself (for help buttons or context-sensitive right-click).

Note that for some points I was not sure if my understanding is right, I have surrounded these text sections with {curly brackets}. Especially, the concept of "gap limit" is completely unclear to my, I did not find anything when searching and googling. So you can "CTRL-F" for "{" or "}" to jump to those parts.

Now here we go (sorry if you cannot read it easily in that window - just copy-paste it to a text editor on your PC for more convenient reading...):

Code:

Documentation of Basic and Advanced Features in Electrum:
=========================================================

Legend in this documentation:
-----------------------------
* A [word or term in square brackets] means that this is explained in another dedicated entry of this documentation.
* A {text in curly brackest} means I am not really sure about this... --> other people should correct/clarify


What is the "Wallet"? (general, not specific to Electrum)
---------------------------------------------------------
Your wallet is a list of Bitcoin addresses (more precisely: the privat/public key pairs). Each address "contains" (or is associated with) a certain amount of Bitcoins at a given time.
Your wallet's balance is the sum of all Bitcoins of all your wallet's Bitcoin addresses.
Your wallet consists of both [normal addresses] and [change addresses]. Although they are fully equivalent from the Bitcoin protocol's point of view {right?}, they are different in how they are used by Bitcoin clients like Electrum.


How are New "Normal Addresses" Created for my Wallet? (more or less general, not too specific to Electrum)
----------------------------------------------------------------------------------------------------------
The Bitcoin client (e.g. Electrum) allows you to trigger manually the generation of a new Bitcoin address. you typically want to create a new address when you want to receive Bitcoins from somebody and do not want to use any of the wallet's present addresses for this, for privacy reasons (note that all transfers are publically visible in the blockchain).


What is a "Change Address", and why is it useful? (general, not specific to Electrum)
-------------------------------------------------------------------------------------
The concept of change addresses is a feature not of the Bitcoin protocol, but of a Bitcoin client. It is implemented in most {if not all?} Bitcoin clients, including Electrum.

How it works:
Whenever your Bitcoin client (e.g. Electrum) sends Bitcoins from your wallet's address "A" to a foreing address "B", a new change address "C" is created by Electrum and added to your wallet.
Example: Address "A" has 20 BTC. Electrum sends 9 BTC from "A" to "B". The change (20-9 = 11 BTC) is sent to the "change address" "C". For this purpose, address "C" is created by Electrum at this moment and added to your wallet.
{Exception: If all the Bitcoins of "A" are sent to "B", there is no point in creating a change address "C" {or is "C" created anyway, yet without any Bitcoins sent to it??? - depends on the bitcoin client's implementation, would not make any sense, but would not harm either}}

Actually, Bitcoin clients would also work without change addresses. In this case, the change would be sent back to "A" instead of the new address "C".

Why the concept of "change addresses" is useful:
* Using a new change address makes it more difficult for other people (by analyzing the blockchain) to track how many Bitcoins you have or where you're spending them.
* It also conceals which output is the "spend" and which is the "change".


What is a "Deterministic Wallet" in Electrum?
---------------------------------------------
Traditionally, all new addresses (incl. the private keys of course) added to the wallet ([Normal Addresses] or [Change Addresses]) are generated randomly. This is the case e.g. for the original "Satoshi Bitcoin Client" (at least as of today, version 0.6.2).
Contrary to that, a Bitcoin client with a "Deterministic Wallet" will generate all new addresses accoding to a pre-defined (i.e. "deterministic") algorithm as a function of a wallet-specific [seed] (a 128 bit number). This means, if the seed is known, all new addresses that Electrum will ever create for this wallet are known, because Electrum's algorithm is known (and open source).
This is a big advantage when it comes to making wallet backups:
* _Traditionally_, a wallet backup just contains the bitcoin addresses (and private keys of course) that have been created by the client by the time the backup was made. If the user performs transactions after the backup, new addresses ([normal] or [change] addresses) will be generated and added to the wallet. These are not included in the backup yet. If the wallet in use gets lost, all the Bitcoins that are associated with the new addresses will also be lost. To avoid the risk of a too high loss, regular wallet backup are important.
* _With a Deterministic Wallet_ (like with Electrum), the wallet backup only needs to contain the seed, and all new addresses generated in the future are safe. Regular successive backup are not required! {or is this not entirely true?? I do not know exactly if the "[gap limit]" plays a role here...?!?}


What is the "Seed" of a Deterministic Wallet in Electrum?
---------------------------------------------------------
The Seed of a [deterministic wallet] is a series of 128 random bits in Electrum.
For convenience, a seed can also be expressed by a sequence of 12 {always 12?} words in Electrum. Also generation of a QR code is supported to facilitate the backup of the seed.

So there are 2^128 possible seeds for a deterministic wallet in Electrum.
For comparison, the total number of Bitcoin addresses is 2^160, and the number of atoms on earth is 2^166.
So there exists one Bitcoin address per 1 Million atoms on earth, and there exists one seed of Electrum wallets per 4.3 Billion Bitcoin addresses.
(BTW: The number of atoms in the complete universe is estimated as 2^266).

{
Open Point: I _do not know_ whether the algorithm of deterministic address generation is designed such that for any two seeds "S1" and "S2" (out of the 2^128 possible different seeds) the following condition holds true: If 4.3 Billion (2^32 to be exact) new addresses are calculated from S1 and from S2, the algorithm guarantees that there will be no collision between the set of 2^32 addresses from S1 and the set of 2^32 addresses from S2.
If this condition does not hold true, I am wonderng whether the use of deterministic wallets still bares an acceptably low probability of address collisions.
}


What is the "Gap Limit" in Electrum?
------------------------------------
{
Apparently, when I generate too many new addresses, I exceed the "gap limit" at some point - whatever this means. It reads to me that this could be dangerous somehow in the sense that the new addresses might not be recoverable from the wallet's seed...?!??!?? Or not?? Not clear to me at all...
Not clear to me what this means. I thought the wallet is deterministic, so why should the be a problem wiht a "gap limit" (whatever this means).
}

{
Quote of ThomasV on v.0.54 of Electrum:
The 'receive' tab now has a 'new' button, that allows the user to create addresses beyond the wallet's gap limit. The user gets a warning, and addresses that are beyond the gap limit are displayed in red. The red color will remain until the gap has been filled. (in other words, to fill the gap you need to send coins to the last non-red address of your list).

Quote of ThomasV on v.0.55 of Electrum:
the 'receive' tab has a 'new' button that allows to create new addresses by raising the wallet's gap limit. Note that the gap limit can be lowered too. The dialog also displays the minimum value of the gap limit that can be set without losing any of your current addresses (this assumes you are connected, because it needs to compute the maximal gap of your sequence of addresses)

But still I do not understand at all the meaning of "gap limit" and what should be my concerns as a user about it.
}


What does it mean to "Prioritze" or "Freeze" Addresses in Electrum?
-------------------------------------------------------------------
{
{This is my understanding/assumption - please correct if necessary}
When sending Bitcoins to a foreign address, Electrum will by default use a built-in method to select the address(es) of the wallet used for sending these Bitcoins.

* When you _prioritize_ some of your wallet's addresses, these addresses will be used with priorities, and other addresses will not be used until the prioritized addresses contain no more Bitcoins.
* When you _freeze_ some of your wallet's addresses, these addresses will not be used for sending bitcoins but they will keep their balance.
  {Will they still not be used if all other addresses have zero balance,such that sending Bitcoins is not possible although the wallet has a vbalance? I think so, just not 100% sure...}

Note: Clearly, an address can not be tagged "prioritied" and "frozen" at the same time.
}


What does the "Tx" column mean in Electrum?
-------------------------------------------
--> Applies to "Receive" tab (own wallet's addresses) and "Contacts" tab (foreing addresses).

Tx stands for {... ?? "Transaction"? "Transmission" ?? ...}

The Tx column in Electrum displays a number for each Bitcoin address in the address list, both for own addresses ("Receive" tab) and for foreing addresses ("Contacts" tab).

In the "Receive" tab (own addresses):
The number in the Tx column indicates the total number of _incoming_ Bitcoin transactions that have ever been sent to this address.
{
The number of outgoing transactions is apparently not counted. I am wondering why the column is called "Tx" and not "Rx", because I understand that it indicates the number of times that Bitcoins had been sent to this address, i.e. how often This address "received" Bitcoins.
Does this "Tx" come from blockchain/blockexplorer terminology? Or why is it called "Tx" ("transmit") and not "Rx" ("receive")?
}

In the "Contacts" tab (foreign addresses):
The number in the Tx column indicates the total number of Bitcoin transactions that have ever been received by this address {from anyobody? or just from myself, i.e. from addresses in my wallet? - I assume the latter - but to be confirmed...}.


What does the "Balance" column mean in Electrum?
------------------------------------------------
--> Applies to "Receive" tab  only (i.e. own wallet's addresses).

The balance column indicates the amount of Bitcoins belonging to the given address.
The individual balances add up to the total balance of your wallet.


What does the "Flag" column mean in Electrum?
---------------------------------------------
--> Applies to "Receive" tab  only (i.e. own wallet's addresses).

This column indicates certain properties of the different addresses:
C = [Change address]
    Without a "C" it means it is a [normal address]
P = [Prioritized address]
F = [Frozen address]

Note: P and F flags can be applied to both [normal] and [change] addresses.

{Am I missing any flags?}

PS: I would like to say that I like the concept of Electrum a lot, and the way Thomas is developing the client, the conceptual work and the way he structures it - this is all really good indeed. I think this is going to become a terrific client (an excellent one it already is today)!

[ThomasV]

I think this material can be used both for the Wiki (I do not know how to best put it into the Electrum Wiki - it is quite a lot of text and I did not want to "spam" the wiki page with it), and also for some "help" text in the client itself (for help buttons or context-sensitive right-click).

thanks for that!
I guess the best way to proceed is to create a new wiki page, distinct from the existing one.

edit: text moved here https://en.bitcoin.it/wiki/Electrum/Documentation

[ThomasV]

May be the option to set the change addr will be added to the gui in near future  

indeed, I think that a checkbox to return the change to the sending address is simple enough to be added to the gui (in expert mode).

[bitcats]

indeed, I think that a checkbox to return the change to the sending address is simple enough to be added to the gui (in expert mode).

That would be one of my favorite options 

[ThomasV]

Here is version 0.56

new features (Qt gui only):

* Labels found in URIs are added to your address book
Example: bitcoin:1NTiGdrGgQrA46x9dv7XKhznKgcHrhVxo?label=ThomasV
(there is a confirmation dialog)

* Auto-completions: the 'Pay to' text entry has auto-completions, just like a web browser's URL box.
  It uses the set of labels in your addressbook (no, it does not use firstbits)

[arby]

anyone else having a LOT of problems with their servers recently?

[flatfly]

anyone else having a LOT of problems with their servers recently?

Not that I know of... Which server in particular?

[arby]

Edit:

It was because I was using 0.41, after updating to the latest client (0.56) everything seems to be working fine.


I keep getting server not ready.

I have been trying to use electrum.novit.ro, btcback.com, ecdsa.org, electrum.bitcoin.sk.

electrum.bitcoin.sk seems to be working but, it does not show my recent transactions.

Anyway, what server are you using? I tried to find a server list but I was unable to.

anyone else having a LOT of problems with their servers recently?

Not that I know of... Which server in particular?

[Lumpy]

Is there an option to delete a contact?

[ThomasV]

Is there an option to delete a contact?

I just wrote it today
it will be in the next version

[ThomasV]

version 0.57 is available.

Changes:
* fixed language code for vietnamese and slovenian translations
* gui option to send change back to the input address of a transaction (expert mode)
* new menu items: delete a contact from your list, view details of an alias, of a tx
* various keyboard shortcuts to allow navigation without the mouse.

[bitcats]

That deserves another donation   

[Lumpy]

I love this fast-and-furious development.

BTW, on Windows I've taken to using:

python setup.py build
python setup.py install

The install breaks at "running install_data" but since it successfully does "running install_lib" it works to use python electrum afterwards. If I don't build/install, the libraries for the new version(s) aren't updated.

[Lumpy]

A couple more suggestions:

In the transactions details window, could the text be selectable?
Any thoughts on adding a link to blockchain.info and/or blockexplorer.com for the transaction as well?

[ThomasV]

I love this fast-and-furious development.

BTW, on Windows I've taken to using:

python setup build
python setup install

The install breaks at "running install_data" but since it successfully does "running install_lib" it works to use python electrum afterwards. If I don't build/install, the libraries for the new version(s) aren't updated.

oh, I see. I can skip that step for Windows.

edit: I modified the install script so that it does not install data files on windows. can you check that it works? (use version 0.57b)

[ThomasV]

A couple more suggestions:

In the transactions details window, could the text be selectable?
Any thoughts on adding a link to blockchain.info and/or blockexplorer.com for the transaction as well?

not easily.
The text is not selectable because you are using Windows; I do not know how to fix that.
What I can do is add a button to paste the transaction ID into the clipboard, so that you can paste it in your browser.