Bitcoin Forum
January 20, 2018, 01:18:13 PM *
News: Latest stable version of Bitcoin Core: 0.15.1  [Torrent].
  Home Help Search Donate Login Register  
  Show Posts
Pages: [1] 2 3 4 5 »
1  Alternate cryptocurrencies / Announcements (Altcoins) / [CURE] Illustrated Protein Folding EC2 Setup Guide: 300k PPD per Server! on: May 11, 2014, 06:23:08 AM
Hello! While folding on GPU hardware is a great way to earn Folding@Home points for protein research, if you do not have GPUs, or want to do a lot of folding, EC2 can be an alternate option to rack up those folding points.

For this tutorial, you need an amazon EC2 account, and a computer. This tutorial is done at a keyboard of a Windows computer. Linux and Mac OS X are extremely similar. This will be using the Oregon region. You can select other regions to test pricing. Each region requires the creation of a different private key.

Step 1:  
Log in to your EC2 account. Click on "Request Spot Instance".

Step 2:
Click "Select" for Ubuntu Server 14.04 LTS (PV). HVM will also work, but will perform about 1%-2% slower.

Step 3:
Choose the c3.8xlarge instance type (108 ECUs).

Step 4:
Enter the maximum per-hour price you are willing to pay. Make sure it is at least 25% greater than the above-shown "Current Price" options.

Step 5:
Click the "Launch" button.

Step 6:
Select "Create a new key pair" from the dropdown menu, then name your keypair, and click the "Download Key Pair" button. NOTE: if you have already set up one instance before, you can skip down to step 25, and just double-click on the saved instance.

Step 7:
After downloading the private key (.pem) file, click on "Request Spot Instance".

Step 8:
Make sure that EC2 has successfully created your Spot Instance request (A green check-mark in a green confirmation box will appear, as shown). Then click on "View Spot Requests".

Step 9:
Click on the "Instances" option, as shown below. At first, nothing will show up. Leave this window as is for now.

Step 10:
Download PuTTYGen from, then open it up. Click on the "Load" button.

Step 11:
Change the file selector to "All Files (*.*)" to allow you to choose the .pem file you downloaded from Amazon. Then browse for and select the keyfile, and open it up.

Step 12:
You will get a message about the successful import. Click "Ok" to continue.

Step 13:
Inside of PuTTYGen, make sure the SSH-2 RSA radiobutton is selected (this is the default), and click on "Save Private Key".

Step 14:
You will get a warning prompt about saving the private key without a password. This is fine, click "Yes".

Step 15:
You will get a "Save As" prompt. Choose a place to save the keyfile, and name it something simple.

Step 16:
Download PuTTY from and open it up. Then, click on the "Data" option under "Connection" on the left options pane.

Step 17:
On the "Auto-login username" box, enter "ubuntu".

Step 18:
Click on the + sign next to "SSH" under "Connection" in the left options pane.

Step 19:
Click on the word "Auth" (not the plus) under "SSH" under "Connection" in the left options pane.

Step 20:
Click on the "Browse..." button next to the box for "Private key file for authentication".

Step 21:
An "open file" dialog prompt will appear. Browse to and select the new keyfile (.ppk) that we generated with PuTTYGen. Click on the "Open" button.

Step 22:
Click on the text at the top labeled "Session" in the left options pane.

Step 23:
Type a name in the "Saved Sessions" box. Then, click the "Save" button.

Step 24:
Go back to the EC2 "Instances" page. You may need to click on the refresh button (either in the browser or on the page) in order to see your server. Note the IP.

Step 25:
Enter this IP address into PuTTY, under the "Host Name (or IP address)" box.

Step 26:
A new window will pop up. You may be asked about trusting a fingerprint, accept. Type into the window:
sudo -i

Step 27:
Now, type:
apt-get update

Step 28:
Now, type:
apt-get install htop

Step 29:
Now, type:
mkdir /etc/fahclient

Step 30:
Now, type:
wget -O /etc/fahclient/config.xml


Step 31:
Now, type:
nano /etc/fahclient/config.xml

Step 32:
Now, use the arrow keys to move through the file. Enter your passkey and username as shown below.

Step 33:
Now, type:

Step 34:
Now, type:
sudo dpkg -i --force-depends fahclient_7.4.4_amd64.deb

Step 35:
Press the "Enter" key on your keyboard to accept <Yes> for whether FAHClient should be automatically started.

Step 36:
Wait 30 seconds.
Now, type:
nano /var/lib/fahclient/log.txt

Step 37:
Press Control + v four times to scroll down the log. Get to where it shows your Project. If it is 8101, 8102, 8103, 8104, or 8105, you successfully got a BigAdv WU. Alternately, check that is says 0xa5 to the left of the colon. Press Control + X when you are done.

