New answers tagged

1

The price feeds / reference contracts work as you described: Independent Chainlink nodes collect data from highly respected APIs They place the data on-chain Other services make calls to the reference contracts The price given is considered the last price which is what most all exchanges consider to be the "market" price. Most exchanges have some ...


1

Saying Chainlink is "not decentralized enough" is a lot like saying "a tree is not a forest enough". Chainlink is a framework for connecting off-chain data to smart contracts in a decentralized manner. In the same sense that one Ethereum node is a part of the whole decentralized ecosystem, one Chainlink node is apart of the whole ...


0

This might be a good use case for Unlock protocol.


2

try change data :'' to data:"0x"


0

When I try to send a 256 bit integer (uint) on contract.methods.set(0x849787ab...), console throw an overflow error (1e77) In Javascript, Number.MAX_SAFE_INTEGER is equal to 2 ^ 53 - 1. Therefore, always use strings: contract.methods.set("0x849787ab..."). Is there a simpler method to do so? Here is what I use (tested with web3.js v1.2.1): const ...


0

I'm not sure to correctly understand your question. If you want to create a fully decentralized application I advise you to read the Ethereum book, chapter 12 : https://github.com/ethereumbook/ethereumbook/blob/develop/12dapps.asciidoc . Swarm is a good alternative to IPFS to host the frontend in a decentralized way : https://ethersphere.github.io/swarm-home/...


0

You just need to specify you are in the testnet const tx = new Tx(txObject, {chain: 'rinkeby'});


0

var TX = require('ethereumjs-tx').Transaction will remove this error.


0

Try this var transaction = new TX(rawTransaction); instead of this var transaction = new EthereumTransaction(rawTransaction)


0

I solved it myself!! ValidationUser.sol: function validAddress( int256 theMsg, uint8 v, bytes32 r, bytes32 s ) public payable returns (bool) { bytes32 hash = keccak256(abi.encodePacked(msg.sender, owner, theMsg)); return isSigned(owner, hash, v, r, s); } function isSigned( address _addr, bytes32 msgHash, uint8 v, ...


0

Some things to check Does the message's hash match the signed one? The concatenation in a buffer looks wrong. Does signed message include "Ethereum signed.." prefix? ECRecover doesn't prepend it. Make sure v parameter is either 27 or 28, some libraries return 0 or 1 instead.


Top 50 recent answers are included