dorgtech/homebase-lite-app

Homebase Lite App (Deprecated)

Overview

This repository, homebase-lite-app, has been deprecated. All functionalities and future development have been moved to the main repository, homebase-app. This README serves as a guide for developers and users during this transition.

Deprecation Notice

As part of our ongoing efforts to streamline our development process and consolidate our resources, homebase-lite-app is officially deprecated. We have integrated its features and capabilities into the main repository, homebase-app.

For future development, contributions, and updates, please refer to: homebase-app.

Why Deprecate?

The decision to deprecate homebase-lite-app was made to:

• Enhance the overall functionality by consolidating features.
• Provide a unified experience for our users and developers.
• Simplify maintenance and support for our team.

Migration Guide

If you are transitioning from homebase-lite-app to homebase-app, here's what you need to know:

1. Check Out the Main Repository: Visit homebase-app for the latest version and updates.
2. Migrating Your Work: If you have ongoing work or contributions in homebase-lite-app, please migrate them to homebase-app. Instructions for migration are available in the homebase-app repository.

Archiving the Repository

Homebase-lite-app is now in a read-only state. It will no longer receive updates or accept contributions. This is part of the archiving process on GitHub, marking the end of its active development and maintenance.

Before Archiving

• All open issues and pull requests have been resolved or migrated to homebase-app.
• All relevant features and information are transferred to the main repository.

Post-Archiving

The repository will remain accessible for historical purposes, but it will not be updated. For active development and contributions, please use the homebase-app repository.

Additional Information

We appreciate the community's support and contributions to homebase-lite-app. As we move forward with homebase-app, we aim to provide a more integrated and efficient experience for all users and developers.

For any questions or concerns regarding this transition, please reach out to the project maintainers.

References

• Deprecated Repository: homebase-lite-app
• Main Repository: homebase-app

homebase-lite-app's Issues

[Lite] As a user I should be able to see the proposal details

• Get and show all the proposal details from the selected one
• Add “Cast Your Vote” functionality enable if connected address is a DAO Member

Resources
Design: https://www.figma.com/file/3FjWauVMU4H75qJUDafs6q/Homebase-lite?node-id=99%3A121

UI design of token deployment - Deadline March 6

Description (what needs to be done) / Expected Behavior
UI design of token deployment - Deadline March 6

Acceptance Criteria
Token deployment is user friendly and not missing any key functional pieces for the user.

Supporting information (Figma link, notes, etc)

When finished, please add Link to the PR or completed Figma / design asset, as a comment to the ticket.

[Lite] As a connect user I should be able to Create a DAO

• Integrate filled form with the homebase lite contract in order to create a DAO
• Validate that all the fields are required in order to proceed with the creation
• Add loader while the DAO is being created (similar to the one in Homebase App)

Resources

• Design: https://www.figma.com/file/3FjWauVMU4H75qJUDafs6q/Homebase-lite?node-id=120%3A140

Switch Lite to tzkt api

Description (what needs to be done) / Expected Behavior
Switch from bcd to tzkt api to reduce downtime and risk of community creation failing

Acceptance Criteria
Communities are created
We no longer call a deprecated api

Supporting information (Figma link, notes, etc)

Manank completed this switch on the main Homebase app if you have questions.

Issues from Homebase main's switch, if helpful context:
Switch from BCD/tzstats to TZKT: dOrgTech/homebase-app#333
Fix Better Call API Issue: dOrgTech/homebase-app#340

When finished, please add Link to the PR or completed Figma / design asset, as a comment to the ticket.

[Lite] As a DAO Member I should be able to create proposals

• Get Title, Description, Start Date, End Date, Options to Choose and create the proposal
• Validate all the required fields
• Add loader while the proposal is being published
• Handle creation errors

Resources:

• Design: https://www.figma.com/file/3FjWauVMU4H75qJUDafs6q/Homebase-lite?node-id=82%3A28

Token number display on proposals

Description (what needs to be done) / Expected Behavior

On the single proposal view, the frontend should know the decimal value of token and divide the tokens value from the backend with that number

Eg -

100000000000 - Value
Decimal - 6
Display on Frontend - 100000000000/10 ** 6 = 100000

On the proposals summary page for each community, the display for # of tokens voting for each option should calculate as above, and abbreviate the display as follows:

K as a symbol for 1000, and M as a symbol for 1,000,000 (one million)
Eg -If there were 10,207,430 tokens voting yes, that would display as 10.2M. If 1200, display 1.2K. If 1022, display 1K.

Acceptance Criteria
The individual proposal page shows the above notation format, and the proposals summary page shows the above abbreviation format.

Supporting information (Figma link, notes, etc)

When finished, please add Link to the PR or completed Figma / design asset, as a comment to the ticket.

[Lite] Display the Community on create proposal page

