Grant Tool Collab: Allo Protocol

[Rashmi-278]

No description provided.

[linear]

STK-163 Grant Tool Collab: Allo Protocol

[Rashmi-278]

Henry from Gitcoin Mentioned that Allo 2.1 is still in Audit Stage

[Rashmi-278]

From thelostone-mc | gitcoin

Hey @rashmivabbigeri !
So henry gave us the TLDR:

• He's done a mapping of the fields we use and what's the proposed metadata standard
• A few details aren't stored in our metadata schema like start and end dates as we store them on-chain. We had intentionally done this as we've got on-chain logic which would require this data.
• Additionally few of these params would updated by the person managing the round. Earlier on we did an exercise and realised it didn't make sense to store the same information in the metadata and on-chain if it's something which would likely be updated (else we'd have to update the metadata any time we change the on-chain variable)
• This means we won't be able to update our schema to exactly match the standard set by metagov

BUT

When allo stores an metadata, it uses something called a Metadata struct
https://github.com/allo-protocol/allo-v2/blob/main/contracts/core/libraries/Metadata.sol
Which has

• protocol: an integer (1 == gitcoin's metadata structure )
• pointer : usually the IPFS hash where the data is stored

@MasterHW proposed reserving protocol 2 for the metagov standard and this would enable gitcoin to support both formats
This also means that as more folks adopt the standard -> they would be able to port / sync their data onto allo.
I think this is a solid way to showing that Gitcoin also supports standard set by DAOIP5 and ensures the gitcoin dapps continue to work as expected with. both structures