Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Verify bSOV, and bridges SC. publish on wiki4dev the methodology #18

Open
bravepooh opened this issue Jun 23, 2021 · 2 comments
Open

Verify bSOV, and bridges SC. publish on wiki4dev the methodology #18

bravepooh opened this issue Jun 23, 2021 · 2 comments
Assignees
Labels
documentation Improvements or additions to documentation enhancement New feature or request hight priority

Comments

@bravepooh
Copy link
Contributor

According to special methodology of verify complex SC (that truffle flattener cannot).
Should verify with multi files. full details were given to Julio.

eSOV address on ETH mainnet , example of verified SC:
0xbdab72602e9ad40fc6a6852caf43258113b8f7a5 eSOV

SC to verify:
BSC:
0x8753ede1b3a36358e4d7780f384f3f7a2d9e4359 bSOV

ETH
Bridge 0x33C0D33a0d4312562ad622F91d12B0AC47366EE1

RSK
Bridge 0x1CcAd820B6d031B41C54f1F3dA11c0d48b399581

BSC
Bridge 0xdfc7127593c8af1a17146893f10e08528f4c2aa7

RSK
Bridge 0x971b97c8cc82e7d27bc467c2dc3f219c6ee2e350

@jjmr007 jjmr007 added documentation Improvements or additions to documentation enhancement New feature or request hight priority labels Jun 24, 2021
@jjmr007
Copy link

jjmr007 commented Aug 1, 2021

1.- https://etherscan.io/address/0xbdab72602e9ad40fc6a6852caf43258113b8f7a5#code
eSOV is an instance of the contract SideToken.

2.- BSC: 0x8753ede1b3a36358e4d7780f384f3f7a2d9e4359 bSOV <-- this is the equivalent of eSOV but in the Binance network.
To verify it, a flatten version of the contract is obtained by the means of the PAO tool. To use this tool, the repo can be cloned locally, and we execute in the command line (in the directory of the cloned repo): $npm install. Then we can use the instruction $npm start ./path/to/my/contract/SmartToken.sol. The flattenized version of the contract is stored in the out directory. The features for the verification on eSOV were taken for the verification on BSC chain. However the verification fails, as it is not standard the verification of a contract that has been created by another contract. rather it is strange that eSOV could be verified.

3.- VERIFICATION FAIL: Sometimes a contract created by other contract can be verified in an etherscan type explorer, other times it will fail. Constructor arguments used:

000000000000000000000000000000000000000000000000000000000000008000000000000000000000000000000000000000000000000000000000000000c0000000000000000000000000dfc7127593c8af1a17146893f10e08528f4c2aa70000000000000000000000000000000000000000000000000000000000000001000000000000000000000000000000000000000000000000000000000000000462534f5600000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000462534f5600000000000000000000000000000000000000000000000000000000

Flatten Version of SideToken contract:
SideToken_flat.zip

In another try this set of contract were supplied to the exploer without success.

@jjmr007
Copy link

jjmr007 commented Aug 1, 2021

All these contracts seem to be different instances of AdminUpgradeabilityProxy.sol:

ETH
Bridge 0x33C0D33a0d4312562ad622F91d12B0AC47366EE1 (verified)

RSK
Bridge 0x1CcAd820B6d031B41C54f1F3dA11c0d48b399581 (Verification Failed)
constructor arguments tried:
0x2fb3b361000000000000000000000000b64322e10b5ae1be121b8bb0dead560c53d9dbc30000000000000000000000001a98f4e6df0dd48c519179d4289feb7c1700dd590000000000000000000000003e58bc4dff75ac8a9d53acdfef752debee3700d1000000000000000000000000ec3fabc3517e64e07669dd1d2d673f466f93a32800000000000000000000000000000000000000000000000000000000000000a000000000000000000000000000000000000000000000000000000000000000026573000000000000000000000000000000000000000000000000000000000000

BSC
Bridge 0xdfc7127593c8af1a17146893f10e08528f4c2aa7 (verified)

RSK
Bridge 0x971b97c8cc82e7d27bc467c2dc3f219c6ee2e350 (Verification Failed)
constructor arguments tried:
0x2fb3b361000000000000000000000000ee9ea57555d9533d71f6f77e0e480961f068a6c5000000000000000000000000c6e039d90d76cfcbb55d8324585dc3a2d9c045b10000000000000000000000009b989525b5836cbabf1017980d974c352a39f94e0000000000000000000000006e5f68f38269ea558805bc1c70cd7cdd536f557f00000000000000000000000000000000000000000000000000000000000000a000000000000000000000000000000000000000000000000000000000000000026273000000000000000000000000000000000000000000000000000000000000

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation enhancement New feature or request hight priority
Projects
None yet
Development

No branches or pull requests

2 participants