Description (what needs to be done) / Expected Behavior

(dependency: wireframe from designer)

Display the Community name and image on the create a proposal page so it's clearly visible which community you are proposing to.

Acceptance Criteria

The correct community is displayed when the user clicks in to make a proposal.

Supporting information (Figma link, notes, etc)
Waiting for Figma wireframe

When finished, please add Link to the PR or completed Figma / design asset, as a comment to the ticket.

Take signatures

Description (what needs to be done) / Expected Behavior
Take signatures so user signs with their private key at every step, to verify it's from the right person.

Acceptance Criteria
When a user creates a new DAO, when they make a proposal, and when they vote, they sign with their wallet address. That means the app prompts the wallet for an action which results in a string that is encrypted using the user's private key. That string is sent back from the wallet to the app, and then stored along with the other fields of the vote, so that it may be pulled up at a later time for verification. The thing that gets encrypted needs to uniquely identify the proposal on which the user is voting, so it may be a concatenation of the DAO name, the proposal name, the date and time, the user's public address and their vote option.

Supporting information (Figma link, notes, etc)

When finished, please add Link to the PR or completed Figma / design asset, as a comment to the ticket.

[Lite] As a user I should be able to see all the available DAOs and search through them based on DAO Name

• Get and show all the v2 available DAOs
• While DAOs are being retrieve show a loading placeholder for better UX
• Default order should be: High amount of members to Low amount of members
• Validate if connected address it’s already a member in order to Display “Leave” or “Join”
• Search/Filter through the v2 available DAOS based on DAO name
• Show total “community” (DAOs) available
• Add Create Community trigger action

Resources:

• Design: https://www.figma.com/file/3FjWauVMU4H75qJUDafs6q/Homebase-lite?node-id=11%3A2
• https://tezostaquito.io/ (web3 tool for tezos)
• https://github.com/dOrgTech/homebase-app/tree/master/src/modules/explorer

[Lite] Setup Vercel Autodeploy

[Lite] As a user I should be able to get DAO details

• Validate if connected address it’s already a member in order to Display “Leave” or “Join”
• Add “New Proposal” trigger action if connected address is a DAO member
• Get and show all the historical proposals from the selected DAO and display:
  Description
  Status
  Who created it
• Proposal list should be ordered by the most recent to the oldest
• Add Dropdown Filter with the following options:
  All
  Passed
  Rejected
  (...)

Resources:

• Design: figma.com/file/3FjWauVMU4H75qJUDafs6q/Homebase-lite?node-id=11%3A70
• https://tezostaquito.io/ (web3 tool for tezos)
• https://github.com/dOrgTech/homebase-app/tree/master/src/modules/explorer

[Lite] Integrate Homebase Lite contracts (General Research about implementation)

This task is related to research about Homebase Lite contracts specifications and the integration with the new Homebase Lite FrontEnd dApp.

The expected result of this ticket should be to generate more specific tasks for the complete contract integration within the dApp.

Resources:

• https://github.com/tezos-commons/homebase-lite
• https://github.com/tezos-commons/homebase-lite/releases/tag/v0.1.0
• https://github.com/dOrgTech/homebase-app contract ref

Proposal window validation for both start and end time

Description (what needs to be done) / Expected Behavior

Start and end time of proposal should not allow dates prior to now, down to the minute.

Acceptance Criteria

Start and end times of proposal have two validations:

• disallow past (only allow future)
• end time must be greater than start time
• the interval between stars and end can't be shorter than 5 minutes or longer than 14 days (for now).

It would be nice to have an error message for each type of validation fail. So if they put less than 5 minutes it can show "can't allow less than 5 minutes for voting". But if that's too much for now we can just have a text box where we specify the minimum and maximum interval for voting.

Design UI elements (what certain buttons or graphics do when you click them) from Luis' questions in Figma

[Lite] As a user I should be able to connect my wallet

• Add “Connect Wallet” functionality (i.e Temple)
• Persist reconnection after reload
• Ability to Log Out (Disconnect wallet)

Resources:

• Design: https://www.figma.com/file/3FjWauVMU4H75qJUDafs6q/Homebase-lite?node-id=11%3A2
• https://tezostaquito.io/ (web3 tool for tezos)
• https://www.npmjs.com/package/@taquito/beacon-wallet
• Temple Wallet

[Lite] Add a snippet of each proposals' descriptions on the community page's proposal feed

Name pops out of the div if too long in new proposal page

Name
The name of the DAO comes out of the div if too long - this happens on the proposal page.

Description (what needs to be done) / Expected Behavior
Make the div dynamic

Acceptance Criteria
should not mess up the div

Supporting information (Figma link, notes, etc)

When finished, please add Link to the PR or completed Figma / design asset, as a comment to the ticket.