Out of curiousity, and I think it's relevant here, what sort of encryption does bitcoin-core use to encrypt wallets? I would guess that it's going to be something in the aes suite. I guess I'm just imagining if I had to make a cracker for my own wallet, what would I put in the shell script. Here's pseudocode: for guess in guesses.next(); do
# run some command to try decryption
openssl -d ?? -i wallet.dat.encrypted
# test for success, maybe just $?, or is there a magic number in wallet.dat to look for
if $?==0; then
echo "we win!"
break
done
So, really, I have two questions? What's the encryption algo? And what's the test for success? Depending on your python you should find the answer here -> https://github.com/gurnec/btcrecoverIIRC its AES 256 bitWallet encryption uses AES-256-CBC to encrypt only the private keys that are held in a wallet. The keys are encrypted with a master key which is entirely random. This master key is then encrypted with AES-256-CBC with a key derived from the passphrase using SHA512 and OpenSSL's EVP_BytesToKey and a dynamic number of rounds determined by the speed of the machine which does the initial encryption (and is updated based on the speed of a computer which does a subsequent passphrase change). Although the underlying code supports multiple encrypted copies of the same master key (and thus multiple passphrases) the client does not yet have a method to add additional passphrases.
https://en.bitcoin.it/wiki/Wallet_encryptionThanks, Shorena, it definitely seems to be a lot more complex than just descrypting the wallet file. You may be right that the specific question I'm curious about is answered somewhere in the source for the btcrecover tool (thanks for the link!). Just looking at that paragraph from the bitcoin wiki, I'm imagining that you know the passphrase (say), so you'd hash it with sha512 and you'd have to see what this EVP_BytesToKey gives you, then you'd have to gues at how many rounds might have been used? After that I guess you have the "master key" and you can use that to decrypt individual private keys with AES-256-CBC. There must be somewhere that you can tell how many rounds have been used. Anyway, to be clear, I don't need to do this right now, I'm just curous about the procedure. |
|
|
|
Faking a ban would be the dumbest since verifying it is as easy as asking Theymos or Badbear.
The fact that someone is banned is supposed to be private information...I don't blame BadBear for what happened though. QS, you routinely display signs and symptoms of serious personality disorder, the above is but one of them. What don't you get? Nobody, and I mean NOBODY, gives a flying fuck if you 'blame' BadBear or not, the ONLY issue is that you lied about having been banned for your own gain. Dishonesty and deceit are your trademark. At least to me, the fact that he was stealing escrow fees seems as bad or worse than the lies about being banned. |
|
|
|
Hello,
I just upgraded my bitcoin server to 0.11.1 and discovered fresh transaction with fee, which bitcoind server set to 0.00001865 , I want to pay more fee ~0.0001.
Which bitcoind parameter could achieve this ?
Thanks.
You can achieve this by using the -paytxfee parameter. Example: ./bitcoind --rpcconnect=127.0.0.1 -paytxfee=EnterTxfeeHere sendtoaddress EnterAddressHere EnterAmount yep, it works. Just for clarification - you can use param -paytxfee while starting bitcoind server for all your future outputs. AFAIK, It needs to be specified for each transaction. Normally the fee bitcoind sets as default is enough(Within 6 blocks). If you have a very high priority transaction its better to pay a higher fee to process it within the next 2-3 blocks. Disagree, I have tested it on my bitcoind server and it works good for every transaction. Usually, if it's something that you want to run everytime you run bitcoind, it's something that you should put in your bitcoin.conf (so you don't have to remember an elaborate command line invocation in order to start the program). |
|
|
|
Out of curiousity, and I think it's relevant here, what sort of encryption does bitcoin-core use to encrypt wallets? I would guess that it's going to be something in the aes suite. I guess I'm just imagining if I had to make a cracker for my own wallet, what would I put in the shell script. Here's pseudocode: for guess in guesses.next(); do
# run some command to try decryption
openssl -d ?? -i wallet.dat.encrypted
# test for success, maybe just $?, or is there a magic number in wallet.dat to look for
if $?==0; then
echo "we win!"
break
done
So, really, I have two questions? What's the encryption algo? And what's the test for success? |
|
|
|
shorena explains it
Oh yah, hehe, I guess that makes perfect sense and I'm sorry for being so obtuse. I guess I just didn't expect that one guy's betting could kick up expected profit by that much, but I guess that was an epic run of play from dental. |
|
|
|
Don't over-complicate the solution and don't be overly idealistic.
Not directed at any particular idea, and not meant to be rude, but keep it in mind as a mantra.
I have seen many devs, coins, and communities make this mistake time and time again.
The simplest and fastest implemented ideas that actually make a big difference are the best ones.
Well, the simplest and fastest idea to implement is always "do nothing", closely followed by "cut off all digging with a hard fork". Neither seems optimal. I guess I'm still not understand the crisis here. Surely when the CLAM devs decided to distribute so many clams to BTC addresses they did this on the understand that someone might come along and dig them. Wait, more than "understanding", I think it's actually an invitation, right? So what justification is there to try to undo that invitation when someone comes along to take you up on it? The best rationale that I've seen for making changes has to do with the idea of an "unfairness" related to those who are digging sooner basically financing those who dig later due to the storage of the UTXO corresponding to undug clams (did I get that right?). If I do understand that argument correctly, I can see some validity to it. But I would say to move forward with any changes which devalue undug clams with extreme caution, give people 6 months to a year to prepare. Otherwise you risk impugning your own trustworthiness as developers of CLAM. As SuperClam was saying, the promises made at the original distrubution should be seen as sacred, and undoing them shouldn't be an off-the-cuff response to someone selling a lot on the market. |
|
|
|
If a Bitcoin angel will give me 1 BTC now then I will run my full node as long as possible.
1 BTC/month? Are you kidding me? That node probably costs you maybe $0.50/month to run, if you even notice a higher cost of living due to running it. Myself and clients combined have dozens of full nodes running across the internet. The $$$ to run a node never factors into anything. FWIW, he didn't say 1BTC per month, he says give him 1BTC and he'll run it as long as possible. From what I can tell, he left the value of "as long as possible" underspecified. |
|
|
|
|
So, I happen to have gotten a better computer recently, makes me consider loading some sort of WINDOZE in a vm in order to try out Seals for the first time in 2015(!). Anyone know how to do that? Is there some free clone of WINDOZE XP I can download somewhere? Surely no one buys XP anymore. Surely no one buys WINDOZE just to run it as a virus attraction machine inside VM?
|
|
|
|
What's up with that little step-up in the expected profit (green) line? I would have guessed that the expected profit would track linearly with bet volume. Was there some huge jump in bet volume around 16 Oct? Or am I just misunderstanding things as usual? |
|
|
|
|
I really think that nothing should be done. The number of diggable clams was well considered (I assume) before the initial distribution snapshot was taken and the fact that Clam achieved enough value to attract a while digger to find his/her share is part of the ground rules as they were laid out. I really don't like the idea that people would say beforehand "We've distributed n clams to these addresses" and then try to renege on that when someone comes along to claim them.
|
|
|
|
Hey everybody.
So here we are.. I'm kleineaap and fibo.
Long long shit ass story about how I turned the faucet into real money, then lost it, then got it back, then got more into it, etc, etc.
My swings of losing and winning were so large that at some point I was -30 on two different accounts. I was broke. Waited a long time so I could buy in again and challenge my losses.
-30, -12, + 5, +17, -22, etc.
One night, facing the inevitability of my personal life, I put down 3 BTC that I turned into 20. Cashed out and put ten more. Lose, win, cashout, deposit. When I looked at my wallet again I had 60 BTC.
I decided to deposit 10 more for fun, which I lost.
Then I went all in. 50 BTC. Hardly got any greens, it was over in under 5 mins.
I lost 10k in my currency trying to gamble my future. The future I don't have anymore. A few months left to live. I will spend that time finding the best family to my little daughter.
I do have her covered. I'm not a jerk completely. I wanted to give her a plus, a push, a jump, so I risked around 2000 euros to make it happen.
It didnt work. My life in this forum is done as well.
Thanks for the company and support and the good wishes. I am fibo. I probably tipped and rained many of you. When I'm gone, make sure you tip yourself along the way.
Be good.
It's a scam, dudes. |
|
|
|
|
Thanks, dooglus, I was helping FreeHealthCare to deposit a paper wallet and so I pushed the tx through your page and I wanted to be able to tell him, "here ya go: TXID". I ended up finding it by using a block explorer and looking for his/her deposit address. Just that that's what prompted the question. Thanks again for the explanation. I actually went and asked about how to calculate it in the Technical Discussion board, perhaps someone there can explain why its not coming out the way you expected.
|
|
|
|
Holy Moly Batman! Success! You rock tspacepilot. I followed your advice and confirmed the Makefile in src/leveldb/ with a rule that builds libleveldb.a. I changed directory to /src/leveldb/ and successfully performed a make clean && make. I ran the configure script './configure –without-gui –disable-wallet – with-cli' successfully and then performed the Make. I confirmed it with a 'make check' with the following results. I was then able to perform a 'sudo make install' successfully. bitcoind runs successfully and I see it beginning to sync. I am so curious on why leveldb did not automatically compile in the first place.
[snip]
I really appreciate your assistance tspacepilot. I have been researching this problem for about two weeks and I have learned a lot. I am going to put together my procedures for installing bitcoind 0.11 headless on a Raspberrt Pi 2 post them next.
Glad to hear about your success, man! |
|
|
|
|
I think this is an easy question but I couldn't turn it up by searching on the wiki, so I thought I'd just ask here. Assuming I have the raw hex of a signed transaction, how do I get the txid? I tried:
echo -n "01234567890abcdefrawhexofsignedtransactioninherefedcba09876543210" | sha256sum
and that didn't seem to be it. I also tried:
cho -n "01234567890abcdefrawhexofsignedtransactioninherefedcba09876543210" | sha256sum | sha256sum
and that didn't seem to be it either.
Thanks in advance, you wizards!
|
|
|
|
Today I used the pushtx page of just-dice to push a raw transaction, I got the message "OK", but it would be nice to have a transaction ID to go along with that. This is just my request/suggestion in regards this page: https://just-dice.com/pushtxIf there's another pushtx page elsewhere that can push txs in hex format into the clam network and which gives you back the txid, that'd be great. Oh, and I guess I can just hash my transaction to get my transaction id? Is that correct? Do I use sha256sum or something like that? |
|
|
|
How does the overall community feel about dooglus giving positive trust to a scammer ponzi who ended up stealing at least 0.1 BTC? I think this might be forgivable if it is a one time occurrence and the offending party (dooglus in this case) wee to reimburse those who lose money because of his positive trust rating (he was saying that the scamming ponzi should be trusted when this was not a true statement. I think what happened with the scamming ponzi was a form of trust farming because someone on Default Trust gave them positive trust when such positive trust was not due. It has been speculated a couple of times today in a thread that I created about this scamming ponzi that dooglus might have been selling his positive trust. People should be aware that this account is a likely alt of Quickseller, he's been on a slam-dooglus mission for approximately ~2 months. Being in the trust network means you should call them out. While you are at it feel free to look over my sent feedbacks also. We are supposed to be held to a higher standard. Look at Tspacepilot now...he is green for nothing. Give him 6 months and he will have great trust for no reason at all lol. Nothing against him, but he got free trust with no deals.
Since you brought it up, I may as well respond. (1) I got positive ratings, not inclusion in any trust list (that I know of); (2) I also have been given "free" negative ratings with no deals: they were from a known scammer Tradefortress for what were effectively lies against me and I then acquired further negatives for "free", still with no deals, these being from from 3 or 4 of Quickseller's alts (one of them has since been removed) in an attempt to smear me away from these forums because I dared to disagree with him and call him out on his temper. As to my "free" positive rating, when I continued to stand up to QS' bullying, he continued to bring in more and more alts and sockpuppets to try to smear me. When dooglus stood up to him and effectively made him account for his bullying behavior, he brought in yet another alt, which was crucial in outing his escrow scam. Side note: you can see QS doing this same attack vectors against dooglus and Vod nowadays (although, I suspect he'll get a lot less far against them than he did against me because effectively, I'm a nobody around here and dooglus and Vod have long reputations with many backers). QS's continual sockpuppetry ended up outing an escrow scam he was running in which he was stealing escrow fees from his customers, and several people gave me positive ratings for investigating and reporting this. You can call that "nothing" if you want to, but I guess I think you have to consider the standard in two directions: if it was okay for TF and QS to neg-rep me without any "deals", then why wouldn't it be okay for other people to positive rate me without any "deals". If it's not okay to neg-rep without deals, then I could see your point that I shouldn't be positive rated just for outing a thief. In any case, I don't really need or want the green-ratings, as you say, I don't trade around here and I have no plans to begin doing so. But I do think that if you don't like people getting positive rated without deals, then you ought to consider whether it's okay to negative rate without deals. Just my two satoshis. |
|
|
|
NB4 someone posts a screenshot of dentals 39.5k win from a 0.4 bet.
Here's a cut-n-paste, just so you're not completely out in the cold on it: betid 875431071 date 2015-10-15 12:24:29 name dental user id 1163245 payout multiplier 99000x stake 0.4 CLAM profit 39599.6 CLAM chance to win 0.001 % target < 00.00 10 lucky number 00.00 05 result win hash of server seed 09d1e431628b7549904ac3b25650363e7c55f534ade7c4a99740174709a48646 server seed not yet published client seed 496682223676167626122357 nonce 156408 Amazing luck from the dental, eh? |
|
|
|
Dooglus has left positive trust for the following scammers: I haven't scammed anyone. And guess what, that's the main reason why there's no proof that I've scammed anyone. Now, I have been accused of scamming by, let's see, two known scammers: Tradefortress and Quickseller You got caught escrow scamming and stealing escrow fees from your customers, now you're butthurt. But really, this is on you. If you hadn't been stealing from your customers, you wouldn't have been caught doing it. EDIT: I have also found evidence that OP is an alt of Quickseller. I cannot release any proof at the moment, but people should bear this in mind when evaluating the posts of OP.[/list] |
|
|
|
Anyway I think I'm gonna switch back to windows. Linux is just too complicated for me!
Sad to hear it. FWIW, I find windows impossible to use. I guess it's what you're used to. As you know Linux is a clone of UNIX, which was envisioned as a multi-user time-sharing operating system from the start (way back in the late 70s). Windows only got multisuer functionality in like windows 95, I think. Anyway, if you have multiple users you need a good system of permissions and ownership. It seems to me that your difficulties are in part from the fact that you're trying to use a FAT32 partition. Why not use ext files system? Anyway, good luck to you. If you want to keep debugging there are plenty of people here who are willing to try to help. Best, TSP |
|
|
|
|
Show Posts
