I take that back. 1 confrimation already. IM SO EXICTED AND I JUST CANT FIGHT IT.
.25 BTC to the first person to find and post the lyrics
just leave your wallet address.
Tonight's the night we're gonna make it happen Tonight we'll put all other things aside Get in this time and show me some affection We're goin' for those pleasures in the night I want to love you, feel you, wrap myself around you I want to squeeze you, please you, I just can't get enough And if you move real slow I let it go I'm so excited and I just can't hide it I'm about to lose control and I think I like it I'm so excited and I just can't hide it And I know I know I know I know I know I want you We shouldn't even think about tomorrow Sweet memories will last for long long time We'll have a good time, Baby, don't do worry And if we're still playin' around boy that's just fine Let's get excited, we just can't hide it I'm about to lose control and I think I like it I'm so excited and I just can't hide it I know I know I know I know I know I want you, I want you I want to love you, feel you, wrap myself around you I want to squeeze you, please you, I just can't get enough And if you move real slow I let it go I'm so excited, I just can't hide it I'm about to lose control and I think I like it I'm so excited and I just can't hide it I know I know I know I know I know I want you 15REbfCLtuoeRGtp6ck7AHErSm4pejfi4e |
|
|
|
So it uses a blockchain just like Bitcoin then?
How is it different than bitcoin, and no hype please.
If it does, it looks like the average time between blocks is only a few seconds. At that rate, network latency is more important than hashpower when mining, resulting in less security than a wet cardboard box (anyone with average hashpower and a low-latency connection can take over the network). |
|
|
|
In the end, everyone who cares about this tiny attack vector uses wallets that were born encrypted. And Armory does guarantee that born-encrypted wallets are secure.
If you're worried about (2) and (3) and electron-tunneling microscopes pulling your key off even after shredding: create your wallet encrypted and never remove the passphrase! Problem solved!
The problem is not solved for people who don't know about these things, create an unencrypted wallet, then later learn about the danger and encrypt the wallet, then their computer gets stolen, but it's okay because their wallet is encrypted, so they restore from a backup only to find that all their addresses have been cleaned out completely, then they sue you because you "guaranteed" that their unencrypted wallet would be overwritten. I am not suggesting that you find a way to ensure that unencrypted wallets are completely destroyed (since that's almost impossible), just that it's probably not the best idea to make guarantees with other people's money that you can't back up.  |
|
|
|
- If you add encryption to an unencrypted wallet, the old keys are overwritten in-place so that the new file is guaranteed not to contain unencrypted data.
How exactly do you guarantee that files will in fact be overwritten "in-place"? This is not only operating-system and filesystem dependent, but even you can manage to do this in all operating system and on all filesystems, the hardware is not guaranteed to write data where the operating-system tells it to. Solid-state drives in particular are guaranteed not to do this due to their wear-levelling mechanism. I'm sorry, but if an unencrypted private key is ever written to disc, the only secure options are to stop using that private key or start using thermite. |
|
|
|
Except for the fact that you're not compiling, you may be right.
Also, what you mean by remove the dependency, is it completely removing it or changing it to libpython2.6?
It is a combination of C++ and Python, so it is compiled. And yes, I do mean remove the dependency completely, so that it only depends on python-qt4 and python-twisted, not libpython. python-qt4 depends on an appropriate version of libpython anyway, so unless Armory requires a specific version of libpython (and it doesn't look it does, when compiled against python 2.7), there shouldn't be a problem. |
|
|
|
BTW, the most fundamental req. of any currency system is speed of the transaction. Unlike BTC, wherein it takes minutes for transactions to complete, microcash is nearly instant. This has been written from the ground up and designed for mobility.
How did you accomplish this feat? The reason bitcoin takes several minutes to confirm transactions (the transactions themselves are almost instant) is to prevent stale blocks resulting from network propagation delays, which would greatly reduce the effective hashpower of the network and basically allow anyone with the lowest network latency to take control of the network. How did you solve this problem? And the most fundamental requirements of a currency system are fungibility (one coin is just as good as any other of the same denomination), divisibility (you can easily make change for large amounts), and difficulty of counterfeiting (you can easily tell a genuine coin from a fake one). MicroCash falls flat on its face for the last point if you don't have a cold answer to my above question. |
|
|
|
Any ideas on how I might create an all-in-one offline installation in Ubuntu? For now, maybe I'll just "endorse" 10.04 32-bit, execute the offline package download on 10.04 and tar up all the dependencies into one downloadable thing.
Well, you could include the dependencies, but the dependencies have dependencies of their own, so you have to include those, as well as their dependencies... If you keep going on like that you'll end up creating a whole distribution just for Armory. Which is a perfectly valid option, and probably a good idea if you want to ensure a completely secure software environment, but it's probably more effort than it's worth at this stage. Other than that I don't think there's any way to guarantee that all the dependencies will be met without having to go online. That's easy. I create a fresh installation, then execute the offline-package-installation -- I select the two top-level dependencies in Synaptic and it collects the entire dependency tree for me. When I select "Generate Download List", I get a wget-list of all 65 packages (it's 65 if I do the build-dependencies). I run the script and zip it up the directory. I think it's about 100 MB. It's not small, but it's acceptable. But it will be tied the particular distro I did it for... 100MB for an installer that's only guaranteed to work on one particular distro is easy?  I think you would be better off creating a whole distribution. A distribution would definitely be the Right Thing for a one-step installation on an offline system, and it lets you do things like remove the network drivers to guarantee that it stays an offline system. As for the python thing: check that you don't have both pythons on your system. As I said before, even though 11.10 is python2.7, it did work with my 2.6 build, because it apparently has libpython2.6.so on it (no idea why). Maybe I should try the other way: build everything on 2.7 and it might work on lower...?
$ ls -d /usr/lib/*python*
/usr/lib/libpyglib-2.0-python2.5.so.0 /usr/lib/libpython2.6.so
/usr/lib/libpyglib-2.0-python2.5.so.0.0.0 /usr/lib/libpython2.6.so.1
/usr/lib/libpyglib-2.0-python2.6.so.0 /usr/lib/libpython2.6.so.1.0
/usr/lib/libpyglib-2.0-python2.6.so.0.0.0 /usr/lib/python2.4
/usr/lib/libpython2.5.so.1 /usr/lib/python2.5
/usr/lib/libpython2.5.so.1.0 /usr/lib/python2.6
/usr/lib/libpython2.6.a Nope. Just compile on 2.7, remove the libpython2.7 dependency, and see what happens. Hopefully there's someone else with python 2.6 who can confirm that I'm not going crazy. |
|
|
|
Since Nyaaan apparently doesn't know how to count:  And to avoid screwing up the post count:  |
|
|
|
Ok, I removed the previous package. Instealled the new amd64-python2.7... ...and it works  As soon as I get some extra BTC in my wallet gonna throw you some for all the trouble. After all I was the only one to complaint. FYI, you're not going crazy. I just tested the python2.6 package on a fresh install of 12.04 and it failed. I had to recompile the package without the (= python2.6) in order to get it to install, and it appears that the dependency check is valid. Argh! So this means I will have to have 4 different packages for Ubuntu: {i386, amd64}{python2.6, python2.7}. Anyone who cannot use one of those packages can just follow the regular build-from source instructions: they've been fairly unobtrusive so far, just needed the desktop icons. If you're using a different distribution than one of the modern Ubuntus, your probably capable of checking your python version or compiling yourself (I'll list Ubuntu release versions with the packages). What the Hell? If psy's not going then crazy, then perhaps I am: $ sudo dpkg --force-depends -i armory_0.74-python2.7-1_amd64.deb
[sudo] password for foxpup:
Selecting previously deselected package armory.
(Reading database ... 154253 files and directories currently installed.)
Unpacking armory (from armory_0.74-python2.7-1_amd64.deb) ...
dpkg: armory: dependency problems, but configuring anyway as you requested:
armory depends on libpython2.7; however:
Package libpython2.7 is not installed.
Setting up armory (0.74-python2.7-1) ...
$ python --version
Python 2.6.6
$ python /usr/share/armory/ArmoryQt.py --nettimeout 10
********************************************************************************
Loading Armory Engine:
Armory Version: 0.74
PyBtcAddress Version: 1.00
PyBtcWallet Version: 1.35
Detected Operating system: Linux
User home-directory : /home/foxpup
Satoshi BTC directory : /home/foxpup/.bitcoin/
Satoshi blk0001.dat : /home/foxpup/.bitcoin/blk0001.dat
Armory home dir : /home/foxpup/.armory/
Using settings file: /home/foxpup/.armory/ArmorySettings.txt
Loading wallets...
Number of wallets read in: 1
Wallet (7FVyhG1d): "Primary Wallet " (No Encryption)
Internet connection is Available: True
Satoshi Client is Available: True
Loading blockchain
Attempting to read blockchain from file: /home/foxpup/.bitcoin/blk0001.dat
/home/foxpup/.bitcoin/blk0001.dat is 1165.64 MB
Syncing wallets with blockchain...
Syncing wallet: 7FVyhG1d
Loading blockchain took 56.7 seconds
Usermode: Advanced
Handshake finished, connection open!
Attempting to close the main window! The python 2.7 version works absolutely fine with python 2.6! What's going on here? If it requires a specific version of libpython, why does this work? And yes, I did remove the version I already had prior to installing this one. But why does it work? I don't understand.  |
|
|
|
Any ideas on how I might create an all-in-one offline installation in Ubuntu? For now, maybe I'll just "endorse" 10.04 32-bit, execute the offline package download on 10.04 and tar up all the dependencies into one downloadable thing.
Well, you could include the dependencies, but the dependencies have dependencies of their own, so you have to include those, as well as their dependencies... If you keep going on like that you'll end up creating a whole distribution just for Armory. Which is a perfectly valid option, and probably a good idea if you want to ensure a completely secure software environment, but it's probably more effort than it's worth at this stage. Other than that I don't think there's any way to guarantee that all the dependencies will be met without having to go online. |
|
|
|
Also I tested your custom port version and tried a handful of 62,200 ports and it always gave that problem but 61,119 and below appear to work. No idea whats up with the 62200 and above.
Good to know! Maybe I will choose a port that is in a more-normal range: I assumed that picking a huge number would decrease the likelihood that any other program was using that port, but apparently not all systems like those big ports... Any guidance on how I should select a port? Bitcoin uses 8333 and 18333 (testnet)... how were those chosen and how did we know they weren't going to be consumed by other processes? Ports in the range 1024-49151 are supposed to be registered with the IANA for a specific protocol, though in practice many protocols that use these port aren't registered (Bitcoin isn't registered, for example). The range 49152–65535 is designated for private or experimental purposes such as what you're doing, and doesn't need to be registered. How do you chose a port above 49151? You pick one at random and hope no-one else is using it. Easy. (This plan doesn't always work out so well for ports below 49152.) No idea why Windows doesn't seem to like ports above 61119; there's nothing special about them, as far as I know. |
|
|
|
The Haaretz article also says that Centralized inspection ensures that the coins are mined at a pace determined in advance. I thought it was a chrome's translation issue... The Haaretz article is in English, and is not actually related to the article mentioned in the OP except that both newspapers (Haaretz and TheMarker) are published by the same company (Haaretz Group). |
|
|
|
The Haaretz article also says that Centralized inspection ensures that the coins are mined at a pace determined in advance.  |
|
|
|
How long has that been there? And more importantly, will forcing people to install it from there break any existing installation? Looking at the version numbers, I'm guessing it would. |
|
|
|
Gah! I added python to the version number, but forgot to automate the depends line. This really is a PITA! I just replaced that version on the downloads page. It should be correct.
At least I'm getting these stupid little things out the way before I declare a real release...
Hey, wait a minute, if that's all it was, then it shouldn't have worked at all, because I don't have python 2.7, so the python version obviously doesn't make any difference at all. Where exactly did psy's error come from? You know what, just remove libpython from the dependency list, put up one version per architecture, and see if that works on both my and psy's system. If it does, problem solved. Except for the problem of why it didn't work on psy's system originally after he hacked the dependencies, that trick should have worked... Also, I've discovered a bug in the handling of white-on-black color schemes, and it's a big one. When printing a paper wallet, it turns out that white text does not actually make it easier to read.  |
|
|
|
The python 2.7 version works fine on my system even though I have python 2.6, so either you've screwed up the dependencies again... Package: armory Version: 0.74-python 2.7-1 Architecture: amd64 Maintainer: Alan C. Reiner < alan.reiner@gmail.com> Installed-Size: 13296 Depends: libpython 2.6, python-qt4, python-twisted ...yup, you've screwed up again  ...or it doesn't depend on a particular version of python at all, in which case you can safely remove it from the dependency list, and I have no idea what was causing psy's problems. |
|
|
|
|
Show Posts
