Pages:
Author

Topic: Electrum 2.0 release - page 4. (Read 11413 times)

legendary
Activity: 1512
Merit: 1012
March 06, 2015, 06:35:31 PM
#31
Still no luck setting up amodem. Anyone tried it? What's the best frequency?
sr. member
Activity: 644
Merit: 250
March 06, 2015, 03:15:46 PM
#30
Thanks, have been using electrum for long time now  Cheesy
copper member
Activity: 3948
Merit: 2201
Verified awesomeness ✔
March 06, 2015, 03:13:32 PM
#29
It appears this isn't technically correct. In 1.9.8, I used the importprivkey('5Key...') console command to add my own private keys, which still works; in 2.0 there is also Wallet > Private Keys > Import. It might not matter to you: I opened my 1.9.8 wallets with 2.0, had to enter my password once and wait for resync for each wallet to update, and now have no problems. 2.0 is much less flaky than 1.9.8 was for me (YMMV)
Oh, I see. Thanks stingleword! I wonder why they would add something like that to their FAQ if it isn't technically correct. Well, let's try 2.0!

EDIT: A new icon once again? Hmmm, it looks pretty good.
EDIT2: I got that C runtime error, but after that it worked like it should. Strange. Oh man, I can sweep address, sweet!
EDIT3: An invoice tab? That is freaking awesome! These are some amazing changes!
legendary
Activity: 1246
Merit: 1024
March 06, 2015, 02:42:01 PM
#28
How do I turn on HW1 support?
you need to install from sources; HW1 is not supported in the current executables.
Any reasons to why these aren't standard or are they not 100% ready?
I'm also interested in the answer to this.

it is because the developer who is doing the builds did not receive his HW1 yet

That does not explain the lack of Trezor support also in this current build.
legendary
Activity: 1896
Merit: 1353
March 06, 2015, 02:34:23 PM
#27
How do I turn on HW1 support?
you need to install from sources; HW1 is not supported in the current executables.
Any reasons to why these aren't standard or are they not 100% ready?
I'm also interested in the answer to this.

it is because the developer who is doing the builds did not receive his HW1 yet
legendary
Activity: 1008
Merit: 1001
Out of crypto entirely and don't miss it
March 06, 2015, 02:28:57 PM
#26
I'm going to repeat the question I had last time, which sadly went unanswered:

you need to create a special wallet, that will contain only imported keys.
see https://electrum.orain.org/wiki/Frequently_Asked_Questions#Can_I_import_addresses_from_other_Bitcoin_clients.3F
Could you guys explain the reasoning behind this and is their anyway around it? I have some imported addresses that are important to me, so I'm going to stick with 1.9.8 for now, I guess.
It appears this isn't technically correct. In 1.9.8, I used the importprivkey('5Key...') console command to add my own private keys, which still works; in 2.0 there is also Wallet > Private Keys > Import. It might not matter to you: I opened my 1.9.8 wallets with 2.0, had to enter my password once and wait for resync for each wallet to update, and now have no problems. 2.0 is much less flaky than 1.9.8 was for me (YMMV)
legendary
Activity: 1246
Merit: 1024
March 06, 2015, 06:52:49 AM
#25
How do I turn on HW1 support?
you need to install from sources; HW1 is not supported in the current executables.
Any reasons to why these aren't standard or are they not 100% ready?
I'm also interested in the answer to this.

And can someone give step by step instructions on compiling it with both HW1 and Trezor modules?
legendary
Activity: 942
Merit: 1026
March 06, 2015, 06:51:30 AM
#24
How do I turn on HW1 support?
you need to install from sources; HW1 is not supported in the current executables.
Any reasons to why these aren't standard or are they not 100% ready?
I'm also interested in the answer to this.
legendary
Activity: 1470
Merit: 1007
March 05, 2015, 02:41:35 PM
#23
I have to say, 2.0 is amazing - works out of the box, and has exactly the features I was hoping for.

Great job, devs.
legendary
Activity: 1246
Merit: 1024
March 05, 2015, 08:25:47 AM
#22
2 strange things in this release:
1. The default transaction fee was changed from 20000 satoshi (0.0002) to 50000 satoshi (0.0005 BTC) per kb
2. The default unit was changed from BTC to mBTC.

Yes, I noticed the change in default fee. It's a bit high to default at 0.0005btc. You can change the default fee in "Tools/Preference" anyway.

This is because the previous version was rounding the number of kilobytes in the transaction.
The new version uses the number of bytes to compute the fee, which is often smaller.

I have found that using a fee less than .0001 per kb results in the tx taking up to ten blocks or more to be mined. Better off paying .0001 per kb and getting the tx mined in one or two blocks.
legendary
Activity: 1896
Merit: 1353
March 05, 2015, 08:04:36 AM
#21
2 strange things in this release:
1. The default transaction fee was changed from 20000 satoshi (0.0002) to 50000 satoshi (0.0005 BTC) per kb
2. The default unit was changed from BTC to mBTC.

