• © Goverland Inc. 2026
  • v1.0.8
  • Privacy Policy
  • Terms of Use
Kwenta Kwenta by0x0c4EA5F0219fbC4Decf9536463524953Cd75F0cB0x0c4E…F0cB

KIP-109: Endorse both centralized and decentralized deploys

Voting ended about 2 years agoSucceeded

Simple Summary

Add a centralized deployment option next to the existing decentralized deployment.

Abstract

Next to offering a decentralized deployment under the officially endorsed ipns://kwenta.eth/ ENS domain resp. https://kwenta.eth.limo, offer users the alternative option to use the frontend deployed through a centralized entity at https://kwenta.io

Motivation

While Kwenta officially endorses decentralized protocols and deployments, and the source code is open source and can be run locally on any machine or through IPFS, given the yet to mature technology surrounding IPFS and irregular hiccups experienced with it.

It only makes sense to have the code deployed on a centralized entity that allows us to offer a specialized, secure and fast deployment alternative. It also gives users an additional options to experience the Kwenta frontend might one or the other option experiences DDos attacks or downtime.

Specification

For more information, visit the: Kwenta State Log

Off-Chain Vote

Pass
4 stKwenta100%
Reject
0 stKwenta0%
Download mobile app to vote

Timeline

Dec 18, 2023Proposal created
Dec 18, 2023Proposal vote started
Dec 25, 2023Proposal vote ended
Dec 25, 2023Proposal updated