Helper utilities for Humanbound

[0xpApaSmURf]

React hooks for Humanbound token helpers.

Use useHumanbound providing an Alchemy configuration with api keys to expose functions that return humanbound token data for supported networks:

Usage:

const alchemyConfig = {
    [1]: "mainnetApiKey",
    [10]: "optimismApiKey",
    ...
};

const Component: React.FC = () => {
    const { hasHBT, getHBTIdOfOwner, getOwnerOf} = useHumanbound(alchemyConfig);

    useEffect(() => {
        const fetchHBTInfo = async () => {
            await hasHbt(address);                    // returns bool
            await getHBTIdOfOwner(address);           // returns uint256
            await getOwnerOf(hbtId);                  // returns string
        };
        
        fetchHBTInfo();
    }, [hasHBT, getHBTIdOfOwner, getOwnerOf]);
}

Currently only supported networks are:

• Ethereum Mainnet: chainId: 1
• Optimism: chainId: 10
• Optimism Goerli: chainId: 420
• Arbitrum One: chainId: 42161
• Arbitrum Goerli: chainId: 421613
• Polygon Mainnet: chainId: 137
• Polygon Mumbai: chainId: 80001

Alchemy config must be provided with api keys corresponding to the networks above for any network that your dApp intends to support. Using useHumanbound on networks that are not supported will throw an error.

[ra-phael]

Really cool! ✨

[ra-phael]

Quite annoying to have to repeat "as Web3ChainReference" so many times 😅

[0xpApaSmURf]

Yeh... I don't think it's much of an issue from a user perspective since it's abstracted away but in any case is there a better way to do this whilst keeping the type?

[ra-phael]

Do you know how this array of events is sorted?

[0xpApaSmURf]

I think it's latest first from what I remember.

[ra-phael]

These checks seem unecessary given what this hook returns, the functions can't be called unless humanbounContract is defined.

[0xpApaSmURf]

Ah yes, this was here before I changed the way the hook was returning

[0xpApaSmURf]

Ah so the compiler doesn't like this because from a type point of view the value of humanboundContract could be null

[ra-phael]

It doesn't apply for hasHBT as it's meant to be has HBT on any network but I wonder if for the 2 other functions we should give the option to pass in a specific network to check. Since HBTs are humanbound and not address-bound theoretically you could have different addresses for a same HBT ID on 2 different networks?

[ra-phael]

Ouuh actually this is checking one network at a time for hasHBT 🤔

[0xpApaSmURf]

Yeh it's checking one network at a time because we're assuming the same kind of stack of web3 providers, which are always one network at a time. It's the simplest IMO.