I personal use https://8gadgetpack.net/. They still push updates and also they've updated the old gadget with new high dpi versions. |
|
|
|
Still thanks for telling and actually fixing it  |
|
|
|
Yes, I can confirm it works now as intended on my machine. Do you mind telling me what caused the issue? Thanks again for fixing. |
|
|
|
Ok here are the results when I have open the litecoin gadget and edit the mycoin gadget:  Every API request is valid but it sends just 100 per second until I get blocked for to many requests. |
|
|
|
Hi here are some answers to your questions. - I use fiddler to detect and debug API requests.
- At the moment I have one instance of each gadget open. 1x Bitcoin, 1x Litecoin and 1x MyCoin
What data would help you to find the source of this issue? |
|
|
|
|
Thanks for the reply.
I did add the value you recommended but the behavior didn't change.
I still get 100 api request per second after I apply the settings.
What I noticed it's only on my Windows 10 machine with "8gadgetpack" installed.
Maybe that's the reason for the strange behavior?
Thanks
|
|
|
|
|
First I want to say thanks for the work.
Also I got a little issue.
If I change some variables in the gadget, for example switch from LTC/BTC to LTC/USD, nothing happens.
After I restart the sidebar I noticed the gadget spams the API Server with requests.
Am I doing something wrong?
|
|
|
|
Thanks a lot.
According to the bitcoin wiki I should't use this format until further adoption. Should I crate a new wallet an move my btc over?
"shouldn't" is not the right word to use here. it is basically about when you want to receive bitcoin payments. for example if you want to cash out from a casino that casino may not support Bech32 address format so you are forced to give them another format (the legacy starting with 1 or 3). the best solution is that if you are already using a wallet that supports this then use that anywhere that you can so that you can use the benefits of it such as a smaller transaction size hence a lower fee but also keep another wallet so that you can still receive bitcoin in case you encountered a problem like the payer didn't accept Bech32. I don't think bitcoin wiki would say that... as pooya says it's just advice that you should be prepared that not every service you use will be able to support it yet. It's just as if you've adopted a new format that's not widely supported. No different from upgrading a software for documents in a new format older versions won't be able to read. I still maintain my original pre-Segwit wallet. But I already find I don't need it as much anymore as my SegWit address. Look forward to using only bech, I'd say 2020 is a good date to target. That what's written in the wiki While this address format has been included in some implementations, as of December 2017, the address format is not recommended for use until more software supports the format. source: https://en.bitcoin.it/wiki/Bech32But anyway I will try to use the bench32 + SegWit until I hit an insurmountable resistance. Thanks |
|
|
|
|
Thanks a lot.
According to the bitcoin wiki I should't use this format until further adoption. Should I crate a new wallet an move my btc over?
|
|
|
|
Thanks a lot. Especially DannyHamilton's explanation helped me to understand how transaction fees work. |
|
|
|
@TryNinja Thanks for clearing this up with the inputs and the major privacy concerns. Payment with several addresses in the same wallet does not require an additional fee.
How can I understand this? If all my addresses are generated by the same seed they don't require additional fee? Exactly How will the BTC network know that I used the same seed? |
|
|
|
@TryNinja Thanks for clearing this up with the inputs and the major privacy concerns. Payment with several addresses in the same wallet does not require an additional fee.
How can I understand this? If all my addresses are generated by the same seed they don't require additional fee? |
|
|
|
|
Hi,
Wallets like Electrum or Ledger Nano S generate a different receiving address every time I use them. I noticed I can reuse the previous generates addresses again.
Why shouldn't I use the same address for every transaction? Wouldn't this save me some fees when I spend the coins?
I'm curios for your thoughts.
Thanks
|
|
|
|
@AdolfinWolf thanks for the anwser I was curios and did a test with jaxx and exodus. Long story short my ETC funds showed up in both walltes while using the same seed. Is it possible, say, have the same seed for different Electrum wallets? For example, I have BTC, BCH, VTC, etc Electrum wallets. Can I use the same seed for all of them?
So this shows that you definitely can use the same seed but your funds may not show up. |
|
|
|
|
Hi,
I'm wondering if it's a good idea to use the same seed in differtent wallets applications like electreum, jaxx or exodus?
If not what are the risks?
Already thx for an anwser.
|
|
|
|
Thanks for the anwser. You really helped me out. but in reality, it is more complicated than that. So I can't calculate all the private keys manually outside of the wallet software? |
|
|
|
|
Hi,
I'm looking for some anwsers that I can't figure out my self.
Type 1 deterministic wallet use SHA256(string + n) n=numbers of adress since creation to restore adresses.
Does a Type 2 hierarchical deterministic wallet the same? Just with a seed generated from 12 words out of a list and some mechanics to slow down bruteforce?
Hope someone can help me or point me in the right direction.
Thanks
|
|
|
|
|
Show Posts
