Sato Hub
analysis

COTI Sets Year-End Shutdown for DJED and SHEN: What Builders Should Check

A December 31 cutoff, about 1 million DJED reported in circulation, and a checklist for agents that hold tokens.

  • Published2026-11-20
  • Read4 min

COTI says it is shutting down its DJED and SHEN services at year-end, and it is asking holders to act by the December 31 cutoff. The Defiant reports that holders should first withdraw any tokens they have deposited in DeFi, and that about 1 million DJED remain in circulation. That is most of what the public reporting says so far, and it is worth saying out loud, because a shutdown notice with a deadline is the kind of story where people fill the gaps with guesses.

We will not fill them. This post sticks to what the source states, flags what it does not, and turns the notice into a checklist builders can use.

What was claimed, and by whom

Everything below comes from one outlet's report of COTI's notice:

  • ▸COTI is ending its DJED and SHEN services at year-end.
  • ▸The cutoff for holders to act is December 31.
  • ▸Holders are told to withdraw DJED or SHEN deposited in DeFi first.
  • ▸About 1 million DJED remain in circulation, per The Defiant.

We have not independently verified the circulation figure, and the report does not give a SHEN figure. Treat the number as reported, not measured.

What the report does not say

The article is short. As fetched, it gives no reason for the shutdown. It does not describe what "services" covers in mechanical terms, what happens to tokens still held after December 31, or whether there is any redemption path. It carries no direct quote from COTI.

Those are the questions that matter most to a holder, and the answers live in COTI's own announcement, not in a news summary and not in this post. If you hold either token, read the primary notice before you do anything. If you cannot find one, ask COTI through its official channels rather than relying on a secondary account, including this one.

Why builders should care anyway

Sato Hub is where you build onchain agents, and agents hold and move tokens without anyone watching the news. A person who misses a sunset notice loses a few days. An agent that misses one keeps running its loop against a service that has stopped answering.

The pattern is general. Any stack that touches a stablecoin or a protocol token has a dependency on someone else's roadmap. Notice periods like this one are the moment that dependency becomes visible. A few things to check in your own build:

1. Inventory what your agent holds. List every token in the agent wallet and every position it has opened in DeFi, by contract, not by ticker. If DJED or SHEN is in that list, this notice is about you. 2. Look for deposits, not just balances. The notice specifically points at tokens deposited in DeFi. A wallet balance of zero can hide a position sitting in a pool or a lending market. 3. Give the agent a stop condition. Spend limits and allow-lists are the usual advice. Add an expiry: a date after which the agent refuses to touch an asset unless a human re-approves it. 4. Separate the exit from the loop. A withdrawal before a deadline is a deliberate action. Wire it to a human approval step, not to the agent's autonomous strategy. 5. Watch the source, not the headline. Subscribe to the issuer's own announcement channel and treat news coverage as a pointer to it.

The sass, aimed where it belongs

"Stablecoin" and "service" are comfortable words until a date shows up next to them. Nothing in this report suggests anyone did anything wrong, and we are not going to imply otherwise. The lesson is about the idea, not the team: an asset is a dependency, and dependencies have end dates. An agent design that never models an end date is a demo, not a system.

What to watch

  • ▸COTI's primary announcement. Mechanics, redemption details and any reason for the shutdown belong there. Expect the detail to be fuller than a news summary.
  • ▸The circulation figure. About 1 million DJED were reported in circulation. Whether that number moves before December 31 is an observable, onchain fact anyone can check.
  • ▸DeFi deposits. The notice asks holders to pull tokens out of DeFi first. Watch for how the venues that list these tokens respond; each will publish its own handling.
  • ▸Your own agents. If one of them touches DJED or SHEN, decide now who withdraws, and when.

Sato Hub tracks the stack agents are built from: wallets, payment rails, skills and MCPs, with the Sato Score as a transparency and liveness signal, not a safety grade. A listing that goes quiet or is retired is exactly the sort of change worth catching early. Describe the agent you want and see what the stack looks like at satohub.ai/build.

Sources

Join the Sato Hub Briefing

Sign up for the Briefing: the agents, tools, and infrastructure that actually shipped, and why they matter.