The company’s latest 470.05 beta driver has automatically unlocked performance and boosts the hashing rates for Ethereum mining for most RTX 3060 cards.

Mirrors can easily be very easily found online of the driver and the company will not be able to prevent RTX 3060 owners from continuing to use these drivers.

Originally, the company has restricted the RTX 3060 mining performance to steer crypto miners away from purchasing the cards. Despite this, the makers of GPU were confident that its restrictions couldn’t be defeated. In fact, they even claimed that it wasn’t just a driver holding back performance.

It’s not just a driver thing,” said Bryan Del Rizzo, Nvidia’s head of communications.

TRUE because the delegate call made to a died contract.

I believe someone might exploit.”

If traders are able to exploit the Parity wallet contracts to become owners of multi-sig wallets this is a vulnerability which could cause havoc for cryptocurrency trading.

Some Reddit users have suggested that the act was malicious, but in an interview, Devops199 said that he was researching an article based on a former Parity wallet compromise and “I’m walking randomly because I’m a newbie, I even don’t know how to code.”

In order to prevent the public bug from being used to steal wallets or funds, Parity has frozen dependent multi-sig wallets that were deployed after July 20 until a solution is found.

The vulnerability follows an issue in Parity wallets which was exploited in July this year.

The protections reduced the hash rate of Ethereum with the RTX 3060, making it an unideal component for cryptocurrency miners.

RELATED: AMD May Start Producing GPUs Specifically For Cryptomining, Similar To Nvidia

This is no longer the case, as an Nvidia developer driver was accidentally released that removes the hash rate limiter. Nvidia readily states that the release of the developer driver is accidental, and has removed the driver from the shops.
Nothing removed from the internet is truly gone: the driver has been uploaded to third-party websites. The hash rate limiter was claimed to be immovable by Nvidia, which similarly boasted the hash rate limiter did not affect performance for the graphics card.

The protections were defeated within its first month on the market, by Nvidia’s own hand.

The 470.05 driver is designed for developers to test the Windows Subsystem for Linux (WSL) performance and new features like OpenCL 3.0 support.

Nvidia originally restricted RTX 3060 mining performance in an attempt to steer cryptominers away from purchasing the cards. Nvidia is offering a new Cryptocurrency Mining Processor (CMP) for Ethereum miners instead.
The beta driver bypass of Ethereum mining performance will certainly make the cards more attractive to cryptominers now.

Nvidia seemed confident in its software restrictions to nerf RTX 3060 mining performance. “It’s not just a driver thing,” said Bryan Del Rizzo, Nvidia’s head of communications, last month.

By the way, I’m using this on a Mac.instance: Geth/v1.8.11-stable/darwin-amd64/go1.10.3

For example. ./geth account list returns the following.

The first one, #0 was created in 2016. The next two, this week.

Account #0: {c9b74488b8e699b54803464a33d57cfff7eb052c} keystore:///Users/robert/Library/Ethereum/keystore/UTC–2016-05-27T11-31-47.551960099Z–c9b74488b8e699b54803464a33d57cfff7eb052c Account #1: {b8baff0dcc88b9bf7aed45966938a30e2ab23ce4} keystore:///Users/robert/Library/Ethereum/keystore/UTC–2018-06-18T13-40-57.053229334Z–b8baff0dcc88b9bf7aed45966938a30e2ab23ce4 Account #2: {bf7042c963111a96bd4c8d86c179576ddfc07cb8} keystore:///Users/robert/Library/Ethereum/keystore/UTC–2018-06-19T06-11-21.589039961Z–bf7042c963111a96bd4c8d86c179576ddfc07cb8

Now, only account #1 and #2 can be unlocked.

Nvidia made a big deal about reducing the hash rate of Ethereum mining on its new RTX 3060 graphics card last month. A special system was supposed to make the RTX 3060 undesirable for cryptominers, but Nvidia has now confirmed that it has accidentally unlocked those restrictions with a new driver.

“A developer driver inadvertently included code used for internal development which removes the hash rate limiter on RTX 3060 in some configurations,” says an Nvidia spokesperson in a statement to The Verge.
“The driver has been removed.”

While Nvidia has now removed the driver, the genie is out of the bottle. Nvidia’s latest 470.05 beta driver automatically unlocks performance for most RTX 3060 cards, boosting hashing rates for Ethereum mining.

