[erc721-contract-call] feat: erc721-contract-call

[abysnart]

xSGT NFT Voting Power Strategy

Overview

This PR introduces a new voting strategy for NFTs where each token ID has a specific voting power. The strategy is useful for NFT-based governance where different token IDs carry different voting weights.

Use Case

The strategy enables Snapshot spaces to support voting with NFTs where:

• A user may hold multiple NFTs with different token IDs
• Each token ID can have a different, predefined voting power (e.g., token ID 1 = 1 vote, token ID 2 = 9 votes)
• The voting power for each token ID is stored in the NFT contract itself

Contract Requirements

The NFT contract must implement:

• tokensOfOwner(address _owner) external view returns (uint256[]) - Gets all token IDs owned by an address
• getVotingPower(uint256 _tokenId) external view returns (uint256) - Gets the voting power for a specific token ID

Implementation Details

The strategy:

1. Retrieves all token IDs owned by each voting address
2. Fetches the voting power for each token ID from the contract
3. Sums up the total voting power per address

Testing

I've tested this strategy with the xSGT NFT contract (at address 0x...) and confirmed that it correctly calculates voting power based on token ID weightings.

Changes

• Added strategy TypeScript file
• Added schema.json for configuration validation
• Added example.json for reference implementation

Thank you for reviewing!

[ChaituVR]

should be same as strategy name

[ChaituVR]

actually the name xsgt-nft-voting-power makes more sense than erc721-contract-call

[ChaituVR]

Lint / tests are failing in this fail, could take a look?