Skip to content

Instantly share code, notes, and snippets.

Embed
What would you like to do?
vouching-deploy-scripts*!+1› »»»» npm run dodathing-ropsten 0|17:08:13
> zos-vouching@2.0.0-alpha.1 dodathing-ropsten /home/ajs/zos/packages/vouching
> npm run prepare && npm run deploy-ropsten && npm run create-ropsten && npm run configure-ropsten && npm run validate-ropsten
> zos-vouching@2.0.0-alpha.1 prepare /home/ajs/zos/packages/vouching
> rm -rf lib && babel src --out-dir lib
src/bin/configure.js -> lib/bin/configure.js
src/bin/create.js -> lib/bin/create.js
src/bin/deploy.js -> lib/bin/deploy.js
src/bin/validate.js -> lib/bin/validate.js
src/scripts/configure.js -> lib/scripts/configure.js
src/scripts/constants.js -> lib/scripts/constants.js
src/scripts/create.js -> lib/scripts/create.js
src/scripts/deploy.js -> lib/scripts/deploy.js
src/scripts/validate.js -> lib/scripts/validate.js
> zos-vouching@2.0.0-alpha.1 deploy-ropsten /home/ajs/zos/packages/vouching
> node ./lib/bin/deploy.js --network=ropsten --from=0x09902a56d04a9446601a0d451e07459dc5af0820
pushing app with options {
"network": "ropsten",
"txParams": {
"from": "0x09902a56d04a9446601a0d451e07459dc5af0820"
}
}
Note: this assumes that tpl-contracts-zos is already deployed in ropsten.
Validating contract ZEPToken before push
- Variable pausers (PauserRole) contain a struct or enum type, which are not being compared for layout changes in this version. Double-check that the storage layout of these types was not modified in the updated contract. Read more at https://docs.zeppelinos.org/docs/advanced.html#preserving-the-storage-structure.
Validating contract Vouching before push
- Variable _registry (Vouching) contain a struct or enum type, which are not being compared for layout changes in this version. Double-check that the storage layout of these types was not modified in the updated contract. Read more at https://docs.zeppelinos.org/docs/advanced.html#preserving-the-storage-structure.
Validating contract ZEPValidator before push
- Variables pausers (PauserRole), organizations (ZEPValidator) contain a struct or enum type, which are not being compared for layout changes in this version. Double-check that the storage layout of these types was not modified in the updated contract. Read more at https://docs.zeppelinos.org/docs/advanced.html#preserving-the-storage-structure.
Uploading ZEPToken contract as ZEPToken
Setting implementation of ZEPToken in directory...
Uploading Vouching contract as Vouching
Setting implementation of Vouching in directory...
Uploading ZEPValidator contract as ZEPValidator
Setting implementation of ZEPValidator in directory...
Setting Vouching implementation 0xaed3e76782242e3832c8bf2c2fe693bfb47761f1...
Setting ZEPValidator implementation 0xf4761204bcfd67c36aa13b36a8556a216497fc19...
Setting ZEPToken implementation 0x244175dd16479ca41f14f5acdee1118bd3fa72d5...
Implementation set 0xf4761204bcfd67c36aa13b36a8556a216497fc19
Implementation set: 0xf4761204bcfd67c36aa13b36a8556a216497fc19
Implementation set 0xaed3e76782242e3832c8bf2c2fe693bfb47761f1
Implementation set: 0xaed3e76782242e3832c8bf2c2fe693bfb47761f1
Implementation set 0x244175dd16479ca41f14f5acdee1118bd3fa72d5
Implementation set: 0x244175dd16479ca41f14f5acdee1118bd3fa72d5
0x69a74068b4e69fc2801a42cad06e2312c5ea63c8
Successfully written zos.ropsten.json
app pushed.
> zos-vouching@2.0.0-alpha.1 create-ropsten /home/ajs/zos/packages/vouching
> node ./lib/bin/create.js --network=ropsten --from=0x09902a56d04a9446601a0d451e07459dc5af0820
creating instances with options {
"network": "ropsten",
"txParams": {
"from": "0x09902a56d04a9446601a0d451e07459dc5af0820"
}
}
creating instance for BasicJurisdiction with owner: 0x09902a56d04a9446601a0d451e07459dc5af0820
Creating tpl-contracts-zos BasicJurisdiction proxy and calling initialize with:
- sender (address): "0x09902a56d04a9446601a0d451e07459dc5af0820"
TX receipt received: 0x354c1eeea131e88b7af058e6949e4907ff8542bcaa24a62aa14b6bf11b91b6e1
tpl-contracts-zos BasicJurisdiction proxy: 0x82671e0872547040fb80e2cc701829c4f98a2080
Successfully written zos.ropsten.json
0x82671e0872547040fb80e2cc701829c4f98a2080
BasicJurisdiction instance created at: 0x82671e0872547040fb80e2cc701829c4f98a2080
creating instance for ZEPToken with owner: 0x09902a56d04a9446601a0d451e07459dc5af0820 basicJurisdictionAddress: 0x82671e0872547040fb80e2cc701829c4f98a2080 and attributeID: 1665201538125898990930
Creating zos-vouching ZEPToken proxy and calling initialize with:
- _sender (address): "0x09902a56d04a9446601a0d451e07459dc5af0820"
- _jurisdictionAddress (address): "0x82671e0872547040fb80e2cc701829c4f98a2080"
- _validRecipientAttributeId (uint256): "1665201538125898990930"
TX receipt received: 0x8bea774e87148c8c50c95fdd2dc4d0a4fd9c147ac23fbd6831626d47ccd80eb8
zos-vouching ZEPToken proxy: 0xc1757e5af57c4da0c92098db34ccdde098196934
Successfully written zos.ropsten.json
0xc1757e5af57c4da0c92098db34ccdde098196934
ZEPToken instance created at: 0xc1757e5af57c4da0c92098db34ccdde098196934
creating instance for Vouching with minimumStake: 10 and zepTokenAddress: 0xc1757e5af57c4da0c92098db34ccdde098196934
Creating zos-vouching Vouching proxy and calling initialize with:
- minimumStake (uint256): 10
- token (address): "0xc1757e5af57c4da0c92098db34ccdde098196934"
TX receipt received: 0xdca4dfc96294f92b49d77d5eb46290dec7a375e94a96791be2f99a0415ea180b
zos-vouching Vouching proxy: 0xa9b39192e4f384aec2cd8e64f941cf141efb6cdb
Successfully written zos.ropsten.json
0xa9b39192e4f384aec2cd8e64f941cf141efb6cdb
Vouching instance created at: 0xa9b39192e4f384aec2cd8e64f941cf141efb6cdb
creating instance for ZEPValidator with owner: 0x09902a56d04a9446601a0d451e07459dc5af0820 basicJurisdictionAddress: 0x82671e0872547040fb80e2cc701829c4f98a2080 and attributeID: 1665201538125898990930
Creating zos-vouching ZEPValidator proxy and calling initialize with:
- _sender (address): "0x09902a56d04a9446601a0d451e07459dc5af0820"
- _jurisdiction (address): "0x82671e0872547040fb80e2cc701829c4f98a2080"
- _validAttributeID (uint256): "1665201538125898990930"
TX receipt received: 0xd6601dde10d7165da48dd4fcec5c3ec7288eb34409d1c4de03622516623562f9
zos-vouching ZEPValidator proxy: 0xaf9278366c25a3ef8c686f8d1f93e14d44b0fb65
Successfully written zos.ropsten.json
0xaf9278366c25a3ef8c686f8d1f93e14d44b0fb65
ZEPValidator instance created at: 0xaf9278366c25a3ef8c686f8d1f93e14d44b0fb65
all instances created!!
> zos-vouching@2.0.0-alpha.1 configure-ropsten /home/ajs/zos/packages/vouching
> node ./lib/bin/configure.js --network=ropsten --from=0x09902a56d04a9446601a0d451e07459dc5af0820
configuring vouching application
BasicJurisdiction proxies found: 2
BasicJurisdiction instance address: 0x82671e0872547040fb80e2cc701829c4f98a2080
ZEPValidator proxies found: 2
ZEPValidator instance address: 0xaf9278366c25a3ef8c686f8d1f93e14d44b0fb65
Adding ZEPValidator 0xaf9278366c25a3ef8c686f8d1f93e14d44b0fb65 to the jurisdiction...
Adding ZEPToken attributes to the jurisdiction: 1665201538125898990930
Approving ZEPValidator for control of the ZEPToken attribute...
Adding organization to the validator: address 0x09902a56d04a9446601a0d451e07459dc5af0820, addresses: 100000, name: ZEP Org
vouching application configured
> zos-vouching@2.0.0-alpha.1 validate-ropsten /home/ajs/zos/packages/vouching
> node ./lib/bin/validate.js --network=ropsten --from=0x09902a56d04a9446601a0d451e07459dc5af0820
validating vouching app on network ropsten
printing app status
Project status for network ropsten
Application is deployed at 0x69a74068b4e69fc2801a42cad06e2312c5ea63c8
- Package zos-vouching is at 0xb65dd5d68d8f11cc4487380ed53c3988468eff20
- Deployed version 0.0.1 matches the latest one defined
Application dependencies:
- tpl-contracts-zos@^0.0.1 is linked to version 0.0.1
Application contracts:
- ZEPToken is deployed and up to date
- Vouching is deployed and up to date
- ZEPValidator is deployed and up to date
Deployed proxies:
- tpl-contracts-zos/BasicJurisdiction at 0xbc74d15f23d118dfd885671c559fff9662964496 version 0.0.1
- tpl-contracts-zos/BasicJurisdiction at 0x82671e0872547040fb80e2cc701829c4f98a2080 version 0.0.1
- zos-vouching/ZEPToken at 0xfe15e5ffa131513e3a207f6fc4309c205514d2fb version 0.0.1
- zos-vouching/ZEPToken at 0xc1757e5af57c4da0c92098db34ccdde098196934 version 0.0.1
- zos-vouching/Vouching at 0xe97cee48b6dc47c4fc254c61675aef2ef4b65f1b version 0.0.1
- zos-vouching/Vouching at 0xa9b39192e4f384aec2cd8e64f941cf141efb6cdb version 0.0.1
- zos-vouching/ZEPValidator at 0xddd2c7eaa2e242371b16c4a97f72e8a9c360939f version 0.0.1
- zos-vouching/ZEPValidator at 0xaf9278366c25a3ef8c686f8d1f93e14d44b0fb65 version 0.0.1
validating jurisdiction
proxies found: 2
BasicJurisdiction instance address: 0x82671e0872547040fb80e2cc701829c4f98a2080
BasicJurisdiction owner: 0x09902a56d04a9446601a0d451e07459dc5af0820
Jurisdiction attribute description for id 1665201538125898990930: can transfer
ZEPToken attribute is correctly set on the jurisdiction.
jurisdiction looks good!!
validating ZEPToken
proxies found: 2
ZEPToken instance address: 0xc1757e5af57c4da0c92098db34ccdde098196934
ZEPToken name: ZeppelinOS Token
ZEPToken symbol: ZEP
ZEPToken looks good!!
validating Vouching
proxies found: 2
Vouching instance address: 0xa9b39192e4f384aec2cd8e64f941cf141efb6cdb
Vouching token address: 0xc1757e5af57c4da0c92098db34ccdde098196934
Vouching looks good!!
validating ZEPValidator
proxies found: 2
ZEPValidator instance address: 0xaf9278366c25a3ef8c686f8d1f93e14d44b0fb65
ZEPValidator owner: 0x09902a56d04a9446601a0d451e07459dc5af0820
ZEPValidator jurisdiction address: 0x82671e0872547040fb80e2cc701829c4f98a2080
ZEPValidator is correctly set as a validator on the jurisdiction.
ZEPValidator is cleared for approval of ZEPToken attribute id: 1665201538125898990930
ZEP Org correctly set as an organization in ZEPValidator.
Vouching looks good!!
vouching app looks good!!
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment