A message from our CEO about the future of Stack Overflow and Stack Exchange. Read now.
1

0x147 ... is going to the constructor and ultimately to wallet in the code. 0xCA3 ... is msg.sender 0x692 ... is the contract. Remix looks after that for you, but raw transactions would be to the contract, from: 0xCA3 ... and about 0x147 ... which is being passed as msg.data and unpacked by functions like buy() ... { which uses it. Hope it helps. ...


1

Expand the transaction receipt to see the log. Hope it helps.


1

You can interact directly with the ganache-core library: github Below is a test with using the infura API. This also works with a local node. const ganache = require("ganache-core"); const Web3 = require("web3"); // set whatever options you'd use in the cli here const options = { fork: "https://ropsten.infura.io/v3/API_KEY", port: 6546, }; const ...


1

According to https://github.com/ethereumbook/ethereumbook, this is the flow: Seed phrase -> Wallet -> Different addresses/accounts (private-public key-pairs) Therefore, If you have wallet A and B (different seed phrases), there is not a reliable way of identifying that your new address and old addresses belong to the same entity or are, in any way, ...


Only top voted, non community-wiki answers of a minimum length are eligible