dopey
|
|
December 26, 2013, 04:48:28 AM |
|
Very good advice, listen to gweedo.
|
|
|
|
|
|
|
|
|
TalkImg was created especially for hosting images on bitcointalk.org: try it next time you want to post an image
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
lanfanblue
Newbie
Offline
Activity: 31
Merit: 0
|
|
December 26, 2013, 05:33:34 AM |
|
Thanks for this OMG client with Coin Control. But I wonder how much can I rely on the tx size/fee estimation in Coin Control? I just noticed that tx size estimated is 300 bytes less than actual tx size in some cases. Maybe that's a minor bug? The underestimation in tx size occurs when multisignature address is involved. This tx https://blockchain.info/tx/d84613726465c27ce641bd20a4385dfada887effee99d77b01548e13403066d2contains 5 inputs and 2 outputs. The address starting with 33 is a 3-of-3 multisignature address. The actual size is 1264 bytes, but in Coin Control it is reported as 946 bytes. Coin Control does not check the address type, I guess. Multisig address is larger than normal address, and ignoring address type leads to this underestimation in tx size. Hope this could be fixed soon, and we can expect a reliable fee estimation. You probably shouldn't be using coin control until you understand what you are doing. You have to decide what the fee is, coin control allows you to easily create a custom transaction so it is just going to take the leftover coins and send them as a fee. Be very careful! Try this on the testnet before using it on your real bitcoins. Thanks for suggestions. I understand the risk using coin control. I will double check when using it. So, for fees, I still need to estimate the fee myself even when using coin control?
|
|
|
|
Heads-Tails
Newbie
Offline
Activity: 19
Merit: 0
|
|
February 25, 2014, 10:48:41 AM |
|
I am interested in using CoinControl and am wondering what direction to go...
I'm running standard Bitcoin-Qt ver 0.8.6 at the moment.
Can I just run an installation of win32 0.8.5-OMG10 and overlay onto my existing 0.8.6 version of bitcoin-QT?
or should I do a seperate install of 0.8.5-OMG10 into its own directory, then copy over existing blockchain and wallet.dat directories?
Which method would least troublesome?
I would of course do full backup of existing sys before trying this.
|
|
|
|
wtogami (OP)
|
|
February 25, 2014, 11:35:32 AM |
|
Bitcoin OMG10 has all the bug fixes that were in Bitcoin-Qt 0.8.6. It is fully compatible with the data and wallet of the standard Bitcoin-Qt. That being said you should always make backups of wallet.dat on a regular basis.
|
If you appreciate my work please consider making a small donation. BTC: 1LkYiL3RaouKXTUhGcE84XLece31JjnLc3 LTC: LYtrtYZsVSn5ymhPepcJMo4HnBeeXXVKW9 GPG: AEC1884398647C47413C1C3FB1179EB7347DC10D
|
|
|
wtogami (OP)
|
|
March 27, 2014, 07:18:19 AM Last edit: March 27, 2014, 10:46:27 AM by wtogami |
|
https://github.com/litecoin-project/bitcoinomg/commits/0.8.7-OMG12tag v0.8.7-OMG12 is similar to Luke-Jr's 0.8.7rc1 with the following differences. * Removed the three OP_RETURN pruning patches. It seemed to have made it incompatible with indexes from 0.8.x. * Reduced the relay fee by 10x to match the behavior of Bitcoin 0.9.0. * Added the getnormalizedtxid RPC that was not accepted in Bitcoin Core. This is an experiment. * Many 0.9 features backported and carried forward from earlier versions of Bitcoin OMG. You really should be using Bitcoin 0.9. But if for some reason you can't, this version should be fully compatible with data from Bitcoin 0.8.x while including the important bug and security fixes from 0.9. Most of the credit for this round of patches goes to Luke-Jr. Status Update March 26th, 2014: v0.8.7-OMG12 contains all of the security and bug fix workarounds pertaining to transaction malleability that were included in Bitcoin 0.9. You really should be using Bitcoin 0.9. Use this only if you need 0.8.x for some reason and you understand how to make backups. At the moment this branch is only lightly tested, so please report back if you run into any issues.
|
If you appreciate my work please consider making a small donation. BTC: 1LkYiL3RaouKXTUhGcE84XLece31JjnLc3 LTC: LYtrtYZsVSn5ymhPepcJMo4HnBeeXXVKW9 GPG: AEC1884398647C47413C1C3FB1179EB7347DC10D
|
|
|
SloRunner
Member
Offline
Activity: 88
Merit: 10
|
|
September 14, 2014, 10:33:52 AM |
|
well, you just saved 380MB of my memory thanks for disablewallet=1
|
|
|
|
iron man
Newbie
Offline
Activity: 28
Merit: 0
|
|
September 17, 2014, 08:29:47 AM |
|
before adding it to litecoin, better have a careful test.
|
|
|
|
wtogami (OP)
|
|
October 01, 2014, 07:24:48 PM |
|
Update Oct 1st, 2014:https://github.com/litecoin-project/bitcoinomg0.9.3 plus many backports including watch-only. Can you help to test especially the watch-only parts?
|
If you appreciate my work please consider making a small donation. BTC: 1LkYiL3RaouKXTUhGcE84XLece31JjnLc3 LTC: LYtrtYZsVSn5ymhPepcJMo4HnBeeXXVKW9 GPG: AEC1884398647C47413C1C3FB1179EB7347DC10D
|
|
|
|
wtogami (OP)
|
|
November 13, 2014, 10:28:54 AM |
|
|
If you appreciate my work please consider making a small donation. BTC: 1LkYiL3RaouKXTUhGcE84XLece31JjnLc3 LTC: LYtrtYZsVSn5ymhPepcJMo4HnBeeXXVKW9 GPG: AEC1884398647C47413C1C3FB1179EB7347DC10D
|
|
|
|