Skip to content

Verify StoryFactory and ZapPlotLinkV2 on Basescan #540

@realproject7

Description

@realproject7

Summary

Run Basescan contract verification for both StoryFactory and ZapPlotLinkV2 using the BASESCAN_API_KEY set in the plotlink-contracts `.env` file.

Commands

```sh

StoryFactory (use new deployed address)

forge verify-contract <NEW_STORY_FACTORY_ADDRESS> src/StoryFactory.sol:StoryFactory
--chain base
--etherscan-api-key $BASESCAN_API_KEY
--constructor-args $(cast abi-encode "constructor(address,address,uint128,uint128[],uint128[],uint256)" )

ZapPlotLinkV2 (existing address)

forge verify-contract 0xAe50C9444DA2Ac80B209dC8B416d1B4A7D3939B0 src/ZapPlotLinkV2.sol:ZapPlotLinkV2
--chain base
--etherscan-api-key $BASESCAN_API_KEY
--constructor-args $(cast abi-encode "constructor(address)" <PLOT_TOKEN_ADDRESS>)
```

Notes

  • BASESCAN_API_KEY is already set in `plotlink-contracts/.env`
  • StoryFactory verification needs the new address after redeploy
  • ZapPlotLinkV2 constructor arg is the PLOT token address (use the original PL_TEST address it was deployed with, NOT the new one set via setPlotToken)

Acceptance Criteria

  • StoryFactory verified on Basescan with source code visible
  • ZapPlotLinkV2 verified on Basescan with source code visible

Metadata

Metadata

Assignees

No one assigned

    Labels

    agent/T3Assigned to T3 builder agent

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions