[AIP-11] Allow round creation via Registry

[thelostone-mc]

Based off the discussion off : https://github.com/orgs/allo-protocol/discussions/8
PR : #19

[gravityblast]

Updating the project struct to include projectMetadata provides a more comprehensive representation of projects

The project struct already has the metadata pointer, so do you mean just rename it from metadata to projectMetadata?
I think it would be redundant since it's already inside the Project struct, so I would prefer project.metadata than project.project_metadata

[gravityblast]

Introduce the updateProjectMetadata function in the Registry contract to allow updates to project metadata.

The registry already has this function:

    function updateProjectMetadata(uint256 projectID, MetaPtr calldata metadata) external onlyProjectOwner(projectID) {

[gravityblast]

• Update the metadata event to emit the metadata type.

The even already has the metadata type in the pointer

    event MetadataUpdated(uint256 indexed projectID, MetaPtr metaPtr);

[0xKurt]

@gravityblast
The proposed change involves removing the Program contracts and introducing a second metapointer to the Project Struct. This means that a Project will now have both a project-metapointer, as before, and an additional program-metapointer.

Since a second metapointer is introduced, a new function for the second metapointer is added. To simplify the implementation, a single event is used when updating a metapointer. To distinguish between the two metapointers, a type (enum) is introduced, indicating whether the updated metapointer corresponds to the Project or Program metapointer.

[gravityblast]

I don't think it makes sense to have programMetadata inside the project struct, since most of the project won't have a program, they will be simple projects.

It makes sense to have a different mapping with projects => program initialized when a project creates a round.

[gravityblast]

Since a second metapointer is introduced, a new function for the second metapointer is added. To simplify the implementation, a single event is used when updating a metapointer. To distinguish between the two metapointers, a type (enum) is introduced, indicating whether the updated metapointer corresponds to the Project or Program metapointer.

@KurtMerbeth ok so we should update the document because now it says:

- Update the project struct to include projectMetadata for a more comprehensive representation of projects.

Introduce the updateProjectMetadata function in the Registry contract to allow updates to project metadata.

so maybe they need to be renamed to "update Program metadata"?
or do we need to change the text to add a parameter to the already existing methods?

[thelostone-mc]

@gravityblast You are right. I had confused the name while writing the AIP.
We are adding a new updateProgramMetadata. Like you mentioned we already have updateProjectMetadata.
Updated the AIP

[gravityblast]

nice thank you @thelostone-mc ! ❤️