ethereum/solidity

The Solidity Contract-Oriented Programming Language - By chatting here you agree to the https://github.com/ethereum/solidity/blob/develop/CODE_OF_CONDUCT.md

cameel

@cameel:matrix.org

[m]

ok, by still, I get X2_metadata.json when I compile your file and it has these settings:

    "settings": {
        "compilationTarget": {
            "X2.sol": "X2"
        },
        "evmVersion": "istanbul",
        "libraries": {},
        "optimizer": {
            "enabled": false,
            "runs": 200
        },
        "remappings": []
    },

No "metadata": { "useLiteralContent": true }. So I think you gave me wrong file.

I mean, if you want to compare bytecode with the one produced by Remix and remix does not use useLiteralContent then you have to compile without that option locally too.

Otherwise the metadata hash will be different (because metadata JSON is different when useLiteralContent is enabled).

Kimiro

@kimiro34

Then where "metadata": { "useLiteralContent": true } came from?

cameel

@cameel:matrix.org

[m]

probably from here :)
https://github.com/kimiro34/solidity-contract-source-code-verifier-example/blob/main/verifier-single-with-metadata-and-loadRemoteVersion.js#L33

I think this file must have come from your script rather than from Remix.

That's the most likely explanation.

Kimiro

@kimiro34

I am sorry, but can you make a bytecode without that option?

I just tried without that option but it still gives me different bytecode

cameel

@cameel:matrix.org

[m]

Can you visit Remix in a fresh, private tab (so that it does not have any previous data) and try again?
Create X2.sol, run compilation, check the artifact. If you get this option there, please give me the exact steps you did and I'll try that on my side.

Kimiro

@kimiro34

Yeah, no problem.

Kimiro

@kimiro34

Yeah, you are right. On fresh remix tab, the metadata is different

no "metadata": { "useLiteralContent": true }

and instead appeared

"urls": [
                "bzz-raw://18a9cdadc2aab8996c84715151968e678fb99a17c65a414b3b751c200e3ac1f2",
                "dweb:/ipfs/QmNuf4gscWZbshwLVDsdP7M7R5vy6Hix3HtTYs3offpLxK"
            ]

and source code string under content key disappeared.

So I have errors compiling this metadata on solc-js

Kimiro

@kimiro34

Of course remix-compiled bytecode is exactly same with the blockchain bytecode

How can I make use of this metadata with solc-js?

I have uploaded new metadata file

Here is my setting.

Kimiro

@kimiro34

    var input = {
      language: "Solidity",
      settings: {
        evmVersion: "istanbul",
        libraries: {},
        optimizer: {
          enabled: false,
          runs: 200,
        },
        remappings: [],
      },
      sources: {
        "contracts/X2.sol": {
          keccak256:
            "0xce0fdd5edf018d11acf1b78c568bbc900cdec244bd35a41509cd34d20fa8d9c1",
          urls: [
            "bzz-raw://18a9cdadc2aab8996c84715151968e678fb99a17c65a414b3b751c200e3ac1f2",
            "dweb:/ipfs/QmNuf4gscWZbshwLVDsdP7M7R5vy6Hix3HtTYs3offpLxK",
          ],
        },
      },
    };

And got this error

{
  errors: [
    {
      component: 'general',
      formattedMessage: 'Cannot import url ("bzz-raw://18a9cdadc2aab8996c84715151968e678fb99a17c65a414b3b751c200e3ac1f2"): File import callback not supported',
      message: 'Cannot import url ("bzz-raw://18a9cdadc2aab8996c84715151968e678fb99a17c65a414b3b751c200e3ac1f2"): File import callback not supported',
      severity: 'error',
      type: 'IOError'
    },
    {
      component: 'general',
      formattedMessage: 'Cannot import url ("dweb:/ipfs/QmNuf4gscWZbshwLVDsdP7M7R5vy6Hix3HtTYs3offpLxK"): File import callback not supported',
      message: 'Cannot import url ("dweb:/ipfs/QmNuf4gscWZbshwLVDsdP7M7R5vy6Hix3HtTYs3offpLxK"): File import callback not supported',
      severity: 'error',
      type: 'IOError'
    }
  ],
  sources: {}
}

Oh, sorrrrrrrrry, @cameel. It's a already midnight. I will keep trying by myself.

2 replies

cameel

@cameel:matrix.org

[m]

You need to remove the stuff inside contracts/X2.sol key and add a content key. Then put the file content under that key.

Also make sure to check that the keccak256 hash matches the hash of the code you're putting in there (make sure to preserve the file exactly - same line endings, indentation, etc.).

Kimiro

@kimiro34

I tried and gave me this result

{ sources: { 'contracts/X2.sol': { id: 0 } } }

I think I have no right to spare your time any more. So please leave the rest of this to me. I will resolve it by myself.

Kimiro

@kimiro34

I am really, really sorry for keep asking for my indigence of knowledge. So Please......... have a good night....

Kimiro

@kimiro34

Hiiiiiii, @cameel, I finally able to make the EXACTLY SAME bytecode!!! Without your patient and professional guide, it was impossible. Deep thanks to your effort and patience on me and my project.

And also thanks to entire solc-js develop team with their effort on a such a valuable project! :)

Angela

@DuSKV9pLjlKENQH_twitter

这是什么

SafeFantom

@SafeFantom_twitter

Hi I need help

Angela

@DuSKV9pLjlKENQH_twitter

What kind of help do you need

SafeFantom

@SafeFantom_twitter

I made a coin on bsc net, but cant pull liquidity now

https://bscscan.com/token/0x8ec4c80db19e994aea9428f2304edd0318dc4ffc

Angela

@DuSKV9pLjlKENQH_twitter

Have you established a public chain

SafeFantom

@SafeFantom_twitter

I don't know

i just copy pasted the code

from a working one

and changed the liquidity fee etc

Angela

@DuSKV9pLjlKENQH_twitter

That is wrong

SafeFantom

@SafeFantom_twitter

usually worked with other codes, but this one was more profound i guess

can you take a look?

Angela

@DuSKV9pLjlKENQH_twitter

You are not built on the public chain

SafeFantom

@SafeFantom_twitter

maybe i can change a value in the write contract column

can i fix that?

Angela

@DuSKV9pLjlKENQH_twitter

yes

SafeFantom

@SafeFantom_twitter

thankfully

Where communities thrive

People

Repo info

Activity