Category: Hashrate

Executive Order 6102

History Lessons,
never to be forgotten!¡

Executive Order 6102 is an executive order signed on April 5, 1933, by US President Franklin D. Roosevelt “forbidding the hoarding of gold coin, gold bullion, and gold certificates within the continental United States.”

The executive order was made under the authority of the Trading with the Enemy Act of 1917, as amended by the Emergency Banking Act in March 1933.

Summary

  • Forbade ownership of quantities of gold coin, bullion, and gold certificates worth in excess of $100 (about 5 troy ounces), with exemptions for specific uses and collections;
  • Required all persons to deliver excess quantities of the above on or before May 1, 1933 in exchange for $20.67 per troy ounce;
  • Enabled Federal funding of Exchange Stabilization Fund using profit realized from international transactions against new Federal reserves.

The limitation on gold ownership in the United States was repealed after President Gerald Ford signed a bill legalizing private ownership of gold coins, bars, and certificates by an Act of Congress, codified in Pub.L.93–373,which went into effect December 31, 1974.

The stated reason for the order was that hard times had caused “hoarding” of gold, stalling economic growth and worsening the depression as the US was then using the gold standard for its currency

On April 6, 1933, The New York Times wrote, under the headline Hoarding of Gold, “The Executive Order issued by the President yesterday amplifies and particularizes his earlier warnings against hoarding.

On March 6, taking advantage of a wartime statute that had not been repealed, he issued Presidential Proclamation 2039 that forbade the hoarding ‘of gold or silver coin or bullion or currency’, under penalty of $10,000 and/or up to five to ten years imprisonment.”

The main rationale behind the order was actually to remove the constraint on the Federal Reserve preventing it from increasing the money supply during the depression.

The Federal Reserve Act (1913) required 40% gold backing of Federal Reserve Notes that were issued. By the late 1920s, the Federal Reserve had almost reached the limit of allowable credit, in the form of Federal Reserve demand notes, which could be backed by the gold in its possession.

Source:
https://wikipedia.com/

What is Hashrate ?

Hashrate

Hashrate Bitcoin network h/s
Bitcoin Hash Rate

Hashrate (Hash per second, h/s) is an SI-derived unit representing the number of double SHA-256 computations performed in one second in the bitcoin network for cryptocurrency mining.

Hashrate is also called as hashing power. It is usually symbolized as h/s (with an appropriate SI prefix).

What is hashing power or hash rate?

The hash rate is the primary measure of a Bitcoin miner‘s performance.

In 2014, a miner’s performance was generally measured in Ghash/s, or billions of hashes per second.

The hash/second unit is also part of a common measure of a Bitcoin miner’s electric efficiency in the term watts /Ghash/s, denoted as W/Ghash/s. As 1 watt is equal to 1 joule/s, this measure can also be expressed as J/Ghash, or joules per 1 billion hashes.

Bitcoin network hash rate

Bitcoin network hashrate chart

The hash/s is also used in calculations of the Bitcoin network’s overall hash rate. Because each miner or mining pool only relays a solved block to the network, the overall hash rate of the network is calculated based on the time between blocks.

While not an accurate measure of network hash rate at any given instance in time, measurements over longer periods can be considered indicative and similar calculations are used in Bitcoin’s difficulty  adjustment.

In January 2015, the network hash rate was around 300 Phash/s, or 300 quadrillion hashes per second.

If you compare a bitcoin mining device to one that is designed to mine, for example, Ethereum, you will notice a very large apparent difference in hash rates.

This is because there are many different algorithms that cryptocurrencies use. They all require different amounts of memory and computing power in order to be mined.

To put it simply, bitcoin and its SHA256 algorithm is considered by today standards to be relatively easy to compute. As a result, a mining device that is still relevant today would need to produce hashes in the terahash range and up.

If we were to compare this to Ethereum, you’ll find that most modern Ethereum mining devices (typically GPU’s) operate in the megahash range.

At first glance, you may think that the bitcoin mining device is significantly more powerful or more productive.

While it’s true that it produces more hashes (of the SHA256 variety), this is because bitcoin hashes are easier to produce computationally.

As a consequence, the network difficulty is significantly higher for bitcoin.

To make things even more confusing, some cryptocurrencies intentionally chose algorithms that can only be mined using a basic CPU.

As a result, mining devices for this network that can produce hundreds of hashes per second are considered to be high and very competitive.

So what does all this mean?

Basically, it means that looking at the hash rate alone doesn’t necessarily tell you the effectiveness of the miner.

You also need to understand the network difficulty, and what the norm is for most mining devices for that particular cryptocurrency.

How can I calculate how many hashes I generate per second?

Your problem breaks down nicely into 3 separate tasks:

  • Sharing a single count variable across threads
  • Benchmarking thread completion time
  • Calculating hashes p/sec
  • Sharing a single count variable across threads

Now that we know that not all hashes are the same we need to know how to calculate the estimated profitability of a miner based on its hash rate.

For this, will need to use a mining profitability calculators, they are available in the Internet.

public static class GlobalCounter

 {
   public static int Value { get; private set; }
   public static void Increment()
   {
       Value = GetNextValue(Value);
   }
   private static int GetNextValue(int curValue)
   {
       return Interlocked.Increment(ref curValue);
   }
   public static void Reset()
   {
       Value = 0;
   }
 }

Before you spin off the threads call GlobalCounter.

Reset and then in each thread (after each successful hash) you would call GlobalCounter.

Increment – using Interlocked.X performs atomic operations of Value in a thread-safe manner, it’s also much faster than lock.

Benchmarking thread completion time

var sw = Stopwatch.StartNew();
Parallel.ForEach(someCollection, someValue =>
 {
   // generate hash
   GlobalCounter.Increment();
 });
 sw.Stop();
Parallel.ForEach will block until all threads have finished

Calculating hashes per second

...
sw.Stop();
var hashesPerSecond = GlobalCounter.Value / sw.Elapsed.Seconds;

How is the hash rate measured?

Hash rate is a unit measured in hashes per second or h/s and here are some usual denominations used to refer it.

Hash rate denominations:

  • 1 kH/s is 1,000 (one thousand) hashes per second;
  • 1 MH/s is 1,000,000 (one million) hashes per second;
  • 1 GH/s is 1,000,000,000 (one billion) hashes per second;
  • 1 TH/s is 1,000,000,000,000 (one trillion) hashes per second;
  • 1 PH/s is 1,000,000,000,000,000 (one quadrillion) hashes per second;
  • 1 EH/s is 1,000,000,000,000,000,000 (one quintillion) hashes per second.

Common Hash rate Conversions:

  • 1 MH/s = 1,000 kH/s;
  • 1 GH/s = 1,000 MH/s = 1,000,000 kH/s;
  • 1 TH/s = 1,000 GH/s = 1,000,000 MH/s = 1,000,000,000 kH/s.

Shared with 💚 by Free Spirit

✌ & 💚