Is anyone else starting to become a bit excited?

Pretty convincing scam email today purporting to be from Chainlink.

"
Chainlink Smart Contract Upgrade
The upgraded smart contract uses 68% less gas, supports updates thanks to proxy patterns and allows you to participate in future votes.

Chainlink
Jan 14


The upgraded smart contract is not a different contract, but just a new version. This post is intended to serve as a reminder and reaffirmation of Chainlink’s smart contract upgrade on Tuesday, January 14th, 2021 for all community members, users and ecosystem participants. Current LINK holders will need to manually update their LINK tokens via a so called proxy contract, whose main purpose is to ensure a safe and seamless upgrade without breaking any dependencies.

Although no immediate action needs to be taken, however, LINK holders who update early will be eligible for the new liquidity rewards program, starting on January 20th and lasting one week.

To provide enough time for holders to receive the upgrade information, we decided that the deadline should be 12:00, 19th, January 2021 (UTC+8). After the deadline, for those old LINK token failed to update, you could send an email to update@chain.link. Chainlink Team will verify the condition of your old LINK and conduct the swap process once a month. If you have any questions, comments or concerns, please get in touch at update@chain.link or by replying to this email.

Why do we need to upgrade? If a smart contract has already deployed it cannot be modified, so how can we update it? We use a proxy contract that receives all message calls from the outside world and redirects then to a contract containing the application logic. We can then deploy a new logic contract and update the proxy contract to reference that new contract. In Ethereum this is possible thanks to the delegatecall opcode: by putting it into the contract’s fallback function, all calls will be proxied no matter what. This doesn’t mean that the application contract will be in responsible for executing the transaction, as the proxy actually call function code from the logic contract, executing that code in proxy contracts own context. Our application state will then naturally be inside the proxy storage, and context variables such as msg.sender or msg.value will still be related to the account which sent the transaction towards the proxy.

LINK Update Guide
There are three accessible methods to update your LINK tokens:

via interacting with the LINK contract directly on Etherscan.

via MyEtherWallet's Interact with Contract interface.

via the automatic update-script published on Chainlink's Github.

The first two updating methods are pretty straightforward and intuitive. The third one, even though rather simple as well, has some limitations which should be considered before deciding to go forward. In this post we outline and detail and step by step walkthrough for each option.

Recommended wallets:

MetaMask: Best for if you already have an existing wallet or if you have a hardware wallet. If you have a Trezor or Ledger you can connect through MetaMask and update without having your LINK leave your hardware wallet.

Portis, Torus, Fortmatic: Best for if you do not have an active existing wallet and need to send your LINK out of an exchange, custodian service or cold storage.

In any wallet choice, the LINK you wish to update must be in that active wallet along with a small amount of Ether to pay for the transaction cost of performing the update.

Note:

If you have LINK in exchanges or other places, you will need to withdraw it to whatever decentralized wallet you’re using.

Despite the fact that we provide direct links in this walkthrough, we advise all users to manually insert the necessary website addresses (Etherscan, MyEtherWallet, Github) in their browser's address bar, check the website address and the SECURITY CERTIFICATE (green padlock symbol next to the address). Please check this every time you visit the chosen update website just to avoid falling into scams such as duplicate sites.

LINK Contract: 0x514910771af9ca656af840dff83e8264ecf986ca

LINK Proxy Contract: 0x093fAd33c3Ff3534428Fd18126235E1e44fA0d19

Update via Etherscan+MetaMask:
Begin by navigating to the LINK contract on Etherscan. If you wish to approve the exact amount of LINK that you hold, navigate to the “Read Contract” tab on the LINK token contract, click on “balanceOf” function, enter your ethereum address in the “_owner(address)” field and proceed by selecting the “Query” button - this will show, in attoLINK (ex: 'wei' or 10^18), the exact amount of LINK tokens that you hold in the queried address. If you do not wish to do the conversion, you can simply skip this part and when required, enter 1000000000000000000000000000 in the “_value(uint256)” field to set the maximum approval amount for the LINK token.


You now need to set an approval for the LINK proxy contract. Switch to “Write Contract” tab on the LINK contract. You must connect to a Web3 instance such as MetaMask. You can connect a hardware wallet such as Trezor or Ledger to your MetaMask extension and thus interact without LINK leaving your hardware wallet. Proceed by connecting your Web3 instance by selecting “Connect to Web3”. If you have more than one address connected to MetaMask, make sure you select the one that holds LINK tokens.


First, select the “Approve” function, enter the LINK proxy contract address in the “_spender(address)” field, 0x093fAd33c3Ff3534428Fd18126235E1e44fA0d19.

Second, enter however much LINK you wish to update in the “_value(uint256)” field.

Third, select “Write” button and confirm the approval in MetaMask - this will approve the full balance of LINK in your connected account.


When the transaction is confirmed the update is complete. Meanwhile, you may sell, trade and swap LINK tokens, this will not affect the upgrading process. That's it, you're all done!

Updating via MyEtherWallet:
Begin by navigating to www.myetherwallet.com, access your wallet via preferred method and head to the “Contract” section, to the left of your wallet interface.


Enter the current LINK contract address in the “Enter Contract Address” field, 0x514910771af9ca656af840dff83e8264ecf986ca.

For the “ABI/JSON Interface” field, you need to head over to LINK contract “Code” tab on Etherscan.


Scroll down to “Contract ABI” section and click on “Copy ABI to clipboard” button, to the upper right of the ABI code.


Paste the contract ABI to “ABI/JSON Interface” on MyEtherWallet and proceed by selecting “Continue” button. Finally, should look like this:


If you wish to approve the exact amount of LINK that you hold, click on “Select an item” button next to the contract address and choose “balanceOf” function, enter your ethereum address in the “_owner (address)”field and proceed by selecting the “Read” button - this will show in the “Result:” field the exact amount in attoLINK (ex: 'wei' or 10^18) of LINK tokens that you hold in the queried address. If you do not wish to do the conversion, you can simply skip this part and when required, enter 1000000000000000000000000000 in the “_value (uint256)” field to set the maximum approval amount for the LINK token.


Click on “Select an item” button next to the contract address and choose “approve” function.

First, enter the LINK proxy contract address in the “_spender (address)” field, 0x093fAd33c3Ff3534428Fd18126235E1e44fA0d19.

Second, enter however much LINK you wish to update in the “_value (uint256)” field.

Note: “Value in ETH:” field must be left blank.

Third, select “Write” and confirm the approval.


When the transaction is confirmed the update is complete. Meanwhile, you may sell, trade and swap LINK tokens, this will not affect the updating process. That's it, you're all done!

Updating via Automated Script:
This process is not recommended for a normal user or LINK holder, and only commonly used by exchanges or other custodians with proper engineering teams and security protocols that have the relevant experience and knowledge.

Navigate and clone the update-script from the Chainlink Github repo.

Requirements for this process entail:

(a) Python 3.6+ installed.

(b) HTTP Ethereum endpoint that can receive requests (--rpcvhosts=* if local).

(c) Private key of Ethereum account stored as environment variable.

Proceed with running the setup and automatic update-script.

Steps for running the script:

cd Update

virtualenv venv

. venv/bin/activate

pip install -e .

ETHEREUM_HTTP=[YOUR_ETHEREUM_HTTP_ENDPOINT] ETHEREUM_PRIVATE_KEY=[YOUR_PRIVATE_KEY] update

If you do not have a local Ethereum node running, you must specify one with the environment variable ETHEREUM_HTTP. That's it!



If you liked this post from Chainlink, why not share it?

Share

© 2021 Chainlink Unsubscribe
548 Market Street PMB 72296, San Francisco, CA 94104

Publish on Substack

OEP wrote: »

What I mean by "a thing" is widely adopted and used. Nothing to do with making x times your investment

Do you think that the technology universities are offering degree courses in blockchain for the craic?