Why is `bytecode` and `deployedBytecode` from Hardhat/Truffle different than in solc-js

Hi, I am using solc-js independently as I am trying to deploy some contracts in Hedera.
I have a question for you.
Truffle and Hardhat generate a bytecode in the json that the ABI has. But it has a different format than the one generated by solc-js and I don't understand why.

But I can think of using Truffle or Hardhat to generate the bytecodes and then deploy them with the Hedera SDK, how do you see it?

Format generated by solc-js:

60806040523480156200........

Format generated by Hardhat - Truffle

0x60806040526040516200107..

do you have any explanation? the bytecodes are different anyway.
In Truffle - Hardhat it generates two bytecode and deployedBytecode that start with the same characters as the one generated by solc-js but then they are different.

thanks

No source files or tests are named. Start by comparing the solc-js output with the Hardhat and Truffle bytecode and deployedBytecode formats described in the issue, then identify whether the differences are expected compiler output or an issue in solc-js. Done should be a documented explanation of the differing prefixes and contents.

Written by the indexing model from the issue text.