Verify Crowdsale contract on Etherscan deployed using Remix

Support Contracts
1

Hi
I have created two contract , ERC20 and Crowdsale suggested by ABCOATHUP earlier

I can successfully able to verify the Simple Contract but the Crowdsale is unable to verify

Screen Shot 09-09-20 at 07.40 AM
Screen Shot 09-09-20 at 07.40 AM1236×259 15.6 KB

I have removed all the text in the constructor Argument and uploaded the flatten source code

Screen Shot 09-09-20 at 07.44 AM
Screen Shot 09-09-20 at 07.44 AM1229×881 52.6 KB

I have deployed the both the contracts from Remix ,used the compiler 0.5.17 and Flatten with Truffle in Ubuntu18.
My Crowdsale contract address is 0x8599820a642ef194a7119bd9442b3882f3a37cb0 on the real net

Code Used

pragma solidity ^0.5.0;
import "https://github.com/OpenZeppelin/openzeppelin-contracts/blob/v2.5.0/contracts/crowdsale/Crowdsale.sol";
/**
 @title YieldCrowdsale
 @dev This is an example of a fully fledged crowdsale.
*/contract YieldCrowdsale is Crowdsale {
    constructor (
        uint256 rate,
        address payable wallet,
        IERC20 token
    )
        public
        Crowdsale(rate, wallet, token)
    {
    }
}

Please help me to verify in the mainnet

1 Like
2

Hi @MarquisOgre,

Welcome to the community :wave:

I recommend reading Points to consider when creating a fungible token (ERC20, ERC777)

What values did you use for rate, wallet and token when you deployed the Crowdsale?

3

I have used the values as "40","0xb56bc45e5fe77Fa8349EF5E816E899b5A1357D3d","0x4A0B2e3f0C798F93e4369F4d58BcE2BaaCD2C0eF"

1 Like
4

Hi @MarquisOgre,

:warning: You should seek appropriate advice on regulatory compliance and your solution should have appropriate testing and auditing.

I have verified the contract with a flattened contract from truffle-flattener and the constructor parameters provided: https://etherscan.io/address/0x8599820a642ef194a7119bd9442b3882f3a37cb0#code

5

Thank you for verifying the contract, But where exactly i was doing wrong, can u plz guide me

1 Like
6

Hi @MarquisOgre,

The contract has constructor arguments so we need to supply them when verifying. Etherscan provides them so just needed to cut out the text before the 0000...00028

7

Hi @MarquisOgre,

Let me know if you need more information.

8

Thank you for all the support Abcoathup, I have learned the process of Verifying contracts with https://abi.hashex.org/# and Truffle as well

1 Like
9

Hi @MarquisOgre,

Welcome to the community :wave: