|
One certainly hopes it isn't too optimistic, but if you can wait 10 years, I'll let you know for sure. :-)
Chef, I agree, given the issues with the value of the euro, and potential issues with the value (or devalue) of the dollar. Then there is the renminbi which, while an alternative to the dollar and euro, is certainly nothing besides a different brand of fiat backed by thugs.
|
|
|
|
I answered you in the other thread, but the values you have for the SHA-256, are hashing the string (ASCII representation of the hex number) instead of the hex number itself. Like hashing the number 120 vs the ASCII representation of "120", you'll get much different values. If you do the hash on the number instead of the ASCII string, I suspect that things may fall into place quite quickly. ;-) Does that help? |
|
|
|
Are there different implementations of SHA256 ? from the bx library: >bx sha256 800C28FCA386C7A227600B2FE50B7CAE11EC86D3BF1FBE471BE89827E19D72AA1D 8147786c4d15106333bf278d71dadaf1079ef2d2440a4dde37d747ded5403592 from https://en.bitcoin.it/wiki/Wallet_import_formatsha256 (800C28FCA386C7A227600B2FE50B7CAE11EC86D3BF1FBE471BE89827E19D72AA1D) = 8147786c4d15106333bf278d71dadaf1079ef2d2440a4dde37d747ded5403592 and from c++ crypto++: sha256(800C28FCA386C7A227600B2FE50B7CAE11EC86D3BF1FBE471BE89827E19D72AA1D) = E2E4146A36E9C455CF95A4F259F162C353CD419CC3FD0E69AE36D7D1B6CD2C09 from: http://www.xorbin.com/tools/sha256-hash-calculatorsha256(800C28FCA386C7A227600B2FE50B7CAE11EC86D3BF1FBE471BE89827E19D72AA1D) = e2e4146a36e9c455cf95a4f259f162c353cd419cc3fd0e69ae36d7d1b6cd2c09 The difference is in hashing the string (an ASCII representation of a hex number) instead of the actual hex number itself. The wiki hashes the number, the calculator is hashing the string. |
|
|
|
So you will probably want to export the private key and import it elsewhere. Then probably move the coins to a new address just to be safe. |
|
|
|
Ubuntu? Debian? version?
Ubuntu 12.04 I wonder if there is something different happening between 12.04 or 14.04. Odd. At least it is working. |
|
|
|
...
blocknotify is now working!!
...
Glad that is now working. The odd thing to me is that apparmor is (at least on my three servers - one bitcoin related, two not) there by default (Ubuntu 14.04 on them). But it causes no problems and I have no profile for bitcoind. I am not sure if I would auto remove it. Since it is part of the mainline, now that you know it was the problem, you might want to see if you can figure out why it was causing an issue and fix it that way. Ubuntu? Debian? version? e.g. AppArmor is an established technology first seen in Immunix and later integrated into Ubuntu, Novell/SUSE, and Mandriva. Core AppArmor functionality is in the mainline Linux kernel from 2.6.36 onwards; work is ongoing by AppArmor, Ubuntu and other developers to merge additional AppArmor functionality into the mainline kernel. https://wiki.ubuntu.com/AppArmor |
|
|
|
I can. 1) Open folder with wallet.dat 2) Delete everything except wallet.dat 3) Run Bitcoin-qt 4) Open debug console 4a) Enter walletpassphrase YOUR_PASSWORD 600 5) Enter dumpprivkey YOUR_BITCOIN_ADDRESS 6) Copy a output 7) Create file 1.txt(or any name)  Paste the output in the file 9) Save file as 1.key 10) Open Multibit 11) Tools -> Import private keys -> Import from ... 12) Choose 1.key 13) Press Import private keys Added the part that unlocks the wallet.dat Do you have skype? btw my bitcoin core wont open... so I cant do that. I'd pay someone a few bucks to walk me through on skype PM me The solution above in the steps listed, should help you open bitcoin core. It will delete the DB and start over. You do not need to let it complete, just start up, export the key and then stop. If the problem is the database and not Bitcoin Core itself corrupted on the disk, then follow the steps above and you will be fine. Just be SURE you have a few extra backups of the wallet.dat - 1. in case your hard disk has more issues, 2. in case you mistype something. |
|
|
|
Sigh... im getting the ''connection refused'' when i try to back it up on blockchain info...
I just need to see that address 1 time so i can copy it and put in it mulitbit. can someone do a skype call with me if i share my screen? i'll obv pay you for the help.
I saw in here: https://bitcointalk.org/index.php?topic=917978.msg10661082#msg10661082that blockchain.info no longer supports the drag and drop method. Multibit and others will import it, but make a copy first since (as noted above), it sounds like you are having HDD issues. |
|
|
|
It looks like you are running Windows. Which one? What version of Bitcoin? 0.10.0? The log location is in here: https://en.bitcoin.it/wiki/Data_directoryDid you check those spots? Is the wallet.dat in there? If so, make a backup right away just to be safe. Yes windows 8 and bitcoin core 10 i found the file and the wallet.dat file IS in there. How do i back up the file? the errors are... 015-03-15 14:17:14 StopNode() 2015-03-15 14:17:14 Corruption: block checksum mismatch 2015-03-15 14:17:14 *** System error while flushing: Database corrupted You can back it up like any other file - just make a copy of it on your PC to a USB drive or the like. This way, at least you have a degree of safety if the one copy somehow gets messed up. It has the keys that you need to access your coins so is the most important thing to have safe and secure. see: https://en.bitcoin.it/wiki/Backingup_your_walletIf you didn't have it password protected, I believe that other wallets should import the private keys. It is hard to say exactly what the error is, except it isn't good for the block DB. |
|
|
|
It looks like you are running Windows. Which one? What version of Bitcoin? 0.10.0? The log location is in here: https://en.bitcoin.it/wiki/Data_directoryDid you check those spots? Is the wallet.dat in there? If so, make a backup right away just to be safe. |
|
|
|
...
mywalletpassphrase dumpprivkey "my publicaddress "
...
If you are truly typing it as above, what you want is: walletpassphrase your-walletpassphrase-here 600
dumpprivkey your-public-key-here
That would unlock the wallet for 600 seconds (10 minutes) and then dump the key. Each is on its own line. |
|
|
|
According to Coindesk, "Chainalysis denies any malicious behaviour – "the accusations got a little out of hand," Grønager said – and rather points to its technology being used to help law enforcement, for example in tracking and locating stolen funds."
So basically from what I understand is they were monitoring and recording all transaction that I have made because I was under general suspicion? Cryptograpic geeks writing their maters thesis and doing some analysis on the blockchain is absolutely fine, but I am not OK with companies monitoring a large number of users in order to do "something" with the archived data afterwards. Yeah. And their multiple statements seem at odds with each other. Their statement quote above with regard to regulations and in the coin deskarticle do not match this: We were preparing data for a blogpost on bitcoin traffic by volume btw different counties. We chose specifically to setup a number of nodes on the same /24 net to avoid any bitcoind or other vital parts of the network to be caught only on our nodes as we initially havn't build the transaction forwarding into the probes. Their explanations make their motivations even more questionable and, to me, increase the degree that one should be suspicious of them and their actions since they try to excuse the behavior in ways that are at opposite extremes depending on who they are talking to. It is good though to see this type of activity now and take steps to mitigate it at least some. While Tor is not the be-all, as has been discussed up thread, it is a useful tool in the bitcoin world. It isn't difficult to set up, so if you are running a node, consider adding a hidden service. There is a guide on setting up bitcoin core with Tor ( https://www.sky-ip.org/configure-bitcoin-node-debian-ubuntu.html ) that seems to be reasonably complete from looking it over. Some things you may need to tailor to your own uses, such as if you want to be on Tor and clear. There may be other guides out there too, but thought that one might be useful if anyone was looking for one. Thank you E.K for bring this up, by the way. |
|
|
|
|
Yeah, you don't need a blockchain for this, just IBM and the central banks maintaining a ledger. It takes just the buzzwords and removes the benefits so that they can try to get in on the hype without anything real.
It uses a centralized blockchain so that you get something less secure than a decentralized leader that is more costly and less efficient than a regular ledger.
Seems just a way to try and control something while trying to mislead everyone about the loss of security and benefits.
|
|
|
|
Try looking into AppArmour and see if it could be the culprit. I think we're running out of Bitcoin related things. :-) As cryptowatch.com said, perhaps it is interfering with app permissions. Thanks for your suggestion. Automatic had the following in his bitcoin.conf. However, he stated that the notify commands randomly started working and randomly stopped working. rpcuser=no.
rpcpassword=no.
maxconnections=1000
checklevel=4
keypool=10000
rpcallowip=127.0.0.1
server=1
blocknotify=/home/bitcoin/block.sh %s
walletnotify=/home/bitcoin/wallet.sh %s
alertnotify=/home/bitcoin/alert.sh %s I tried the following configs in my bitcoin.conf: rpcuser=XXXXXXXXXX
rpcpassword=XXXXXXXXXX
maxconnections=1000
checklevel=4
keypool=10000
rpcallowip=127.0.0.1
server=1
blocknotify=/bin/true
walletnotify=/bin/true
alertnotify=/bin/true and rpcuser=XXXXXXXXXX
rpcpassword=XXXXXXXXXX
blocknotify=/bin/true
walletnotify=/bin/true
After restarting bitcoind each time, I'm still getting the same error in .bitcoin/debug.log: 2015-03-13 18:45:17 runCommand error: system(/bin/true) returned -1 Any other suggestions that I can try? |
|
|
|
The post quoted below and the one above from them above seem very different. Traffic analysis vs tracking transactions for "travel rules" etc. The one above makes it sound much more innocuous than the quotes below. New article at CoinDesk: http://www.coindesk.com/chainalysis-ceo-denies-launching-sybil-attack-on-bitcoin-network/Chainalysis denies any malicious behaviour – "the accusations got a little out of hand," Grønager said – and rather points to its technology being used to help law enforcement, for example in tracking and locating stolen funds.
He told CoinDesk:
"Funnily, following the Reddit post we have received a ton of emails from people with stolen bitcoins and requests for finding them – so yes, there is indeed a need [for this kind of service] and yes, we have received a lot of positive feedback from potential customers." Chainalysis sides with the regulators. In providing what it calls 'automated transaction reporting', the company says it is helping bitcoin companies conform to existing money transfer regulations, including the travel rule.
This, Grønager said, will help bitcoin businesses get bank accounts and promote the currency's use among mainstream financial institutions.
He added:
"If you as a MSB (money services business) are offering automated transactions you are obliged to have suitable automated transaction monitoring. That is not to be confused with monitoring the entire bitcoin network, but transfers between you and your client, may that be fiat or may that be bitcoin. We are providing tools for facilitating exactly that." |
|
|
|
As you said, miners can always accept a smaller fee, but (as you said as one alternative) I don't think the incentive to take a smaller fee now to potentially slightly increase the value of their hypothetical holdings sooner is there.
A soft fork which changes what the rules will be in 5 years time is more likely to be accepted. Once it is accepted, then it becomes a network rule. Miners in 5 years who violate the rule risk getting their blocks rejected. This is especially true if the reference client rejects them. Anything is possible, but I still think unlikely. Also 5 years would be roughly after two more halvings, so the block reward (12.5 in ~2016, 6.25 in ~2020) would mean the reward would be down significantly by then, so would not doubt have less push back from people mining then as compared to a 25 BTC reward if the BTC/$/Euro value is similar to now. If the value has skyrocketed in fiat terms, then you might get more pushback against the fork even then, but if 0.01 BTC is worth $2-$3...who knows. I am just not convinced that changing to a semi-continuous function will matter much in terms of network security since the halving time is widely known and miners have planned for it. :-) |
|
|
|
Yep ! Actually we should even thank these guys because this "attack" is quite cheap: use of IP addresses in the same subdomain isn't really smart for a sybil attack  I may be wrong but it's likely that similar attackers are still acting undetected because they can afford a better strategy (different ip ranges, imitation of full nodes behaviors, ...). With IPv6 this type of attack will become even more difficult to detect and prevent merely by blocking the IPs. |
|
|
|
That has nothing to do with the result of the program. The error means that bitcoin core is unable to run /bin/true and that's the problem you have to tackle.
Thanks for your help. Do you have any ideas on what I can try next? In this thread: https://bitcointalk.org/index.php?topic=385146.msg4154179#msg4154179there was an error elsewhere in the config file that was messing things up. Perhaps this is a symptom of a different problem that is manifesting itself in an odd way? |
|
|
|
this is why we cant have nice things
There were two from that IP range that were attached to my node. |
|
|
|
|
Show Posts
