* 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...}
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")? }
@Michael_S: Did you find out more about this? Can you add some more content to the documentation?
|
|
|
Gut Cheffe, falls du irgendwelche Ratschläge suchst, kannst du dich bei mir melden.
tsupp4: Ich habe dir vor zwei Tagen ein paar Fragen geschickt und noch keine Antwort bekommen. Ich wollte ein paar Ratschläge zu deinem Geschäftsmodell.
|
|
|
Und Mint hat doch jetzt Cinnamon welches sich eher an GNOME2 anlehnt. Letztlich wird man nur durch ausprobieren feststellen was einem liegt. Ich kann KDE nicht ausstehen, wenn ich für jedesmal wenn der Krashmanager aufpoppte nen Bitcoin hätte, wäre ich reich.
Cinnamon und MATE (ist stabiler).
|
|
|
Does the bitcoin protocol support the ability to send a portion of your balance from address A to someone else's address X without sending ALL the coins from address A?
As I understand, the default transaction method in the standard client would take all the coins from A, send whatever amount you specified to address X, and send the remainder to address B, which is just another address in your wallet address pool.
You can use Electrum if you automatically want to get the change back to the sending address.
|
|
|
A command line argument for this purpose is not really necessary. You can use the gui for this.
|
|
|
Nur etwas Sarkasmus mit Würze Alles ok?
|
|
|
verkaufe 16 000BTC gegen Cash, überall Gekauft!! Treffen am Sonntag, 22:00 in Panama (hinter der Schleuse) Parole: Vollpfosten! (Bitcoins nicht vergessen)
|
|
|
Maybe I was wrong. So you can reseed imported addresses?
The possibility to create transactions offline is one of the most useful features. Though you can't do it straight forward on the command line. Wouldn't it be much easier with buttons for mktx/sendtx in the GUI?
|
|
|
And my last donation will go to the First 100 forum members (newbies not allowed) that post here on this thread the following:
I LOVE BITCOIN
YOUR BTC ADDRESS.
Donation amount: 500 BTC Maria.
I LOVE BITCOIN LOVE BITCOIN LOVE BITCOIN LOVE BITCOIN LOVE BITCOIN 1MANDXFHVUEcc8bsCrN3gnTtigArP3A2Ke
|
|
|
Is it possible to create a transaction offline using an imported address? (Deseed and reseed doesnt work with imported addresses)
|
|
|
The only reason the "other" person's card is in high demand is because it can be reloaded with BTC. What you're selling is not all that significant, and can be picked up... anywhere.
Which card is reloadable with BTC?
|
|
|
But the other color backgrounds still exist?
|
|
|
That deserves another donation
|
|
|
* 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). * Frozen addresses are displayed with a blue background. * Addresses have a 'priority' flag. Prioritized addresses will be used first when creating a transaction. Prioritized addresses are displayed with a green background.
|
|
|
Now i get this: electrum -W Ä..#..#..#..#electrum.datÄ -o addresses And no colors.
|
|
|
Thanks, this update works. I could install it on the stick.
When I open the console (shift) it shows some strange letters: electrum -w ÄIÜÊlectrumêlectrum.datÄ -o addresses
|
|
|
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
|
|
|
A few more questions: Did you run the portable version off a USB stick, or your hard drive? It's supposed to unpack all Python files into a subdirectory (the Electrum-P folder), next to the executable (elec055-portable.exe). Did it do that?
EDIT: Note that in portable mode, the executable doesn't need the -w parameter. It will automatically use the wallet file (electrum.dat) located in the same directory. Sorry, I should have mentioned this.
Indeed, I installed it on a USB Stick. (without -w) During the unpacking process, it locked up. I had to shutdown.
|
|
|
|