The ongoing feud between cryptocurrency miners and gamers often has both sides frustrated, with GPU manufacturers squarely between the two sides. Now, Nvidia’s most recent introduction of the RTX 3060 seems to favor the cryptocurrency miners, after an apparent gaffe rendered protection moot.

The RTX 3060 was shipped with mining protection that, Nvidia stated, was implemented to ensure that gamers received cards from the current generation. This has been done to curry favor with gamers, frustrated after multiple launches of the Ampere series only went to cryptocurrency miners. Few have been able to retrieve the Ampere generation due to a myriad of supply problems.

Nvidia implemented a special system to reduce the hash rate of Ethereum mining on its new RTX 3060 graphics card last month. It was supposed to limit mining performance by around 50 percent, but multiple reports now claim cryptominers have bypassed the protection.

Japanese site PC Watch first revealed that Nvidia’s protections can be bypassed without needing to modify a driver or BIOS.
ComputerBase has since confirmed PC Watch’s report and revealed that Nvidia’s latest 470.05 beta driver is automatically unlocking performance for most RTX 3060 owners. Andreas Schilling, an editor at Hardwareluxx, has also backed up these findings.

The beta driver appears to unlock Ethereum mining performance across a variety of RTX 3060 cards, which was likely not what Nvidia had planned for its test drivers.


The company said the vulnerability exists in the Parity wallet library contract of the standard multi-sig contract and was “found” by a user.

The bug was indeed found, albeit by complete accident.

“It would seem that issue was triggered accidentally 6th Nov 2017 02:33:47 PM +UTC and subsequently a user suicided the library-turned-into-wallet, wiping out the library code which in turn rendered all multi-sig contracts unusable since their logic (any state-modifying function) was inside the library,” Parity says.

An Ethereum user called devops199 said he was able to make himself the owner of a contract which he later “killed” by accident by removing a critical element of library code, which in turn made Parity multi-sig wallets tied to the contract unworkable — locking up the funds.

Devops199 explained:

“I’m not the owner of that contract.

So, using ./geth attach I do this. personal.unlockAccount(‘0xb8baff0dcc88b9bf7aed45966938a30e2ab23ce4’, null, 1) Unlock account 0xb8baff0dcc88b9bf7aed45966938a30e2ab23ce4 Passphrase: true

And as you see, that works. Fortunately when I created that account, again it must have been with ./geth, I used my usual password.

So the question remains, how do I tell if an address is locked or unlocked? How do I add an address to that keystore other than by creating it with ./geth address new? Which didn’t happen with the #0 address, because that’s a created address.

How did it get into the keystore?

As I think address #0 is unlocked, the error ‘could not decrypt key’ is actually telling me that it’s already unlocked.

Last month, Nvidia made a huge deal about them reducing the hash rate of Ethereum mining. They did this for their all-new RTX 3060 graphics cards which is a special system supposed to make the RTX 3060 undesirable for crypto miners.

However, the company has only recently confirmed that with a new driver they have accidentally unlocked those restrictions.

Nvidia spokesperson, in a statement, said “A developer driver inadvertently included code used for internal development which removes the hash rate limiter on RTX 3060 in some configurations.

The driver has been removed.”

Also Read: Nvidia Launches Cyberpunk 2077 NVIDIA DLSS with Immersive Graphics and Realistic Visuals

While the company has now successfully removed the driver, the damage is already done.

It’s one I created with geth, using ./geth account new

To unlock this account, I use this

geth –unlock 0xbf7042c963111a96bd4c8d86c179576ddfc07cb8 –datadir=/Users/robert/Library/Ethereum –password password.txt

That works, BUT. accounts #0 and #1 will not unlock – because I have no idea what or if they are even password protected. locked or unlocked? How can I tell?

So, the first address, address #0 is actually a created address, and is actually Unlocked. I never locked it when created. If indeed I ever could lock it.

Unlock account 0xc9b74488b8e699b54803464a33d57cfff7eb052c Passphrase: Error: could not decrypt key with given passphrase

The second address, #1, I don’t know.

I suspect I’ve accidentally created it. No idea if it’s locked or unlocked.

Similar Posts:

Leave a comment