What the "King Safety" paper should include

Sustainability of staking
It is now sponsored by the AF for one more year.
Possible solutions: Algo price boost and/or txn price increase

Limited treasury
The Foundation has Algos for 2 more years.
Possible solutions: Raising the 10 billion Algo limit, and/or decreasing AF spending

Partnership problems
World Chess costs 700 K USD/year, seems too costly.
FIFA is already gone — a big loss.

Relay nodes
Not transparent, a closed club.
Solution: p2p, where relays are optional and user-funded. Also, a deadline for this transition.

Transaction fees
Txn fees should depend on the amount. E.g. max(0.001*amount, 0.001) Algo

Leadership incentives
AF leaders should have skin in the game.
They should take 30% of their salary in ALGO with a 2-year lock-up.

No more “kings”
Big spending decisions should not be made by the Foundation alone.
Any expense above $500k should go thru xGov Coucillors vote first.

Bottom line:
The technology is good. The economics are broken.
The “King Safety” paper is the last chance to fix this.
Vague promises are not enough anymore.

  • min tx fee increase (it’s a must, yes it will break a lot of things)
  • clarity on no uncapping, commit
  • top-up of node runner rewards, put your money where your mouth is, if network succeeds AF succeeds… hogging community/network/adoption allocated funds for “AF operational costs” is not something ima fan of. We need this longer horizon stability, that only a top-up to fee singk can guarantee.
  • sustainable xgov or simmilar mechanism for community goods funding. If there is money for chess and charity there should be money for actual ecosystem builders and users that have kept this chain relevant over the years.
  • Some sort of accountability for AF to tied to their spending/selling of algo: for an example % of variable ALGO allocation(on top of the min needed to keep things running) towards AF based on certain KPIs, and no not the vanity metrics.

Why did you create a second thread on the same topic you posted about elsewhere?

I didn’t. Please be more specific, @iGetAlgo

Practically the same topic…

Hi, @iGetAlgo ,
essentially you are right.

But:

  1. I didn’t get any answer to my open letter to AF CEO Staci Warden
  2. I think “King Safety” should be discussed publicly, so this time I didn’t address it to any “C” level boss, and tried to condense the topic as much as possible
  3. the paper was promised long ago, first on 11-Dec-2025 by AF, then again at the March Community Call. Expected delivery time is always 30 - 60 days :slight_smile:

I’ d like to get a response from you regarding the content of the two topics…

i agree on all these fronts and just like i said last time…

i wish you the best of luck trying to get answer. Cheers! :saluting_face:

The foundation and its employees keep making excuses that they havent released it because staff changes and the new board structure has delayed when we all know they just dont stick to deadlines in general…

Here is the current structure of the Algorand network: instead of collecting revenue from network and database users, the Algorand Foundation sells its own ALGO holdings and draws funds from the pool of capital that ALGO buyers have put into the market, then distributes those funds to public goods. In other words, those who purchase ALGO are ultimately funding the maintenance and operation of these public goods through the dilution of their token’s value. Under this current structure, an influx of users and developers who hold only the bare minimum amount of ALGO simply means an expanding public goods deficit. For this network to become sustainable, there is no other way around it—we must increase the number of people who buy ALGO.

To achieve this, we face three structural problems that prevent people from buying ALGO:

  1. No incentive for investors: Under the current mechanism, the price of ALGO is structurally pushed downward, giving investors no incentive to buy.

  2. Lack of attractive utilities: There are no compelling investment opportunities on Algorand that can only be purchased with ALGO, leaving no reason to buy it.

  3. Fees are too low: Because transaction fees are negligible, the amount of ALGO that users and developers actually need to purchase is minuscule.

In my personal opinion, the current KPI of simply increasing the number of developers in the Algorand ecosystem is flawed. For example, let’s say a developer builds a dApp used by 10,000 users. If that dApp utilizes fee sponsorship mechanisms so the developer covers the users’ gas fees, those 10,000 users do not have to pay anything to use it. Even if each user generates 100 transactions, the developer only needs to purchase 1,000 ALGO. Since those 10,000 users do not hold any ALGO, they will neither participate in the broader Algorand ecosystem nor purchase any ALGO themselves. If 1 ALGO is worth $0.10, the economic value of attracting this developer is only $100.

Our KPI should focus on how much capital is actually flowing into the network.

I also do not personally think the current xGov mechanism is working well. The aspects that xGov grants currently evaluate focus heavily on metrics like the “10,000 users” mentioned above, rather than assessing whether capital is actually flowing into the network. What xGov changed was simply the flow of the funds that had already been drawn from the market. Previously, those funds were spent almost exclusively by the Foundation; now a portion of them also reaches ecosystem developers. In other words, the distribution of resources has changed, but the total amount of resources has not.

Therefore, the fundamental problem remains unchanged: once there is no more capital left to extract, the system effectively comes to an end.

Because most other Councils are on the receiving side of this distribution, discussions tend to focus on how to reallocate the available funds rather than how to structurally transform the economy. If full authority is delegated to xGov in its current form, I fear it will end in a situation where the network collapses, but participants are satisfied because they managed to extract some value before it happened.