All imported libraries end up as one file
what am i looking at here
That may be, but flattening didnt work for my contract
Also the code was written in 0.8.2 and after flattening it was 0.8.0 version
If you would jsut make a video it would also help more than 100s of messages
Besides after flattening i had after every contract isntance pragma solidity 0.8.0 and the spdf identifier
Why do you tell me to use those imports aswell when i obviously dont need them, the contract works without those imports and as you see my contract was verified aswell without those imports, so why are you telling me i need to use them?
The imports are meant to make your code a little more easier to use. Once compiled, all the code comes into a single file anyway. If you manually add all your code into a single file, you don’t need to add the imports. Its just a standard way of development that developers follow.
Looks like your contract is verified on bscScan right now. Is there anything else you’d like to clear up or does everything work good?
Looking forward to your response! 
Apperently bscscan verifies some standard contracts automatically, so I still dont know how to verify a contract with imports
Hi, Can you verify my contract on bscscan?
What kind of smart contract you have?
https://github.com/OpenZeppelin/openzeppelin-contracts/blob/master/contracts/token/ERC20/ERC20.sol bsc
It should be easy, can you post what imports it uses?
(post withdrawn by author, will be automatically deleted in 24 hours unless flagged)
I can look in 1-2 hours
thank you in advance
Did you manage to look my contract?
dud you compile it with some specific parameters?
no, i didnt . i deploy exactly as above
i had to change https with XXX as I can’t post link here
I don’t know how to verify it, I also don’t know how you sent that initialSuply parameter in constructor at deploy.
so, solution is to deploy a new contract?
maybe, or you can live it this way without validating it, you don’t have to necessarily validate it