March 31, April 1st, April 2nd 2023
Organizers: Think and Dev
Location: Cordoba, Argentina
- Luciano Martin Garriga
- Franco Cerino
- Federico Rascon
- Benjamin Juarez
- Neri Bocchi (Ripio)
- Juan Ignacio Bocchi
Painpoint detected: Services that have intermediaries always have an additional cost. So some payment systems entail a process in which, one party A pays to B, who then pays to C.
Solution Approach: The workaround in web3 is that sometimes not all parties are required. So payer A can send assets directly to C without intermediary B. This allows for quicker processes and less expensive ones.
Contextual Solution: In the local context of this project, the development aims to comply with legal regulations, which may require that the intermediary party still exists. If the project includes this party, B, then the web3 solution we propose could still provide more transparency and traceability to the process.
Use Case: The proposed development here is a payment system, that includes custody and distribution, aiming to simplify payments for the end users (A and C) and make the process more efficient. The dApp (decentralized Application) could do without centralized intermediaries.
Goal: Reduce costs and speed up and secure financial transactions. Operations become transparent and public, and every payment shows its traceability with the origin and destiny of funds.
The context and use case described above is only a fraction of what this analysis can tackle. The pain point is generic, and the use case for payments can be found in a wide array of situations.
The dApp can be used in any field in which payers and receivers coexist: employees, partners, collaborators, etc. The dApp can be used in environments such as corporations, collaborations, and businesses.
A very common use case is the control of communal expenses that are handed into a fund and then used to pay expenses of the building, services, and employee salaries.
The idea from the project kick-off is to give a web3 solution that can be useful to a massive audience. Between the 1st party A, and the end user C the ideal plan would be to have FIAT payments and FIAT cashouts. Everything that happens in the middle should be fueled on the blockchain with Smart Contracts which make the flow secure, traceable, and simple.
The system is aimed to be used with FIAT users with no knowledge of web3:
- Tenants
- Employees
- Admins
The user experience is expected to be as seamless as any web2 application, with the gains of working with web3 in the background.
What happens if:
- a tenant doesn't pay enough to cover the costs of the fund: salaries, or destination accounts? There could be a penalty such as a partial claim. Such tenants should also cover the fees for the transaction costs of activating the smart contract.
- a tenant changes? or a tenant leaves and no one replaces them for a period of time?
The spirit of the brand is to convey a serious tone in which users can rely on a system without thinking about how the technicalities workaround in the background. Blue is a cold color that represents objectivity, and calmness and does not raise alarms. The tones that aim to represent this perspective is a palette that is at the same time: simple, quick, effective, and most importantly secure and transparent.
- Color Palette from coolors.co: LINK here
- Idea Concept
- Branding
- Product Naming
- Logo
- Color Palette
- Readme Documentation version 1
- SmartContract: Smart contract deployed en Testent Polygon
- Research Frontend: libraries, examples, etc. Build the Dapp and connect Wallet
- Business Rules: Review case scenarios in which the tenants, and representative/leader of the community, may need to consider special situations such as extraordinary expenses.
- Installation and Deploy Guide
- List of used technologies, with links
- Bug acknowledgment and possible error corrections
- Frequently Asked Questions (FAQ)
- Copyrights, licenses, and legal considerations
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent