|
October 26, 2018, 11:18:09 AM |
|
Hey there,
ok this may be a bad idea, but has anybody ever considered building a dApp on a regular webserver/database? Projects are centralized around the founding team anyway, and the worth of a token pretty much entirely depends on how well they do their job.. so it doesn't seem to make a big difference if the app and token is initially running on their server instead of a trustless architecture. Especially if the goal is to decentralize the foundation itself, e.g. by involving the community as much as possible and having all decision-making done collectively by stakeholders. The foundation that runs the server would then be represented by the whole community and become less of a centralized entity.
This would help with many of the issues that prevent wider user adoption, like having regular username/password authentication, account recovery, name system, no fees, no speed and scaling issues, no need to set up metamask and have eth to engage, easier way of staking tokens (thus higher voter turnout), and many more things that would improve the user experience and with it the social decentralization. Having the software open source and data fully transparent would make it publicly auditable and even give the community the ability to fork to a new server when desired. As soon as platforms like Ethereum or Bitcoin Layer2 have matured, the dApp could then be migrated there later on.
Admittedly this further centralizes the trust model towards the foundation initially, but it may be worth the trade-off for various use-cases. Would love to hear some opinions, especially about the legal aspects when issuing a token on a regular server instead of a blockchain..
cheers mrpug
|