What is the thinking behind this technology.. most people I know, wants to go to shops to interact with other people. {The social side of life} We like to sit in a Coffee shop and watch people and the things they do... check out all the craziness in this world. I do see the need for this, if you are handicapped or anti-social and you do not want to deal with other people. The VR stuff is cool, but I think people are over engineering the technology. If I wanted to buy something from the privacy of my home, a normal website with pictures of the products will do nicely. The Realty & Property business is more suited to VR technology with 3D tours to showcase properties imo. Good point, shopping in malls and shops has its charms and VR takes the social side out but there's a lot more to do with the technology.
|
|
|
sent you a PM
I'm testing it also.
Cool!
|
|
|
I rarely find something extraordinary these days but the Lumiere Virtual Shop is the coolest thing I've seen in a while. It's a sort of collection containing virtual shops from all sectors like clothing, electronics, cars and furniture. You can even take the furniture and place it in your room to see how it looks. This will surely be the next big thing in online shopping. If you're a beta tester as well please hit me up so we can play around the rooms in the same time. I strongly recommend everyone who owns a VR to join the beta testing program and test out the features: https://l-os.com/beta-testing-program/ If you don't have a VR already, you can join the program and purchase an Oculus Rift or HTC Vive and have it shipped in a few days which is unbelievable considering the waiting periods on the official oculus site. I joined the program on Monday and received my Oculus today.
|
|
|
It's currently tuned to run at around 1GB.
that's interesting b/c i had to increase it from 2GB to 4GB to get it to run again.
|
|
|
crap, it's back!: -Ubuntu:~/BitcoinArmory$ python ArmoryQt.py ******************************************************************************** Loading Armory Engine: Armory Version: 0.94.1 Armory Build: 811798a928 PyBtcWallet Version: 1.35 Detected Operating system: Linux OS Variant : ('Ubuntu', '14.04', 'trusty') User home-directory : /home/x Satoshi BTC directory : /home/x/.bitcoin/ Armory home dir : /home/x/.armory/ ArmoryDB directory : /home/x/.armory/databases Armory settings file : /home/x/.armory/ArmorySettings.txt Armory log file : /home/x/.armory/armorylog.txt Do wallet checking : True (ERROR) ArmoryQt.py:1336 - 5 attempts to load blockchain failed. Remove mempool.bin. (ERROR) ArmoryQt.py:1341 - File mempool.bin does not exist. Nothing deleted. -INFO - 1460505492: (BlockUtils.cpp:924) blkfile dir: /home/x/.bitcoin/blocks -INFO - 1460505492: (BlockUtils.cpp:925) lmdb dir: /home/x/.armory/databases -INFO - 1460505492: (lmdb_wrapper.cpp:387) Opening databases... -INFO - 1460505492: (BlockUtils.cpp:1105) Executing: doInitialSyncOnLoad -INFO - 1460505493: (DatabaseBuilder.cpp:162) Reading headers from db -INFO - 1460505499: (DatabaseBuilder.cpp:195) Found 407055 headers in db -INFO - 1460505506: (DatabaseBuilder.cpp:43) updating HEADERS db -INFO - 1460505508: (DatabaseBuilder.cpp:223) parsed block file #491 -DEBUG - 1460505508: (Blockchain.cpp:213) Organizing chain -INFO - 1460505508: (DatabaseBuilder.cpp:47) updated HEADERS db in 1.785s -INFO - 1460505508: (DatabaseBuilder.cpp:98) scanning new blocks from #225967 to #407009 -INFO - 1460505528: (BlockchainScanner.cpp:636) scanned from height #225967 to #229667 -INFO - 1460505551: (BlockchainScanner.cpp:636) scanned from height #229668 to #232781
-INFO - 1460506296: (BlockchainScanner.cpp:636) scanned from height #368954 to #370252 -INFO - 1460506309: (BlockchainScanner.cpp:636) scanned from height #370253 to #371493 -INFO - 1460506321: (BlockchainScanner.cpp:636) scanned from height #371494 to #372486 terminate called after throwing an instance of 'std::bad_alloc' what(): std::bad_alloc Aborted How much RAM does your computer have? I think Armory might be using up too much RAM. well, there you go. doubled my memory and it's working again what clued you in? that mempool.bin error?
|
|
|
crap, it's back!: -Ubuntu:~/BitcoinArmory$ python ArmoryQt.py ******************************************************************************** Loading Armory Engine: Armory Version: 0.94.1 Armory Build: 811798a928 PyBtcWallet Version: 1.35 Detected Operating system: Linux OS Variant : ('Ubuntu', '14.04', 'trusty') User home-directory : /home/x Satoshi BTC directory : /home/x/.bitcoin/ Armory home dir : /home/x/.armory/ ArmoryDB directory : /home/x/.armory/databases Armory settings file : /home/x/.armory/ArmorySettings.txt Armory log file : /home/x/.armory/armorylog.txt Do wallet checking : True (ERROR) ArmoryQt.py:1336 - 5 attempts to load blockchain failed. Remove mempool.bin. (ERROR) ArmoryQt.py:1341 - File mempool.bin does not exist. Nothing deleted. -INFO - 1460505492: (BlockUtils.cpp:924) blkfile dir: /home/x/.bitcoin/blocks -INFO - 1460505492: (BlockUtils.cpp:925) lmdb dir: /home/x/.armory/databases -INFO - 1460505492: (lmdb_wrapper.cpp:387) Opening databases... -INFO - 1460505492: (BlockUtils.cpp:1105) Executing: doInitialSyncOnLoad -INFO - 1460505493: (DatabaseBuilder.cpp:162) Reading headers from db -INFO - 1460505499: (DatabaseBuilder.cpp:195) Found 407055 headers in db -INFO - 1460505506: (DatabaseBuilder.cpp:43) updating HEADERS db -INFO - 1460505508: (DatabaseBuilder.cpp:223) parsed block file #491 -DEBUG - 1460505508: (Blockchain.cpp:213) Organizing chain -INFO - 1460505508: (DatabaseBuilder.cpp:47) updated HEADERS db in 1.785s -INFO - 1460505508: (DatabaseBuilder.cpp:98) scanning new blocks from #225967 to #407009 -INFO - 1460505528: (BlockchainScanner.cpp:636) scanned from height #225967 to #229667 -INFO - 1460505551: (BlockchainScanner.cpp:636) scanned from height #229668 to #232781
-INFO - 1460506296: (BlockchainScanner.cpp:636) scanned from height #368954 to #370252 -INFO - 1460506309: (BlockchainScanner.cpp:636) scanned from height #370253 to #371493 -INFO - 1460506321: (BlockchainScanner.cpp:636) scanned from height #371494 to #372486 terminate called after throwing an instance of 'std::bad_alloc' what(): std::bad_alloc Aborted How much RAM does your computer have? I think Armory might be using up too much RAM. hmmm, how much do you recommend?
|
|
|
crap, it's back!: -Ubuntu:~/BitcoinArmory$ python ArmoryQt.py ******************************************************************************** Loading Armory Engine: Armory Version: 0.94.1 Armory Build: 811798a928 PyBtcWallet Version: 1.35 Detected Operating system: Linux OS Variant : ('Ubuntu', '14.04', 'trusty') User home-directory : /home/x Satoshi BTC directory : /home/x/.bitcoin/ Armory home dir : /home/x/.armory/ ArmoryDB directory : /home/x/.armory/databases Armory settings file : /home/x/.armory/ArmorySettings.txt Armory log file : /home/x/.armory/armorylog.txt Do wallet checking : True (ERROR) ArmoryQt.py:1336 - 5 attempts to load blockchain failed. Remove mempool.bin. (ERROR) ArmoryQt.py:1341 - File mempool.bin does not exist. Nothing deleted. -INFO - 1460505492: (BlockUtils.cpp:924) blkfile dir: /home/x/.bitcoin/blocks -INFO - 1460505492: (BlockUtils.cpp:925) lmdb dir: /home/x/.armory/databases -INFO - 1460505492: (lmdb_wrapper.cpp:387) Opening databases... -INFO - 1460505492: (BlockUtils.cpp:1105) Executing: doInitialSyncOnLoad -INFO - 1460505493: (DatabaseBuilder.cpp:162) Reading headers from db -INFO - 1460505499: (DatabaseBuilder.cpp:195) Found 407055 headers in db -INFO - 1460505506: (DatabaseBuilder.cpp:43) updating HEADERS db -INFO - 1460505508: (DatabaseBuilder.cpp:223) parsed block file #491 -DEBUG - 1460505508: (Blockchain.cpp:213) Organizing chain -INFO - 1460505508: (DatabaseBuilder.cpp:47) updated HEADERS db in 1.785s -INFO - 1460505508: (DatabaseBuilder.cpp:98) scanning new blocks from #225967 to #407009 -INFO - 1460505528: (BlockchainScanner.cpp:636) scanned from height #225967 to #229667 -INFO - 1460505551: (BlockchainScanner.cpp:636) scanned from height #229668 to #232781
-INFO - 1460506296: (BlockchainScanner.cpp:636) scanned from height #368954 to #370252 -INFO - 1460506309: (BlockchainScanner.cpp:636) scanned from height #370253 to #371493 -INFO - 1460506321: (BlockchainScanner.cpp:636) scanned from height #371494 to #372486 terminate called after throwing an instance of 'std::bad_alloc' what(): std::bad_alloc Aborted
|
|
|
That's even more curious. I might be wrong about it being an Armory bug then, it's hard to believe that something so deterministic has not yet happened to someone else so far. I'm stumped by this one, if the re-index doesn't work, you will need goatpig, droark or knightDk to help troubleshoot. Limited knowledge of C++ runtime errors over here.
bitcoind -reindex worked. after a variety of issues, i just now finished it, and 0.94.1 is running.
|
|
|
I used Armory for years, liked it but tired of using two computers for cold storage and changed to Trezor and have not looked back. Armory has been promising Trezor support but it never comes. I doubt it is a priority now. I am aware of the privacy advantages of running your own full node and Trezor owners will have that option soon according to this post on reddit. Mytrezor release with Bitpay Bitcore support is coming soon. If you do not want to run a Bitcore node on your own Linux box you will have the option in myTrezor.com to connect to other public Bitcore servers. Woohoo! that's interesting. any experience with Bitcore? is it just another implementation of Bitcoin Core as a full node?
|
|
|
is there any REAL reason to update the firmware, or is it recommended to leave it be and avoid the risks and complications of backing-up/offloading the coins, formatting, then moving everything back on again?
It depends on what the changes in the firmware are. If anything in the changelog is related to security issues, especially something described as "urgent" or "severe", update update update. Anything about adding a new altcoin, or fixing a bug you've never experienced, you will be OK. I guess you're living proof that missing security updates isn't guaranteed to compromise your device. But to me, hardware wallets are about ultimate protection of BTC accounts, knowing that attackers are now aware of flaws in the firmware I'm running would cause me concern. My recommendation for securely updating the firmware: use an offline PC for the update. - Download firmware from as secure machine as possible
- Burn the firmware to CD-ROM (yes, CD-ROM)
- Take a hash of the files burnt onto the CD-ROM (or take an image file of the whole CD and do the same)
- Ensure that CD/USB autoplay etc is disabled on OFF-line machine
- Take a hash of the files/CD image on the OFF-line machine
- Compare to the hash you took using the ON-line machine (the file/s you supply to the hash command must be the same comparison)
- If the hashes match, proceed with the firmware flashing on the offline machine using your newly hash-checked update file/s.
- If the hashes do not match, find a new online machine and try again
I would take similar levels of precaution when installing the OS to the offline machine in the first place, otherwise you might end up with a trojaned/backdoored OS on the offline machine, and the the whole rigmarole may be a total waste of time (particularly if you did compromise your funds somehow due to the oversight) Carlton, out of curiosity. which platform do you view as more secure today; Armory or Trezor?
|
|
|
You can also delete the /.armory/atisignedannounce directory. Hasn't caused me any problems thus far.
ok, more trouble: -INFO - 1460146744: (BlockchainScanner.cpp:636) scanned from height #362309 to #363439 -INFO - 1460146753: (BlockchainScanner.cpp:636) scanned from height #363440 to #364372 terminate called after throwing an instance of 'std::bad_alloc' what(): std::bad_alloc Aborted
would that call for a bitcoind -reindex? hmmmmm, I think that's the C++ runtime making that complaint, but possibly nothing to do with bitcoind. Try erasing the /.armory/databases folder and rebuild the databases folder from the start. If that's unsuccessful, try bitcoind -reindex, but I'm not confident that's the source of your issue. That part of the code (tx scan) is a multi-threaded high performance wonder, but it took some lengthy debugging in it's original incarnation. It's possible you've done everyone a favour by finding an unknown bug. Keep the log files if you can, goatpig may want to see them. happened again after outright deletion of /.armory/databases folder, this time at a different blockheight: -INFO - 1460155030: (BlockchainScanner.cpp:636) scanned from height #194857 to #200839 -INFO - 1460155039: (BlockchainScanner.cpp:636) scanned from height #200840 to #206610 -INFO - 1460155047: (BlockchainScanner.cpp:636) scanned from height #206611 to #211790 terminate called after throwing an instance of 'std::bad_alloc' what(): std::bad_alloc Aborted running bitcoind -reindex
|
|
|
You can also delete the /.armory/atisignedannounce directory. Hasn't caused me any problems thus far.
ok, more trouble: -INFO - 1460146744: (BlockchainScanner.cpp:636) scanned from height #362309 to #363439 -INFO - 1460146753: (BlockchainScanner.cpp:636) scanned from height #363440 to #364372 terminate called after throwing an instance of 'std::bad_alloc' what(): std::bad_alloc Aborted
would that call for a bitcoind -reindex? edit: actually, bitcoind seems to be running normally.
|
|
|
that's not good, is it?
It's not necessarily bad though. what are these Errors at the bottom? when the gui client opens, it still says 0.93.3 and isn't updating:
Ubuntu:~/BitcoinArmory$ python ArmoryQt.py ******************************************************************************** Loading Armory Engine: Armory Version: 0.94.1 Armory Build: x PyBtcWallet Version: 1.35 Detected Operating system: Linux OS Variant : ('Ubuntu', '14.04', 'trusty') User home-directory : /home/x Satoshi BTC directory : /home/x/.bitcoin/ Armory home dir : /home/x/.armory/ ArmoryDB directory : /home/x/.armory/databases Armory settings file : /home/x/.armory/ArmorySettings.txt Armory log file : /home/x/.armory/armorylog.txt Do wallet checking : True (ERROR) ArmoryQt.py:6996 - Socket already in use. Sending CLI args to existing proc. (ERROR) ArmoryQt.py:7000 - Exiting...
It means the the socket that armory uses is in use. This probably means you already have armory open. yep, had 0.93.3 still open. sheesh. all good now. thks Carlton and KnightDB. would be comforting if goatpig would git tag his source though...
|
|
|
See above! I strongly suspect that's your issue (git checkout master can only have performed that exact command; etotheipi's master branch is still on 93.3, whereas the goatpig master branch is at 94.1)
does goatpig have 0.94.1 git tagged?: Ubuntu:~/BitcoinArmory$ git tag -v v0.94.1 error: 811798a9282d216e0a450fe342d8a4671fee01d3: cannot verify a non-tag object of type commit. error: could not verify the tag 'v0.94.1'
It isn't signed. that's not good, is it? He does. I suspect there's some minor error in the version string you're supplying, but that's only a guess. I don't make use of that particular git command, so can't help you specifically with it from off the top of my head unfortunately.
ok, got it. now how do i delete Armory's copy of the blockchain? Go to the armory data directory and delete everything in the "databases" folder. what are these Errors at the bottom? when the gui client opens, it still says 0.93.3 and isn't updating: Ubuntu:~/BitcoinArmory$ python ArmoryQt.py ******************************************************************************** Loading Armory Engine: Armory Version: 0.94.1 Armory Build: x PyBtcWallet Version: 1.35 Detected Operating system: Linux OS Variant : ('Ubuntu', '14.04', 'trusty') User home-directory : /home/x Satoshi BTC directory : /home/x/.bitcoin/ Armory home dir : /home/x/.armory/ ArmoryDB directory : /home/x/.armory/databases Armory settings file : /home/x/.armory/ArmorySettings.txt Armory log file : /home/x/.armory/armorylog.txt Do wallet checking : True (ERROR) ArmoryQt.py:6996 - Socket already in use. Sending CLI args to existing proc. (ERROR) ArmoryQt.py:7000 - Exiting...
|
|
|
He does. I suspect there's some minor error in the version string you're supplying, but that's only a guess. I don't make use of that particular git command, so can't help you specifically with it from off the top of my head unfortunately.
ok, got it. now how do i delete Armory's copy of the blockchain?
|
|
|
He does. I suspect there's some minor error in the version string you're supplying, but that's only a guess. I don't make use of that particular git command, so can't help you specifically with it from off the top of my head unfortunately.
so i run make and make clean and even make install but still get this: Ubuntu:~/BitcoinArmory$ python ArmoryQt.py Traceback (most recent call last): File "ArmoryQt.py", line 39, in <module> import CppBlockUtils as Cpp ImportError: No module named CppBlockUtils
thanks for your help on this Carlton.
|
|
|
See above! I strongly suspect that's your issue (git checkout master can only have performed that exact command; etotheipi's master branch is still on 93.3, whereas the goatpig master branch is at 94.1)
does goatpig have 0.94.1 git tagged?: Ubuntu:~/BitcoinArmory$ git tag -v v0.94.1 error: 811798a9282d216e0a450fe342d8a4671fee01d3: cannot verify a non-tag object of type commit. error: could not verify the tag 'v0.94.1'
|
|
|
I think you're probably still using the etotheipi repo. You need to run "git clone git://github.com/goatpig/BitcoinArmory" to access goatpig's fork.
yeah, probably. does that mean i go to your first post and delete the entire BitcoinArmory folder with it's contents?
|
|
|
@cypherdoc
If you just want to erase the 0.93.3 location and replace it with 0.94.1:
cd BitcoinArmory (or whatever path gets you to the BitcoinArmory directory) git checkout master git pull make clean && make
Subsequently, you won't need the second line once you're definitively following the master branch.
appears to have failed. ran thru above steps and seemed ok. but when launching, i still get 0.93.3: ~/BitcoinArmory$ python ArmoryQt.py ******************************************************************************** Loading Armory Engine: Armory Version: 0.93.3
/home/*/BitcoinArmory/armoryengine/Transaction.py:2649: SyntaxWarning: import * only allowed at module level def PyCreateAndSignTx_old(srcTxOuts, dstAddrsVals): (ERROR) ArmoryQt.py:7074 - Socket already in use. Sending CLI args to existing proc. (ERROR) ArmoryQt.py:7078 - Exiting...
|
|
|
|