How do you auto-compound reflection rewards on Solana?

Identify the token your project distributes, choose that as the input, and select the holding you want to accumulate as the output. Approve a cumulative spending limit in Autocompounder. Eligible swaps then convert available rewards, but future distributions still depend on the project's separate eligibility and funding rules.

Does buying more of a reflection token guarantee more rewards?

No. A larger eligible holding may affect a project's allocation formula, but rewards also depend on funding, trading activity, snapshots, exclusions, and other distribution rules. Those conditions can change. Autocompounder executes conversions; it cannot guarantee a distribution, a particular reward amount, or a profitable investment.

Should every small reward be compounded immediately?

Not necessarily. Swaps have costs, liquidity constraints, and possible transfer taxes. The keeper may wait until the available balance makes execution economical under its policy. Increasing your approved allowance does not make a tiny balance valuable enough to trade or guarantee a faster execution.

How to Auto-Compound Reflection Rewards on Solana

Reflection rewards often arrive in a different token from the one you hold. Reinvesting them means converting that received asset back into the holding you want to accumulate. Doing so repeatedly can form a compounding loop, provided the project's reward rules give that larger holding a role in future distributions.

The conversion is only one part of the loop. A useful plan separates the project's reward mechanism, your spending permission, and the market trade. Autocompounder handles the conversion step; it does not generate the rewards or determine their value.

How do you auto-compound reflection rewards?

Choose the token you actually receive as Autocompounder's input and the token you want to accumulate as its output. Approve a cumulative input allowance. The keeper attempts eligible conversions when tokens are available; whether the resulting holdings earn further rewards depends on the project's own distribution rules.

Before configuring anything, identify the reward token by its full Solana mint address. Then identify the holding token separately. A familiar ticker is insufficient when several assets share a name or a project distributes a representation of an asset native to another network.

What makes a conversion into compounding?

Consider a hypothetical project that distributes token A to eligible holders of token B. You receive A, convert it into B, and hold the additional B. If a future eligibility calculation includes that larger balance, the reinvestment can change your share of future rewards. This is a mechanism, not a return forecast.

If you convert A into an unrelated asset C instead, you are redirecting rewards. That may match your preferences, but it is not automatically compounding the original position. The same tool can implement either choice, so select the output according to your intended exposure rather than the feature's name.

Some projects already distribute the same token you hold. In that case, receiving more tokens may itself increase your holding without a swap. Autocompounder requires different input and output tokens; do not create an unnecessary round trip merely to describe the process as compounding.

Which parts of the reward loop are outside the tool?

The project decides how rewards are funded and allocated. Its system may use eligible balances, snapshots, exclusions, minimum values, or a claim procedure. An automatic conversion does not replace a required claim or make an ineligible wallet qualify. Verify receipt before diagnosing a missing swap.

The market determines what the received token can buy. Liquidity and prices can change between the reward payment and execution. A larger number of output tokens does not necessarily represent a larger dollar value, and increasing exposure to the original token can increase losses if its price falls.

Finally, your wallet's on-chain permission controls what the tool can spend. Rewards can continue arriving after an allowance is exhausted, but they cannot be converted through that exhausted approval until you authorize more. Each layer has its own state and failure conditions.

How should you choose the spending limit?

Set the limit in units of the received input token. It is cumulative across swaps, not a dollar-denominated budget or a fresh cap for every distribution. Choose an amount you are comfortable making available before reviewing the configuration again; the application cannot infer that preference from your balance.

Already-held input tokens are available too. The account does not distinguish rewards from purchases or transfers you made for another reason. If preserving those holdings matters, account for them before approving or use a wallet arrangement that separates the intended activity.

For an illustrative quantity example, a 12-token allowance with 4 consumed leaves 8. A later deposit of 6 tokens increases the balance but does not raise that remaining 8. If the available balance exceeds the allowance, approval still limits how much can be converted.

How do fees affect reinvestment?

The current service fee is 1% of swap output, collected in that output token. Setup network costs and account rent are separate. The keeper pays ongoing swap transaction costs and uses an economics check before execution. Small available balances can therefore wait rather than being converted on every arrival.

Some token designs also charge transfer taxes. Those are token-level mechanics, distinct from the service fee. They can affect the amount delivered by transfers during the route and into your wallet. Do not assume that subtracting the service percentage from a displayed market estimate gives an exact final receipt.

Keep the accounting in token units first: input consumed, output received, service fee, and any transfer fees. Then, if useful, value those amounts using clearly dated prices. A changing quote is not a reliable record of what an earlier transaction actually delivered.

What should you monitor after enabling the loop?

Follow a single completed transaction before expanding the allowance. Verify the input mint, output mint, recipient wallet, fee recipient, and reduction in remaining permission. A setup confirmation only proves the configuration and approval were created; it does not prove a reward has been received or converted.

When a swap is missing, check the layers in order: did the project deliver the reward, is the balance in the approved account, is allowance available, and can the keeper execute a supported route? Raising the cap does not address missing rewards, illiquid markets, or service outages.

If you change your investment intention, stop the conversion rather than assuming it will follow your new preference. An existing configuration continues to name its stored output. Its behavior does not change because you buy another token manually or stop reading the project's announcements.

How do you set up or end the automation?

Use the incoming-token setup guide for the exact interface sequence. It shows how to select both assets, approve an amount, and recognize the configured state. This avoids duplicating the same walkthrough here while keeping the reinvestment decision separate from the buttons.

Use the spending-limit guide to update or cancel later. Cancellation stops future authorized swaps after confirmation; it does not reverse completed conversions. Keeping the browser closed is not cancellation, because the keeper operates independently of the page.

Autocompounder

Convert received reward tokens into your chosen holding with a finite input-token allowance.

Try it now