SaucerSwap

If your website is on the scam list and you think that you are not a scammer, contact us. After you provide us with all the proof that you are in Crypto World with good intentions, we will delist you. Usually, you get in this category because you are hiding your team, you have a bad reputation(you are tricking, deceiving, scamming people), and you haven't got a written project whitepaper or is a shitty one....

Their Official site text:

If your website is on the scam list and you think that you are not a scammer, contact us. After you provide us with all the proof that you are in Crypto World with good intentions, we will delist you. Usually, you get in this category because you are hiding your team, you have a bad reputation(you are tricking, deceiving, scamming people), and you haven't got a written project whitepaper or is a shitty one....
Their Official site text:
Careers
We are looking to expand our team. Below you can find our current job openings.
Full-Stack Software Engineer (Filled)
As a Full-Stack Software Engineer you will be developing solutions to help SaucerSwap Labs reach the following business goals: 
Integrate with partner services within the Hedera ecosystem
Enhance existing functionality / expand feature set
Improve user experience and system stability
What you’ll be working on as a Full-Stack Software Engineer:
Convert designer specifications (e.g., Figma) into functional features
Add server API features to support UI requirements
Integrate with Hedera network applications and services
What we are looking for:
Fluency in SQL
Fluency in TypeScript / React / MUI
Fluency in Node.js / Express
Experience integrating with external services (APIs, etc.)
Bonus points:
Understanding of DeFi applications and concepts
Smart contract experience
Hedera SDK experience
Web3 / ethers experience
If interested, please send your Portfolio CV to [email protected]. Only shortlisted candidates will be contacted.
Roadmap
The roadmap lays out SaucerSwap's progress and planned features. Note that it is subject to change based on development and community feedback. Items are not chronologically ordered.
Ongoing
Single-Sided Staking
Write Contracts
Audit
Frontend
Community Pools
NFT Staking
Frontend Bridge Integration
Backend
DB Performance Upgrades
Server Optimizations
API Upgrades to Support Integrations
API Upgrades to Support Analytics
Enhance Data Collection for Analytics
Optimize Data Storage for Analytics
Improve Scalability
Increase Modularization
Frontend
Display APY on Farm Page
Improved Token Menu
Additional Trading Information in Swap UI
Analytics Data on Swap and Liquidity Pages
Website Redesign
Improved Portfolio Page
Analytics
Overview, Token, and Pool Pages
Liquidity, Volume, and Price Charts
Global Transactions
Subscription Model
Implement SAUCE as a Method of Payment
User-Specific Transactions
Insights
Notifications
Integrate DEX on Data Aggregators
DeFi Llama
TVL
Yield
Volume
Fees
CoinGecko
CoinMarketCap (Application Pending)
DappRadar
List SAUCE on Data Aggregators
CoinGecko
CoinMarketCap
Add Support for Additional Wallets
MetaMask
Blade
Collaborate on HashPack In-Wallet Swap
Integrate SAUCE on hashport Bridge
Ethereum
Polygon
BSC
Avalanche
SAUCE Exchange Listings
MEXC
Cross-Chain Dex(es)
Open-Source Core and Farm Contracts
Establish Token Whitelist Procedure
Amended Procedure and Classification System
Upcoming
AMM v2
DAO-Based Governance
Expert Mode
Limit Orders
Yield Aggregator Integration(s)
Farm v2
HTS Token Emission
Zap
Game-Theoretic Staking
Batched Transactions
Completed
Initial Market Research & Analysis
Wireframe of Website
Draft Tokenomics 
Draft Website Copy
Frontend Setup w/ Nextjs & Vercel
Backend Setup w/ Express & MySQL
Server Deployment on AWS
Server HTTPS & Nginx Configurations
Team Recruitment & Compensation Breakdown
Assemble Team for Social Media Outreach
Launch of Twitter Campaign
SaucerSwap Branding & Art Assets
Website Design & Art Assets
Finalize NFT Perks 
Website Completion + Cross Browser Testing
Client-Server Integration
Internal Security Review
Website Release
Wallet-Based Authentication
HashConnect Integration
Social Profiles
NFT Sale Begins
Host Biweekly AMAs
Introduce the Team behind the Project
Publish NFT Multisig Address
Faucet Bot Release
Faucet Bot Revise Schedule & Amount
Faucet Bot Privacy Related Tweaks
Deploy & Test Uniswap V2 Core + Periphery SCs on Hedera Testnet
Implement Swap Functionality on Hedera Testnet
Implement Pairing Functionality on Hedera Testnet
Implement Router Functionality on Hedera Testnet
Setup Unit Tests for Factory, Pair, and Router Contracts
Analyze UI/UX of other DeFi Platforms
Design the Following Web Pages: 
Landing Page, Swap, Liquidity, Farm, and Portfolio
Implement Backend Logic for Web Pages
Secure Partnership with IDO Launchpad
Implement all Web Pages on the Frontend
Create Instructional Videos for Swap, Liquidity, and Farm
Complete Round 1 Bug Bounty on Testnet
Form Hedera DeFi Alliance
Technical Whitepaper Release
Complete Round 2 Bug Bounty on Testnet
Perform App-Security Analysis on Website
Perform Security Audits on all SCs
Revise SCs Based on Audit Feedback
Documentation Overhaul
Publish Audit Reports
Finalize Liquidity Partner Pools
Perform Testing of SCs on Mainnet
Receive Grant from The HBAR Foundation
Electromagnetic Liquidity Option
Whitelist Event
Public Launch
Wallet
SaucerSwap currently supports  - a Chrome extension and browser-based crypto wallet built for dApps, DeFi, and NFTs.
HashPack
You can create a free Hedera account in a few simple steps with HashPack.
To get started, access HashPack through either the  or .
Next, you’ll need to Create a Main Password. This password is securely encrypted on your device and is never transmitted over the internet. If you’re using HashPack on multiple browsers or devices, you’ll need to create a new password and import your account on each browser or device.
Once you’ve entered a password with a minimum of 12 characters, click the checkbox to agree to the  and , then click Next.
Select Create New Wallet.
You will need to securely note down your 24-Word Seed Phrase (also known as a mnemonic phrase, or recovery phrase). A Seed Phrase is a special type of password which allows you to recover your account.
Once you're ready, click Next.
Enter the missing words from your phrase, this is to verify that you have noted it down correctly.
Once you've verfied all the missing words, click Next.
Enter a nickname for your HashPack wallet. This step is optional, but may help you keep track of what the account is for.
Press Create Wallet.
Save your account information, carefully note down your Account ID. You’ll use this to send, receive and pay with HBAR. You’ll also need your Account ID when importing or recovering your account. 
Press Reveal Recovery Keys, and Securely note down your Private Key. Like your 24-Word Seed Phrase, this is a special type of password which allows you to recover your account. Always keep your Private Keys safe and secure, and don't share them with anyone.
Once you're ready, press Done and then Let's Go!
These step-by-step instructions, along with visual aids, can be found . If you need any further support with account creation, join the HashPack . 
Obtain HBAR
To perform transactions on SaucerSwap, you will need  for gas fees.
Centralized Exchanges
HBAR is available to purchase on many exchanges, including Binance, Upbit, Bitrue, KuCoin, among others. A full list can be found . Once purchased, simply transfer your HBAR to a supported  to begin using SaucerSwap.
Discord Faucet
SaucerSwap has repurposed the SAUCE faucet to instead dispense HBAR to members of the community. Upon linking your account via Discord, you are eligible to a one-time pull of $0.12 worth of HBAR. The intention of the faucet is to provide you with the bare minimum amount of HBAR to cover gas fees on a WHBAR token association (necessary to use SaucerSwap) and direct token swap to HBAR - this newly acquired HBAR will then be used to cover subsequent gas fees.
Account Linking
To use the faucet, follow these simple steps:
First, open Google Chrome or another Chrome-based browser.
Visit .
Navigate to the top right corner of the nav bar and click Connect Wallet. If you have not set up a supported wallet, refer to  instructions.
This will open a window in HashPack that prompts you to connect with SaucerSwap via HashConnect. You may do so by selecting Pair with Wallet, Pair with Code, or Pair with QR Code.
Sign in to your HashPack, check the box adjacent to your nickname, and click Approve. 
Once your wallet is connected, navigate to the nav bar, click on the "..." dropdown to the right of Portfolio, and click on Profile.
You will be automatically redirected to saucerswap.finance/profile/xx. Once there, click Login to Edit and approve the request in HashPack.
After the request is approved, return to the site and click Edit Profile. 
Be sure to add your Discord handle (including the 4-digit hash) and set your profile to public so that the SaucerSwap team can correlate your wallet address and username. You may switch this to private after your account is linked. All other fields are optional.
Join the SaucerSwap  server.
Post a link to your social profile in the #account-linking channel and a social manager will verify your account.
To pull from the faucet, navigate to the #faucet channel and run the command !sparechange
You can verify that you have received HBAR by refreshing your HashPack balance.
Bridge to Hedera
SaucerSwap will offer a seamless in-app . For now, tokens such as ETH, MATIC, DAI, LINK, USDT, USDC, WBTC, and AAVE can be bridged to Hedera from Ethereum and Polygon directly through hashport - a public utility that enables network interoperability by leveraging the HCS. Note that LINK[hts], WETH[hts], etc. denote wrapped tokens.
​​
How to bridge tokens with hashport
FAQ
This FAQ serves as a starting point for understanding DeFi and AMMs.
What is a DEX?
Traditional exchanges require professional market makers to handle orders and are limited by the frequency with which they can quote the best prices. Decentralized exchanges (DEXs) allow for cryptocurrency transactions to take place online, securely, and without the need for an intermediary. Users can swap between tokens in a liquidity pool (e.g., SAUCE for HBAR in a SAUCE/HBAR pool). In a nutshell, DEXs provide users with a simple, fast, affordable, and secure way to swap tokens in a permissionless and trustless environment.
How can a DEX work without intermediaries?
DEXs rely on automated market maker (AMM) protocols, which use mathematical formulas to price assets. This formula can vary between protocols. For example, SaucerSwap's constant product AMM satisfies the equation: 
where x and y are the two token reserves in the liquidity pool and k is constant unless liquidity is deposited in or withdrawn from the pool. You can think of AMMs as peer-to-contract (P2C) - there is no need for counterparties in the traditional sense, as swaps happen between users and contracts.
​​
Where do DEXs get their liquidity from?
AMMs incentivize users to provide liquidity. Liquidity is the ability to convert one asset into another asset without changing its market price. Liquidity providers add funds to liquidity pools. You can think of a liquidity pool as a big pile of funds that traders can trade against. In the case of SaucerSwap, liquidity providers deposit an equivalent value of two tokens, e.g., $500 of $AAA and $500 of $BBB, into a $AAA-$BBB pool in exchange for LP tokens. In doing so, they are adding liquidity to that pool.
What incentives are there for providing liquidity?
Liquidity providers earn fees from the swaps that occur in the pool in which they are providing liquidity. Every swap on SaucerSwap incurs a fee. 5/6 of the fees are aggregated and redistributed to all liquidity providers in proportion to the amount of LP tokens they hold. 
How do I become a liquidity provider?
You will need to deposit two tokens - in equal value parts - into the corresponding liquidity pool. Tokens can be obtained from secondary markets or through the DEX. For example, if you wanted to obtain SAUCE, you would swap HBAR in the SAUCE-HBAR pool. 
 How are LP Rewards calculated?
