website: update Community Vouchers FAQ

This commit is contained in:
Evgeny Poberezkin
2025-11-03 08:28:39 +00:00
parent f6bb645825
commit f5d73e979b
+47 -20
View File
@@ -12,6 +12,10 @@ Group or channel owners can select network operators for better reliability and
These vouchers are blockchain utility tokens — to focus purely on server capacity usage, like prepaid telephone cards.
**What these tokens are not**: Community Vouchers are not freely tradable tokens. They are also not a way to raise funds.
**What they are**: A mechanism to pay for servers, privately. Our goal is to make it possible to buy Community Vouchers via usual credit card and in-app payments, so that everybody can use them, not only people who use cryptocurrencies.
## SMPX: Community Voucher Token planned for 2026
<a href="javascript:void(0);" data-show-overlay="mint-simplex-nft" class="open-overlay-btn"><img src="/img/design_3/simplex_nft_smpx.jpg" width="200" class="float-to-right" style="border-radius: 10px;"></a>
@@ -34,10 +38,27 @@ We're working with blockchain and legal experts for feasibility and compliance,
To receive updates, sign up via email or connect to us [via SimpleX Chat](https://smp6.simplex.im/a#lrdvu2d8A1GumSmoKb2krQmtKhWXq-tyGpHuM7aMwsw).
## Community Vouchers FAQ
## Community Vouchers FAQ &mdash; send your feedback
These are early insights into how Community Vouchers can work &mdash; some of these ideas are still vague; they will evolve based on your feedback and testing.
- [Why Community Vouchers?](#why-community-vouchers)
- [Free Tier?](#free-tier)
- [How Will Vouchers Work?](#how-will-vouchers-work)
- [Will self-hosted servers still be supported by SimpleX network?](#will-self-hosted-servers-still-be-supported-by-simplex-network)
- [What problems Community Vouchers solve that other payment methods can't?](#what-problems-community-vouchers-solve-that-other-payment-methods-cant)
- [How is it possible to provide privacy on public blockchain?](#how-is-it-possible-to-provide-privacy-on-public-blockchain)
- [Will Community Vouchers be pre-sold via private or public sale?](#will-community-vouchers-be-pre-sold-via-private-or-public-sale)
- [Who will sell vouchers?](#who-will-sell-vouchers)
- [How the server operator revenue share is determined?](#how-the-server-operator-revenue-share-is-determined)
- [Who will control and upgrade smart contracts?](#who-will-control-and-upgrade-smart-contracts)
- [Will I be able to sell or transfer Community Vouchers to other people?](#will-i-be-able-to-sell-or-transfer-community-vouchers-to-other-people)
- [Why Not Existing Crypto?](#why-not-existing-crypto)
- [Why build on Ethereum blockchain?](#why-build-on-ethereum-blockchain)
- [Have you considered other blockchains?](#have-you-considered-other-blockchains)
- [Why use ERC20 specification? Isn't it designed for freely tradable tokens?](#why-use-erc20-specification-isnt-it-designed-for-freely-tradable-tokens)
- [If you build on another blockchain, how the NFT will be used to provide access?](#if-you-build-on-another-blockchain-how-the-nft-will-be-used-to-provide-access)
### Why Community Vouchers?
<img src="/img/design_3/community_vouchers_light.jpg" width="38%" class="float-to-right dark:hidden">
@@ -51,7 +72,7 @@ With "free" centralized platforms:
- they de-platform inconvenient users, often based on frivolous complaints.
- you don't own all rights to your content.
Paying for server capacity is cheaper than "free" platforms. Our estimates based on the current costs are $5-10/month for 5,000 active message receivers (could be up to 50,000 listed community members) with 5-10 GB of files/media archive. These estimates are preliminary and may change.
Paying for server capacity may be cheaper than "free" platforms. Our estimates based on the current costs are $5-10/month for 5,000 active message receivers (could be up to 50,000 listed community members) with 5-10 GB of files/media archive. These estimates are preliminary and may change.
### Free Tier?
@@ -59,7 +80,7 @@ It will be determined after testing. Preliminarily, we expect up to 1,000 active
"Active message recipient" in this model is a group member who periodically connects to the network, and receives group messages. Members who are listed but don't open the group for some time, for example two weeks, will stop receiving all group messages even when they are connected to the network. This is an evolving design that will balance security for group members and owners, to avoid inflated expenses, and to present realistic membership statistics to the group owners and to prospective members.
Private messaging with contacts and in private groups within "fair use" limits we apply today will remain free:
Private messaging with contacts and in private groups within "fair use" limits that we apply today will remain free:
- there can be up to 128 undelivered messages per destination,
- the undelivered messages are stored up to 21 days,
- files up to 1 GB can be sent for free,
@@ -67,21 +88,18 @@ Private messaging with contacts and in private groups within "fair use" limits w
Larger limits may be offered in paid tier, but it is not planned initially &mdash; the focus of Community Vouchers is to create a commercial model for communities.
### How Might Vouchers Work?
### How Will Vouchers Work?
Buy via app (like phone top-ups), with unused capacity shown in the app.
Buy via app (like phone top-ups), with unused capacity shown in the app. An important design goal is to make Community Vouchers available to people who don't use any cryptocurrencies.
Testnet is likely to use hashed IDs for privacy and on-chain payments, to validate the pricing and economic model. Zero-knowledge proofs and in-app payments will be added by the time production network is launched.
### Will self-hosted servers still be supported by SimpleX network?
Yes, absolutely. Not only we will continue to provide support to self-hosted servers, but we will improve it. We see network decentralization and server portability as exceptionally important, and while we need to develop a robust commercial model for the servers, we still need community supported servers to function, with all servers operating in single network.
It will be possible for all users:
- to join paid groups that use Community Vouchers via your own servers.
- to join groups that are run on free community-hosted servers.
- to create new server operators (collections of servers operated by one entity), so that the same features that are now available only for preset servers will be available to all servers very soon.
Yes, absolutely. Not only will the apps continue to support self-hosted servers, but we will improve it. We see network decentralization and server portability as very important, and while we need to develop a robust commercial model for the servers, we still need community-hosted servers to function, with all people using a single network:
- users who use self-hosted servers will be able to join groups that use pre-configured servers or Community Vouchers.
- users who use pre-configured servers will be able to join groups that are run on free community-hosted servers, same as today.
- you will be able to create new server operators (collections of messaging and file servers operated by one entity), so that the features currently available only for preset servers will be available to all servers very soon, and all servers that you and your community members want to use can be added to the app by scanning a QR code.
### What problems Community Vouchers solve that other payment methods can't?
@@ -101,20 +119,29 @@ While specific designs are in early stages, here are some of the principles that
- all operations on blockchain will be supported by network servers that will run full blockchain nodes. For important requests, such as name resolution, the clients will use 2 or 3 independent servers, to ensure protection from MITM attacks.
- blockchain operations will be proxied, in the same way as it happens with private message routing.
We will be publishing the whitepaper with this design. It will provide an unprecedented level of security and privacy for blockchain applications, irrespective of which chain we choose to use.
We will be publishing the whitepaper about this design. It will provide an unprecedented level of security and privacy for blockchain applications, irrespective of which chain we choose to use.
### Will Community Vouchers be pre-sold via private or public sale?
### How many Community Vouchers will be pre-sold and available during public sale?
There will be no Community Vouchers pre-sold or in any other way made available to the team, or to investors or to the public.
None. There will be no Community Vouchers pre-sold or in any other way made available to the team, or to investors or to the public.
Any blockchain token that is pre-sold to insiders and/or to the public with the objective to raise funds to develop technology is not a utility token, regardless of how it's named &mdash; it becomes an investment contract that passes [Howey test](https://www.investopedia.com/terms/h/howey-test.asp).
Any blockchain token that is pre-sold to raise funds to develop technology is not a utility token, regardless of how it's named &mdash; it becomes an investment contract that passes [Howey test](https://www.investopedia.com/terms/h/howey-test.asp).
This is not what we are doing. Community Vouchers are restricted utility tokens, not an investment contract. They will be only issued on demand to people who want to pay for network servers, at a fixed price.
### Who will sell vouchers?
Community Vouchers will be sold via a smart contract in exchange for some other tradeable tokens, most likely stablecoins. We don't plan token emission, or any public or private pre-sales. And we won't have access to the funds from voucher sales &mdash; they will be locked in a smart contract, and only released once servers have provided capacity to the users, with the funds shared between server operators and SimpleX network, with operators receiving up to 60%, depending on trust evaluation. SimpleX network funds will be managed by smart contracts, and will be used for governance and development as defined by the contracts. Their price will be fixed based on server costs, with the exact economic model developed during testing phase.
Initially, Community Vouchers will be sold via a smart contract in exchange for some other tradeable tokens, most likely stablecoins. We don't plan any token emission, or any public or private pre-sales. And we won't have access to the funds from voucher sales &mdash; they will be locked in a smart contract, and only released once servers have provided capacity to the users, with the funds shared between server operators and the SimpleX network, with operators receiving up to 60%, depending on trust evaluation. The SimpleX network funds will be managed by smart contracts, and will be used for governance and development as defined by the contracts. Their price will be fixed based on server costs, with the exact economic model developed during the testing phase.
### How the server operator revenue share is determined?
It will be based on the goal that servers must provide both reliability and security to the users. Security in any multi-node network depends on users' ability to choose independent servers that are provided by different entities, and the apps are already programmed not just to use different servers for the message delivery path, but to use servers of different operators. Even though currently there are only 2 preset operators &mdash; SimpleX Chat and Flux &mdash; and all servers added to the app by the user are considered a third operator, it substantially improves privacy and security.
In the future, the operators that confirmed their identity to the network will receive a much higher revenue share than anonymous ones. We believe that for users to be private and secure, operators must be known, and must accept legally binding terms of operation, same as preset operators do today.
The other two factors that will affect "trust evaluation" will be how long the operator was available on the network and servers' availability uptime. Similar to how we monitor the uptime of our servers, the network will monitor the uptime of all servers, and it will affect the revenue share.
We don't have an exact model for revenue sharing yet; it will be determined during testing and will evolve based on feedback from users and server operators.
### Who will control and upgrade smart contracts?
@@ -132,7 +159,7 @@ Community Vouchers are designed with a single purpose &mdash; to facilitate paym
Existing cryptocurrencies do not allow the implementation of the required model for Community Vouchers. The price of cryptocurrencies is determined speculatively, and not based on costs. The fact that they can be freely traded and transferred exposes existing cryptocurrencies and tokens to financial regulations.
The existing cryptocurrencies such as XMR, BTC and some others are very likely to be accepted as payment for Community Vouchers, via bridges, but they cannot be used in the foundation of the system, because they are not as flexible as smart contracts, and cannot directly support the model we are developing.
The existing cryptocurrencies such as XMR, BTC and some others will be accepted as payment for Community Vouchers, via bridges, but they cannot be used in the foundation of the system, because they are not as flexible as smart contracts, and cannot directly support the model we are developing.
### Why build on Ethereum blockchain?
@@ -146,7 +173,7 @@ This was our assessment as well in the past. But the last three years changed it
We are actively considering which blockchain to build on. Ethereum ecosystem is the most widely adopted, and has very mature systems and tools, and it appears sufficient, but it has its downsides, as does everything. So we are not yet committed to Ethereum.
### Why use ERC20 specification &mdash; isn't it designed for freely tradable tokens?
### Why use ERC20 specification? Isn't it designed for freely tradable tokens?
[ERC20 token specification](https://eips.ethereum.org/EIPS/eip-20) has wider scope. It is very simple, one of the earliest, and the most adopted standard on EVM blockchain. It defines tokens, but they don't have to be freely tradeable &mdash; the specification allows any extensions and restrictions implemented on top of it.