Yes, I noticed the change in default fee. It's a bit high to default at 0.0005btc. You can change the default fee in "Tools/Preference" anyway.

This is because the previous version was rounding the number of kilobytes in the transaction.
The new version uses the number of bytes to compute the fee, which is often smaller.
legendary
Activity: 952
Merit: 1005
--Signature Designs-- http://bit.ly/1Pjbx77
March 05, 2015, 04:16:17 AM
#20
2 strange things in this release:
1. The default transaction fee was changed from 20000 satoshi (0.0002) to 50000 satoshi (0.0005 BTC) per kb
2. The default unit was changed from BTC to mBTC.

Yes, I noticed the change in default fee. It's a bit high to default at 0.0005btc. You can change the default fee in "Tools/Preference" anyway.
sr. member
Activity: 252
Merit: 250
March 04, 2015, 08:54:42 PM
#19
2 strange things in this release:

1. The default transaction fee was changed from 20000 satoshi (0.0002) to 50000 satoshi (0.0005 BTC) per kb, an increase of 150%. Why this change? Isn't this a little expensive?
2. The default unit was changed from BTC to mBTC.
legendary
Activity: 1512
Merit: 1012
March 04, 2015, 03:20:33 PM
#18
Hi unamis76,

I am the developer of amodem, and would be happy to help you with the installation.
Could you please run the following commands on your console (to make sure the package is installed correctly on your OS):


$ python -c "import platform; print(platform.platform())"
$ python -c "import amodem; print(amodem)"


Any tutorial to use amodem? It's says it isn't recognized on terminal after I install it...


Hello, thank you for your time in developing this tool. I saw the thread in which you presented this a while ago. Your reward was well deserved Wink

On to business: Altough it errors out on the console, amodem seems to be working directly inside electrum. I haven't had much time to fiddle with it, but it does broadcast the transaction audio. It still gives me an error on the console though.

Here's the output of what you requested

Code:
d*****@s*****:~$ python -c "import platform; print(platform.platform())"
Linux-3.13.0-32-generic-x86_64-with-Ubuntu-14.04-trusty
d****@s*****:~$ python -c "import amodem; print(amodem)"


Besides this, have you tried your tool with a Raspberry Pi? If so, can you recomend anything for audio input? Maybe a specific external/USB soundcard?

Thanks in advance Smiley
sr. member
Activity: 333
Merit: 250
March 04, 2015, 12:37:56 PM
#17
Hello

I've downloaded the portable and non-portable versions and I've got this message (Avast) :


Thank you
newbie
Activity: 26
Merit: 0
March 04, 2015, 06:50:03 AM
#16
Im having issues with Electrum Sync'ing up, and when i click the network button the client freezes, i am restarting my pc now and will report back if anything changes / fixes its self.


*edit - No change, stuck in sync mode, it looks like it is connecting to a server, and i base that off the fact that ive seen a few different messages in the console tab.

ive also tried using the "wallet.synchronize()" option as well, and that did not fix it.

I'm having similar issue. Ubuntu 14.10 if it matters.
legendary
Activity: 952
Merit: 1005
--Signature Designs-- http://bit.ly/1Pjbx77
March 04, 2015, 04:16:27 AM
#15
Downloaded it and installed it just now. The new wallet seed now has 13 words instead of 12 previously.

There seem to be a hard limit of 5 decimals to be shown for all sums. This regardless of your choice of unit of measure (BTC, mBTC or bits).

I have the full 8 decimal points when I select BTC as unit. Try to select "BTC", close preference window, then open again to adjust decimal points.
newbie
Activity: 1
Merit: 0
March 04, 2015, 03:22:20 AM
#14
Just upgraded. Looks nice, worked smoothly - good job! ...except for one thing:

There seem to be a hard limit of 5 decimals to be shown for all sums. This regardless of your choice of unit of measure (BTC, mBTC or bits). I happen to prefer BTC, but with merely 5 decimals, this will truncate a lot of my sums.

Why is there a hard limit of 5 decimals?
Is there a way, by means of console or whatever, to override this?

I want to see my satoshis! Wink
newbie
Activity: 16
Merit: 0
March 04, 2015, 02:50:47 AM
#13
Hi unamis76,

I am the developer of amodem, and would be happy to help you with the installation.
Could you please run the following commands on your console (to make sure the package is installed correctly on your OS):


$ python -c "import platform; print(platform.platform())"
$ python -c "import amodem; print(amodem)"


Any tutorial to use amodem? It's says it isn't recognized on terminal after I install it...
legendary
Activity: 1512
Merit: 1012
March 03, 2015, 02:26:56 PM
#12
Any tutorial to use amodem? It's says it isn't recognized on terminal after I install it...
Pages:
Jump to: