ThomasV probably did not update that file. It is unlikely for a hack as ThomasV himself posted it here. Nevertheless, I recommend you to verify both executable and sources. |
|
|
|
Trust is not moderated. Admins may remove trust feedback spam but only if it is excessive. -snip-
All these happened without any reason. What is the best thing I can do to avoid such unwanted disturbances??
It will only be a disturbance for you if you care about them. So don't care about such trust ratings, like Klomann said. Ignore. |
|
|
|
What I completely dislike in this forum is when everyone - especially those on the default trust list - jump in to leave negative feedback for deals they have absolutely nothing to do with.
In my opinion, this is also some kind of abuse of power. I don't want to attack anyone here; I just want to leave my opinion.
The only ones leaving negative feedback here should be those who were involved in the trades, and no one else. There is no need for some sort of altruistic Samaritans jumping in on any situation possible.
This makes the reputation system flawed, misleading and a direct invitation for abuse. Actually, there should be an option to hide the trust data of any user, and it should be hidden by default.
What if the users involved in trade is not in default trust list? People in default trust must leave feedback so others can know atleast when they see negative trust score. Also, the default list should not exist. There should be some other way to define if a user's rating matters or not.
What about trust spam? If all trusts are weighed equally, then how can we prevent trust spam? Keeping trust feedback moderated? How can we prevent abuse of trust moderators, then? What you said is not plausible but if you have a better idea which I(& others) may have missed, feel free to post in Meta. If you want to continue discussion, please post in Meta. |
|
|
|
Speed comparison: Just to get back to the performance bit of non-ocl vanitygen ( standard v0.22 lifeboat version), some figures (applicable to the i7-4702MQ 2.2GHz config). Ran each test for 5 minutes. Relative efficiency is based only on the number of 'found' keys in that timespan. | type | command | generated keys | 'found' keys | % matched | relative efficiency | | regex | vanitygen.exe -o file.lst -k -q -F compressed -r .* | 21,262,638 | 82,797 | 0.38940% | 98.72% | | standard | vanitygen.exe -o file.lst -k -q -F compressed 1 | 21,534,544 | 83,874 | 0.38949% | 100.00% | input list
(1A,1B,..,1a,1b,..,11,12,..) | vanitygen.exe -o file.lst -k -q -F compressed -f input.lst | 21,688,744 | 84,499 | 0.38960% | 100.75% | | case insensitive | vanitygen.exe -o file.lst -k -q -F compressed -i 1 | 21,917,217 | 85,410 | 0.38969% | 101.83% | | non-compressed | vanitygen.exe -o file.lst -k -q 1 | 22,324,562 | 87,019 | 0.38979% | 103.75% | | 64-bit version | vanitygen64.exe -o file.lst -k -q -F compressed 1 | 27,455,567 | 106,980 | 0.38965% | 127.55% | | 64-bit, non-compressed | vanitygen64.exe -o file.lst -k -q 1 | 29,042,542 | 113,150 | 0.38960% | 134.90% | | 64-bit, non-compressed, four processes | vanitygen64.exe -o file.lst -k -q 1 | 104,220,011 | 406,105 | 0.38966% | 484.18% |
Using compressed keys adds a few percent overhead, so dropping that might be a reasonable idea (remember though that 'compressed keys' are preferred). The 64bit version is quite a bit faster than the 32bit version as well. Combining the two there's a pretty reasonable speed gain. There's maybe a bit more to gain with the case-insensitive option, but I'd have to run much longer tests to see if that's a real gain or just a wee bit of luck in that run. Running four concurrent processes was much faster still - apparently there's a good bit of overhead of code that doesn't/can't be run multithreaded when using such short prefixes. The other thing that stands out is that even though there's a significant number of keys generated, vanitygen only selects a very, very small portion of them as matches - even though every single one of them should be valid. This is primarily why a program that's specifically written for the task would be much better. In fact, given how few vanitygen actually returns here, I wouldn't be surprised if one of the existing python libraries or even javascript (bitaddress.org's bulk generator is slower, but there might be some performance to gain in their implementation as well) would perform much better. It also reminds me of that weird bounty/'rendezvous points' hunt, which - at least for CPU - might be an easier starting point for modification (if not starting from scratch):- A comparison against longer patterns: | type | command | generated keys | 'found' keys | % matched | relative efficiency | | '1' | vanitygen.exe -o file.lst -k -q -F compressed 1 | 21,534,544 | 83,874 | 0.38949% | 100.00% | | '1A' | vanitygen.exe -o file.lst -k -q -F compressed 1A | 16,982,045 | 66,152 | 0.38954% | 78.87% | | '1AA' | vanitygen.exe -o file.lst -k -q -F compressed 1AA | 72,843,612 | 49,592 | 0.06808% | 59.13% | | '1AAA' | vanitygen.exe -o file.lst -k -q -F compressed 1AAA | 256,016,211 | 3,419 | 0.00134% | 4.08% |
One thing that stands out here is that the percentage that 'matched' is the same for patterns '1' and '1A', which I think shouldn't be the case. The other thing is the total number of keys generated. '1A' having generated fewer than '1', while '1AA' and '1AAA' generated more and far more respectively. tl;dr: vanitygen is weird when used for purposes other than what it was designed for 
Edit: As the above tables were made using the Lifeboat version of vanitygen, the tables again with vanilla v0.22 (note that there's no 'compressed key' support unless patched in): | type | command | generated keys | 'found' keys | % matched | relative efficiency | input list
(1A,1B,..,1a,1b,..,11,12,..) | vanitygen.exe -o file.lst -k -f input.txt -q 1 | 21,858,878 | 85,213 | 0.38983% | 98.62% | | regex | vanitygen.exe -o file.lst -k -r -q .* | 22,057,282 | 85,920 | 0.38953% | 99.44% | | standard | vanitygen.exe -o file.lst -k -q 1 | 22,179,614 | 86,408 | 0.38958% | 100.00% | | case insensitive | vanitygen.exe -o file.lst -k -i -q 1 | 22,208,398 | 86,570 | 0.38981% | 100.19% | | 64-bit version | vanitygen64.exe -o file.lst -k -q 1 | 29,060,532 | 113,316 | 0.38993% | 131.14% | | 64-bit version, four processes | vanitygen64.exe -o file.lst -k -q 1 | 94,486,821 | 368,135 | 0.38962% | 426.04% |
| type | command | generated keys | 'found' keys | % matched | relative efficiency | | 1 | vanitygen64.exe -o file.lst -k -q 1 | 29,060,532 | 113,316 | 0.38993% | 100.00% | | 1A | vanitygen64.exe -o file.lst -k -q 1A | 23,848,310 | 93,430 | 0.39177% | 82.45% | | 1AA | vanitygen64.exe -o file.lst -k -q 1AA | 92,005,255 | 63,455 | 0.06897% | 56.00% | | 1AAA | vanitygen64.exe -o file.lst -k -q 1AAA | 316,811,630 | 4,000 | 0.00126% | 3.53% |
P.S. If someone else is looking to generate a vanitygen address, see https://bitcointalk.org/index.php?topic=25804.msg12220012#msg12220012. |
|
|
|
Please help me i want ask, what is the reason my account banned and how long my account banned ? Thank you !  You're not very good at this scamming thing, are you? thank you howbtc, i already buy 4 codes, and you fast respon me ...
thanks
no, howbtc just ask you please to me ... no be stupid here bro ... ok  Please help me i want ask, what is the reason my account banned and how long my account banned ?
-snip-
|
|
|
|
|
Reason is there. "Insubstantial posts and sig ad".
It means, you are permanently banned for spamming. Your ban might be taken off if you don't post in this forum for sometime, say 30 days.
P.S. Posting outside Meta from any of your accounts is ban evasion. All accounts will be perma-banned and you will have to wait more time to get it lifted off!
|
|
|
|
Another curious thing: /Lang (en-GB)For somebody in timezone -6 or -7 this would probably be "/Lang (en-US)". Is he Canadian? From Wikipedia: Occasional British English spelling and terminology (such as the phrase "bloody hard") in both source code comments and forum postings led to speculation that Nakamoto, or at least one individual in the consortium claiming to be him, was of Commonwealth origin. He posted in both British and American English. |
|
|
|
|
Idea can popup in anybody's mind. Only a few give life to that idea. You can not tell "I am the first person to come with this idea". Therefore, you can't reserve rights for an idea.
|
|
|
|
I have 5 prefix letters , what is the command line for find at least a BTC address for it ?
Case-sensitive prefix search:"path\to\vanitygen.exe" 1Prefix
"path\to\vanitygen.exe" -i 1Prefix
"path\to\vanitygen.exe" -k 1Prefix
"path\to\vanitygen.exe" -k -o anything 1Prefix
Edit: Searching for compressed key is faster than uncompressed key. Download Lifeboat's vanitygen. See https://bitcointalk.org/index.php?topic=301068.0. Also, see https://bitcointalk.org/index.php?topic=25804.msg10590011#msg10590011. Case-sensitive prefix search but not limited to 1 match and saves all matches to a file (compressed):"path\to\vanitygen.exe" -k -F compressed -o anything 1Prefix
|
|
|
|
Loan Amount : 0.01
Reason : To buy VPN
BTC Address : 1Co1YgJMFvn986kA1RfPoGnC9s2D55EsvM
Term Length : 3 Days.
Collateral : Account if you accept.
Denied. |
|
|
|
nice catch!
Still, I will assign a temporary BTC address based on session. Each visitor opens a new session which can be saved to the database. Each deposit request will call a script that creates a new wallet on Coinbase, which will be saved on the database with it's session identifier (and/or user id) and expiration time.
Another script will run every x minutes (probably a cronjob) and requests wallets balance. If user sent some BTC to the wallet, the script adds the difference to users balance.
Thats my point of view. I'll post an update if it works out or not.
Why don't you use Electrum [1]? Its easy and secure. But instead of that, I suggest to export your xpub key and use a tool [2] to generate addresses from it. For WordPress, use Adbussamad's [3] WordPress plugin [4]. What you only need to do is keep your Electrum seed safe, but when you use Coinbase.com API, you will have to trust them for whole work. Its not at all safe to store Bitcoins on an online wallet. [1] https://electrum.orain.org/wiki/How_to_accept_Bitcoin_on_a_website_using_Electrum[2] https://github.com/bitcoin/bips/blob/master/bip-0032.mediawiki#Implementations[3]https://bitcointalk.org/index.php?action=profile;u=85981 [4] https://wordpress.org/plugins/bitcoin-address/ |
|
|
|
The usual. Another cloud mining service acting shady...
They were a ponzi from the start but none of the "investors" cared. They were warned by several people. Anyway, we can soon see a few threads popping up when it go down. |
|
|
|
Answer this -- https://bitcointalk.org/index.php?topic=1158259.msg12219558#msg12219558. Edit: It's not.
It usually never is. There are various ways of making an informed guess, but of those candidates that display the most suspicious characteristics, there is frequently no death bed confession or suchlike. They're often killed or imprisoned for life under suspicious circumstances before they ever get a chance to do so (Lee Harvey Oswald being a possible exception, the "I'm just a patsy" line simultaneously served as a confession of his role, not just a denial of culpability).
I suspect that Hearn and Anresen are working with "five eyes" people, as there are good grounds to do so. There is zero evidence to support it at present.
Look at hdbuck's evidence. According to him, giving a talk to CIA makes one an asset of CIA.  |
|
|
|
-snip-
[ color=red][ u][ b]Two known CIA/NSA assets infiltrated in the Bitcoin community - Gavin Andresen and Mike Hearn - have joined forces to push a hastily concocted privacy nightmare/scamcoin, which they call Bitcoin-XT.
How is Gavin and Hearn a known CIA or NSA asset? [ size=18pt]It is currently completely irrelevant, owing to an absolute lack of financial, economical, technical or social support. [ /size][ /b][ /u][ /color]
|
|
|
|
Why does everyone keep asking about this question, can we just discuss it in a same topic. So please search any other topic that has the same question, before you asking it. BTW I use Multibit, easy to use and lightweight.  electrum is great too, and one thing it has over multibit is the ability to adjust the tx fee and also choose which addresses outputs are spent from. Electrum has some issues, and perhaps some bugs too I already signalled in this thread: https://bitcointalk.org/index.php?topic=1152808.0So i`m not FUD-ing but I think Electrum needs more development before we can use it safely. I can not see any bugs but suggestions. Read ThomasV's post. He has addressed all your questions/statements. Electrum is pretty safe as a wallet. |
|
|
|
-snip-
I'm not a professional cryptologist.
Neither am I. I can use tools to encrypt and decrypt files but I don't have deep understanding of the underlying mechanisms.
You don't have to study cryptography to encrypt private keys. Just study the basics. https://github.com/bitcoin/bips/blob/master/bip-0038.mediawikiBecause of that should I avoid BIP38 and just be careful where I store the papers?
That's your choice. If you want to use BIP38 encrypted paper wallet, you can use it. Else, don't. Either way, store your paper wallet safe. But the clients can scan the QR code and handle it seamlessly even with BIP38. What do you guys think?
Most of the clients now have option to sweep from or import BIP38 encrypted private keys. I would gp with it. If I decide to encrypt it with bip38 then I could store the password elsewhere. Any other drawbacks of BIP38?
I don't think "storing password somewhere else" is a drawback of BIP38. If you are writing down your password, don't write it as a "password". Write something and along with it, write your password. So it is less obvious. Of course it could be that I misplace or forget (Maybe a disease?) and then the papers would be useless.
That's not a drawback of BIP38. -snip-
1. Paper wallets for 3-5 years storage without BIP38
Paper wallets are good-to-go for long-term storage. But physical security is low. I highly recommend you to print/write private keys in a thick paper & make a few copies and try not to store it inside a plastic cover. If you are doing so, then you should take printed/written paper out once every few months and if you are in coastal area, take it out more frequently. For little more security, put one or two papers on both sides of the printed/written paper so that it does not touch plastic. By doing so, you don't need to take it out frequently. 2. Bitcoin android Wallet for android and Mycelium
|
|
|
|
|
Trust is not moderated. His trust won't affect your trust score. So just ignore it.
|
|
|
|
|
Show Posts
