Please enable HSTS to avoid sslstrip or a MITM replacing the http page. https://en.wikipedia.org/wiki/HTTP_Strict_Transport_SecurityWith PHP check if the page is been served in HTTP, if so redirect to HTTPS. In HTTPS set the HSTS header: header("strict-transport-security: max-age=31536000"); That tells the browser to only use the HTTPS versión of inputs.io for a year (31536000 seconds). So, my browser will go directly to https even if I have no internet conection. Done. Thank you.
|
|
|
Just out of curiosity, why not just move bitfunder to a friendlier country like China?
I don't think Ukto wants to move away from the us along with his family.
|
|
|
I think you missed me in the latest round, I didn't received a payment to my inputs.io account. I reconfirmed my participation on the 7th September: <snip> Thanks TF payment received Confirming that I will continue with the signature ad for another month. Thanks TF Oops, paid, thanks!
|
|
|
I believe BTCTalkaccounts is associated with:
Dannyjr89 tkone r3wt
And who else? Theres many of his accounts! Its so annoying!
I don't think Dannjr89 is associated with BTCTalkAccs. tkone's account appears to have been hacked. r3wt definitely isn't BTCTalkAccs. If you're interested in people who is associated with BTCTalkAccounts, try ironcross and Blazr.
|
|
|
Conclusion: Don't send a large sum of money in a single transaction. Instead, make many small transactions that you can afford to lose in case of this rarely occurring MITM attack. When the other party receives this small transaction, it should somehow communicate to you "Keep going, you're sending to the right address". The communication part should obviously use another channel based on some existing trust. If you know you can trust blockchain.info then you can just check the receiver on that site, trusting the CA used by blockchain.info.
That's silly. Assume a CA is rogue, they are able to generate a cert for blockchain.info and MITM. I'm not sure how checking Blockchain.info will help because that will just tell you if a transaction was received or not.
|
|
|
Google still has 1.39 million results from bitcointalk.org - https://www.google.com/search?q=site:bitcointalk.orgBecause of Bitcointalk.org's request timeouts, Google probably applied a significant enough penalty for it to pushed into a supplementary index (which generally does not show up) for the next couple of days.
|
|
|
You don't need a registar for namecoin domains. In fact, it is the best idea to not use a registar, because the domain belongs to them instead of you and there is no regulatory agency to keep their behavior in check.
Download namecoin-qt or namecoind and follow instructions to register namecoin domains yourself - for 0.01 NMC.
|
|
|
Why these platforms closed? Can anyone post the back reason?
The US government is 'protecting' its citizens against the evils of bitcoin stocks. Well, they are protecting some citizens all right.
|
|
|
A share of - is still a share. The BitFunder events along with other downturns in the investment sector have been very unfortunate, but I'm confident that we can get past that. If you are curious about BTCINVEST in relation to CL, note that we started at 0.1 per share.
|
|
|
The most important thing right now is don't panic. We have a number of different options.
Please make sure your public address listed on BitFunder is correct. Depending on which option BTCINVEST takes, it may simplify possible claims processes if you use an Inputs Bitcoin address.
|
|
|
If the 1 BTC is too steep, you might want to split the cost with some(one/people) that you trust.
|
|
|
btct.co 9 ASICMINER-PT: 11.7 BTC 222 Crypto-Trade: 37.74 BTC 248 BitVPS: 0.4717 BTC 356 DMS.SELLING: 3.35 BTC 300 CB.IDIFF-E: 7.5 BTC
btct.co total value: 60.7617 BTC
What's the plan with the BTC60 worth of btct assets? ASICMINER-PT will be migrated to direct shares Crypto-Trade's plans are to relist trading of their shares on their own site. BitVPS has no announced plans yet, unfortunately. DMS.SELLING is very likely to migrate to BitFunder CB.IDIFF-E's payouts will be simply made to our BTC address set in btct.co
|
|
|
Revenue DMS SELLING dividends: 1.09 BTC ASICMINER dividends: 5.2257 BTC Graet.Loan interest: 1.223 BTC Ukyo.Loan interest: 0.1669 BTC Crypt-Trade dividends: 0.5166 BTC Btct.co trading of BTC-Bond, CIPHERMINE.B1, etc): 4.182 BTC Share buyback spread: 4.26 BTC
TOTAL: 16.6642 BTC Paid as dividends: 14.9977 BTC Dividends per share: "You will be issueing (14.99770000 / 5926) = 0.00253083 per share. Final Total: 14.99769858.".
Assets Not traded on an exchange: 260 ASICMINER (directly) - 338 BTC Just-Dice investment: 432 BTC
BitFunder 42 G.ASICMINER-PT shares (valued at btct price): 54.6 BTC 2,057 Ukyo.Loan: 20.93 BTC 105,020 btcQuick: 36.967 BTC 16,309 Graet.Loan: 164.72 BTC 2949 TAT.MINIGAME: 0.737 BTC
Bitfunder total value: 277.954 BTC
btct.co 9 ASICMINER-PT: 11.7 BTC 222 Crypto-Trade: 37.74 BTC 248 BitVPS: 0.4717 BTC 356 DMS.SELLING: 3.35 BTC 300 CB.IDIFF-E: 7.5 BTC
btct.co total value: 60.7617 BTC
CoinLenders 90 day CD #3: 100 BTC
Total coins: 37.582 BTC
Total: 1246.2977 BTC Shares outstanding: 5926 NAV/share: 0.21031 BTC / share
|
|
|
https://coinchat.org room #tag - mBTC prizes! The game involves creating a sentence when given it's acronym. Example: KQCIP -> Keep Quiet. Copulation in Progress.
|
|
|
The backdoor is specific to the forum. It's probably something as simple as eval() with certain arguments passed in obscure and unintended methods.
|
|
|
Ah, alright. I generate my own but I understand why people would want it. Is it possible to import private keys into Inputs? Like, generate in example 1yoloswag and import this privatekey (once generated) into inputs, and then use that address on inputs.io? Also, question apart from inputs.io, I just realized, if I were to generate 1BoeLens (like I have), it'll have some random things after it like ATmad51 etc. However, what happens if someone were to generate the exact same address? I'm no math experts but I think the odds would be astronomically small, but couldn't you "brute force" addresses like that? Especially tiny ones.
Importing private keys can't be implemented. It is possible however as the odds are astronomically small, making it irrelevant. Bitcoin uses secp256k1, and private keys are 256 bits, or 1.1579209e+77.
|
|
|
|