OK, i am mining in the upwards of 2500 Ghash/s range and was wondering if i should go solo or just use a pool. if anyone is wondering, i am running an NVIDIA GT 420m CUDA and these are the flags: -cuda -gpugrid=500 -gputhreads=512 -aggression=14 is this even safe for my laptop? i have a cooler under it. nothing feels too warm, and my system is stable. i guess it helps to have an integrated card and a dedicated graphics card, huh?  Sorry, but there is no possible way you are running 2.5TH/s on a NVidia 420m graphics processor. I get around 5MH/s on a laptop of mine's 320M, so you are probably getting around 7MH/s at most. If your mining software is showing 2500GH/s (as you said) something is certainly wrong. You I imagine are mining to a pool, what does the pool report your numbers as? For some benchmarks, the best dedicated graphics cards have a hell-of-a-time reaching 1GH/s, you are claiming 2500GH/s with a laptop's 3-generation-old integrated graphics processor. What mining software are you using that's spitting out these erroneous numbers? And to answer your question, if you are mining with a mobile GPU, you should pool-mine, it will take far too long to solo-mine (literally years upon years). Edit: it appears you are using 500GPU threads... I've seen mining software have issues with a lot of threads as far as calculating hashing speed. This is likely the case. Lower that to something like 1-2 perhaps? i'm using gui miner. it really pisses me off though that i let my laptop sit for three days and all i have to show for it is .0042 BTC. THAT IS REDICULOUS! is there a way to get more BTC faster? ok, i set my gpu grid to 200 and same for the threading. it gives off 10mhash/s is that more acurrate? BTW how many miners do you have running at the same time? 10MH/s is much more accurate. You are not going to mine much with a mobile GPU unfortunately, they have extremely low capabilities when it comes to data crunching such as hashing. I have 2 threads per gpu at most for me. |
|
|
|
OK, i am mining in the upwards of 2500 Ghash/s range and was wondering if i should go solo or just use a pool. if anyone is wondering, i am running an NVIDIA GT 420m CUDA and these are the flags: -cuda -gpugrid=500 -gputhreads=512 -aggression=14 is this even safe for my laptop? i have a cooler under it. nothing feels too warm, and my system is stable. i guess it helps to have an integrated card and a dedicated graphics card, huh? Sorry, but there is no possible way you are running 2.5TH/s on a NVidia 420m graphics processor. I get around 5MH/s on a laptop of mine's 320M, so you are probably getting around 7MH/s at most. If your mining software is showing 2500GH/s (as you said) something is certainly wrong. You I imagine are mining to a pool, what does the pool report your numbers as? For some benchmarks, the best dedicated graphics cards have a hell-of-a-time reaching 1GH/s, you are claiming 2500GH/s with a laptop's 3-generation-old integrated graphics processor. What mining software are you using that's spitting out these erroneous numbers? And to answer your question, if you are mining with a mobile GPU, you should pool-mine, it will take far too long to solo-mine (literally years upon years). Edit: it appears you are using 500GPU threads... I've seen mining software have issues with a lot of threads as far as calculating hashing speed. This is likely the case. Lower that to something like 1-2 perhaps? |
|
|
|
|
If there is one exchange I really trust it is this one--they handeled the most recent break-in extremely well, the fact that they store most assets in an offline account is great, and the fact that they absorbed the losses is very comforting.
|
|
|
|
|
Did you send a transaction fee with it?
|
|
|
|
When withdrawing from your website, it says "payment sent".
However, block explorer still doesn't show any incoming tx to this address (not even 0 confirms).
Transfers are usually near-immediate in Bitcoin, so I believe payment hasn't actually been sent yet.
Why is that?
If withdrawls take more time, you should state this clearly, and not just write "payment sent".
You should state how much time it takes for the payment to be actually sent.
Pass-through Deposits can take up to 24 hours to be sent as it requires Hash to contact Pirate for withdrawal. Wait ... is it only Pass-through deposits, or all deposits? I certainly did not invest in any pass-through. All deposits take some time to withdraw, although in my experience PPT take longer. Deposits that don't include PPT still take a bit of time because hashking does the payout manually (I think). |
|
|
|
|
Take a look at some of the great depositing opportunities from 1% to 6.9% weekly.
|
|
|
|
To clarify a bit about what the interface might look like here's what I was thinking:  <Added to OP> |
|
|
|
Hey Hashking, what would would you think about a service like I describe here: https://bitcointalk.org/index.php?topic=96732.0. Basically a service that is a passthrough to your (and many other's) deposit opportunities in one integrated system? Would you be open to having your service available in something like it? Thanks for your time  I will read about it and get back to you. Thanks. Thank you. I plan to have a demo (with fake coins and no actual deposits) out soon if you would like to see a proof of concept. |
|
|
|
Hi Vorksholk, Though I think this idea of you being a pass through for several lenders, I'm afraid I will not be very interested in these kind of operations. One of the main reasons for me running this deposit is because it let me keeps direct contact with my investors. The human interactions strengthen the web of trust that I want to build around the bitcoin community so this is why I prefer dealing with people in a peer-to-peer fashion. Anyway, thank you for thinking about offering my service. I wish you all the best, good luck with your initiative. Thanks for the input. |
|
|
|
From https://btc-e.com/news/81: At 04:07 MSK (GMT+4) our LR API Secret Key was compromised. It's 16 uppercase, lowercase letters and digits. They may have bruteforced it for long. Really? That would make it the longest known brute forced key I've heard of. caveat: I haven't studied the actual implementation in LR, maybe there are shortcuts. I would've just assumed to end up in the right ballpark with an estimation along these lines: GPU brute forcing speed - let's go with 3Mhash/s (SHA-1) based on http://golubev.com/gpuest.htmTime-to-find 16 char l/U/# at 3Mhash/s estimation using http://lastbit.com/pswcalc.aspResult: 510892508003511 years (Feel free to halve for each added GPU and a final halving for 50% time instead of 100% - assume a lucky hacker) Any idea how LibertyReserve stores passwords? |
|
|
|
Apparently btc-e will have most everything sorted out in 1-2 days, all transactions during the period of hacking have been reversed, only ~4500BTC were stolen (still a lot, but most of their BTC was in offline cold storage). So you will likely still be able to use their service. |
|
|
|
While anyone with a bit of logic could figure out what you mean by biweekly and bimonthly in your OP, just to avoid people trying squirrely things (saying they thought it meant something different) you may want to clear that up. You see, biweekly is a vague term, many take it to mean twice a week, many to mean every two weeks. From Merriam-Webster: biweekly
1: occurring twice a week
2: occurring every two weeks
|
|
|
|
I know I've been posting this a lot, but I want everyone to see this: from https://btc-e.com/news/81: Dear users of the Exchange Btc-e.com The exchange is not going to close. We will refund all losses from our reserves. Neither the servers nor the database were compromised. There were no SQL injections. At 04:07 MSK (GMT+4) our LR API Secret Key was compromised. It's 16 uppercase, lowercase letters and digits. They may have bruteforced it for long. Using the key the hacker imitated LR deposits from many accounts and bought up Bitcoins, Namecoins and Litecoins. We lost our daily volume, approx. 4500 BTC. The attacker couldn't withdraw more as most BTC were distributed over several offline wallets. At 10:30 we restored the database to the state it was at 04:00, right before the attack. All trades after 4:00 are reverted. People who attempted withdrawals before 04:00 MSK will get their funds withdrawn later today. For people who deposited BTC, LTC and NMC after 04:00 MSK the funds will be put to their balances before market opens. We are working on the scripts for this. If you deposited USD after 04:00 MSK you should send us your login, amount and payment system used by email or PM. Our plan: 1. The trade will be disabled until we restore the balances to the point before market crash. 2. After that, the trade and deposit/withdrawal will be back on, approx. within 1-2 days. Icq - 610112128 Skype - btc-e.support E-mail - support@btc-e.com |
|
|
|
from https://btc-e.com/news/81: Dear users of the Exchange Btc-e.com The exchange is not going to close. We will refund all losses from our reserves. Neither the servers nor the database were compromised. There were no SQL injections. At 04:07 MSK (GMT+4) our LR API Secret Key was compromised. It's 16 uppercase, lowercase letters and digits. They may have bruteforced it for long. Using the key the hacker imitated LR deposits from many accounts and bought up Bitcoins, Namecoins and Litecoins. We lost our daily volume, approx. 4500 BTC. The attacker couldn't withdraw more as most BTC were distributed over several offline wallets. At 10:30 we restored the database to the state it was at 04:00, right before the attack. All trades after 4:00 are reverted. People who attempted withdrawals before 04:00 MSK will get their funds withdrawn later today. For people who deposited BTC, LTC and NMC after 04:00 MSK the funds will be put to their balances before market opens. We are working on the scripts for this. If you deposited USD after 04:00 MSK you should send us your login, amount and payment system used by email or PM. Our plan: 1. The trade will be disabled until we restore the balances to the point before market crash. 2. After that, the trade and deposit/withdrawal will be back on, approx. within 1-2 days. Icq - 610112128 Skype - btc-e.support E-mail - support@btc-e.com |
|
|
|
From https://btc-e.com/news/81: Dear users of the Exchange Btc-e.com The exchange is not going to close. We will refund all losses from our reserves. Neither the servers nor the database were compromised. There were no SQL injections. At 04:07 MSK (GMT+4) our LR API Secret Key was compromised. It's 16 uppercase, lowercase letters and digits. They may have bruteforced it for long. Using the key the hacker imitated LR deposits from many accounts and bought up Bitcoins, Namecoins and Litecoins. We lost our daily volume, approx. 4500 BTC. The attacker couldn't withdraw more as most BTC were distributed over several offline wallets. At 10:30 we restored the database to the state it was at 04:00, right before the attack. All trades after 4:00 are reverted. People who attempted withdrawals before 04:00 MSK will get their funds withdrawn later today. For people who deposited BTC, LTC and NMC after 04:00 MSK the funds will be put to their balances before market opens. We are working on the scripts for this. If you deposited USD after 04:00 MSK you should send us your login, amount and payment system used by email or PM. Our plan: 1. The trade will be disabled until we restore the balances to the point before market crash. 2. After that, the trade and deposit/withdrawal will be back on, approx. within 1-2 days. Icq - 610112128 Skype - btc-e.support E-mail - support@btc-e.com |
|
|
|
from https://btc-e.com/news/81: Dear users of the Exchange Btc-e.com The exchange is not going to close. We will refund all losses from our reserves. Neither the servers nor the database were compromised. There were no SQL injections. At 04:07 MSK (GMT+4) our LR API Secret Key was compromised. It's 16 uppercase, lowercase letters and digits. They may have bruteforced it for long. Using the key the hacker imitated LR deposits from many accounts and bought up Bitcoins, Namecoins and Litecoins. We lost our daily volume, approx. 4500 BTC. The attacker couldn't withdraw more as most BTC were distributed over several offline wallets. At 10:30 we restored the database to the state it was at 04:00, right before the attack. All trades after 4:00 are reverted. People who attempted withdrawals before 04:00 MSK will get their funds withdrawn later today. For people who deposited BTC, LTC and NMC after 04:00 MSK the funds will be put to their balances before market opens. We are working on the scripts for this. If you deposited USD after 04:00 MSK you should send us your login, amount and payment system used by email or PM. Our plan: 1. The trade will be disabled until we restore the balances to the point before market crash. 2. After that, the trade and deposit/withdrawal will be back on, approx. within 1-2 days. Icq - 610112128 Skype - btc-e.support E-mail - support@btc-e.com |
|
|
|
Here's the current news: Dear users of the Exchange Btc-e.com The exchange is not going to close. We will refund all losses from our reserves. Neither the servers nor the database were compromised. There were no SQL injections. At 04:07 MSK (GMT+4) our LR API Secret Key was compromised. It's 16 uppercase, lowercase letters and digits. They may have bruteforced it for long. Using the key the hacker imitated LR deposits from many accounts and bought up Bitcoins, Namecoins and Litecoins. We lost our daily volume, approx. 4500 BTC. The attacker couldn't withdraw more as most BTC were distributed over several offline wallets. At 10:30 we restored the database to the state it was at 04:00, right before the attack. All trades after 4:00 are reverted. People who attempted withdrawals before 04:00 MSK will get their funds withdrawn later today. For people who deposited BTC, LTC and NMC after 04:00 MSK the funds will be put to their balances before market opens. We are working on the scripts for this. If you deposited USD after 04:00 MSK you should send us your login, amount and payment system used by email or PM. Our plan: 1. The trade will be disabled until we restore the balances to the point before market crash. 2. After that, the trade and deposit/withdrawal will be back on, approx. within 1-2 days. Icq - 610112128 Skype - btc-e.support E-mail - support@btc-e.com |
|
|
|
Just PM'd about a 5BTC, 1 week deposit.
ur playin' great today kiddo I'm a bit confused... I'm testing the market for several deposit takers with relatively small amounts. What are you talking about? |
|
|
|
This is a terrible idea in its present form.
Your plan is: I send the BTC to you, then I use a custom software program to instruct you whom to send it to, so I do all of the work of deciding where to invest but none of the benefit of directly working with the programs, so if your software is buggy or if you disappear (intentionally or not), I'm out of luck. Plus you know all of my deposit and withdrawal addresses and can track me in the blockchain. You realize the same benefits (having a software app to track your investment) can be done WITHOUT going through yet another middleman. Sorry, the point of bitcoin is to cut out middlemen, not to create more.
Make the program manage all the different "deposits," store all data locally on the hard drive, with no server whatsoever, and fully release source and it might be useful. It would be OK if the program encrypts all the addresses and stores them remotely for backups- as long as you have 0 access to the addresses and balances.
If you want to provide "convenience" of transferring between different people, sorry, we have bitcoin for that. As a hypothetical example, I could contact imsaguy today with a PGP signed message saying "transfer 50 BTC to znort" and provide my deposit address to znort if I didn't mind both guys knew about the tx. If you are offering something that competes with that, it's gotta be easy to use and more secure than existing bitcoin clients. Reducing security by making another server that can be broken into isn't the way to go.
I understand where you are coming from. The idea is that it makes depositing easier for small investors in a multitude of ways: 1.) They can change withdrawal address mid-deposit as I am essentially proxying the request 2.) They can get in on investments that require a larger minimum then they want/are able to put in 3.) They can easily compare deposit amounts between services and move Bitcoins around as they want I wouldn't have access to the private keys or anything like that of people's personal withdrawal addresses. It would basically work like this: Someone deposits 10BTC to a 6.75% PPT through me: I invest that 10BTC, and they "set it and forget it" to, after a month, change over to a hashking 1.9%, 8-week lock-in. After ~3 months, I send back the final amount earned (minus a small cut possibly, depending on how this goes) to the withdrawal address I have on file for them. The convenience is a all-in-one place to see all possible deposits and compare them, to be able to set plans for paths of investments months in advance, and to be able to change withdrawal address mid-way through deposits, which may be a really nice thing for new users to deposits or Bitcoin in general. Again, not for the large or medium investor. |
|
|
|
|
Just PM'd about a 5BTC, 1 week deposit.
|
|
|
|
|
Show Posts
