|
Version 0.34 is now available.
It introduces "type 2" key derivation: bitcoin addresses can be generated without access to the main seed.
The immediate benefit is synchronization between multiple instances of your wallet. You can open the same wallet on two different computers, if you spend bitcoins on one of them, the second wallet will be synchronized automatically. In the future, this "type2" key derivation will also allow us to implement a BCCAPI layer on the server.
This, however, comes at a cost: another forced migration of your coins to a new wallet, because older wallets will not work with the new version.
I hope that we have now reached a final format, and that is the last time such a migration is required.
Please refer to the release notes for explanations about the upgrade.
|
|
|
|
Green addresses can for example be used to have a merchant accept money faster. So unless you're somehow using electrum as a merchant, this proposal doesn't seem to make much sense, since you can spend money with 0 confirmations anyway and spending is the only thing electrum can do with newly received money.
I do not think that you can spend money with 0 confirmations currently in Electrum; but this is something I was planning to add anyway |
|
|
|
|
Today I pushed the new key generation method ("type 2 wallet"). You can test it already if you use git.
It will be included in version 0.34; please allow a few days of testing.
note that this change will requires another wallet upgrade; this should be the last one, unless we find a security flaw.
type 2 will allow us to implement nice features, such as the automatic synchronization between different instances of your wallet
|
|
|
|
Can you add support for green addresses?
Essentially its a list of addresses that you will trust even with 0 confirmations.
what would be the desired behaviour when coins come from such an address? |
|
|
|
I have an old wallet.dat file (the one before encryption) can I recover the wallet using Electrum? If so, how?
no, you need to use the official bitcoin client in order to open wallet.dat; Electrum uses a different wallet format. did you try with the official bitcoin client? |
|
|
|
Electrum doesn't seem to try to reconnect after that, just sits there.
what makes you believe that it did not reconnect ? did the icon remain red? |
|
|
|
- Shouldn't the wallet store its own version number? Otherwise we'll need to
guess it when we recover an old wallet.
the wallet stores its version number. see SEED_VERSION. Also remember that the current version is not the final one. there will be at lese one more change to the seed generation. - It would be nice if a standard data format such as JSON was used to
communicate with the server
indeed - The 'for_change' thing in 'create_new_address' is a bit odd. I suggest
considering the created address to be 'for change' when no password is
provided.
I do not understand what you mean. the password is necessary to create a new address (for now, until we have type 2 wallets) - In the wallet, addresses should be stored in a dictionnary, not an array.
Pretty much everything should be stored in a dictionnary anyway.
Yes this is one option. Someone else suggested using ParseConfig |
|
|
|
lol, maybe I should read some book about this gui? Enter? Really? That works? I've been double-clicking the stuff in history to death  . The tooltips (everywhere) only work very seldomly here. Please enable double-click, so people can find this feature ok, that's done. thanks for the feedback, btw. Any other hidden rooms or secret keys to press?
well, I guess you already noticed that labels can be edited  |
|
|
|
|
Please post the names of the banks that refuse to make transfers, or that are creating difficulties.
|
|
|
|
I don’t think you understand, my point is that the market is struggling with this initial allocation and trying to spread it out, but in doing so lowering its usefulness. (you can’t tell me that the huge volatility we have seen and are seeing is NOT largely due to this, and NOT reducing Bitcoin’s value overall)
I agree, but there are other reasons to volatility. I expect volatility to be reduced in the future My theory with the sigmoid curve is that naturally, as the reward/block grows over time, the incentive to adopt Bitcoin actually grows, and the growth of the community will adapt to it. It simply spreads out more Bitcoins to later people (this is exactly what the market has done the past 6 months!) while still maintaining its basic properties, as "peak bitcoin" would eventually be hit.
There is no way you could have matched the time constants of your sigmoid with future adoption rate. For example, the june spike was very sudden; it was completely impossible to predict when such an event, caused by mediatisation, would occur. |
|
|
|
I bring it up because I don’t like the way people think it’s perfect [...]
Bitcoin is a currency. It is not a wealth redistribution system. Therefore, it does not have to be perfect, nor even good, at allocating wealth. Unlike many people on this forum, I do believe in wealth redistribution. However, this should be achieved by governments and taxes, not by the way a currency is allocated. |
|
|
|
I know an alternative that wouldn’t have done so. It’s called a sigmoid curve ...
fair enough. indeed, Bitcoin could have been allocated differently. but you do understand that the past is history, and that we are not going to change it, don't you? |
|
|
|
This is the main reason why I still doubt bitcoins success (or think it is likely to fail once there is an alternative to it)
And, quite frankly if some people would adopt my suggestion in practice bitcoins intended purpose would be obsolete, and it's current state of existence a sophisticated gambling system would loose it's merit once people realize rapid economic growth is indeed possible.
sounds like wishful thinking... you doubt it will succeed because you want it to fail? |
|
|
|
Weekend is coming.  weekends are terrible! |
|
|
|
Litecoin has this nice clock-like icon for pending transactions. If it has 6 or more, it just shows a check-mark. If it has less, it's a pie-chart that fills up, and changes from red for no confirmations, to green for 5 confirmations.
yes, we could do that; for the moment there are only 2 icons (pending and confirmed) but we can add more |
|
|
|
A suggestion: it would be nice to see the number of confimations of each transaction in the history tab.
you have it in the tooltip, and also in the details of the transaction (navigate the history and press enter). I did not want to display it directly, because it makes bitcoin look complicated, and it becomes irrelevant after a few blocks (who wants to know if a tx has 452 or 435 confirmations?) |
|
|
|
I don't quite understand this random number generation algorithm (the "randrange_from_seed_trytryagain"). It seems overly complicated to me.
this function call is not needed. It is still in the code because it was used in the first version of Electrum, where the key was derived from a user-chosen passphrase. Since user-chosen passphrases are not secure enough, I replaced them with 128 bits random seeds, but I kept this function call in the code for backward compatibility. I will remove it when we switch to type 2 wallets. |
|
|
|
OP is a classical example of unwarranted self-importance.
and what are you? |
|
|
|
Nice This may be a stupid question but… where are the release notes? Don't know if you are keeping an official changelog somewhere or something… No, there's no real changelog at this point, except this thread. There is a file named RELEASE-NOTES, but it is intended to explain how to upgrade your wallet when changes are made that break backward compatibility (as was the case with 0.31). For the moment I still consider that this software is in an alpha stage, because there are other changes that need to be made and that will similarly break backward compatibility. Whenever such a change is made, it will be explained in the RELEASE-NOTES. |
|
|
|
Actually, you didn't include the client code either…
oh sorry. it is there now. |
|
|
|
|
Show Posts
