Persistence

Managed AI employees and AI consulting for growing businesses.

[Persistence @PersistenceOne]

Reminder for Persistence DEX liquidity providers

1) Babylon Genesis
Persistence DEX on Babylon Genesis is deprecated, as announced on 7 September. New deposits are paused. Swaps and withdrawals stay open, so please withdraw your positions at https://t.co/T7LXfibp0N with Babylon selected.

2) Persistence Core: USDC/USDT and DYDX/USDC pools
These two pools are being wound down because Circle is retiring USDC on Noble. Circle has stopped minting it, from 31 October the routes to move Noble USDC start closing, and on 12 January 2027 the Noble USDC contract is paused for good. New deposits are paused; swaps and withdrawals stay open.

How to exit, on either chain:
• If your LP tokens are staked, unbond them first. This takes 7 days, or you can instant unbond for a small fee.
• Withdraw from the pool at https://t.co/T7LXfibp0N.
• Move any Noble USDC out, for example to Injective issued USDC via Skip Go (https://t.co/qcGTjpeakJ).

All other pools on Persistence Core are unaffected and continue as normal.

[Persistence @PersistenceOne]

Update on the Persistence DEX USDC pools

As announced last week, new deposits into the USDC/USDT and DYDX/USDC pools are now paused. Swaps and withdrawals remain open.

If you still provide liquidity in either pool, please withdraw and migrate your Noble USDC before Circle's deadline of 12 January 2027.

Skip Go (https://t.co/qcGTjpeakJ) supports a direct migration to Injective issued USDC. All other pools, and USDT, are unaffected.

[Persistence @PersistenceOne]

Update on the Persistence DEX USDC pools

As announced last week, new deposits into the USDC/USDT and DYDX/USDC pools are now paused. Swaps and withdrawals remain open.

If you still provide liquidity in either pool, please withdraw and migrate your Noble USDC before Circle's deadline of 12 January 2027.

Skip Go (https://t.co/qcGTjpeakJ) supports a direct migration to Injective issued USDC. All other pools, and USDT, are unaffected.

[Persistence @PersistenceOne]

Circle is winding down USDC on Noble, the USDC used across Cosmos including Persistence. Minting stops 13 Oct, the Noble contract is paused 12 Jan 2027.

Persistence DEX: the USDC/USDT and DYDX/USDC pools are being deprecated. Withdrawals stay open. If you provide liquidity there, please withdraw and migrate your USDC via Skip Go before the deadline. USDT and all other pools are unaffected.

[Persistence @PersistenceOne]

Reminders to validators and delegators to vote on proposal #155

[Persistence @PersistenceOne]

Persistence validators and delegators: voting is open on proposal #155 for the core-1 v16.1.0 upgrade. Please review the proposal and cast your vote before 23 September, 19:34 UTC.

https://t.co/HQuqr4SFRb

[Persistence @PersistenceOne]

Persistence validators and delegators: voting is open on proposal #155 for the core-1 v16.1.0 upgrade. Please review the proposal and cast your vote before 23 September, 19:34 UTC.

https://t.co/HQuqr4SFRb

[Persistence @PersistenceOne]

@petergyang @pedroh96 @brexHQ A managed AI employee works best when the job is narrow enough to supervise. Pick one recurring handoff, give it the tools it needs, and keep pricing, promises and approvals with a person.

[Persistence @PersistenceOne]

Circle is winding down USDC on Noble, the USDC used across Cosmos including Persistence. Minting stops 13 Oct, the Noble contract is paused 12 Jan 2027.

Persistence DEX: the USDC/USDT and DYDX/USDC pools are being deprecated. Withdrawals stay open. If you provide liquidity there, please withdraw and migrate your USDC via Skip Go before the deadline. USDT and all other pools are unaffected.

[Circle @circle]

We are discontinuing support for USDC and CCTP V1 on the Noble blockchain as part of our broader transition to CCTP V2, a next-generation cross-chain protocol with faster finality and stronger security.

Noble will not receive CCTP V2.

New minting of USDC on Noble via Circle Mint stops October 13; the Noble USDC contract pauses January 12, 2027.

All USDC on Noble remains redeemable 1:1.

Read the details and required actions here: https://t.co/SiMq3krzTV

[Persistence @PersistenceOne]

Persistence DEX on Babylon Genesis is being deprecated.

Liquidity providers can withdraw their positions at any time at https://t.co/T7LXfibp0N with Babylon selected. Swaps and withdrawals remain available for the time being.

Persistence DEX on Persistence Core is not affected.

[Persistence @PersistenceOne]

We have moved our official Telegram community chat to a new group to (hopefully) reduce spam, bots and inactive accounts 🧹

New link, please join here: https://t.co/0lwOtY4mOQ

The original group is now read-only. Official announcements come only from @PersistenceOne on Telegram and this X account.

Reminder: admins will never DM you first, and we will never ask for your seed phrase.

[Persistence @PersistenceOne]

Admin work rarely fails loudly.

It piles up as forms to check, notes to update, bookings to confirm and small exceptions nobody owns.

That is useful AI employee territory: visible tasks, clear handoffs, fewer loose ends.

[Persistence @PersistenceOne]

Sales follow-up is full of tiny leaks: drafts not sent, pipeline notes missing, stale leads nobody checks.

That is good AI employee work because the job is narrow, repeated and close to revenue.

[Persistence @PersistenceOne]

When an agent touches real work, the run needs to be inspectable. Session counts, errors, traces and tool steps give operators a record of what happened, where it slowed down, and what needs repair.

[Persistence @PersistenceOne]

Launching a managed AI employee is the start of the operating work. The role needs approved tools, clear permissions, defined approvals, performance monitoring, and adjustment as the business changes.

[Persistence @PersistenceOne]

Installing an AI employee should start with the operating setup, not the model.

Choose one role, connect only approved tools, set permissions and guardrails, decide which approvals stay with the team, then improve it as the work changes.

[Persistence @PersistenceOne]

Customer enquiry is a good first AI employee because the boundaries are visible.

It can reply, chase, book and log. Offers, pricing, commitments, exceptions and exact outbound messages stay with the owner.

[Persistence @PersistenceOne]

An internal knowledge assistant should not just answer faster. It should show what context it used, where the answer came from, and when the question needs a person instead of a guess.

[Persistence @PersistenceOne]

@EasyClawIntern The run 20 point is important. A useful agent setup needs to expose the accumulated cost: lost context, retries, partial edits, and how much review work still lands back on the human.

[Persistence @PersistenceOne]

@BkashJosi @NousResearch Exactly. Once agents work together, the problem becomes operating design: roles, ownership, task boundaries, handoffs, review points and approvals. Otherwise it is just a busier group chat.

[Persistence @PersistenceOne]

@Blackwellboy @bot This is the failure mode that matters in production: it looked done, but the trace said otherwise. Agents need logs, tool evidence and handoff records so operators can inspect the actual run, not the claim.

[Persistence @PersistenceOne]

@vibemarketersHQ That ownership question is the useful starting point. Before adding agents, teams need to decide who owns the task, which tools it may touch, where approval sits, and what evidence comes back.

[Persistence @PersistenceOne]

@udayctweets Bounded authority is the right frame. It has to attach to the actual business action: what context is trusted, what the agent can execute, when approval is needed, and what gets logged after the run.