Topic: [ANNOUNCE] Electrum - Lightweight Bitcoin Client - page 20. (Read 274569 times)
Could the Electrum server be made to work over I2p using the bitcoin I2p patch - https://bitcointalksearch.org/topic/bitcoin-client-with-i2p-patch-151181
It looks like binary data. What does this represent?
the serialized transaction.
Where can I find some documentation on the Electrum server protocol?
More specifically, I would like to know what kind of data the server is returning after calling "blockchain.transaction.get"
I always get a string of 514 characters but I don't understand it.
It looks like binary data. What does this represent?
More specifically, I would like to know what kind of data the server is returning after calling "blockchain.transaction.get"
I always get a string of 514 characters but I don't understand it.
It looks like binary data. What does this represent?
Code:
Opened the 'curl_log.log' file
Request
[{"id":"862110703-51e456ceec82e","method":"blockchain.transaction.get","params":["220b98a69a48b54628f20a184f03ea7f02ffb84607bbf13ad521b12cb5618b84",137988]}]
Responce
HTTP/1.0 200 OK Server: BaseHTTP/0.3 Python/2.7.1+ Date: Mon, 15 Jul 2013 20:08:48 GMT Set-Cookie: SESSION=XYLYM7PB5X Content-type: application/json-rpc Access-Control-Allow-Origin: * Content-length: 0
Request
[]
Responce
HTTP/1.0 200 OK Server: BaseHTTP/0.3 Python/2.7.1+ Date: Mon, 15 Jul 2013 20:08:48 GMT Set-Cookie: SESSION=XYLYM7PB5X Content-type: application/json-rpc Access-Control-Allow-Origin: * Content-length: 561 {"id": "862110703-51e456ceec82e", "result": "01000000011aefed5f80fcafea1b360c3f88aacc9569c9a344459bff39ba1ae79f6893d91d010000008a4730440220427a61aca2754798478aca1d0e49ca91203ebda26316b314e23ab87ef5d19a4f022077edd964a52b0a5c19394387509c9687ef5ce7bc8df5552bb85646378a1dac17014104cf90502732e522352e6b6cc91281ea7424689e581c2cb4af9004d611a4b09244ced0bc97a78d82725977d5640d54f4a89a481fc8a622377919de3757e292093dffffffff0240299894000000001976a91479e4695d38fa6ef341d634457c7dd136130d440b88acc0fc9b01000000001976a9140165587152ef8d3767d91d4485121a3b650d741188ac00000000"}
Result
string '01000000011aefed5f80fcafea1b360c3f88aacc9569c9a344459bff39ba1ae79f6893d91d010000008a4730440220427a61aca2754798478aca1d0e49ca91203ebda26316b314e23ab87ef5d19a4f022077edd964a52b0a5c19394387509c9687ef5ce7bc8df5552bb85646378a1dac17014104cf90502732e522352e6b6cc91281ea7424689e581c2cb4af9004d611a4b09244ced0bc97a78d82725977d5640d54f4a89a481fc8a622377919de3757e292093dffffffff0240299894000000001976a91479e4695d38fa6ef341d634457c7dd136130d440b88acc0fc9b01000000001976a9140165587152ef8d3767d91d4485121a3b650d741188ac000000'... (length=514)
I think that project is legit. I forwarded 2 btc from the old Electrum donation address.
In the latest MultiBit release (0.5.12) I have changed the fee from a flat 0.0005 BTC to match the bitcoin-QT fees (basically 0.0001 BTC per 1000 bytes as Tacticat mentions).
...
:-)
Jim
...
:-)
Jim
fees in electrum seem to be modifiable by user. at least I managed to change the fees proposed by client app and it was still accepted in the blockchain. I mean if it is a sensitive topic (0.0005 vs 0.0002 vs 0.0001) just make fees variable/editable by users
You can set the fee you see enough for the TX, non sufficient will be rejected before broadcasting, but the 0.0005 is a editable recommended fee.
In the latest MultiBit release (0.5.12) I have changed the fee from a flat 0.0005 BTC to match the bitcoin-QT fees (basically 0.0001 BTC per 1000 bytes as Tacticat mentions).
...
:-)
Jim
...
:-)
Jim
fees in electrum seem to be modifiable by user. at least I managed to change the fees proposed by client app and it was still accepted in the blockchain. I mean if it is a sensitive topic (0.0005 vs 0.0002 vs 0.0001) just make fees variable/editable by users
Now that the QT client recommends a 0.0001 fee, could electrum go back to do the same? The sooner we all switch to the lower fee, the sooner miners will include it in new blocks as frequently as they did with the previous 0.0005 fee.
yes, I will do that.
(I know MultiBit is off topic in this thread but bear with me).
In the latest MultiBit release (0.5.12) I have changed the fee from a flat 0.0005 BTC to match the bitcoin-QT fees (basically 0.0001 BTC per 1000 bytes as Tacticat mentions).
There is an odd phenomenom that if all the clients drop their fees our users are all better off, but if only one does their users' transactions will get 'bumped down the list' and probably end up in later blocks. (This happens especially when there is a long gap between blocks and the unconfirmed tx start piling up).
I suggest we seize the day and ALL decrease our default fees and save our users some cash. The miners get that lovely 25 BTC coinbase so I don't think they will notice.
I think I will cross post in the Armory and Bitcoin wallet threads whilst I am feeling rebellious !
:-)
Jim
edit:
Bitcoin Wallet cross post : https://bitcointalksearch.org/topic/fee-rebellion-242257
Armory cross post: https://bitcointalksearch.org/topic/fee-rebellion-242255
I am running Electrum 1.8 (Python sources) on Windows Vista. It initially took a long time to connect and then to synchronize but nothing compared to how long a full node would. I restarted the client several times, finally it is displaying my balance.
When this happen, switch servers or restart the client.
I am running Electrum 1.8 (Python sources) on Windows Vista. It initially took a long time to connect and then to synchronize but nothing compared to how long a full node would. I restarted the client several times, finally it is displaying my balance.
use electrum.coinwallet.me server, fast and great uptime
I am running Electrum 1.8 (Python sources) on Windows Vista. It initially took a long time to connect and then to synchronize but nothing compared to how long a full node would. I restarted the client several times, finally it is displaying my balance.
Is there a more thorough console documentation anywhere? Or is the existing documentation as thorough as it gets?
The transaction worked when the newly generated input got fully confirmed. When the wallet has unconfirmed newly generated input and you deposit bitcoin on top then you can't send any transaction since the client will try to send the first unconfirmed newly generated input first. Even if using separate deposit address.
Try freezing the addresses you don't want the client to het funds from.
The transaction worked when the newly generated input got fully confirmed. When the wallet has unconfirmed newly generated input and you deposit bitcoin on top then you can't send any transaction since the client will try to send the first unconfirmed newly generated input first. Even if using separate deposit address.
All my balance has 20+ confirm but I get this when trying to send a transaction:
Any idea what is happening?
Using Electrum 1.8
EDIT: Realised those are newly generated coins... Maybe I need more than 20+ confirm.
Any idea what is happening?
Using Electrum 1.8
EDIT: Realised those are newly generated coins... Maybe I need more than 20+ confirm.
"Coins generated aren't considered confirmed by the Bitcoin protocol for 100 blocks. It is advisable to wait some additional time for a better chance that the transaction will be propogated by all nodes. The classic bitcoin client won't show generated coins as confirmed until the 120th block."
https://en.bitcoin.it/wiki/Confirmation
edit: nvm
All my balance has 20+ confirm but I get this when trying to send a transaction:
Any idea what is happening?
Using Electrum 1.8
EDIT: Realised those are newly generated coins... Maybe I need more than 20+ confirm.
Any idea what is happening?
Using Electrum 1.8
EDIT: Realised those are newly generated coins... Maybe I need more than 20+ confirm.
"Coins generated aren't considered confirmed by the Bitcoin protocol for 100 blocks. It is advisable to wait some additional time for a better chance that the transaction will be propogated by all nodes. The classic bitcoin client won't show generated coins as confirmed until the 120th block."
https://en.bitcoin.it/wiki/Confirmation
All my balance has 20+ confirm but I get this when trying to send a transaction:
Any idea what is happening?
Using Electrum 1.8
EDIT: Realised those are newly generated coins... Maybe I need more than 20+ confirm.
Any idea what is happening?
Using Electrum 1.8
EDIT: Realised those are newly generated coins... Maybe I need more than 20+ confirm.
"Coins generated aren't considered confirmed by the Bitcoin protocol for 100 blocks. It is advisable to wait some additional time for a better chance that the transaction will be propogated by all nodes. The classic bitcoin client won't show generated coins as confirmed until the 120th block."
https://en.bitcoin.it/wiki/Confirmation
All my balance has 20+ confirm but I get this when trying to send a transaction:
Any idea what is happening?
Using Electrum 1.8
EDIT: Realised those are newly generated coins... Maybe I need more than 20+ confirm.
Any idea what is happening?
Using Electrum 1.8
EDIT: Realised those are newly generated coins... Maybe I need more than 20+ confirm.
Found this on google : http://download.electrum.org/
Scam ?
Have lunch the last portable nighlty build in a VM and nothing happen
https://www.virustotal.com/en/file/3e8892ca0c1464e2ecf0ac8427f1ba7e91d4fbd9775fd32df3b167730a7a40c7/analysis/
Scam ?
Have lunch the last portable nighlty build in a VM and nothing happen
https://www.virustotal.com/en/file/3e8892ca0c1464e2ecf0ac8427f1ba7e91d4fbd9775fd32df3b167730a7a40c7/analysis/
I would call 1 out of 47 a false positive. Slush hosts the binaries since Github stopped offering binary downloads.
What is the difference between slush fork and official ?
I don't find the slush repo on Github
Jump to: