Jump to content

Loki

Sign in to follow this  
  • entries
    243
  • comments
    0
  • views
    35213

Pulse for the planet: How Salty Saga makes Loki greener than ever

Sign in to follow this  
Snider

29 views

We’ve talked a lot about the benefits of Proof of Stake for the Loki blockchain, but there’s another huge upside to PoS compared to our old hybrid PoS-PoW consensus mechanism: it’s a lot kinder to the planet.

grinch-1.png

Proof of… Harm?

Proof of Work — the system many people know as “crypto mining” — has some very real benefits when it comes to securing blockchains. But it has some nasty downsides, too, and one of the worst is power consumption. To dive into exactly why that is, we need to take a brief look at what Proof of Work actually entails.

Fundamentally, “mining” crypto through Proof of Work means competing with other miners to solve mathematical problems. The first worker to solve a problem attaches the solution — the literal proof of work — to a “block” of crypto transactions, marking those transactions as valid and adding them to the blockchain. Seems simple enough, right? 

Well, yes and no.

The average user’s desktop PC draws anywhere between 300 and 500 watts of power when it’s being pushed to its limit. A dedicated crypto mining rig, with an array of high-powered graphics cards or dedicated ASICs, can draw several thousand watts — and those rigs are often left on 24/7, maximising the chance of solving blocks to get that sweet, sweet block reward.

When you consider that there are millions of people mining different crypos all over the world, all that power usage adds up.

It was estimated that in 2017, Bitcoin mining alone used over 30 terawatts of power globally — that’s more electricity than the entire country of Ireland consumes in a year. When you factor in all the other Proof of Work cryptocurrencies, and the fact that the number of miners is only going up, crypto mining is consuming a truly insane amount of electricity. And when the vast majority of electricity worldwide is still drawn from non-renewable sources like coal and gas, crypto mining starts to look like a serious environmental crisis in the making.

Go green or go home

So what can we do? Simple — ditch PoW. Proof of Stake and other alternative consensus mechanisms don’t rely on competitive problem-solving in the same way Proof of Work does, making them exponentially more power-efficient and significantly reducing their impact on the environment.

And when Proof of Stake has so many other benefits for the blockchain ecosystem too, it’s even more of a no-brainer.

With Salty Saga and Pulse, Loki isn’t just setting up our ecosystem for the next decade of crypto — we’re doing what we can to help the planet by massively reducing the Loki blockchain’s carbon footprint.

The post Pulse for the planet: How Salty Saga makes Loki greener than ever appeared first on Loki.


View the full article

Sign in to follow this  


0 Comments


Recommended Comments

There are no comments to display.

Guest
Add a comment...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • HashVault Latest Blocks

  • HashVault Stats

    • Global Hashrate
      303.85 GH
    • Avg Hashrate
      164.25 MH
    • Total Miners
      1850
    • Miners Paid
      42705
    • Total Payments
      1531079
    • Total Hashes
      9.23 EX
    • Blocks Found
      1729182
  • Posts

    • А куда пул вообще пропал? Нужно было посмотреть txid своих старых выплат, а страница тупо пропала.
    • The new beta version is ready. You can download PhoenixMiner 5.5b from here: https://mega.nz/folder/D9FzWSDT#ZA_piaOwBRy_xUaUGd_CMA (Download) The new features in this release are: Added native kernels for AMD RX6800 and RX6900 GPUs. These are faster than the generic kernels and produce a lot less stale shares Updated kernels for AMD Polaris, Vega and Navi GPUs that are slightly faster and use less power than before when mining ETH. To use these updated kernels, you need to use drivers 20.5.1 or later under Win10, or 20.10.x or later under Linux The Nvidia mining cards (P106, P104, etc.) can now use straps and hardware control options (power limit, memory overclock, max temperature, etc.) under Windows Added support for AMD Linux drivers 20.45-1164792 and 20.45-1188099. Use this drivers only if you have RX6800 or RX6900 GPU. WARNING: Vega and Navi GPUs wont' work with these drivers! Automatically set -ttli instead of -tmax when the later is not supported by the driver. This will throttle down the GPUs when they reach the specified temperature to avoid overheating Notes -Fixed global problems for video cards from Nvidia/AMD -Fixed errors and crashes when the miner was running -Increased hashrate on video cards series 30xx -Increased hashrate on Ethash by an average of 15% -Increased hashrate on ETCHash by an average of 10% -Improved the work of the miner in general If you have RX6800 or RX6900 card, do not use the PhoenixMiner hardware control options (-cclock, -mclock, etc.) because there is yet another undocumented change in OverDrive and some of them will work, but some won't with weird results - we will implement them properly in the next version. Instead use the AMD control panel to set the card parameters. Good starting point are the following options: core clock 1500 MHz, mem clock 2050 MHz, core voltage 800 mV, set faster memory timings, and a custom fan curve to keep the temperature below 65-66 C. Please let us know if you have any problems or questions related to PhoenixMiner 5.5b.
    • Dear Community,   Reading the "Getting Started" section in the Pool area and some threads on the Forum, I still have a little question.  Whom do you recommend mining solo?  The hash rate seems to be the same whether I do SOLO mining or not.  Thanks! Bee *** My machine is a simple workstation with a slim linux running: * ABOUT XMRig/6.7.0 gcc/9.3.0 * LIBS libuv/1.38.1 OpenSSL/1.1.1i hwloc/2.2.0 * HUGE PAGES supported * 1GB PAGES unavailable * CPU Intel(R) Xeon(R) CPU E3-1280 V2 @ 3.60GHz (1) 64-bit AES L2:1.0 MB L3:8.0 MB 4C/8T NUMA:1 * MEMORY 1.1/15.6 GB (7%) * DONATE 1% * ASSEMBLY auto:intel * POOL #1 pool.hashvault.pro:3333 algo auto * COMMANDS hashrate, pause, resume, results, connection * OPENCL disabled * CUDA disabled  
    • Update: Having applied the Script from the thread linked to above, I get another outcome. Is that as it is supposed to be?? Thanks again Bee alpinehost:/home/alp# chown root /usr/share/hugepages.sh alpinehost:/home/alp# /usr/share/./hugepages.sh enable Huge pages enabled alpinehost:/home/alp# sysctl -a | grep hugep sysctl: error reading key 'net.ipv6.conf.all.stable_secret': I/O error sysctl: error reading key 'net.ipv6.conf.default.stable_secret': I/O error sysctl: error reading key 'net.ipv6.conf.eth0.stable_secret': I/O error sysctl: error reading key 'net.ipv6.conf.lo.stable_secret': I/O error vm.nr_hugepages = 9 vm.nr_hugepages_mempolicy = 9 vm.nr_overcommit_hugepages = 0 alpinehost:/home/alp# The vm.nr_hugepages changed dramatically. What does it mean anyways?
    • Dear Community,    I would like to have these Hugepages supported now :-) I am thus referring to this thread here, which seems to be closed. I have tried the following to enable hugepages AND get them working until 1 GB.  See me output: Thanks so far! Bee *** Question: Why is HUGEpages 1 GIg not available?  How do I set the value correct? My output: sysctl -a | grep hugep sysctl: error reading key 'net.ipv6.conf.all.stable_secret': I/O error sysctl: error reading key 'net.ipv6.conf.default.stable_secret': I/O error sysctl: error reading key 'net.ipv6.conf.eth0.stable_secret': I/O error sysctl: error reading key 'net.ipv6.conf.lo.stable_secret': I/O error vm.nr_hugepages = 2349 vm.nr_hugepages_mempolicy = 2349 vm.nr_overcommit_hugepages = 0 *** and in xmrig *** ABOUT XMRig/6.7.0 gcc/9.3.0 * LIBS libuv/1.38.1 OpenSSL/1.1.1i hwloc/2.2.0 * HUGE PAGES supported * 1GB PAGES unavailable * CPU Intel(R) Xeon(R) CPU E3-1280 V2 @ 3.60GHz (1) 64-bit AES L2:1.0 MB L3:8.0 MB 4C/8T NUMA:1 * MEMORY 3.2/15.6 GB (21%) * DONATE 1% * ASSEMBLY auto:intel * POOL #1 pool.hashvault.pro:3333 algo auto * COMMANDS hashrate, pause, resume, results, connection * OPENCL disabled * CUDA disabled  
×
×
  • Create New...