 Show Posts
|
|
Pages: « 1 2 3 [4] 5 »
|
Use your zTex to mine blakecoin!
Thanks for the advice...Nice to be able to solo mine again! - Lyddite |
|
|
|
I don't know why people have trouble the username only requires a length of 6-16 chars with at least 1 capital and the password is 6-16 characters at least 1 capital and one number) I don't think that's too unreasonable...  I'f I am wrong people please tell me and I will make the changes Has it been tested with different browers? |
|
|
|
|
Will there be an API for trades, bids and asks?
|
|
|
|
|
"category" : "receive",
"amount" : 0.25000000,
"confirmations" : 47,
"blockhash" : "9058373379660f9625b74734ed4209a0ff56959e2ff9afff66edaafc27e11f1c",
"blockindex" : 6,
"txid" : "9469942cd0438d4883718e3a53a6e342c63ab1bcb3d320659f235c370ba821a5",
"time" : 1386632845
Thank you very much!
- Lyddite
|
|
|
|
|
PGvvAWpuMp2DbxK9W8uj9nb3TGTFt4vgzu
Thank you.
|
|
|
|
shutdown every few days without notice
This started happening after hp-8.
Don't know if this is related but I have a win7 laptop that shuts down at night once in a while with the ypool miner. From the system event log it appears that the laptop just weny to sleep. In power management I had set it so that it should never sleep. It's strange. Keep an eye on your cpu core temps. Your fan may need a cleaning. Makes sense. My laptop went to sleep during the hot summer days. Siesta time perhaps?  |
|
|
|
Hey folks, I was given a unit in a trade, Ztex 1.15y. Can someone help me set up the board with cgminer? I've done the google searching and forum searching and I've come up short on a noob guide. Thanks in advance.
I'd try getting it running with the java client first. Check which firmware is running on it and then update if necessary. http://www.ztex.de/btcminer/(Note that the command lines in the examples might point to a difference version of the software than what you may have.) |
|
|
|
|
I managed to get this running on a DE0-Nano without modifications.
How did you determine the hash rate?
|
|
|
|
Maybe our users are not aware of what products/services are available through Coin Payments, looks like pr0d1gy decided to delist XPM and PPC from Coin Payments for now. https://bitcointalk.org/index.php?topic=285619.0I feel having support of the first multi-currency payment processor is important, not just for our sake, but also for a healthy competitive currency market in general. So please let Coin Payments know that our community is really active and interested in using their service, so hopefully they can reconsider this unfortunate decision to desupport two of the most innovative currencies both in the top ten market cap ranking. You can leave your feedback in the above thread or PM pr0d1gy. Now there is a vote on which currency to add back. https://bitcointalk.org/index.php?topic=285619.0 |
|
|
|
FYI primecoin.org home page now has a link to the hp client download. Hope the miner icon I add is likeable  I think this helps new users to find it easier. Once again let's give Mikael a big round of applause for his hard work, dedication and selfless contribution! I like it! Any reason to not only use the hp client? Even if not mining? |
|
|
|
Incidentally the cc2.8xlarge is not the most cost effective for xpm as the L1 cache appears to be a bottleneck. To prove it, try running just 16 threads instead of all 32 and you'll see little difference!! Or at least that was true for hp9. You can get more bang for buck with 8 cores.
The slowdown is caused by Hyperthreading. The cc2.8xlarge instances have 32 logical cores, 16 physical cores. |
|
|
|
I'm very sorry to hear about this. I guess the time span and amount of instances you have been running, you probably have not kept any or may disk images or logfiles. It would be interesting to find out how your wallet or hosts have been compromised. My guesses would be via a disk image or via ssh and weak credentials. Some suggestions to miners about what can you do with ssh to improve security. - Open up ssh only to what is necessary. 0.0.0.0 is alot of addresses, not to mention IPv6 addresses. If you are using ec2, you can update the firewall from the web interface when your IP when you need to log in from elsewhere. If you are on DHCP (your ip address changes), you can use a subnet (eg, x.x.x.x/24) which will still greatly reduce your exposure to attack
- use ssh keys, not passwords
- keep your ssh private key secure (keep it only on the machines you need use to connect to instances, a backup on USB )
- you can encrypt your key with a passphrase, look into this and also ssh-agent
- If you must use windows, use anti virus software, scan regularly, keep it up to date. MacOS and Linux are not immune either
- If you muse use a password, use a strong one. http://en.wikipedia.org/wiki/Strong_password
- Check the documentation for sshd, and edit your ssh_config file, especially these options
- AllowUsers - use this option in sshd_config to whitelist the usernames you need to access your system
- PermitRootLogin - set this to no or without-password, use sudo to become root if you need to
- Don't run a sshd on the machine you use to connect to your instances if you don't need to. If you must, then secure that too.
ssh ports are being probed for weak passwords all the time. If you run sshd without a firewall, just look at the logs. By running the primecoind daemon (or any coin for that matter) you publicize your IP number to others (and the fact that you probably have a wallet that might even cointain some coins in it) Regarding wallets, I won't go into protecting your wallet or the best way to move your funds around but leaving copies of wallets lying around is not a good idea. Ideally a provider zeroes the disk when a customer stops using it but it may not always be the case, deleting a physical disk takes time. When you are done using a machine and no longer need it's wallet file should can delete your wallet or even better, "wipe" (apt-get install wipe, wipe FILENAME) or write zeroes over it (dd if=/dev/zero of=PATHTOYOURWALLET bs=1024 count=100). WIth SSDs, you can't be sure that everything is ever deleted, but if the file is wiped or zeroed, you can be fairly sure that the file cannot be recovered without special tools and physical access to the disk, or without administrative access to the disk system in a larger provider. When you "rm" a file, usually, it is just the directory entry and list of block a file is using that is deleted. If not wiped or written over, it is possible for a file to be reconstructed. Treat your wallet backups as you would treat your wallet, if someone finds your backup, it's almost as good as your wallet.dat Ideally the ssh settings and user accounts are set on your first miner which you then clone. Wiping the wallet could be made part of the shutdown script, make your you have a safe backup. |
|
|
|
Difficulty increase as clearly been slowing down for the past 48h clearly showing that the number of blocks found is lowering (as most of us miners sadly experienced). Only = +0.01888007 which is ridiculous compared to what we were used to see that was around +0.07 a day if not more. The lowering started around 08/08. Lyddite will surelly have a nice graph for us  This is resulting in a huge increase in price which is great for us miners having to cope with lower and lower blocks each days especially since the last 48h. I was about to close my little farm, might keep it up a little more... My luck has turned for the worse also but 1-2 blocks per day is ok. This will be a kind of pain point for Primecoin I think. The increased price on the exchanges probably will keep miners motivated despite the diminishing returns. Many more miners will be necessary to push the difficulty up to 10. From what I have mined over while the difficulty has been > 9, about 10% are 10-chains, the rest all all 9 chains. The high performance primecoin miner has had many fixes and optimizations over the past while and I believe that there if probably little left in terms of low hanging fruit there. Now that the "fractional difficulty" for 9-chains is high enough, tweaking roundsievepercentage, sievepercentage and sievesize for the best efficiency is where one should focus if one continues to mine intensively. For those who are new to linux and the bash shell and are curious to find out what kind of primes have been have generated by their miners, here's the oneliner to I used. primecoind listtransactions "" 100 |grep blockhash | sed -e "s/.* : //" -e "s/,//" |xargs -n 1 -I '{}' primecoind getblock '{}' |grep primechainAppend to the above line to count your 9-chains and to count your 10-chains. The "[CN]" in the grep keeps 09 or 0a in the latter hexadecimal part of the data from being counted. If you have more than 100 transactions in your account then increase the 100 to something greater than the amount of transactions for that account. |
|
|
|
If you can, please run a public (open port accessible from the outside) of Primecoin.
I think that will all the solo mining, there are a lot of nodes, but not enough public nodes.
I have around 1000 connections total for only running 4 public nodes, it's pretty crazy.
Ouch, maybe should restart the daemon every once in a while. I haven't tried to limit anything and this is what I have. "connections" : 40, "connections" : 16, "connections" : 37, "connections" : 20, "connections" : 55, |
|
|
|
In case you are interested in the validity of the chains per day metric, with the following setup running on 9 identical machines I managed 8 chains over 24 hours.
8/9=0.8888 chains per day.
I would say, close enough for government work in this case.
Lucky you then. I have 8 machines running at ~1.0 chains/day + a few spare machines on the side. I got 3 blocks in the last 24 hours.  Hmmm...hopefully 13 blocks tomorrow... Here's a useful oneliner if you want to see exactlya sorted list of when your blocks were found and if you are not comfortable with reading times and dates as seconds since 1970... UTC. primecoind listtransactions | grep blocktime | sed -e "s/.* : //" -e "s/,//" | sort | xargs -n 1 -I '{}' date --date=@'{}' |
|
|
|
Its a bit embarassing (like my electronics-fu is now totally blown), but seeing as the chip on the left just found a block (and at a ridiculous 1 billion difficulty), its just so much of an unlikely event that I just had to share. BTW that's an EP4CE10E22C8N mining at 12 MHash/sec !!
Cool, I have a 3 DE0-Nanos and was running them at 6.67 MHash a sec, powered by USB. I thought it would be cool to try to build something with the largest non-bga FPGAs from Altera but I guess it would be far from profitable at this point. |
|
|
|
In case you are interested in the validity of the chains per day metric, with the following setup running on 9 identical machines I managed 8 chains over 24 hours. 8/9=0.8888 chains per day. I would say, close enough for government work in this case. "blocks" : 105938,
"chainspermin" : 3,
"chainsperday" : 0.92945471,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 9.59519291,
"errors" : "",
"generate" : true,
"genproclimit" : -1,
"roundsievepercentage" : 70,
"primespersec" : 1707,
"pooledtx" : 0,
"sievepercentage" : 10,
"sievesize" : 1100000,
"testnet" : false |
|
|
|
logarithmic scale on the difficulty chart might be interesting
Not really, just makes everything look more flat. |
|
|
|
I have also been working on some charting for Primecoin. It's pretty crude so far but a detailed zoomable graph on the difficulty can be found here: http://192.241.170.170/The bar at the bottom lets you adjust the data the graph displays. It takes a few seconds to load as it downloads all the diff data up to a few hours ago. I'll fix it so that it only loads enough data for the current zoom and updates the data in real time later. Let me know what you think. Nice, quick enough. Is all the work done on the client? Data for block 0 is missing but I guess it is not too interesting. |
|
|
|
|