You are done setting up! However, to keep your folding@home account in good standing, always finish your WUs. If you want to shut down your EC2 server, type:
nc 36330

You can look in the log again, and scroll all of the way to the bottom to see the current percentage:
nano /var/lib/fahclient/log.txt

Again, use Control + X to exit.

On average, each percentage point takes 14 minutes. It takes less for faster projects such as 8104 (averaging around 12 minutes), and longer for slower projects like 8101 (17 minutes).
You can type:
To see your current processor usage. When finished, all of the 32 cores will drop from full 100% utilization to near-zero. When you see this, it is safe to terminate your EC2 instance from the EC2 panel without losing any folding@home work.
2  Alternate cryptocurrencies / Announcements (Altcoins) / [ANN] Curecoin Release: Now! on: May 10, 2014, 07:39:15 PM
Check out Cygnusxi's thread!
3  Alternate cryptocurrencies / Altcoin Discussion / CureCoin Progress Update--Launch Approaching! on: January 26, 2014, 02:05:39 AM
Hey everyone! CureCoin's moving along and we are expecting to launch within the coming two or three weeks!

Edit: A bit of clarification, CureCoin's goal is to reward miners for directing their OpenCL- and CUDA-capable (AMD and NVidia) as well as CPU computing power towards protein folding (Folding@Home) to help cure cancer. The coin will be rewarded out to folders on a proportional Points-Per-Day basis.

Unfortunately cygnusxi had an IRL mini-crisis unrelated to the project so he wasn't able to write this update which he was planning to release today, but here's a summary of our current progress:
>No longer using any 3rd-party stats for anything
>F@H Pool redundancy (if main payout pool goes down, secondary one will continue payouts as scheduled)
>Lightweight F@H client (optional) is easy to use, and can quickly halt/pause/resume folding, also estimates PPD
>Foundation moving along nicely
>Future plans for safe holding of Folding Payout coins by F@H staff
>Reduced Dev Fund premine to align with community's beliefs
>Higher percentage of coins paid out to folders than miners, though mining will still be worthwhile

We should be able to launch a stable, tested client in the next two or three weeks! At launch time we will have Windows binaries, full source code available, folding pool, backup folding payout system, 8 addnodes on servers with 100Mbps or 1Gbps connections separated geographically, at least one mining pool (likely two or three), and a block explorer. Additionally, a standalone, simplified client will be available for download which makes starting/stopping/setting up folding much easier.

From there, we can focus on helping people get folding set up, getting the coin onto exchanges, and working with Stanford to further integrate into their system.

All donations which were 1 BTC for 10,000 CUR are still valid and will be paid out approximately one week after the launch of the coin. If, for whatever reason, you want to withdraw your donation, please let me know, as there are others interested in buying your slot, and we can facilitate donation-credit transfers.

$5000 of donation money has been donated to help F@H with server infrastructure.

Let me know if you have any questions! Thanks for your support! Smiley
4  Alternate cryptocurrencies / Altcoin Discussion / [WTB] Assassin's Creed IV: 3.5 ProtoShares on: December 04, 2013, 02:06:55 AM
Hello! Wanting to buy Assassin's Creed IV on Steam for 3.5 ProtoShares, if you have a counteroffer, list it below. Smiley
5  Alternate cryptocurrencies / Altcoin Discussion / [PTS] Mining ProtoShares on Amazon EC2: Cheaper Than DigitalOcean! on: November 18, 2013, 06:08:25 PM
So, if you want to mine ProtoShares with cloud servers, you might want to take a look at amazon EC2.

 Each instance costs ~$0.28/hr for a cc2.8xlarge at spot prices. Each spot instance of a cc2.8xlarge gives you 480 Collisions Per Minute when using the optimized 1024M jhProtoMiner ProtoShare Miner for

tar zxvf jhprotominer-yvg1900-M7c-linux64-core2.tgz
cd jhprotominer-yvg1900-M7c-linux64-core2
cd linux64-core2-1024M
./jhprotominer -O -u username.worker -p password -t 32

The above code will quickly get you running on EC2's 32-core systems. The 32-core systems are available at a good price in N. Carolina and Oregon, and you need to use HVM-compatible linux OSes (I used Ubuntu 13.10) for your server OS.

Currently, I'm paying $11.20/hour for almost 20,000 CPM. Not bad.
6  Alternate cryptocurrencies / Altcoin Discussion / True ASIC-proof Attack-Resistant CryptoCurrency Design on: November 01, 2013, 01:07:26 AM
Some people in another thread thought this was an interesting idea, so I'm gonna expand on it a bit. Before I lose you when you see the wall of text, the basic idea is that the algorithm(s) hard-coded into cryptocurrences are hard-coded into the ASIC chips. If this algorithm dynamically changed in a non-predictable fashion, ASICs would be MUCH harder if not impossible to design, and would certainly, if designed, be orders of magnitude less efficient than their static counterparts.