LP rewards are measured in terms of annual percentage rate (APR), a rate of interest applied on an amount per year. APR indicates how much interest you will earn at the end of the year from the amount invested. 
The yearly fee income is calculated as a fraction of your liquidity over all other existing liquidity multiplied by the 24h swap volume (annualized) and swap fee rate. The swap fee rate is 0.30%, where 5/6 (0.25%) is distributed to liquidity providers.
What are yield farms?
In addition to being a liquidity provider, users can earn even more rewards (in the form of SAUCE and HBAR) by staking LP tokens in yield farmss. LP farm rewards are determined by the release schedule of SAUCE tokens (i.e., emissions). 62.5% of emissions will go to LP farm rewards, with each farm being assigned a weight.
How do I participate in yield farms and what incentives do they provide?
Once you have obtained LP tokens for a supported pair, simply stake them in the corresponding farm to reap higher rewards. You may harvest rewards and / or unstake your LP tokens at any time.
What risks are inherent to AMMs?
The primary risks inherent to AMMs are slippage and impermanent loss. See  for more information. 
How does the release schedule work?
20.0% of the max supply of SAUCE tokens (200,000,000) will be minted at genesis, with 2.0% allocated to the SAUCE/HBAR liquidity pool, 14.0% allocated to airdrop, 2.0% allocated to faucet & giveaways, and 2.0% allocated to the DAO treasury. This leaves 80.0% (800,000,000) of the max supply of SAUCE to be released over the course of 3 years in the form of emissions. 62.5% of emissions will go to LP farm rewards. SAUCE emitted (as a function of time) will follow a fixed supply, linear decay model, where the rate at which SAUCE tokens are brought into circulation is constant, and maintained until all 1 billion SAUCE are released.
For more information, see .
How does SaucerSwap differ from Uniswap v2?
SaucerSwap differs from Uniswap v2 in some fundamental ways. For example, the Ethereum network uses the ERC20 and ERC721 standards for token operations, meaning tokens are themselves contracts. On Hedera, however, token operations are performed on HTS, therefore tokens are controlled through HTS. This is made possible by recent HSCS upgrades allowing smart contracts to use HTS through EVM precompiles. It must be stated that, while it was always possible to create a DEX on Hedera using the ERC20 standard, the ecosystem is now more amenable to tokens created by and controlled through HTS, representing the novelty of SaucerSwap. This is a significant differentiating factor, as SaucerSwap is positioned to take advantage of the network’s consistent and predictable fee structures for token operations.
How does SaucerSwap governance work?
SaucerSwap aims to democratize DeFi by structuring its governance model after a decentralized autonomous organization (DAO). A DAO treasury fund will serve to retain value on the protocol and fund development of community-voted features. 
SaucerSwap's DAO enables the community to work towards a common goal, without the need for centralized decision-making. It resolves the issues of trust by programming governance rules in smart contracts to steer the organization towards the interests of the participants. SaucerSwap allows users to create community proposals which they may vote on, with each SAUCE equal to 1 vote (this will be capped). A proposal may be promoted to a core proposal, which will become a feature after passing vote by quorum. In addition to 2.0% of the initial supply being allocated to the DAO treasury, a portion of emissions and swap fees will go towards this fund.
For more information, see .
What can we expect in the future?
SaucerSwap will be a one-stop shop for DeFi services on the Hedera network. Future implementations are listed on the .
Inquiries
Contact Us
For support or general inquiries, reach out to the core maintainers over . Alternatively, contact us via email.
General: [email protected]
Support: [email protected]
Business Development Contacts
Peter Campbell | [email protected] | Discord: Gliese#0581 |  | TG: @gliesesauce 
Joseph Bergvinson | [email protected] | Discord: Hashburglar#5904 |  | TG: @Hashburglar 
Apply for Token Whitelisting
SaucerSwap defines 3 classes of tokens. To apply for a token listing, first read the  section of the docs, then complete the following request form:
​​
You must provide liquidity for your token prior to it being listed. With the exception of default listings, there are no liquidity requirements.
Note that anyone can create a liquidity pool with any two HTS tokens, regardless of if they are listed in the menus. If a token is not listed, try pasting the token ID into the search box. It will populate the dropdown with the token you are looking for. For step-by-step instructions, click .
Default List Instructions
Complete a  through HeadStarter. This involves answering basic questions about your project.
Once the report is published and you are prepared to add $10,000 of liquidity for your token, submit a .
A  poll will be created for eligible candidates. This poll will include a description of your project and link to the Sentinel report. 
Planck Epoch NFT holders will have 48 hours to vote yes or no. A >50% majority is considered a passing vote.
Once the poll has closed, you will have 7 days to provide $10,000 of liquidity to your token pair. Note that this liquidity can be sourced from multiple parties (e.g., team, community).
SaucerSwap will promptly whitelist your token.
Apply for Farm or Collaboration
Projects can apply for yield farms after their token has been added to either the default or extended list. There will be a limit to how many farms a given token can receive, with this number generally being capped at two. A project can submit a new request form if it has one or more farms and wishes to incentivize an additional token pair. Once the SaucerSwap team has received a form, the decision will be brought to a community vote in the same manner as token listings. Note that the token must have a reasonable amount of liquidity and sustained trading volume for it to be considered for a farm. This is to ensure there is organic demand for the token without additional incentives. Liquidity and volume will be assessed on a case-by-case basis. All yield farms will receive dual token emissions (SAUCE and HBAR). Farm weights and initial listings will vary per project and will be governed via DAO-based token-weighted voting once it is phased in.
For farm inquiries and other collaborations, please complete the following request form:
​​
SAUCE Token
SaucerSwap's native token is $SAUCE: a transferable representation of attributed utility functions; namely, liquidity, staking, and governance, specified in the code. It is therefore designed to be a utility token essential to the protocol. 200 million SAUCE tokens were minted at genesis, while the remaining 800 million will be brought into circulation according to the .
The total supply of SAUCE is hard-capped and will not exceed 1 billion tokens. Furthermore, SaucerSwap will not utilize a burn-and-mint equilibrium (BME) model. SAUCE is, however, a buyback deflationary token due to its staking mechanism.
Liquidity
Newly minted SAUCE serves a liquidity mining incentive, used to offset impermanent loss and bootstrap liquidity on the protocol. 
Staking
Furthermore, the token plays an integral role in  and . Users can stake SAUCE in a contract to receive a percentage of swap fees, HBAR native staking rewards, and farm emissions. By staking SAUCE, a user immediately receives xSAUCE tokens as receipt of the liquidity they provided, which they can then stake in Community Pools to compound yield. 
Governance
SaucerSwap is structured as a DAO, where the community can create and vote on proposals to steer protocol development. This governance framework leverages a Hedera Consensus Service (HCS)-based ballot & voting architecture. Votes will be proportional to the amount of SAUCE in a user's account, where 1 SAUCE token = 1 vote.
​
​Initial Supply Breakdown
20.0% (200,000,000) of the max supply of SAUCE will be initially released.
The initial supply breakdown is as follows:
Percentages are out of 80.0% max supply
These tokens go towards liquidity (2.0%), airdrops (14.0%), faucet & giveaways (2.0%), and the DAO treasury (2.0%).
Allocation Category
% of Max Supply
% of Initial Supply
Number of
SAUCE Tokens
Liquidity
2.0%
10.0%
20,000,000
Airdrops
14.0%
70.0%
140,000,000
Faucet & Giveaways
2.0%
10.0%
20,000,000
DAO Treasury
2.0%
10.0%
20,000,000
Sum
20.0%
100.0%
200,000,000
There are no pre-sales or private sales of the SAUCE token. All tokens are distributed according to emission schedule. SAUCE unaccounted for will be sent the DAO treasury.
Emission Schedule
The remaining 80.0% (800,000,000) of SAUCE tokens will be released over a period of 3 years. SAUCE in circulation (as a function of time) will follow a fixed supply, linear decay model, where the emission rate is constant. All tokens (excluding the 20.0% initially released) are distributed according to this emission schedule, meaning funds for the team, advisors, and marketing are locked in vesting contracts and distributed at the same pace as the LP farm rewards and DAO treasury emissions.
Percentages are out of 80.0% max supply
With Hedera (and within a native smart contract), there is no concept of a block, however, Hedera translates block.timestamp to be the consensus timestamp of the transaction. Emissions will therefore be calculated based on SAUCE per minute, rather than SAUCE per block. Approximately 507.36 SAUCE are brought into circulation every minute.
The emission rate for each respective allocation category is as follows:
Allocation Category
Emissions (% of Max Supply)
SAUCE / Min
Team
24.0%
152.21
Advisor
2.0%
12.68
Marketing
2.0%
12.68
DAO Treasury
2.0%
12.68
LP Farm Rewards
50.0%
317.10
Total
80.0%
507.36
The release schedule is visually represented in the Figure below:
The justification for emitting SAUCE via a linear decay emission model (emission rate is constant) over a non-linear model (emission rate decreases over time) is that farms will sustain high APRs while the development team implements additional mechanisms serving the role of, not only improving user experience, but also compensating for LP farm rewards once emissions run out.
Risks
The two main risks inherent to AMMs are slippage and impermanent loss (IL). 
Slippage
The constant product function xy = k forms a hyperbola when plotting two assets, which creates the desirable property of always having liquidity as prices approach infinity on both sides of the spectrum. While this may be true, the available reserve of asset A will approach zero as the trade size of asset B approaches infinity. This results in slippage, i.e., the tendency of prices to move against a trader’s actions as the trader absorbs liquidity - the larger the trade, the greater the slippage. 
Put another way, slippage is the difference between the expected price of an order and the price when the order actually executes. It can be exacerbated by price volatility, as traders affect the price in different directions at the same time. Slippage is reduced as more liquidity is added to a pool, since its depth is measured by the k constant. 
Impermanent Loss
Impermanent loss occurs when you provide liquidity to a pool, and price divergence between your deposited assets occured compared to when you deposited them. The bigger this divergence is, the more you are exposed to IL.
Consider an example where Alice deposits 1 $AAA and 100 $BBB in a liquidity pool, and let 1 $BBB = 1 USD (a stablecoin). Since SaucerSwap is a constant product market maker protocol, the deposited token pair needs to be of equivalent value. This means that the price of 1 $AAA is 100 $BBB and the dollar value of Alice’s deposit is 200 $BBB at the time of deposit.
In addition, assume there is a total of 10 $AAA and 1000 $BBB in the pool - funded by other liquidity providers. So, Alice has a 10% share of the pool, and the total liquidity is 10,000 USD.
Next, say that the price of $AAA increases to 400 $BBB. While this is happening, arbitrageurs are incentivized to add $BBB and withdraw $AAA from the pool until the reserve ratio reflects the current market price. It is important to remember that the price of the assets in the pool is determined by their reserve ratio, so while liquidity remains constant in the pool (10,000 USD), the ratio of the assets in it changes.
Since 1 $AAA is now 400 $BBB, the reserve ratio ratio has changed. As a result of arbitrage trading, there are now 5 $AAA and 2000 $BBB in the pool. 
Alice now decides to withdraw her funds. As we know from earlier, she’s entitled to a 10% share of the pool. She can, therefore, withdraw 0.5 $AAA and 200 $BBB, totaling 400 USD. One would think that she profited since her initial deposit was worth 200 USD. However, if she simply held her 1 $AAA and 100 $BBB, the combined dollar value of these holdings would now be 500 USD.
We can see that Alice would have been better off by holding these assets in a wallet rather than depositing them into the liquidity pool. If Alice had kept her assets in the pool, her loss would be impermanent. The moment she withdrew these assets, the losses were realized, hence the loss is permanent. Note that this does not account for interest accrued on her LP tokens from swap fees and interest earned from staking, which may have negated the losses and made liquidity provision profitable. 
Lastly, it is important to understand that IL occurs no matter which direction the price changes. The only thing IL is concerned with is the price divergence relative to the time of deposit.
​​
​​DAO Overview
SaucerSwap's decentralized governance will be gradually phased in. The team will initially control the protocol and implement core features such as Swap, Liquidity, Farm, Single-Sided Staking, and Bridge. Once these features are implemented, governance will transition to a DAO. To ensure true decentralized governance, SaucerSwap is exploring various frameworks. One such framework is Calaxy’s Creator’s Galaxy Improvement Proposal (); namely, leveraging a Hedera Consensus Service (HCS)-based ballot & voting architecture. HCS messages will be used to record the creation of proposals, SAUCE-weighted voting on these proposals, and subsequent ballot results. An HCS-based governance architecture provides an open, transparent and provable repository/database of propositions, votes, and ballot results. As the HCS messages are archived on 3rd-party mirror nodes, the history of propositions and votes is public and auditable.
The community will first gain the ability to vote on core proposals pertaining to Community Pools. In other words, they will determine which HTS projects are onboarded to the platform. Over time, SaucerSwap's governance will become more decentralized, allowing users to create community proposals and vote on both community and core proposals.
This governance model is inspired by Hedera’s path to decentralization; namely, how their nodes are operated by governing council members but will grow to include permissioned community nodes, then anonymous nodes. Similar to how Hedera will open node operation to more entities and individuals as performance, security, stability, and incentives of the network mature; SaucerSwap’s DAO-based governance model will become more decentralized as core features are added to the protocol.
Voting
The community can create and vote on proposals. The weight of their vote will be proportional to the amount of SAUCE in their account, where 1 SAUCE token = 1 vote. xSAUCE may also serve as a governance token to reward users who have staked liquidity in the protocol.
The voting process itself is simple: the community creates and votes on time-sensitive proposals that are set to expire after 7 days. Votes are signed messages easily verifiable using the HCS. If a community proposal receives a passing vote by supermajority (> 70%), it will be made into a core proposal. If a core proposal receives a passing vote by quorum (> 50%), it will be enacted.
Voting Process
Management of DAO Treasury
The DAO treasury will initially contain 2.0% of the max supply of SAUCE. Over the first 3 years, it will receive an additional 20,000,000 SAUCE from emissions. Furthermore, it will receive 20% of SAUCE buybacks from (i) 0.05% of swap fees, (ii) HBAR native staking rewards, and (iii) 3% of farm emissions. The former 2 sources of revenue will persist indefinitely, ensuring the DAO is financially sustained. This SAUCE will be diversified into a basket of assets, including HBAR, stablecoins, and LP tokens. These LP tokens may be farmed to maximize capital efficiency. Likewise, the SAUCE may be staked in the Infinity Pool, so long as this does not significantly impact the APR. Once the DAO is phased in, these assets will be allocated to fund various operations.
Swap
Introduction
SaucerSwap operates through an on-chain system of smart contracts forked from Uniswap v2. This is made possible by leveraging HSCS to include Solidity smart contract integration with the HTS. These contracts implement an automated liquidity protocol based on a constant product formula:
Where, for any given SaucerSwap pair, x and y are the number of tokens and k is the constant product. Traders pay a 30-basis-point fee on swaps, of which 5/6 goes to liquidity providers, while the remaining 1/6 goes to the DAO treasury. Whenever a swap occurs, the ratio of x and y changes such that the invariant, k, is maintained before fees.
Token Swap
For example, let $AAA and $BBB be the liquidity pair, with token amounts 2500 and 100, respectively. Here, the constant product is 2500 * 100 = 250,000.
Figure 1. AMM-Faciliated Token Swap. Note that rounded numbers were used in the calculations.
In this example, a trader wants to swap 500 $AAA. In order to withdraw some amount of $BBB, they must deposit a proportional amount of $AAA to maintain the constant product before fees.
Firstly, we must account for the swap fee. 500 $AAA * 0.3% = 1.50 $AAA in fees is deducted and added to the liquidity pool reserves, slightly increasing the value of k, hence 500 - 1.50 = 498.50 $AAA is swapped for $BBB.
The number of $AAA tokens increases by 498.50, while the number of $BBB tokens decreases by y. After rearranging the equation (2500 + 498.50) * (100 - y) = 250,000 and solving for y, we learn that the trader receives 16.62 $BBB on this token swap.
Pricing Based on Inputs
Let x and y represent the number of $AAA and $BBB tokens in a $AAA-$BBB liquidity pool. If getInputPrice denotes how many $BBB tokens (i.e., 
�
�
d 
y
​
 
) can be bought by selling a given number of $AAA tokens (i.e., 
�
�
d 
x
​
 
), factoring in a 30-basis-point swap fee, 
or in code,
getInputPrice(x, y, dx) = (y * 997 * dx) / (1000 * x + 997 * dx)
If getOutputPrice denotes how many $AAA tokens is needed to buy 
�
�
d 
y
​
 
 $BBB tokens,
