Related Issue

• Information about the related issue

Closes: #

Describe the changes you've made

Type of change

What sort of change have you made: Added a transparent logo.

• [ ] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Code style update (formatting, local variables)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [ ] Documentation update.
• [ ] This change requires a documentation update

How Has This Been Tested?

Checklist

• [x] My code follows the guidelines of this project.
• [x] I have performed a self-review of my own code.
• [x] I have commented on my code, particularly wherever it was hard to understand.
• [x] I have made corresponding changes to the documentation.
• [x] My changes generate no new warnings.
• [x] I have added tests that prove my fix is effective or that my feature works.
• [x] Any dependent changes have been merged and published in downstream modules.

Screenshots (if applicable)

Original | Updated :--------------------: |:--------------------: original screenshot | updated screenshot |

Code of Conduct

• [ ] I agree to follow this project's Code of Conduct

What would you like to share?

Hey @mkubdev, I think it's good to add a license for this repo.

Additional information

No response

Would you like to work on this issue?

• [X] Yes, I want to work on this issue!

Code of Conduct

• [X] I agree to follow this project's Code of Conduct

Describe the changes you've made

Add: New homepage + Tailwind + Lottie animation

Type of change

What sort of change have you made:

• [ ] Bug fix (non-breaking change which fixes an issue)
• [x] New feature (non-breaking change which adds functionality)
• [ ] Code style update (formatting, local variables)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [ ] Documentation update.
• [ ] This change requires a documentation update

How Has This Been Tested?

Same as before.

Checklist

• [x] My code follows the guidelines of this project.
• [x] I have performed a self-review of my own code.
• [x] I have commented on my code, particularly wherever it was hard to understand.
• [x] I have made corresponding changes to the documentation.
• [x] My changes generate no new warnings.
• [x] I have added tests that prove my fix is effective or that my feature works.
• [x] Any dependent changes have been merged and published in downstream modules.

Screenshots (if applicable)

Original | Updated :--------------------: |:--------------------: | |

Code of Conduct

• [x] I agree to follow this project's Code of Conduct

What would you like to share?

The first iteration of the dao dapp is running on Rinkeby Testnet. ETH gasfee are super high, maybe we should switch to Mumbai testnet ?

Additional information

No response

Would you like to work on this issue?

• [ ] Yes, I want to work on this issue!

Code of Conduct

• [X] I agree to follow this project's Code of Conduct

Detailed description

On index.js file :

  const [hasVoted, setHasVoted] = useState(false);

...

const checkIfUserHasVoted = async () => {
      try {
        // Actually it only check the first proposal, we need to check all proposals
        // and dispatch states
        const hasVoted = await vote.hasVoted(proposals[0].proposalId, address);
        setHasVoted(hasVoted);
        ...

We check only the first DAO proposals !

I suggest to update this function and the setHasVoted state logic to be able to list all proposals states.

Context

This is a requiered feature because the dapp actually set state only for the first proposal.

Possible implementation

Maybe we can make something like :

  const [hasVoted, setHasVoted] = useState([]);

...

 proposals.forEach(proposal => {
      const hasVoted = await vote.hasVoted(proposal.proposalId, address);
      setHasVoted( ... );
})

Additional information

No response

Code of Conduct

• [X] I agree to follow this project's Code of Conduct