CryptoCurrency mining is essential. It's how the network continues. It creates blocks, which, to simplify, hold chunks of transactions, inputs and outputs that move money around. A currency is useless if you can't spend it. You can't spend current cryptos without putting the transaction into a block. You can't put the transaction inside a block if no one is making blocks. The trouble comes when people's ability to create blocks is abused. This can be done by a multitude of people in a variety of ways for many different reasons. Someone doesn't like a competing currency? A business that deals with monetary transactions doesn't like the system as they can't control it? A corrupt government wants to destroy free currency? They could execute a 51% attack, and rewrite the attacked parts of the chain. It's important to note that, given enough computational power, a knowledgeable person could rewrite the  blockchain back to the latest client-hard-coded and network-accepted block. They would release new blocks at a higher difficulty than the original chain, and would 'fork' or replace blocks on the chain.

51% attacks involve a ton of computational power, and a ridiculous amount of electricity. However, for a large vested interest, they're certainly not out of the question, no matter the coin. If a large institution really wanted to take down Litecoin, for example, they could develop a high-memory ASIC chip made for Scrypt(1024,1,1) calculations. And they could mine faster than the current network is mining. Sure, it would be expensive. But they also have a lot of money.

Another problem is the ASIC mining scene. Mining was developed to be free, distributed, open to anyone. However, due to the advent of ASIC devices, mining has been consolidated. It has become a rich-get-richer game. People have lost fortunes investing in ASICs with no clear delivery dates or ROI. While this is a part of free market, many see it as undesirable, myself included. I personally have invested significant money into ASICs, and for the most part, I'm happy with my investment. This isn't some deep-seated hatred towards ASIC companies, but rather a general analysis of the negative effects ASICs have had on the blockchain. Unlike consumer-oriented hardware (such as CPUs and GPUs), ASICs are not widely-available to consumers, they aren't carefully monitored for safety, and they don't have large, reliable companies behind them. It's rare that someone runs a scam around making their own GPU chips and selling them, haven't seen it yet. However, it's important to note that many scammers latch onto the idea of making fake ASIC companies to rip consumers off.

However, these above points aren't even the most important focus. They all revolve around the mining. Sure, mining is important, but it isn't the whole coin. Although it's rather unlikely due to the nature of hashing algorithms, what if a way of reversing SHA256 became possible? Let's step back and take a wider look at what hashing algorithms are. To simplify it, imagine I have a function called multiply. It accepts two numbers, and returns the result of multiplying them together. There's nothing special. Even this is, in its simplest form, a hashing algorithm. It loses some sort of data, some sort of understanding. Given this, say I call mult(6, 9). It returns 54. Now, it's trivial to list the possible inputs to mult(something, somethingelse) to give me 54, right? You could have (1,54), (2,27), (3,18), and (6, 9). Sure, 6,9 is in there. However, without any additional context, you can't tell me for sure which one is the original input. You could even say that the above possibilities all result in a collision--where two inputs result in one output.

Now, let's look at an actual example of how this loss of data results in protection. Hashing algorithms rely on circuit logic at some level. If you want some additional details, you can check out At any rate, say we have a XOR function. XOR (Exclusive-OR, which says that true,true = false, true,false = true, false,true=true, and false,false=false. Let's change this to binary:
1010010110101101 XOR:
0110101100101011 =:

Given 1100111010000110, you could tell me all the possibilities for input. There are quite a few of them. As a result, it's hard to reverse. Now, imagine that both of those input lines were the result of other such functions, building a reverse tree feeding system. And the inputs for those came from circuit logic. Quickly, the possible sample area for brute-force reversing the algorithm becomes unthinkably large. However, if you were able to successfully reverse an algorithm like this, you would end up with a list of inputs that collide--give identical output for different inputs.

Understanding the complexity of the algorithm, it's hard to prove for sure that there isn't a method by which to reverse it. If a reversal mechanism was discovered for the algorithm, it would be a big deal. And given billions if not trillions of dollars at stake, if it's possible, it's likely someone will find a way. No matter your faith (or lack thereof) in modern cryptographic one-way hashing functions, creating a currency, it would be nice to build it in such a way that a broken hash function wouldn't be the end of the project/crypto currency.

How to protect against 51% attacks
51% attacks, as explained earlier, rely on the ability to create blocks at a higher difficulty than the network itself can produce. One powerful step forward in preventing 51% attacks and further distributing mining/block production has been the idea of Proof-Of-Stake, where you can mine blocks with hashing power, but a large percentage of blocks are also created by owning large amounts of the currency. As a result, anyone who wanted to 51% attack the coin would have to have a significant portion of stake in the coin, and would therefore be at an economic disadvantage by attacking. However, for large institutions, it may still make financial sense (in a twisted way) to invest millions, or even billions, into a currency, for the ability to destroy it.

Proof of Stake is a strong contender. However, another issue with 51% attacks is a group's ability to obtain ridiculous amounts of computational power. For simplicity, considering a coin that only has proof of work (hashing) and no proof of stake, say the total hash rate is 1TH. Each 7970 can generate 500MH. If someone could create an ASIC, it's not at all unlikely for them to easily be able to obtain 1TH of computational power. Considering only electrical consumption, an ASIC for Bitcoin currently is somewhere around 200-400x more efficient than GPUs for the same hash rate. This enables a long-term attack to only require a large initial investment. In perpetuity, even if a GPU farm of 1TH was somewhat cheaper to make, for a long-term effective 51% attack, power consumption would become a major price. Therefore, we can conclude that ASICs make the network easier to attack.

Many people will tell you that the advent of ASICs make Bitcoin more secure. This is true. This is because Bitcoin is vulnerable to ASICs, the network is protected when ASICs are in the hand of normal people, as it makes an ASIC-based attack harder. However, Bitcoin would be better off not even being able to have ASICs made for it. A smaller financial investment would protect the network with the same power, and a huge attack on Bitcoin would instead require exorbant amounts of consumer hardware rather than being able to pay a large initial investment, and then run the attack for a long time cheap. GPUs use a lot of power. We're talking an increase in orders of magnitude. GPUs cost much more to run over a period of time, making costly attacks even more costly. This exorbant amount of electricity would make a long-term attack infeasible, and would make short-term attacks much more expensive. If interested to the point where the party wanting to take over the network was willing to make their own GPUs to lower cost/unit, they would be consuming a large amount of power to run such a big farm, and the added complexity of creating GPUs or high-performance CPUs, even geared towards a specific purpose, would make the cost per unit much higher for the business.

If an ASIC can be created for a coin, then the coin is the most secure if ASICs have been made for it. This is because, if ASICs are possible but not-yet-public, then a private group would require much less investment to pull off a successful attack. However, if ASICs are out in the wild, the private attack group would require much more ASIC hardware and electricity.

So, we have concluded that, to prevent 51% attacks, a mix of proof-of-stake block minting and an algorithm or algorithms that can't be calculated efficiently by ASICs.

Preventing reversal-attacks
Though unlikely, it would be potentially possible for an algorithm to be reversed, and, given this idea, we have to build a coin with the idea that one or two of the algorithms that we use might end up eventually broken. If a currency uses only one algorithm, then that one algorithm being reversed would essentially spell doom for the currency. Patches could be applied and a new version released, but almost all faith would be lost in the currency, and when stakes are in the billions or trillions of dollars, a network hiccup like this is a HUGE deal, and would likely spell the end of public faith in crypto currencies.

The obvious solution to this is simply using multiple algorithms. However, there are some not-so-evident worries about using multiple hashing algorithms. The major one is entropy. Entropy is a measure of chaos. It's difficult to explain, but consider that we are generating random strings that are 16 characters long, and draw from a sample of 8 possible characters for each position. We would have 8^16 possibilities, so that would be our entropy. Hashing algorithms strive to be one-to-one mappings in a certain sample space of entropy. However, it's important to remember that, due to the data-losing nature of hashing algorithms, collisions are possible. To put this in scale, we have not yet found one single collision for SHA256. Don't let that deceive you, however, the math checks out in that it is most likely vulnerable. As a result, the hashing function is considered to lose entropy, or output less entropy than is put in. To put this in perspective, this then says that, if run enough, trillions upon trillions upon trillions of SHA256 functions would likely result in any input being converted to one single output. Since the entropy loss carries from round to round, if we could find the exact average entropy loss of the function, we could predict how many functions would needed to be calculated on a single input. However, that is neither the point nor the intention of this talk. Instead, I want to present the fact that running the same algorithm a ridiculous amount of times isn't smart. SHA256(SHA256("input")) isn't bad. Entropy loss is minimal and can be ignored. It's not a problem, we don't have to worry about it. However, we would have to worry if, for example, SHA256 was calculated a ridiculous number of times.

New algorithms are touted to have very little entropy reduction, however it's a hard concept to prove. The existence of collisions is not surprising, but finding one is. However, if in making a new coin that used a bunch of nested algorithms (say hashing algorithms a,b,c,d,e,f,g,and h) in such a fashion as a(b(c(d(e(f(g(h(input)))))))) would result in the output having something slightly lower than the lowest-entropy algorithm. So the only weakness of this system is one of the algorithms losing a significant portion of entropy over the sample area of the input.

While not a huge concern, this entropy reduction would have to be accounted for, perhaps even if only to make sure that, in a sample set of significant size (millions or billions) of hashes, collisions don't occur.