or in code,
getOutputPrice(x, y, dy) = (1000 * x * dy) / ((y - dy) * 997) + 1
where / in the above equations denotes divToInteger, which means divide with rounding to floor of the results.
Price Impact
Price impact is the influence of a user's individual trade over the market price of an underlying token pair. There are two ways in which price impact can be calculated: x, y, 
�
�
d 
x
​
 
; or x, y, 
�
�
d 
y
​
 
. One is based on input, while the other is based on output.
or
in code,
price impact(x, y, dx) = (1000 * x)^2 / (1000 * x + 997 * dx)^2 - 1
price impact(x, y, dy) = (y - dy)^2 / y^2 - 1
Summary
Put more generally, every time a trader buys $AAA, the price of $AAA goes up as there is now less $AAA in the pool than before the purchase. Conversely, the price of $BBB goes down as there is more $BBB in the pool. The pool stays in constant balance, where the total value of $AAA in the pool will always equal the total value of $BBB in the pool. Only when new liquidity providers join will the pool expand in size.
​
Token Classification
Tokens on SaucerSwap fall into 3 classes: default, extended, and experimental. These classes are defined below:
Class
Characteristics
Criteria
Default
Appears in default menus
No disclaimer
Appears in analytics
No disclaimer
Listing announcement from SaucerSwap on Twitter
Eligible for listing on data aggregators (CoinGecko, CMC)
Price API
Token price displays in HashPack and other applications
Discord price bot
HeadStarter Sentinel report
SaucerSwap request form
Passing community vote (>50%)
Minimum $10k token liquidity
Extended
Appears in default menus
User prompted with “Caution” disclaimer
Appears in analytics
User prompted with “Caution” disclaimer
Eligible for listing on data aggregators (CoinGecko, CMC)
Eligible for yield farms
Price API
Token price displays in HashPack and other applications
SaucerSwap request form
Listing ETA is 48 hours
Experimental
Does not appear in default menus
Tokens must be imported by ID (e.g., 0.0.123456)
User prompted with “Warning” disclaimer
Does not appear in analytics
Price API
Token price displays in HashPack and other applications
No criteria; any HTS token can be imported, used to create a liquidity pool, and traded
If you represent a project and would like to apply for a token listing, please complete the following request form:
​​
​Liquidity
Introduction
Anyone can provide liquidity to earn passive income. A liquidity provider supplies equal value parts of two different tokens in exchange for LP tokens. Liquidity providers receive a 0.25% fee for every swap that is made in their pair. The 0.25% fee is added back to the pool, increasing the value of ssLP tokens. Liquidity providers can also participate in  with supported pools.
Liquidity Pool Creation
Let us first cover the process of LP creation. Consider a token pair $AAA and $BBB. By creating a pool, a liquidity provider is setting the ratio of tokens, which determines the price of the tokens in the pool. Generally speaking, if a token has an established market price, it makes sense to set the ratio such that the prices of the tokens approximate market prices. If the prices deviate from market prices, arbitrageurs will step in and rebalance the pool to match market prices at the liquidity provider's expense. 
Figure 1. Liquidity Pool Creation. Note that rounded numbers were used in the calculations. 
In the above example, 2500 $AAA and 100 $BBB are used to create a new liquidity pool. The number of ssLP shares minted is the geometric mean of these token amounts, i.e.,
Applying this, we get sqrt(2500 * 100) = 500 ssLP tokens. The constant product, k, is simply 2500 * 100 = 250,000.
Liquidity Provision to an Existing Pool 
Next, let us cover the process of providing liquidity to an existing pool. 
Figure 2. Adding Liquidity to an Existing Liquidity Pool. Note that rounded numbers were used in the calculations. 
Figure 2 depicts the pool in Figure 1 after a  has occured. It now contains 3000 $AAA tokens, 83.38 $BBB tokens, 500 ssLP tokens, and has a k constant of 250,140.   
Consider an example in which a user wants to provide 719.60 $AAA tokens to this pool. The protocol mandates that equal value parts of $AAA and $BBB are added, so based on the relative prices of these tokens, 20 $BBB tokens must also be added.
Protocol Fee
The factory contract first computes accumulated swap fees, and mints new liquidity tokens to the fee beneficiary which, in the case of SaucerSwap, is the DAO Treasury. This is to remain gas efficient. The number of LP tokens minted is based on the equation:
Where s is the number of outstanding ssLP tokens, k2 is the current k value of the LP, and k1 is the k value of the LP at the last deposit / withdraw from the LP, and φ = 1/6. In our example, the number of LP tokens minted and sent to the DAO Treasury is 0.023.
Minting LP Tokens
Next, the procotol calculates the number of ssLP tokens minted to the liquidity provider according to the equation:
Where x, deposited is equal to the number of $AAA tokens deposited by the new liquidity provider, s is the number of outstanding ssLP shares (including the newly minted shares for the DAO Treasury), and x is the number of $AAA tokens in the pool. In our case, 719.60 * (500 + 0.023) / 3000 = 119.93 ssLP tokens minted. The new k constant is (3000 + 719.60) * (83.38 + 20) = 384,532.25.
These newly minted LP tokens represent the liquidity provider's share of the $AAA-$BBB LP. In this case, they would own 19.35% of the pool. 
Incentives
Swap fees are automatically put back into the pool and distributed to liquidity providers in proportion to their share of the pool. Put another way, fees are aggregated and distributed to liquidity providers on a pro-rata basis based on the amount of LP tokens they hold.
A liquidity pool's LP Reward APR, which can be found on SaucerSwap's analytics subdomain, is calculated as follows:
Liquidity Tutorial
How to Add Liquidity: Instructional Video
How to Add Liquidity: Guide
First, connect your  and ensure you have sufficient  to cover gas fees, as well as some tokens, coins, or stablecoins that you would like to deposit into an LP.
Navigate to the Liquidity page.
On the user interface, select Token A and Token B - the token pair you wish to deposit in a liquidity pool in exchange for LP tokens.
If you do not see a token you wish to swap, you can import it by entering the token ID in the search bar, acknowledging the disclaimer, and clicking OK. 
You will be notified if a pool does not yet exist. 
Enter some values in the upper and lower fields. These values determine what amount of each token you want to provide as liquidity. 
If you are creating the pool, you must set the ratio of tokens in the pool, which determines the price of the tokens. Usually, if a token has a market price, it makes sense to set the ratio such that the prices of the tokens approximate market prices. If the prices are set too far from market prices, arbitrageurs will step in and rebalance the pool to match market prices at your expense. Note that the protocol charges a $50 fee to create a pool - this is to prevent spamming.
If the pool does exist, entering a value in the upper field auto-populates the lower field based on the ratio - the combined value of A tokens must always equal the value of B tokens.
Next, shift your attention to the bottom of the interface. Adjust the , and make note of Share of Pool, and LP Tokens.
Share of Pool: your percent ownership of the liquidity pool based on the token amounts you have entered. A higher percent ownership translates into a better return on your principal investment. 
LP Tokens: a derivative asset acting as a receipt of the liquidity you have provided. 5/6 of all fees are aggregated and distributed to liquidity providers on a pro-rata basis based on the number of LP tokens they hold.
Once you are ready to proceed, click Supply. HashPack will first prompt you to associate the LP token, after which point you can approve the transaction. The gas fee will be displayed in-wallet.
The transaction should succeed within several seconds. If it fails, try increasing your slippage tolerance. If the issue persists, reach out to the team in a  support channel.
Transaction details are avaiable on. Click the link in the top right pop-up window to be redirected. 
How to Withdraw Liquidity: Instructional Video
How to Withdraw Liquidity: Guide
Navigate to the My Pools interface on the Liquidity Page.
Here you will see a list of pairs that you are providing liquidity to.
If you do not see a pool you joined, you can import it by clicking the upper link and selecting a combination of verified and / or unverified tokens in the pop-up window.
If 100% of your LP tokens are staked in a Crop Circle, those LP tokens will not appear in the My Pools tab on the Liquidity page until any number of them have been unstaked.
Click on a pool to expand the interface. Displayed, from top to bottom, are:
Your LP token amount
Pooled Token A: number of A tokens representing 1/2 the total value of your LP tokens
Pooled Token B: number of B tokens representing 1/2 the total value of your LP tokens
USD Value: the U.S. dollar value of your LP tokens
​​
Note that staked LP tokens will not appear under My Pools.
Clicking Supply will redirect you to the Supply tab on the Liquidity page.
Clicking Withdraw will expand the interface further. 
Enter the number of LP tokens you would like to withdraw. The amount of Token A and Token B, displayed in green text, will appear below Pooled Token A and Pooled Token B, respectively.
Once ready, click Withdraw and approve the transaction in HashPack.
The transaction should succeed within several seconds. If you are encountering issues, reach out to the team in a  support channel.
Transaction details are avaiable on. Click the link in the top right pop-up window to be redirected. 
Liquidity Migration
Note: the public liquidity migration will begin on December 1st at 11pm UTC.
For SaucerSwap to take advantage of native staking rewards, a new WHBAR and router contract have been deployed. This requires users to migrate their liquidity from deprecated pools.
All liquidity pools containing the existing WHBAR token will be deprecated on December 1st, i.e., no longer used to route swaps; instead, upgraded pools containing the new WHBAR token will be used. Users can withdraw liquidity from the deprecated pools at any time; however, they will no longer have the ability to provide liquidity to these deprecated pools through SaucerSwap’s website. Instead, the site will automatically direct all deposits to the upgraded pools.
Unless otherwise done by a project founder on Wednesday, Nov 30th, the SaucerSwap team will seed pools with a small amount of liquidity for all HBAR pairs to ensure a smooth user experience. The one-time fee associated with creating other pools will be lowered to $10 for one week following the migration, after which it will be set back to $50.
How to Migrate Liquidity: Instructional Video
How to Migrate Liquidity: Guide
After December 1st, 11pm UTC, we encourage all liquidity providers to do the following:
Identify if you are providing liquidity in a pool containing WHBAR — all existing pairs containing HBAR fall in this category (e.g., HBAR-SAUCE, HBAR-USDC, etc.)
If you have LP tokens containing WHBAR, unstake those LP tokens on the farm page if applicable — these deprecated farms will be found in the “inactive” tab.
Withdraw your liquidity for pairs containing WHBAR in the “My Pools” tab on the liquidity page.
Provide liquidity to the same pair — for example, if you withdraw HBAR-SAUCE LP tokens, provide liquidity back to the HBAR-SAUCE pool. Our site will automatically route your liquidity to the upgraded pools.
If applicable, stake those LP tokens in the new farm to receive HBAR and SAUCE emissions. These farms can be found in the "active" tab of the farm page.
Be mindful of the inverse relationship between APR and liquidity — those who stake first will receive a higher yield.
Note: If you have any questions about the above process, please reach out in the SaucerSwap  and a team member will assist you.
Farm emissions to supported pools containing the current WHBAR will be set to zero – these farms will appear in the inactive tab of the farm page. A new farm will be created for each existing farm containing HBAR. The same token pairs are to be incentivized, with the same weighting scheme. The only difference here is the use of the new WHBAR.
WHBAR and Native Staking Explained
HBAR is not an HTS token — analogous to ETH vs. ERC-20 — so it must be wrapped to interact with the SaucerSwap contracts. This is achieved via a smart contract that stores incoming HBAR and mints wrapped HBAR. These WHBAR tokens are used to provide liquidity in SaucerSwap’s decentralized exchange. When liquidity is withdrawn, WHBAR tokens are sent back to the smart contract and burned, and an equal amount of HBAR is returned to the user.
With the introduction of native staking, the HBAR in this smart contract can be dynamically staked to a permissioned node to generate real yield for users. Since Hedera does not impose slashing or lockup periods, SaucerSwap users can withdraw liquidity instantaneously.
The native staking mechanics of the WHBAR contract are described in the above figure. Here, the WHBAR contract is deployed, setting the stakedAccountId to a simple smart contract. This StakeToSetter contract has an admin key to select a node for staking and allows its beneficiary to withdraw the accrued rewards. The WHBAR contract will not have an admin key and will therefore be completely decentralized.
Once daily, at a random time, an allocation of HBAR native staking rewards is pulled from an intermediary payment splitter contract. This HBAR is swapped for SAUCE in the BrewSaucer contract before being sent to the Infinity Pool. Since the ratio of SAUCE to xSAUCE in the pool increases, so does the relative value of xSAUCE.
Farm
Introduction
Upon providing liquidity to a pool, LP tokens can then be staked in yield farms. Each farm on the protocol corresponds to a liquidity pool (e.g., HBAR-DOV[hts]) and receives weighted token emissions from the farm contract. Farming helps improve the capital efficiency of assets by utilising idle LP pairs to generate yield. Note that users are still collecting swap fees on their staked liquidity.
In addition to gas fees, the protocol charges a $0.25 deposit fee for staking LP tokens in Crop Circles. 
Yield Farming
In this section, we will cover the process of yield farming.
Figure 1. Yield Farming. Note that rounded numbers were used in the calculations. Note that 'Crop Circle' <-> 'yield farm.'
Consider a liquidity provider who stakes 119.93 $AAA-$BBB ssLP tokens in a farm containing 880.07 ssLP tokens. It follows that the farm now contains 1000 ssLP tokens, and the liquidity provider has a ~12% ownership. This farm receives 317.0 SAUCE / min; therefore, the LP earns 317.0 * 0.12 = 38.03 SAUCE every minute.    
APR
The Farm Base APR is calculated as follows:
Where W is the weight of emissions to a farm; P denotes price; E denotes rate of emissions in seconds, where E(SAUCE) = 4.80454 SAUCE/s and E(HBAR) = 0.052083 HBAR/s; and 31536000 is the annualization factor. 
Note that, as additional farm are added, emissions to existing farms will decrease due to reweighting.
The Farm Base APY assumes earnings are reinvested once per day. It is calculated as follows:
The Farm Total APR, or the actual APR earned by yield farmers, is the sum of the LP Reward APR and Farm Base APR:
The Farm Total APY is the sum of the LP Reward APR and Farm Base APY:
Game-Theoretic Farming (WIP)
There will be no lockup period for staking LP tokens in farms, however, there will be a game-theoretic LP staking mechanism, i.e., an option to timelock LP tokens in farms. Users who stake LP tokens without the lockup period earn the standard rates dictated by the protocol. Users who decide to lock up their tokens for a period of time (e.g., 3 months) can unstake early if they so choose, however, this early withdrawal comes at a penalty of the interest accrued in the form of SAUCE. This penalty is paid out on a constant basis (minute by minute) to other users who have locked their LP tokens. Once the lockup period has ended, users who have kept their LP tokens staked will claim their SAUCE and reap significantly higher farm rewards. In essence, this model creates value from market behavior rather than from an underlying change in the protocol. It's a voluntary game - a game of chicken between bulls and bears.
For example, say Alice stakes 100 LP tokens with no timelock, while Bob and Claire each stake 100 LP tokens for a 3-month lockup period. Alice can unstake at any time without incurring a penalty. Claire decides to withdraw her LP tokens from the farm early, and in doing so, suffers a penalty (e.g., 50% of her SAUCE accrued via farm rewards). Bob keeps his LP tokens locked for the duration of his term. Claire's penalty is paid directly to Bob. 
To clarify:
Alice earns the standard rates dictated by the protocol.
Bob earns the standard rates dictated by the protocol plus the penalty from Claire.
Claire earns the standard rates dictated by the protocol minus the penalty from unstaking her LP tokens prematurely.
The proposed penalty on the SAUCE accrued via farm rewards must be high due to the fact that users who do not lock their tokens can manually compound their rewards (i.e., use the SAUCE they receive via farm rewards to mint additional LP tokens, which can then be staked), whereas users who do lock their LP tokens will not have this option. Farm rewards are proportional to the duration of the lockup period and the penalty remains constant, as more users are expected to unstake their LP tokens prematurely from a 6-month lockup period versus a 2-week lockup period.
​
​Farm Tutorial
How to Farm Yield: Instructional Video
How to Farm Yield: Guide
First, connect your  and ensure you have sufficient  to cover gas fees, as well as LP tokens of supported pools, i.e., pools with corresponding yield farm. 
Navigate to the Farm page.
You will see a list of token pairs that are receiving a weighted percentage of emissions from the SaucerSwap farm contract.
Your total value staked is located in the top left corner of the interface. You can filter for specific farms in the top right search bar. Clicking the button directly below this allows you to harvest - or transfer accrued rewards to your wallet - from all farms in which you have staked LP tokens.
Featured: a list of token pairs with farms.
​: the Farm Total APR, or the sum of the Farm Base APR and LP Reward APR. 
Liquidity: the combined value of LP tokens staked in a farm.
Earnings: USD value of accrued tokens through yield farming (user-specific).
Click on a farm to expand the interface.
If you do not have the appropriate LP tokens, click Get Token A - Token B, otherwise click Stake.
Next, enter the number of LP tokens you wish to stake in the pop-up window and click Stake once more. 
Approve the transaction in HashPack.
The transaction should execute within several seconds. If you are encountering issues, reach out to the team in a  support channel.
Transaction details are available on. Click the link in the top right pop-up window to be redirected.
Above is a farm with staked LP tokens. Displayed, from top to bottom, are:
Balance: the USD value and number of staked LP tokens
Token A: number of A tokens representing 1/2 the total value of your staked LP tokens
Token B: number of B tokens representing 1/2 the total value of your staked LP tokens
Earned: the estimated number of tokens earned by yield farming that have yet to be harvested
You can Stake, Harvest, or Unstake at any time. There is no lockup period for staking in farms. 
​
Single-Sided Staking
Introduction
Single-sided staking allows users to earn yield by providing liquidity for one type of asset, in contrast to liquidity provisioning on AMMs, which requires a pair of assets.
In the case of SaucerSwap, users stake SAUCE in the Infinity Pool and receive a liquid receipt token called xSAUCE. The ratio of xSAUCE to SAUCE begins at 1 and increases in perpetuity as the Infinity Pool automatically compounds via SAUCE buybacks and farm emissions.
Users can stake xSAUCE (previously referred to as SAUCEr) in Community Pools to earn HTS tokens from projects incubated by . The xSAUCE token will also be used for governance and liquidity provisioning to the SaucerSwap AMM.
Triple Reward Structure
In this model, yield is derived from three distinct sources: swap fees across all SaucerSwap liquidity pools, yield farm emissions, and HBAR native staking rewards. This latter reward mechanism involves dynamically staking all HBAR in the WHBAR contract to a permissioned node. 
A high-level description of the reward structure is as follows:
The 0.05% protocol fee incurred on all token swaps currently accumulates in an account called feeTo via Uniswap v2 smart contracts. This revenue goes to the DAO treasury at present, but will be reallocated to SAUCE buybacks in mothership.sol (aka the Infinity Pool) once single-sided staking is implemented. The Brew contract is authorized to withdraw LP tokens from feeTo and burn them to itself, after which point it swaps the underlying assets (token 0 and token 1) for WHBAR and SAUCE using authorized user specified bridges, which are token addresses that facilitate the conversion to SAUCE. Once the bridge swaps are complete, the contract pulls its allocation of HBAR native staking rewards from an intermediary payment splitter contract. These HBAR are wrapped and added to the Brew contract’s WHBAR balance. The final swap to take place is a conversion of WHBAR to SAUCE, resulting in SAUCE being the only token in the Brew contract. This SAUCE, along with 3% of SAUCE token emissions from the farm contract, is sent to the Infinity Pool.
Infinity Pool
Since the balance of SAUCE in the Infinity Pool is increasing in perpetuity, so too is the ratio of SAUCE to xSAUCE. Conversely, the relative value of xSAUCE to SAUCE is increasing. Consider the following example:
User A is the first to stake SAUCE in the Infinity Pool. They deposit 10 SAUCE and receive 10 xSAUCE, as the initial ratio is 1:1.
Next, 10 SAUCE derived from swap fees, HBAR native staking rewards, and farm emissions is sent to the Infinity Pool. Since there is 20 SAUCE in the contract and 10 xSAUCE is the total supply, the ratio is now 1 xSAUCE : 2 SAUCE. User A can redeem their 10 xSAUCE for the 20 SAUCE at any time, based on this ratio.
Say User A does not redeem their xSAUCE. User B deposits 10 SAUCE in the pool and, since the ratio is 1:2, they get half of their deposit as xSAUCE, which would be 5 xSAUCE. Now the Infinity Pool contains 30 SAUCE and 15 xSAUCE, hence the ratio is maintained.
The ratio only changes as SAUCE are sent to the Infinity Pool and distributed equally among all xSAUCE holders, because each xSAUCE becomes worth more SAUCE.
APR
The single-sided staking APR is as follows:
Where SAUCE/xSAUCE is the balance of each token in the Infinity Pool, taken as the exchange rate. This rate is updated once per day, therefore subscripts f - i ≈ 24h. Note that the APR displayed on the Stake SAUCE UI is the 5-day average of the above formula.
Single-Sided Staking Tutorial
How to Stake SAUCE: Instructional Video
How to Stake SAUCE: Guide
First, connect your HashPack and ensure you have a non-zero balance of SAUCE and sufficient HBAR to cover gas fees.
Navigate to the Stake page.
Scroll down to the interface with header Phase 1.
SAUCE/xSAUCE: the balance of SAUCE in the Infinity Pool divided by the circulating supply of xSAUCE. This exchange rate updates once a day when rewards are sent to mothership.sol.
Claimable SAUCE: the total number and dollar amount of SAUCE you can claim by unstaking all of the xSAUCE in your account. This is a measure of principal and accrued rewards, and is calculated by multiplying your xSAUCE by the SAUCE/xSAUCE exchange rate.
TVL: the total claimable SAUCE in the Infinity Pool, expressed in dollar amount.
Approximate APR: 5-day average of day-over-day change in the SAUCE/xSAUCE exchange rate, annualized. For more information, see .
First click Stake.
Next, enter the number of SAUCE tokens you wish to stake in the pop-up window and click Stake once more. If you have not already associated xSAUCE, you will be prompted to do this first. Approve the association transaction in HashPack.
Next, approve the stake transaction in HashPack.
The transaction should execute within several seconds. If you are encountering issues, reach out to the team in a  support channel.
Transaction details are available on Hashscan. Click the link in the top right pop-up window to be redirected.
Once staked, your Claimable SAUCE will update once a day at random. This number will always increase, although the dollar amount will fluctuate up and down depending on the token’s price.
To unstake, simply click Unstake, enter the number of tokens you wish to unstake in the pop-up window, and click Unstake once more.
Approve the transaction in HashPack.
You can stake or unstake at any time. There is no lockup period or slashing in the Infinity Pool.
Community Pools
Community Pools are complementary to single-sided staking and serve as an onboarding ramp for HTS projects. These projects will have a liquid market for their token without the need to approach accredited investors and / or seek listing on centralized exchanges. This enables them to accelerate their development within the Hedera ecosystem.
There are several moving parts to Community Pools. Firstly, an HTS project must apply for an IDO through  - a premier launchpad & accelerator of the Hedera ecosystem. This is to ensure the project has been vetted, its code is secure (which may necessitate an audit), and the developers behind said project are acting in good faith - SaucerSwap does not want to become a playground for bad actors. Next, a core proposal will be made and the community will vote on whether this project should be listed. If the proposal reaches a passing vote by quorum, the HTS project will be listed.
HTS projects voted in by the DAO will first create a liquidity pair (their token and HBAR). By initializing this LP, the project is setting the price of their token. These pools will have a minimum liquidity requirement to ensure risks inherent to the AMM (i.e., slippage and IL) are minimized.
Once this LP is created, the HTS project will create a single stake pool containing their token. This single stake pool will require the project to allocate a percentage of their token’s max supply, which will be emitted over a period of time, hence single stake pools are time-sensitive. This % token allocation and time duration are up to the discretion of the project’s development team, so they set the rate at which their token is emitted. This emission rate will determine the staking rewards of their pool. Users are incentivized to stake xSAUCE in this single-stake pool, as they will receive staking rewards in the form of the project’s token. Furthermore, xSAUCE holders can participate in multiple single stake pools simultaneously, allowing them to pull in multiple income streams (sum of APRs).
Given that multiple single-stake pools will be open at the same time, each with varying staking rewards, there will be an element of competition between HTS projects on the protocol. This will create a free market economy, which embodies the decentralized spirit of SaucerSwap, and by extension, cryptocurrencies as a whole. With this being said, certain parameters will be put in place to mitigate against negative externalities.
SaucerSwap will support a farm for the corresponding HTS project. Users who have obtained the project’s token via staking xSAUCE in the single stake pool, swapping for it in the LP, or purchasing it on secondary markets (should this apply), can exchange it - with equal value parts HBAR - for LP tokens, which can then be staked in this farm. SAUCE emissions will be used to reward users for staking in this farm. The HTS project team can swap their project’s token for HBAR in this pool, which affords them capital to accelerate development of their project. This process should come at a very low overhead, given Hedera’s low fee structure (e.g., creating, minting, and transferring their token).
SaucerSwap offers a novel model designed to grow the ecosystem, all while incentivizing members of the community to participate.
Bridge
SaucerSwap can leverage applications such as  (an agnostic, utility-first approach to transferring digital assets across public distributed networks) to bring wrapped ETH (WETH) and MATIC (WMATIC), among other cross-chain assets, to the protocol.
SaucerSwap plans to integrate a third-party bridge on its front-end. Here, much attention will be directed towards simple and elegant UI/UX design. This integration will streamline the process of bridging cross-chain assets, which can be swapped or deposited into liquidity pools to earn yield.
Supported networks include:
Ethereum
Avalanche
BSC
Polygon
Social Profiles
SaucerSwap will provide added functionality to social profiles. One such added functionality is a limited series of generative Sauceling NFTs utilizing a set of art assets. Each NFT will have a unique name and description to complement the SaucerSwap lore.