## Proof of Transaction, fees and (SoV)

He said there was no DAO roadmap as it was open-sourced so the community can contribute and help form it.

Hello leaf, mainly control over setting the base fee for juicing transactions and thus setting the TPS of Algorand. Here’s the GH repo of the contract:

Hi Rich, this topic is to share opinions and discussions on the possibilities PoT contracts could unlock for the Algorand network.

We will use $ORA as an example, but any PoT token with enough liquidity can conceptually work.

Fees on Algorand are going higher to incentivize consensus. That could cripple the velocity of money within the network.

Not so fast. An Algorand wallet can run a juicer contract and give the opt...

### Draft Ideas:

A. **Fee scaling mechanism:**  The shape of the curve aims to increase the fees when Global staking % goes down, incentivizing the firing up of new nodes to capture the higher fees. Also incentivizes risk management from node operators to protect their nodes from attacks.

Cc [@JohnWoods](https://forum.algorand.co/u/johnwoods)

Not unpopular at all. Agreed individual participants (retail) most likely won’t be upgrading their nodes as much. Also agreed. Individual consensus participation friction should be reduced—that’s a no-brainer. But with incentives on pools, it will become inevitable, and they do pose a more serious risk.

Easy to install != one-click. Individual participation vs pooled participation should not be a concern if we can align the incentives towards keeping the highest consensus stake online possible. Here is an idea: Making the pools care about protecting the network, they will also be incentivized to invest in better security practices.

Agreed, but we have to consider the pools as attackers first sadly. Any staking pool operator controlling more than 20% of global stake puts the network at risk.

### Mitigation Ideas Already in the Paper:
1. To make nodes as accessible (low cost) and simple to use for individuals (one-click installation).

Oh shoot my bad lol. High max cap* redundant I meant to say, sorry.

10mm min = 1000 max # of nodes
1000 * x watts = network max energy req.
You can start by defining how much max energy is reasonable (compliant) to spend and then get to your min node stake cap. Lower max cap might become redundant then.