So, if we have 8 hashing algorithms, then all 8 would have to be broken to attack the network using reversal. For example, if a was reversible, then an attacker could, theoretically, only have to do b(c(d(e(f(g(h(input))))))). However, if any of the other non-outer-layer hashing algorithms were broken, it wouldn't at all affect the network security in reversing hashes, as it would most likely be faster to compute a hash rather than reverse a potentially-accepted output. Therefore, you would put your weakest algorithm in the center, and your strongest on the outside. Additionally, entropy-permitting, you could nest multiple times, so that a,b,c,d,e,f,g,and h all get run hundreds of times in the hashing process per completed 'hash round'. This idea enables an attack on function a to be orders of magnitude less significant, as a would still be calculated normally in all of the times it was used except for 1. So, nesting multiple algorithms, if done right, only strengthens the currency against algorithm reversal, and any losses in entropy are minimal and insignificant.

Alright, so you do a bunch of functions. Couldn't an ASIC be programmed to do that?
Certainly! We require another change to become ASIC-resistant or even ASIC-proof. Dynamic algorithms. Yes. a,b,c,d,e,f,g, and h have to change in a pre-determined but un-predictable manner. This doesn't mean that the dev changes the code every six months and has other people rewrite miners. This means the network itself reorganizes the hashing functions. In order for this to work, the hashing functions would have to be modular to an extent. And when the network retargets difficulty, it would also retarget the hashing algorithm. It would, based on data from the latest retarget block hash, systematically create a new hashing algorithm by rearranging the modular portions of the hashing algorithms. Say, for example, that algorithm A does a ton of stuff, and then has 32 different modular steps. Each step has a negligible affect on entropy. Based on, say, the last sixteen bits of the retarget block (block right before the retarget) are used to determine the order of the steps. In some way that would be easy-to-calculate for clients, but impossible to predict before the retarget block is mined, the hashing algorithm's steps would be reorganized based on those bits. For example, maybe each bit (a one or a zero) determines which step is used first. If we have 16 1's (so 1111111111111111 was the last 16 bits of the retarget-worthy hash), then we'll do step 7 first, but if we have 15 1's, we'll do step 3 first, etc.). This counting method would be nice as it wouldn't line this first modular piece up with the next way to determine the 2nd step, which, for example, could be based on the number of 1's in the first four and last four bits, etc). If each algorithm had 32 different modular components, some of which could be used multiple times, each algorithm would have a huge number of possible orders. As a result, it would be impossible infeasible to design an ASIC for each possibility. Some steps could be high-memory, so from when the high-memory algorithm is pushed to when it retargets, CPU miners would have an advantage. Other steps would be extremely low-memory, and when those were selected instead, GPUs would have an advantage. However, on average, the algorithms would lie nicely balanced, with some high-memory steps, but not enough to push GPUs out of the game, while still allowing CPUs a bit of room to play catch-up. As a side-note, the order in which algorithms are performed could be changed at the algorithm-level as well as at the hash level, so a could change, and a could be before b, when other times b could be before a, even though both times a is a different-but-similar algorithm consisting of a number of steps.

This dynamic idea would require GPU miners, as I understand it, to recreate a kernel and recompile in order to be efficient. However, if programmed correctly, this could be automatic and only result in minimal downtime during retarget blocks. Retargeting should be done often enough that an ASIC couldn't be produced during the algorithm's lifetime (2 weeks is way more often than necessary at this point in time, but might be a nice number simply because even an ASIC would be a pipe-dream) and would have to be long enough that GPU miners wouldn't be constantly shutting down to recreate kernels, etc.

Finally, it's important to note that such a network of evolving hashing algorithms would require significant thought in the algorithm design.
Some of the steps could be tried-and-true algorithms such as SHA256, blake, keccak, etc. Others could be created specifically to allow modularity by design in steps. The step order would be similar to a salt in function, but different in implementation. In order to create a secure-but-usable dynamic algorithm system, some algorithms could remain constant but buried-deep in the algorithm, and constantly reordered so that an ASIC couldn't be created to do a portion of the hashing function without excessive latency with having an ASIC do part of a hashing algorithm and a GPU or cpu do the other part, which is completely infeasible due to, as mentioned, latency. ASICs are effective because they can check the hashes themselves, they aren't sending billions of hashes back to the computer to check per second. The bandwidth of sending a billion hashes per second (1TH) to the computer for checking would be a minimum of 8TB of data per second. ASICs wouldn't be useful, even if they were able to do a portion of the hashing, especially if that portion was nested inside, and required sending from the ASIC to general-computing devices and back multiple times.

