$ npm install
$ npm run start
- Quick developement in a fast paced hackathon project
- Create dapp using create-react-app.
- Chainlink, ipfs, smart contract, Open Zepplin
- Hyperlane
- React + moralis,
- Database, flask, REPLIT backend
Currently anyone can propose a referendum by depositing the minimum amount of tokens for a certain which is eventually refunded.If someone agrees with the proposal, they may deposit the same amount of tokens to support it - this action is called endorsing. The proposal with the highest amount of bonded support will be selected. But for instance, three accounts bonding 20 DOT each would "outweigh" ten accounts bonding a single DOT each and also if the lock period for one is less than the other, leads to their voting power counting as less. And since many low level accounts don't feel comfortable with locking it for an indeterminate amount of time hence it becomes a problem.
- This financial barrier stifles overall blockchain improvement by preventing many good ideas from being submitted
- Because of the high fees, many community members do not vote on the proposal, which is represented in the governance process as a lack of representation of members who do not have enough coins. This, in turn, Centralizes authority in the hands of stakeholders with more currency.
- A good suggestion that exclusively caters to members with fewer coins may go overlooked.
- Using Hyperlane we made the platform more accessable as it's functionalities are extended to multiple chains, and one doesn't need tokens from specific chain to make contribution to the governance.
A Preliminiary Opinon poll is an unofficial poll that usually takes place before a official governance poll.
Our "Pre Governance" Dapp is a intuitive and a community-based web solution that lets users submit, read, discuss and interact with proposals published by other users. The exciting part is that the web platform is avaible across multiple chains thus making it more easily available
The app collects proposal information (i.e. likes, dislikes, proposer etc) on-chain. Users can read, vote and discuss the proposals. Further, the top voted proposal is submitted for official governance periodically. This information is then conveyed across all the associated chains.
We started with deploying the smart-contract on Replit. The smart contract records the details of the proposals and encloses a wide variety of usable functions that provide decentralization to our project.
Then, we build the front-end. We designed the website on figma keeping in mind user accesibility. The frontend is written in react. We used moralis hooks to connect our smart contract to metamask wallet and to call methods on the smart contract. We have also added packages that provide personalised profile pictures.
Hyperlane connects your applications across many blockchains. This allows users to interact with your application from the chain they're on. Reducing the amount of hoops they have to jump through just to get to your app. It's about abstracting away the complexity of navigating between chains, and letting you and your users simply focus on your app. Here Hyperlane plays a important part as it help the platforms to be function on multiple chains, thus being true to the original purpose of being easy to access. Here, we use QueryAPI provided by hyperlane to call function across both moonbase alpha and goerli testnets.
We store the proposal metadata on-chain using ipfs leveraging pinata apis.
Each proposal has a discussion page, where users can post comments on the proposal, and vote on other users' comments. These discussions are stored in a SQL database connected through REST API built on Flask.
As beginners in web3.0 development attempting to build a solution from scratch, we faced a lot of challenges. We learn a lot in the way and overcame most of the challenges!
Transfering data across chains can be tricky, but hyperlane solved the issue neatly. Though this issue was made easy, it was quite a learning experience as it was our first time trying to tranfer assests across chains. The docs and the discords channels were a great help.
Storing data on chain comes with an extra cost in the form of fees that has to be paid by the user. Data such as the discussion under a proposal can be stored in centralized database with no issues.
The proposal hash is already on the chain which can be used to verify that the proposal is unaltered.
We wanted to use a chainlink keeper to periodically call the pushToGovernance() function, but the support is not yet availabe.
We found a workaround by using Open Zeppelin Defender.
On running into all the challenges mentioned above, we read relavant articles, documentations and other literature for days, and finally built a working solution!
Transfering data, though made simple using hyperlane, is a very powerful tool. We are proud to make use of this to make the platform available across various chains.
Proposal metadata is put on IPFS. Discussion is built on flask and stored in SQL database. We decided not to put user comments on chain to save gas fees.
We designed a web solution that is more intuitive to use and interact with for users belonging to both technical and non-technical backgrounds.