One mechanism, stated plainly, and nothing else claimed.
RETURN is a community token on Arc with a single economic rule: creator fees are split in half, one half goes to a public Circle contract deployer address, the other half buys and burns $RETURN. That is the whole product.
It all comes full circle.
Trading $RETURN generates creator fees, paid in USDC to the project’s creator wallet. Those fees do not sit there. Once a day they are processed under a fixed, public policy: 50% is transferred to a publicly identified Circle contract deployer address, and 50% is used to buy $RETURN on the open market and remove it from circulation.
The first half is a voluntary gesture toward the infrastructure this token lives on. The second half is the part that comes back to everyone still holding. Together they close the loop — which is where the name comes from.
How the money moves.
- Step 01TradingPeople trade $RETURN on Arc.
- Step 02Creator feesTrading generates creator fees in USDC, paid to the project's creator wallet.
- Step 0350 / 50 splitOnce a day at 18:00 UTC, the accrued fees are split in half.
- 50% · One halfReturn to CircleTransferred to the publicly identified Circle contract deployer address. Voluntary, unilateral, unrequested.50% · The other halfBuy $RETURNSpent buying the token on the open market through Arc liquidity.ThenBurnThe purchased tokens are provably removed from circulation.
- And soIt all comes full circleValue leaves as fees and comes back two ways: to the infrastructure the token is built on, and to everyone still holding $RETURN.
RETURN creator fee policy
Creator fees attributable to RETURN are processed through the Daily Return mechanism. The target allocation is:
- 50%to the publicly identified Circle contract deployer address 0xadB384F7fa7486422051D2a896417EAAb9E5A9D1
- 50%to an open-market buyback of $RETURN, followed by a burn
Daily processing is targeted for 18:00 UTC.
Timing and exact amounts may vary because of transaction confirmation, network conditions, gas requirements, swap execution, rounding, or technical failure. Only confirmed on-chain transactions count toward reported totals.
This policy describes intent, not a guarantee or an obligation. It can change, and any change will be stated on this page.
Manual in V1, and we say so.
The Daily Return is executed by a human operator from a wallet they control. It is not an automated smart contract, there is no keeper, and this website has no ability to move funds — it only publishes what has already happened.
V1 is deliberately manual: it keeps the project live without introducing smart-contract risk that nobody has audited. A future version could route fees through a RETURN Router contract with a public processFees() call, but that does not exist today and is not promised.
Because a person executes it, a window can be late, partial, or skipped. When that happens the record on the Daily Returns page says so rather than quietly disappearing.
How the buy is done.
- 01Record the creator-fee USDC balance eligible for that window.
- 02Calculate 50%.
- 03Transfer that half to the Circle contract deployer address.
- 04Use the other half to buy $RETURN through the available Arc liquidity route, with proper slippage protection — never a naive minimum-output of zero.
- 05Remove the purchased $RETURN from circulation.
- 06Record every transaction hash.
- 07Publish the record here.
What “burned” means here.
The burn mechanism has not been finalised and published yet. No tokens are described as burned until it is.
The mechanism has not been finalised. Until it is, no tokens are described as burned anywhere on this site and the burn figure stays at zero.
Where the numbers come from.
Every figure on this site is derived from confirmed transactions. A leg with no transaction hash contributes zero to every total — the site never reports an intention as a result, and there are no mock or placeholder statistics anywhere in production.
V1 stores the confirmed records in a JSON file committed to the repository, so the git history is itself an append-only log of what was published and when. The data layer is built so that reading the same figures directly from Arc is a change in one module rather than a rewrite.
What this project does not claim.
RETURN is not an official Circle token. It is not Circle-backed, Circle-funded, or a Circle partnership. Circle has not approved RETURN, does not receive revenue from it, and the destination address is not a Circle treasury.
What is true is narrower and, we think, more interesting: the destination address has a strong public evidence trail as the deployer of official Circle contracts. That evidence is enough on its own, and exaggerating it would only make it weaker.
See the full evidence chain →RETURN is an independent, community-created token. It is not affiliated with, sponsored by, endorsed by, operated by or connected to Circle Internet Group, Inc., Arc, RadarDEX or any of their affiliates.
RETURN voluntarily and unilaterally sends a portion of its creator fees to 0xadB384F7fa7486422051D2a896417EAAb9E5A9D1 — a public address identified by Etherscan as “Circle: Deployer 2” and independently resolvable on-chain as the contract creator of official Circle CCTP contracts.
Circle has not requested, approved or acknowledged these transfers. Sending funds to an address does not create a relationship with whoever controls it, and no partnership, sponsorship, endorsement, benefit or expectation of benefit is implied by doing so.
A deployer address is not a treasury and is not a fee-recipient address. Circle’s own open-source configuration defines deployer, owner and fee-recipient as separate roles. We describe this address only as what the public record supports: a contract deployer.
Nothing here is financial advice, an offer, or a solicitation. Crypto assets are volatile and you can lose everything you put in. RETURN has no roadmap obligation, no guaranteed continuation of the Daily Return, and no expectation of profit is created by this page. Do your own research.