Sorry about the wall of text. It takes a while to explain this idea, and the people most likely to be interested would read this whole thing, I hope. If you have any additional questions, PM me. If you want to create this algorithm, be my guest, I would love to see it implemented. I don't currently have the programming skills required to complete this project, I simply wanted to introduce the idea so that perhaps someone with the particular skill-set required would pick up the lead.
7  Alternate cryptocurrencies / Altcoin Discussion / [WTB] COD:Ghosts Pre-order ($60 version) [BLC] [XPM] on: October 28, 2013, 10:21:45 PM
Hello! COD:Ghosts is coming out soon, and it looks like it'll be at least a bit fun.

If anyone wants to sell it to me (as a Steam preorder gift), I will pay for it with either 115 XPM (currently about $81) or with 410 Blakecoins (which are admittedly fairly hard to mine now, this might be a good investment, but no promises). PM me or post here if you are interested. Smiley
8  Alternate cryptocurrencies / Altcoin Discussion / [Blakecoin] BlakecoinMinerGUI Setup Guide on: October 28, 2013, 01:27:05 AM
Hello! I made a simple GUI wrapper for reaper, which helps to take much of the confusion out of mining.

-AMD GPU Drivers installed (13.9 tested working)
-Java installed

There are currently no Blakecoin pools. Instead, you can set up Blakecoinas a server, so you can solo-mine.
To setup solo mining:
1.) Simply download blakecoin-qt here:
2.) Click on the start button, and enter "%appdata%". If you are on Windows 8, show hidden files (Control Panel > Folder Options > 2nd tab > Show hidden files and folders), then navigate to C:/Users/You/AppData/Roaming
3.) Make a new text file called 'blakecoin.conf'. If notepad is being annoying with always saving as .txt format, when you do 'save as', choose 'All files.'
4.) Enter the following into this file:

5.) (make sure you change username to a username you want to use, password to a password you want to use, and to something else if you intend to have multiple miners mine to this machine. You can use an asterisk * if you want to allow all IPs to access it, however this makes your wallet much less secure.)
6.) Save the configuration file.
7.) Start blakecoin-qt.exe
8.) Wait for blockchain to download
9.) All done!

-->If you need additional help with solomining setup, let me know, or visit, which is a guide for litecoin solo mining, and can be easily adapted.
When pools are created, I will list them here, and they can be used rather than having to bother with the above instructions!

GPU Miner setup:
1.) Download the GPUMiner from here:
2.) Extract the download once it completes
3.) Launch 'BlakecoinMinerGUI.jar'
4.) When prompted for your pool URL, enter '' (without the quotes) for the pool URL IF YOU HAVE YOUR WALLET RUNNING ON YOUR MINER. Otherwise, enter the IP of the computer on your network that is running your blakecoin wallet configured as shown above for solomining.
5.) For the pool port, enter the port that is set as 'rpcport=someport' in your blakecoin.conf. If you followed the above example, this number is 9200.  
6.) For the username, enter the username as set above, same as for the password popup.
7.) Once you are at the main screen, press 'Start' to begin mining!

Explanation of Fields:
Total Hashes: this is the total number of hashes your miner has calculated since the application launched. Not very useful, but a cool statistic to look at!
Hashrate: Your current hashrate, measured in MH/s. For a 7950, somewhere around 2000 MH/s is expected.
Aggression: The aggression reaper is using. The higher it is, the higher hash rate you will get. The lower it is, the more stable and usable your card will be for desktop performance. Default is 28. Click on it to change it to another number. Smiley
Pool: URL and Port (separated by a ":") that you are currently connected to and mining to
Worker: Current worker.

Why the graph?
If the graph looks like on straight line, you're good. If there's small bumps, you're good. If it's a crazy wave pattern, your GPU isn't mining very stable!

Why did the graph and hashrate drop to zero for a few seconds?
Periodically, BlakecoinMinerGUI will restart reaper, in order to get you the best hashrate. This is not a problem, unless it happens more than a few times per hour.

What's the bar to the side?
It's a graphical representation of your current hash rate, on a scale from 0 (bottom) to 6000.

What happens if my hashrate is over 6000MH/s?
Your GUI will look a bit strange. Smiley

Total Downloads: 20
9  Alternate cryptocurrencies / Altcoin Discussion / [Blakecoin Bounties] Get Blakecoin By Making Something! on: October 20, 2013, 05:56:10 PM
Hello! This is a simple, small bounty thread, certainly subject to change. If you qualify for the bounty, PM me. Smiley

If you want to put up your own bounty in this thread, PM me and I'll add it to OP. If I like it, I'll add some BLC to it from me.

300 BLC : Blakecoin Exchange (200 from me, + 100 donated by atavacron)
Additional Requirements for Blakecoin Exchange:
-Must have Blakecoin<->BTC OR Blakecoin<->LTC trading pairs.
-Can either be Blakecoin added to existing exchange or new exchange
-Extra +25 BLC if exchange mentions a few key statistics of Blakecoin (Different algorithm, perhaps current difficulty and block cound)

