Well, it depends... Who is locked from using his account=>@OP Who is fine without => Me  Great, and I don't have any alligators in my backyard because the alligator replant is working like a charm. As with anything in tech, if you have a backup your pain will be greatly reduced when the shit hits the fan. Any device can get lost, stolen or broken, but that doesn't mean you shouldn't use them. If someone steals your laptop with your hot wallet on it and there's no 2FA, they're gone. If someone steals my laptop, they just stole themselves a 5 year old laptop. Congrats. I'll import my backed up keys and my life goes on. Edit: oh and your online banking, Amazon account and Facebook were all logged in. The attacker now has a full list of your friends/family, all of your banking details , your bitcoin wallets and your address. I sure hope they're a friendly criminal and not one of those nasty ones. That's poor logic. 2FA should be mandatory on every CEX no matter what.
I heavily disagree with that. 2FA's whole purpose is to be a second layer of security in case of the password getting leaked. A user with security in mind and a password which does not composed of the name of a pet + 123, does not need 2FA at all. If the password is secure AND one can somehow 'guarantee' that their system will stay safe, 2FA is no way necessary. Regarding 2FA as mandatory is a wrong approach. 2FA won't help you if you are doing everything without security in mind. I agree with 2FA as a second layer being more tough to hack into, but it is BY FAR not impossible. That's one purpose. Another purpose would be so that no one can log into my account unless they have my physical key. That takes care of "the internet" as an attack vector and my ultra long random password will take care of brute force attacks. Also, how many people out there can "'guarantee' that their system will stay safe"? If I said 1% of the population I would be grossly overestimating. There is no downside to offering 2FA. (No - the extra 10 seconds it takes for you to log in is not a downside). For those that are interested, Google uses physical security keys just like any other security conscious company. If your company doesn't and you're dealing with sensitive data, you may want to nudge them in this direction. https://www.extremetech.com/computing/274067-google-eliminated-phishing-by-giving-all-85000-employees-usb-security-keys |
|
|
|
|
Bitcointalk is a lot more than just a forum where people hang out and talk about a common interest. We're hyper paranoid tech freaks that trust no one, because we don't have to anymore. I don't always trust the machine that I'm on for whatever reason, so I have 2FA on everything that offers it. If the product or service doesn't offer 2FA I look for an alternative. Please, I'm begging you, don't make me go to Reddit.
I know the new forum is coming soon™ but we need this yesterday. The only other short-term solution is to never log into my bitcointalk account or only use a secondary account. It's far less than ideal.
Best case scenario, we would be able to use a physical authentication device, but google authenticator would be a good solution too. I'd even take email or SMS 2FA over nothing. Those aren't ideal solutions though.
Please add 2FA. There's no downside other than the time it would take to implement it. Please.
|
|
|
|
You know you're a shitcoin when even Liqui doesn't want you. Hi, We are announcing that on September 28, 2018 at 12: 00 UCT we will be delisting folowing assets: CFI, TAAS, EDG, MCO, MGO, WAVES, BAT, MLN, TKN, MYST, ICN, TIME, REQ Once the withdrawal deadline has been reached (October 13, 2018 at 12: 00 UCT), withdrawals will be disabled and the asset will be fully decommissioned. From this point forward, we will be unable to process withdrawals of impacted assets. It is imperative that customers withdraw delisted tokens by the withdrawal deadline. Please, read carefully official announcement here https://liqui.io/News/#/article/1Best, - Liqui Team |
|
|
|
Omg and the best one of all, in a 1000 page post about "Do you think bitcoins are good?" Or whatever: First, you quote someone else. It makes your post look bigger even though it's a one-liner. Then you start with "I agree with you". It's perfect, because now you didn't duffer Andy feathers and can regurgitate what has been said 10,000x already. Well worth the 1000 Satoshis you just earned. Here's two accounts that are probably the same shitposter and a typical post you'll see shortly after: if in my opinion because the government and the bank are afraid that the community will choose bitcoin to be used as an investment rather than using paper currency. so because of that the government announced bitcoin was illegal
in my opinion, not only is that a very strong reason, maybe the government is afraid of negative results that will result from investments with crypto currencies, crypto currencies are always preached with negative and bad Another 1000 Satoshis and that only took me 30 seconds to mash a bunch of words together. At this rate I can make 60,000/hr, which is about $3.90. Sure as hell beats lugging bricks across the desert for 13 cents an hour. |
|
|
|
Thank you sir. Now I actually know how to trigger all of these newbies, who have no merit, but are still trying to get into an ICO. Please post more sir due to the fact that I want you to. Nah but seriously, I've always joked about a few things that come up either from Google translate or a weird grasp on the English language. "Avail". I've never in my entire life heard someone say this other than "...to no avail." Anything else is just strange. "I will avail to earn Bit-Coins."  "Entreat". Another hilarious and odd word choice. " Entreat me to Bit Coins!!" Oh and last but not least, when people make grammatical errors like "your an idiot" or "please advice me". In case you aren't sure what the mistakes are there, " You're an idiot." And "Please advise me." Would be correct. I will now avail to find some newbies in ICO threads and Entreat them to some actual merits, sir. |
|
|
|
Woop woop! 1022 for me apparently. About time.
When does the hazing start?
Usually peeps don't want to be hazed, and since you are requesting hazing, the best hazing might be to ignore you. hahahahha  Reverse psychology works every time.  Damn. No hazing for me I guess. This is the worst Legendirthday ever.  |
|
|
|
The main reason why I don't use 2FA, I don't want to be dependent on a 3rd party to be able to log in somewhere. If I can not have a full control over the 2FA, ok, otherwise nope. And if the site doesn't give the choice I simply don't use it and switch to something else. Binance is a good example, you're forced to use 2FA or you are not able to transfer out anything, no problem, there are plenty of exchanges to use instead
@OP, your only hope is what @ETFbitcoin posted above. good luck ^^
That's poor logic. 2FA should be mandatory on every CEX no matter what. Not being educated isn't a good enough excuse anymore. Reputable exchanges aren't letting newbs take risks that they shouldn't. If they offer SMS 2FA then they aren't secure anyway and should be avoided. Google "sim port hack". Buy a physical key like a Yubikey. If you get malware your randomly generated 120 character password won't save you, but a physical OTP device will. It's 100% reliant on you and not your device turning on or your phone carrier keeping your account active.
OP you really need to explain what you're trying to say. If you physically have your phone and you held bitcoins on it then you still have the same information whether you paid your bill "circumstances" happened or not. |
|
|
|
FINALLY!! Thank you! This is what's been needed for years around here. Woohoo!! One step at a time things are really starting to look better around here. If you need help nuking people I can get all over it |
|
|
|
|
Woop woop! 1022 for me apparently. About time.
When does the hazing start?
|
|
|
|
There are multiple mathematical formulas and algorithms involved in both the calculation of a public key from a private key, and from a public key to a bech32 address. I would estimate that it would take you a few decades to do either of these algorithms. With a computer to do some precomputation, you can probably do it in a few years.
For public key from a private key, Andrew Poelstra has a pretty good post describing it here: https://bitcointalk.org/index.php?topic=1534028.msg15594185#msg15594185 along with a precomputed table for you.
For the Bech32 calculation, you will need to be able to do two different hash functions: SHA256 and RIPEMD160. Then you also need to calculate the checksum which uses a BCH error correcting code. For SHA256, Ken Shirriff has a pretty good blog post about how to do SHA256 by hand for mining. It's the same operations, just on different data. Also, you are doing only 1 SHA256 computation, not 2 as mining requires. You perform the SHA256 on your serialized public key in compressed form. For RIPEMD160, I don't think anyone has really explained how to do by hand (and I don't really want to be cause it is long and takes a lot of time which I don't have). The algorithm is described in this paper with pseudocode given in Appendix A. It is similar to SHA256 in that the message is broken up into chunks which are XOR'd initially with some initial values and then later with the previous chunk.. You would like use a similar method as described in the SHA256 blog post but with the modifications to be able to do RIPEMD160. You perform RIPEMD160 on the above SHA256. For calculating the checksum, you use the algorithm described under the Checksum section in the BIP. The gist of it is that, given a list of numbers, you apply multiple polynomials on all of the numbers and the "sum" of the results is the checksum (it's a lot more complicated than that and I don't remember all of the details). The python code given in the bech32_polymod() function describes how to do this. Note that ^= in python means XOR, not exponentiation. To calculate the final bech32 string, you first need to convert the hash160 into a list of numbers usable for bech32's checksum calculation. You do this by splitting up the 160 bit hash into 5 bit chunks. Each 5 bit chunk is then a number so you now have a list of 5 bit numbers. You prepend to that the witness version, which is 0, so the list now starts with the number 0. Then you prepend to that an expansion of the human readable part of a bech32 string, bc. This is expanded by using the bech32_hrp_expand() function in the python code given in the BIP. You will get a list of numbers like so: [3, 3, 0, 2, 3]. So the resulting list of numbers will be 39 numbers in length and begin with [3, 3, 0, 2, 3, 0, .... Lastly you append six 0's to the end of the list which represent the positions that the checksum will go in. Now you do the bech32_polymod() function on this list of numbers and the resulting value you get back is the checksum. Now you must convert all of these numbers to characters. You do this by breaking the checksum into 5 bit chunks to get a list of 6 numbers. Then, given the list of numbers containing the witness version number, the hash160, and the checksum, convert each number to the corresponding character using the lookup table described in the BIP. Note that you do not need to do this to the expanded human readable part. The resulting bech32 address is the human readable part concatenated to the character '1' concatenated to the characters for the witness version number, the hash160, and the checksum. So it will begin with bc1.... Regarding the human readable part expansion, that is done because the human readable part can be any ascii character and the numbers in the list of numbers need to be in the interval [0, 32). However ASCII can have numbers outside of that interval, so the expansion is done to have the higher bits, then the lower bits so it all fits in the interval. So it sounds like going from a public key to any address is just completely out of the question, which is what I expected. I may attempt to learn how to do a private key to public key, but even so it's a lot to go over. Thanks so much for the post and I'll see if it's something I can achieve some day. |
|
|
|
I've learned over the years how to generate a private key with HEX (from binary - coin flips) B6 (dice) but I've always used an air-gapped system to take said private key and find the corresponding Public Key and address. I would like to figure out what the actual formula is for finding a Public Key from a Private Key. If anyone knows how to do this with a bech32 address that would be amazing. I currently have a private key in binary and HEX and wasn't sure how to get it into WIF format manually either. If the Public Key can be located with a binary or HEX Private Key, that'd be even better. From what I've read, the public key to Bitcoin address would be extremely tedious and IMO it's not worth the time (if it's technically possible within a human lifetime). I'm also not worried about someone having my public key, so would have no issue plugging that into any computer and having it find the corresponding address. This looks like a great link, but if someone could explain a lot more in depth what exactly the formula should look like, whether this is possible with pen and paper and/or a scientific calculator, and roughly what timeframe it would take to complete (i.e 5 years assuming you work on it 12hrs/day vs. 20-30 mins) I would really appreciate it! |
|
|
|
The idea has just started its business development. Already I see activity! I liked the idea of your business. I will follow the development of the platform in the future!
They need to do something about all these spammers it's getting out of hand. Dude I hear you. And I feel bad somewhat adding to the spam by talking about all the people spamming! But it is seriously out of control, Google translate getting a workout on the ravencoin thread with rubbish like 'this business could be the turning point when it is realised' and 'from whitepaper its very interesting and worthy to invest idea'. Like wtf am I reading is this pro level trolling or am I losing my mind. Someone needs to moderate/step in and stop signatures and bounties for new accounts and just go on a banning spree. Even though I am the one who created this thread, I don't believe btt allows me to do much about the spam or signature campaigns etc. Just wanted to let you guys know, I'd do something about it if I could. It's mostly bots or scripts that are automated, not sure what the purpose is for though. It's fine. It's like any other thread. Just report shitposts as they come in. Why do they do it? To sell the account later, or join signature campaigns and earn money. Whatever you do, don't make a self-moderated thread. A lot of people on Bitcointalk won't even bother posting if it's possible that they'll be censored. I know I wouldn't. Any project that went with a self-moderated thread did so because they're sketchy (or just look sketchy now because of it). |
|
|
|
I'm sorry to see this turned into a trainwreck. I hope this doesn't harm the participant's will to support DEX projects. They will be an essential cornerstone of the crypto economy.
Those that bought more along the way did better than those that only participated in the ICO, so it didn't turn out horribly for everyone. As for other DEXs, it's honestly hard to find a real DEX still. I hope I find something like this to invest in again, but when I do I'll probably be too late. |
|
|
|
Well well well, BitcoinTalk staff accused of stealing.
I don’t believe anyone is accusing Bitcointalk staff of stealing. They think Lauda is still a mod lol. I guess they missed the news. I got my 45% refund in case anyone was questioning whether refund were done properly or not. |
|
|
|
What different between your exchange from a lot of other decentralized exchanges? There are a lot of existing, but people using only Idex mainly...
The difference is you're shitposting on a dead project and other ones may have real working DEXs (not that you'll ever read this). |
|
|
|
|
End-to-end encryption would be the obvious resolution to this. In the meantime, decentralized internets will be coming out in droves and let's just hope that one of them is half decent and we can avoid all of this crap (mostly).
|
|
|
|
In case anyone is having issues voting from a paper wallet, I wrote up a quick guide. First, you'll need to download the zip file from https://github.com/Jpja/Sweep-XCP-PaperwalletUnzip it and open sweep.html in your favourite web browser. You'll need to input the private key of the paper wallet. Fill in all of the other details and send them to an address that you have generated on counterwallet.io or straight to the voting address. Note: Sweeping counterparty assets can be finicky. You'll need one larger input of at least 0.0005 bitcoins in the address that you're trying to sweep from. I found that sweeping only worked when I swept all of the bitcoins along with the tokens. This is why I would suggest sending to an address generated on counterwallet.io first, then voting from there.The voting addresses can be found at https://medium.com/@nvoteam/vote-started-b3e37e0c1ecfTo vote for a refund, send to 17vvg1h5B5qwP2d2oz7t2GpXXpztxsmjNn To vote for the project to continue, send to 1Caux6gNUB55cALFk1EHiRY5Eo613yuGhE Do not sweep all of your assets to the voting address! Only NVSTVOTING tokens!If you're not sure what you should vote for, join Discord or Telegram. Many users are having issues with censorship on Slack (which is typically full) and Telegram, so Discord is suggested for uncensored discussion. Note: The NVO team does not regularly post on Discord, so there wouldn't typically be any first hand information there.
Telegram: https://t.me/joinchat/Ff92WUidI54g8rv2NdRr1ADiscord: https://discord.gg/YvB5HXpTo view the voting results thus far, please visit https://nvo.party/vote.phpThe voting should be ending some time around August 29th, although no exact deadline has been given. If you haven't voted yet, please attempt to do so ASAP in case there are any technical difficulties that you need to work through. Honestly, I'm not the most technical person so it took me quite a while to figure out how to vote from a paper wallet. I'll try to help with any questions but joining discord or Telegram is highly recommended. Additional tip: The counterparty wallet sweeping process may appear to jam intermittently. I had a number of addresses (Electrum) and some worked while others didn't. After trial and error I figured out the common denominator: If an address has received more than one transaction (i.e. has more than one current spendable input) it would jam the xcp sweep. The solution was to send all BTC on an address to itself (collapse multiple inputs into a single). The sweep process then worked fine. Thanks. I should have clarified that. By "one larger input" I meant exactly this. If you have lots of small inputs be sure to send them to another address and send them back all as one input. |
|
|
|
I'm not familiar with hardware wallets so I couldn't say for sure what the issue would be. Is it a legacy bitcoin address? It may be best to join the telegram or discord in case anyone else has had success with a Ledger Nano S. |
|
|
|
In case anyone is having issues voting from a paper wallet, I wrote up a quick guide. First, you'll need to download the zip file from https://github.com/Jpja/Sweep-XCP-PaperwalletUnzip it and open sweep.html in your favourite web browser. You'll need to input the private key of the paper wallet. Fill in all of the other details and send them to an address that you have generated on counterwallet.io or straight to the voting address. Note: Sweeping counterparty assets can be finicky. You'll need one larger input of at least 0.0005 bitcoins in the address that you're trying to sweep from. I found that sweeping only worked when I swept all of the bitcoins along with the tokens. This is why I would suggest sending to an address generated on counterwallet.io first, then voting from there.The voting addresses can be found at https://medium.com/@nvoteam/vote-started-b3e37e0c1ecfTo vote for a refund, send to 17vvg1h5B5qwP2d2oz7t2GpXXpztxsmjNn To vote for the project to continue, send to 1Caux6gNUB55cALFk1EHiRY5Eo613yuGhE Do not sweep all of your assets to the voting address! Only NVSTVOTING tokens!If you're not sure what you should vote for, join Discord or Telegram. Many users are having issues with censorship on Slack (which is typically full) and Telegram, so Discord is suggested for uncensored discussion. Note: The NVO team does not regularly post on Discord, so there wouldn't typically be any first hand information there.
Telegram: https://t.me/joinchat/Ff92WUidI54g8rv2NdRr1ADiscord: https://discord.gg/YvB5HXpTo view the voting results thus far, please visit https://nvo.party/vote.phpThe voting should be ending some time around August 29th, although no exact deadline has been given. If you haven't voted yet, please attempt to do so ASAP in case there are any technical difficulties that you need to work through. Honestly, I'm not the most technical person so it took me quite a while to figure out how to vote from a paper wallet. I'll try to help with any questions but joining discord or Telegram is highly recommended. |
|
|
|
It's true, it's all true! I just remember looking up these guides and going wtf? I'll just buy an already existing tool. Then you have it for the future if/when this happens again. I've used mine maybe 3x but man does it ever save some blood sweat and tears rather than trying to file the screw so a flathead screwdriver can screw it out, or drill through it to break it up or use an elastic band. They're just - meh. They'll still be a ton of effort. If you can't get it out with plyers it's time for the extractor. That's my rule of thumb. Don't spend an hour trying to get a screw out 
I just thought of something I should have asked in the first place. Are you replacing the wifi card? If so, just cut the corner off, crack the little bits around the screw off then take the screw out with a pair of plyers. Thanks. I've already bought the extractor and it will be used for other broken screws I may encounter with in the future. Yes, I'm replacing the Wi-Fi card on the laptop, and I may try breaking it just to remove the screw, since it doesn't work after all. I'll give you guys an update once I'm done extracting the screw and placing a new Wi-Fi card on my old laptop. And then, I’ll need to find a brand-new screw that would secure the card nicely in its place  Rofl I sincerely hope you got this screw out shortly after that last post |
|
|
|
|
Show Posts
