Bitcoin Forum
May 24, 2024, 10:50:58 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: « 1 ... 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 [76] 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 ... 233 »
1501  Bitcoin / Armory / Armory 0.96.1 is out! on: July 28, 2017, 02:41:07 AM
Builds available on the Github release page, as usual:

https://github.com/goatpig/BitcoinArmory/releases/tag/v0.96.1

Changelog (https://github.com/goatpig/BitcoinArmory/blob/v0.96.1/changelog.txt):

Quote
== Added ==
   - Raised default fee to 200 satoshi/Bytes. This fee will apply when using defaults and the node RPC is down.
     Any applied fee lower than that rate will trigger a warning message box. Users have to actively choose to
     bypass the warning.
   - Split unit tests building from default autotools setup. To build tests, use:
      ./configure --enable-tests.
   - You can now disable GUI in the autotools build system. Use:
      ./configure --without-gui
   - When spawned with a cookie file, the DB now randomizes its listen port to (49150 + [0-15000]) and reports it in the cookie file.
   - Added --fcgi-port command line argument to the DB
   - Address comments are now visible again in the Coin Control GUI
   - DB messages now have checksums; this improves error and version mismatch detection
   - Transactions that failed to broadcast throug the P2P layer will now be pushed to the RPC afterwards, if it's enabled
   - Refresh address view in Wallet Properties dialog on several user interactions.
   - RPC status is now signaled in the bottom right corner status bar. Disabled RPC will result in bold purple text.
   - Highly improved DB corruption self diagnosis and automated fixing.
   - Zero confirmation parser pool now is now capped at 100 threads.
     You can modify this value with the --zcthread-pool command line argument.

== Fixed ==
   - ZC parsing will no longer occur while the BDM is initializing
   - Wait on cookie file creation before connecting to auto managed DB
   - Fixed registration/callback premature garbage collection
   - Translation patch issues
   - Fixed "Fund from wallet" lockbox GUI
   - Fixed TxIn/Out pretty printing
   - Tied init phase spinning icon rotation to progress notifications. The icon will not spin when no progress data is received, correctly
     indicating the DB is hanging.   
   - Fixed cryptopp build against older CPUs (no AES or PCLMUL archs).
   - Fixed RBF bumping with no change.
   - Improved timestamps granularity in logs.
   - Improved transaction broadcast consistency.
   - Improved error message verbose of timed out transaction broadcasts.
   - ./configure --prefix now propagates correctly to Makefiles.
   - Fixed several memleaks in the database code.
   - Fixed false positive throws over bad packet detection in socketing layer.
   - Fixed coin selection edge cases.
   - Fixed the displaying of address comments in the lobby ledger.

== Removed ==
   - Python-twisted dependency. This should remove the underlying openSSL dependency as well.
   - Database command prompt will no longer appear when auto managing the DB on Windows

Note:

0.96.2 is in tow with lots of DB fixes and improvements and offline builds.
1502  Bitcoin / Armory / Re: How to install or Run Armory Plugins? on: July 28, 2017, 12:23:15 AM
I'm sorry. I have no idea what this means or how to do it. Like I said, I'm not a coder, and have no experience with this kind of thing. I really just need a how-to guide, to talk me through the process.

At this rate you are better off paying a service to help you recover.
1503  Bitcoin / Armory / Re: 0.96.1 testing build #4 on: July 27, 2017, 11:55:57 PM
https://github.com/goatpig/BitcoinArmory/blob/master/cppForSwig/BlockDataManagerConfig.cpp#L32
1504  Bitcoin / Armory / Re: Installing Armory on Ubuntu on: July 27, 2017, 11:25:26 PM
It's like Mordor man. You don't simply walk in there, and you don't simply log in a root, do a bunch of stuff, and expect your system to still be sane. If you don't trust me, at least trust in Sean Bean. He dies for your sin like every other year.

How do you even log as root on Ubuntu? I thought that was disabled entirely.
1505  Bitcoin / Armory / Re: Installing Armory on Ubuntu on: July 27, 2017, 11:17:30 PM
Yeah don't. You might as well reinstall your OS at this point.
1506  Bitcoin / Armory / Re: 0.96.1 testing build #4 on: July 27, 2017, 10:57:56 PM
logs
1507  Bitcoin / Armory / Re: Installing Armory on Ubuntu on: July 27, 2017, 10:57:34 PM
Oh boy, are you actually logged in as root, or did you just su?
1508  Bitcoin / Armory / Re: 0.96.1 testing build #4 on: July 27, 2017, 10:36:49 PM
i didn't get an answer to this in the other thread so i thought i'd post it here:

is there any general reason why both 0.95.1 and 0.96 *.deb in a Debian VM would both show Connected status bottom right but be stuck at 470751?  everything else appears ok.

getblockcount shows correct height.

Connected only means the DB is connected to a node over the P2P layer. The block height is what your DB sees as the longest chain. If it's behind your node, your DB has an issue. Try 0.96.0.4, it fixes a lot of that stuff.
1509  Bitcoin / Armory / Re: armory failed to spawn the db on: July 27, 2017, 10:10:05 PM
Coins were moved from your wallet. It's obvious since you received change back. This is for you to figure out, from my perspective nothing went wrong. It is still possible you got hacked, but the scenario is pretty convoluted. It would suggest someone got a copy of your wallet, figured out your password, and went through the process of sending you change back, which is unlikely at best.

If you can't figure it out, try harder, or start looking at people in your entourage. It is entirely easier to for someone with physical access to your computer to drain your wallet than some random hacker online gaining access to it remotely.
1510  Bitcoin / Armory / Re: Bitcoin Cash (BCC) and Armory on: July 27, 2017, 09:58:07 PM
So what is the advice for Armory users post Aug 1st hard fork?

99% chance that stuff won't go anywhere. Just wait and see. If it looks like it's gonna last more than 2 weeks and there's demand to move coins on that chain, I'll update the signer to work with their replay protection.
1511  Bitcoin / Armory / Re: armory failed to spawn the db on: July 27, 2017, 09:56:13 PM
So you're saying someone robbed you but credited you change so as to exactly pay himself 1 BTC? Go through your financial history, figure out which service you paid 1 BTC to and take it with them...
1512  Bitcoin / Armory / Re: Installing Armory on Ubuntu on: July 27, 2017, 09:54:32 PM
Are you trying to install the 32bit package on a 64bit machine? Linux isn't like Windows, you can't mix and match architectures like that.
1513  Bitcoin / Armory / Re: armory failed to spawn the db on: July 27, 2017, 09:52:51 PM
Do you happen to have 0.00020289 BTC left in your wallet?
1514  Bitcoin / Armory / Re: btcarmory.com/ and https://www.bitcoinarmory.com/ on: July 27, 2017, 03:52:47 PM
The one in my sig.
1515  Bitcoin / Armory / Re: Armory Sync issue on: July 27, 2017, 01:32:20 PM
Github release page:

https://github.com/goatpig/BitcoinArmory/releases
1516  Bitcoin / Armory / Re: How to install or Run Armory Plugins? on: July 27, 2017, 01:31:30 PM
The module folder should be in the source dir. Did you build the code from source?
1517  Bitcoin / Armory / Re: Funds not showing in wallet on: July 27, 2017, 01:27:23 PM
1) Start BitcoinQt, let it fully sync.

2) Empty the content of this folder: C:\Users\Vital\AppData\Roaming\Armory\databases

3) From the command prompt, run:
Code:
ArmoryDB.exe --db-type=DB_BARE

4) Start ArmoryQt.exe
1518  Bitcoin / Armory / Re: Bitcoin Cash (BCC) and Armory on: July 26, 2017, 11:33:51 PM
Their transaction replay protection is all opt-in. Transactions on Bitcoin ABC are still in the current transaction format.

Not anymore. BitcoinABC has now strong replay protection.

I don't know if this changes the compatibility with Armory.

You can check your balance on their chain, you can't spend unless I implement their sighash change. Won't bother unless their coin survives the initial 2 weeks.
1519  Bitcoin / Armory / Re: Problem on: July 26, 2017, 07:45:08 PM
1)How to make sure that my BTCQT is running against my custom datadir(what is datadir?)

Start bitcoin-qt with this argument:
Code:
-datadir="D:\Bitcoin"

Either run it from the command prompt or create a shortcut for it and add the argument to the shortcut's target.

Quote
2)Isn't the latest Armory 0.96?

There's been 4 testing builds out for 0.96.1 so far. Check the release page:

https://github.com/goatpig/BitcoinArmory/releases

Quote
3)What does boostrap the DB mean?

Initializing from scratch, i.e. no existing state/empty folder.
1520  Bitcoin / Armory / Re: armory failed to spawn the db on: July 26, 2017, 07:40:57 PM
https://btcarmory.com/docs/pathing
Pages: « 1 ... 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 [76] 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 ... 233 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!