The Crypto Native Portal, an app that creates a mechanism to financially acknowledge the micro contributions of Open Source collaborators along with tools that promote effective governance.
A centralized smart contract is when we have a DAPP where it's a DAPP for every team. So each one don't have to worry about deployment or update.
A Decentralized is when every team have his own DAPP and is responsible of his management.
Actual situation
We have some's issues with the decentralized smart contract who is the first option we chose.
The problem come from the process of deployment.
Context: We have a Bank Smart contract, that when deployed using hardhat is working well. But to have the decentralized way, the final user need to have the ownership.
Now 3 way of doing it.
Deploy the implementation with hardhat and make the user deploy only the proxy.
Deploys The implementation and the proxy with a backend that use OUR Private Key, then transfer the ownership to the user, by charging him.
Deploy by the backend but the user sign the transaction.
We try the first one and there is the issue we have :
We can't retrieve information from the proxy deployed in the frontend.
We don't have any bytecode in the app deployed on etherscan.
Now the goal is to
[x] Find if we can fix the issue in the frontend deployment
[ ] Try the other option we have and see if we can implement one of theme.
Description
Def
Actual situation
We have some's issues with the decentralized smart contract who is the first option we chose. The problem come from the process of deployment.
Context: We have a Bank Smart contract, that when deployed using hardhat is working well. But to have the decentralized way, the final user need to have the ownership.
Now 3 way of doing it.
We try the first one and there is the issue we have :
Now the goal is to
Acceptance Criteria