75 BLC: Blakecoin Mining Calculator
Additional Requirements for Mining Blakecoin Calculator:
-Must be accurate
-Accepts input in GH/s OR MH/s
-Gives output in BLC/day
Bonus +25 for each of the following:
-->Graphs (Network Hashrate, Network Difficulty, Value?) (+25 for any graphs, not +75 for three)
-->Increase %/week difficulty option
-->USD/day OR BTC/day output additionally (requires an exchange to exist)

550 BLC: Blakecoin Mining Pool
Additional Requirements for Blakecoin Pool:
-P2Pool, pushpool, stratum, or custom software
-Block count, network hashrate estimate, charts?
-Pool source code opensource for others to use (Important)
-Works with reaper
Bonus +35 BLC for each of the following:
-->Variable worker difficulty
-->More advanced network statistics page
-->Built-in blakecoin mining calculator (If first calculator, see above)

150 BLC: Blakecoin Block Explorer
Additional Requirements for Blakecoin BE:
-Search function for addresses (block search would be nice too)
Bonus: +25 Blakecoin for each of the following:
-->Live-updating feed (like has)

These are subject to change with BLC value and with BLC developments. If you want to contribute to an above bounty, PM me.
10  Alternate cryptocurrencies / Altcoin Discussion / [Gauging Interest] 0.06BTC/month for Cloud Alt Wallets on: October 10, 2013, 05:41:47 AM
Hi! Would anyone be interested in a service where you can pay 0.06BTC/month and get a remote-managed (probably through a custom program) wallet of any linux-supporting coin wallets?

At any time you could choose to switch it to another wallet, and it would be compiled and would begin syncing. You would have full API access to it, so you could use it for mining, signing transactions, etc.
11  Alternate cryptocurrencies / Altcoin Discussion / [WTS] AMD Game Codes--75 Blakecoins! on: October 09, 2013, 11:43:03 PM
Each code is redeemable for Bioshock Infinite, Crysis 3, and Farcry 3: BloodDragon games. They came with AMD video cards, and I have too many.

Each one is 75 Blakecoins. I will give you the code straight off the back of the card.

Mind as well start the ball rolling with Blakecoins having some intrinsic value Smiley
12  Alternate cryptocurrencies / Altcoin Discussion / [WTS] 256 BlakeCoins for 2 BTC on: October 08, 2013, 12:24:02 PM
No idea if this is anything near the true valuation (in either direction) but the offer is here for anyone who wants to acquire a fair amount of blakecoin right now. PM me if you are interested. Offer subject to change as an actual fair market value is established.

Edit: changed price, firesale? xD

Changed price. 2BTC for 256 BlakeCoins. Smiley
13  Economy / Computer hardware / [WTB] BFL 60GH Single: 7.5BTC + Shipping USA on: September 29, 2013, 08:48:07 PM
If you want to liquidate your BFL 60GH miner, I offer you 7.5BTC today cash, with the assumption that you ship tomorrow. I will also pay you an additional fee for the slowest UPS shipping, no insurance on the box. Happy to use escrow, or you could ship the unit first. If you are a trustworthy community member, I would be happy to send first.

You could probably get a higher price if you wanted, but this is my offer, available right now. Smiley In fact, you could probably get 10+BTC on the forums if you make your own topic. But my offer stands.
14  Alternate cryptocurrencies / Altcoin Discussion / [ANN] ReaperReader--Capture Reaper Output To A File! Filter Out Junk. on: September 08, 2013, 12:23:59 AM
Hello! Many people around have had trouble getting reaper to work correctly (especially the primecoin-based fork) and are getting errors. As well, others want to log their reaper output so they can analyze it, or want to filter out messages that spam the console ("GPU stuff"). To that effect, I made a quick-and-dirty little program which runs in java and works on the Windows version of reaper to allow you to filter reaper output, and capture logs of the reaper output. Additionally, it also allows you to quickly combine your reaper.conf and primecoin.conf files into your output log.

Published under creative commons.
15  Alternate cryptocurrencies / Altcoin Discussion / [XPM GPU Miner] Data Collection Thread! on: September 02, 2013, 10:52:19 PM
Hello! I'll start this off. While 5-chains may not be the best/most telling metric, it's an interesting statistic none-the-less. Here is 5-chains versus sievepercentage:

NOTE: above stats found with 2x7950 with overclock at 1045 core: 650 memory, aggression 31 in reaper....

This thread is for posting any findings you have for the XPM GPU miner, including what settings allowed you to find a block.
16  Economy / Currency exchange / [WTB] 3.5BTC donation to a charity on: August 29, 2013, 02:29:51 AM
I want to donate to the Humane Society, however they don't accept Bitcoins. Is there a way for someone to prove that they paid for a human society donation? If they give like an email saying you donated x amount, etc. that could be donated using an email of mine?

Basically, I would pay you 3.5BTC, you would donate USD: $450 to the humane society. An easy way for you to acquire some bitcoins with, effectively, a credit card, and a good way for me to spend cryptos doing something good. Smiley

Is anyone interested in doing this..?? Cheesy
17  Economy / Computer hardware / [WTS] In-Hand 60GH/s Single SC BFL: 35BTC+free overnight shipping USA* on: August 28, 2013, 01:21:19 AM
Gonna be honest. If you pay 35BTC for this single, I highly doubt that you will see that 35BTC again, the unit will just not ROI to that. That's why I'm selling it at this price.

I can't ship until the weekend, however from now until the weekend (if you purchase now), I will point the ASIC at the pool of your choice, so you don't loose any time. I will overnight it with insurance from UPS on Saturday mid-day to anywhere in the continental United States for free, If you live across the pod we can work out shipping on a case-by-case basis. Smiley

If you believe that the 28nm ASICs will be delayed from KnCMiner, HashFast, CoinTerra, etc. or that they won't meet performance specs, then this offer might be for you. Do you math. Do your homework. The offer is on the table, but it doesn't mean it's a good offer. I make the offer because it appears to work in my advantage.

At any rate, if you need proof of the fact that I have the ASIC, I will point it at the pool of your choice for an hour.

Edit: Oh, and unless you are a trusted community member, I don't want to do escrow, cause you could claim I shipped you a box of bricks. However, if you're a trusted community member, I'd be happy to do escrow, and if you're a mod or something, I'll even send first Smiley

Edit: Image, with 5 fingers:

Lighting is a bit bad, looks almost photoshopped, unfortunately. And it doesn't help that I have a bit of a history of being good a Photoshop for various mockups and such. Anyhow.... For real proof if you are interested I'll point it at a pool of your choice for an hour, or maybe I'll do like a little video thing? That would be a lot less suspicious. Oh, and the thing behind the card is a laptop on the left with EasyMiner, and on the right is a Pencil Sharpener. You don't get either with your order, but if you want to pay an extra 0.05BTC (shipping), I'll send that old pencil sharpener insured for a whopping $17. Steal of the day, an offer of gratuity for buying the ASIC. Tongue
18  Economy / Computer hardware / Will Buy BFL Single 60GH (In-Hand)--19BTC Shipped to USA. on: August 25, 2013, 10:11:48 PM
If anyone has a BFL Single In-Hand that they would like to sell on the cheap, I will purchase it for 19BTC. This is below the current market value of the device, however it is slightly below what I feel the unit will ROI at. 
19  Bitcoin / Group buys / [Group Buy Possibility?] XCrowd Hosted Packages on: August 21, 2013, 12:01:56 AM
So, as many of you likely know, xCrowd offers hosted mining starting at 15TH/s, for $85,000 outright, plus $5,000 per month. I don't want to run a group buy by any means, but would anyone be interested in running a groupbuy of this mining package, where people could buy, say, a minimum of 500GH/s or so, and pay one outright fee, plus a monthly fee, or one outright fee that would cover 6 or 12 months?

For one year, the total cost is around $9670/TH, including the monthly fees. To compare, at a rate of $0.16/kWh, 15TH/s buying their units and hosting them in a datacenter, assuming the only datacenter cost is electric (as $0.16 is a bit high for datacenter electricity), would cost around the same ($9750). Just a thought. Smiley
20  Alternate cryptocurrencies / Altcoin Discussion / [XPM] WTB--Saints Row IV (Steam GAME) [95 XPM] on: August 19, 2013, 12:30:00 AM
Hello! I like Cryptos, and I like Games. And I like buying games with cryptos.

If you want to get your hands on 95 Primecoins (the equivalent of 0.63BTC at market value, or almost $70), just gift me both Saints Row IV + the season pass. In the US, this should cost $55, as the base game is 45 and the season's pass is $10. Smiley EIf you want to sell me the game but not the season's pass, we can work out another slightly lower price.

Please note
: if your Steam account doesn't have games in it or it is really new, you will have to wait a month to gift the game. If that is the case, please do not take up this offer! Smiley

If I either know you (and like you), or you are a trusted community member, you can send first, no problem. If you have far less posts than me and little to no trade history, then please go first. I will use escrow if you are willing to pay the escrow fee.

Part of my reason doing this and paying with more than market value is to get my trading rep up, so (assuming the transaction goes well) I will give you a trade +1, and I hope you will do the same. I've done trades before, but neither parties left feedback, unfortunately. Sad
Pages: [1] 2 3 4 5 »
Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!