design decisions - atticplaygroup/prex GitHub Wiki
As previously discussed, a cloud-based solution is preferred because it doesn't require operators to have a full stack of skills and facilitates easy service switching.
PAID services can be considered decentralized applications (dApps) but without consensus mechanisms. Consensus is costly and essential when handling valuable assets to prevent potentially significant losses. However, in PAID services, user agents minimize the amount of deposits held within any Prex instance. This helps control the potential financial loss in case of default.
Traders using Prex instances, however, are encouraged to withdraw funds frequently and consider the risk of the Prex instance defaulting.
As mentioned the Permissionless section, PAID services don't require human verification to defend against Sybil attacks because all operations involve payment.
It is preferable to permit the resale of access tokens by traders. They can contribute to price stabilization while ensuring the revenue of service providers, fostering a healthy market for all involved parties.
Denial-of-service attacks are possible if a trader accumulates a significant quantity of access tokens. However, in this scenario, the attacker incurs a substantial financial cost.
The aim is to permit spam only if it is commercially supported. However, certain basic operations, such as Get and List methods, can be efficiently implemented with caching to enhance service discoverability. Prex Operators has the freedom to allow these operations without authentication.
Traditionally, online services have been offered at no cost. Over time, this model has led to the emergence of large, dominant entities that impede scalability. An alternative is to treat online services as essential utilities, funded through a subscription model similar to electricity or water. This could lead to a more sustainable and cost-effective system than the current free, ad-supported internet.