# STEAKs 60 pieces of meat per block are reserved for all kind of STEAKs. **Initial STEAKs :** * STEAK - USDC 40x -----> 50x * STEAK - WMATIC 20x -----> 30x * STEAK - USDT 20x -----> 30x * WETH - USDC 10x ***`4% fee`*** * WBTC - USDC 10x ***`4% fee`*** * DAI - USDT 8x ***`4% fee`*** * DAI - USDC 8x ***`4% fee`*** * USDC - USDT 8x ***`4% fee`*** * WETH - WMATIC 5x ***`4% fee`*** * LINK - USDC 5x ***`4% fee`*** * WMATIC - USDC 5x ***`4% fee`*** * AAVE - USDC 3x ***`4% fee`*** ## Controlling STEAK supply ### Why STEAK has no hard cap There's currently no hard cap on the supply of STEAK token, making it an inflationary token. Community members often point to this as a cause for concern, and while the chefs certainly understand the wish for a hard cap, there's a big reason we don't expect to set one in the near future: > STEAK's primary function is to incentivize providing liquidity to the exchange. *Without block rewards, there would be much less incentive to provide liquidity (LP fees etc. would remain).* So what are the other ways STEAK's supply is limited, to counter inflation? ### How STEAK supply is reduced without a hard cap The chefs aim to **making deflation higher than emission** by building deflationary mechanisms into SteakHouse's products**.** The goal is for more STEAK to leave circulation than the amount of STEAK that's produced. #### Reducing block emissions By reducing the amount of STEAK made per block, we slow inflation. But we don't want to do this too frequently, too early, for the same reason we don't want a hard cap: we still need to incentivize people to provide liquidity. #### Deflationary mechanisms Regular token `burns` are built into many of SteakHouse's products. SteakHouse protocol have unique burning mechanics. In every single trasaction, the protocol keeps 1% of transaction at burning address where are collecting and burning STEAKs. Yes thats right - more transactions, more to be burned.