Jonps5

[Cortensor @cortensor]

🛠️ DevLog – Mainnet Full User Task E2E With Payment Worked on Ephemeral Path

A quick follow-up on the Mainnet Full / L3 baseline check.

🔹 Current progress
- We ran the Mainnet Full user-task flow E2E with payment
- The ephemeral-node path worked in this baseline check
- Task execution, miner participation, result flow, and payment-side behavior all moved through the expected path

🔹 Why this matters
- This is an important step beyond basic infra checks
- Earlier baseline checks showed network task, node level, node pool, dashboard, and stats visibility were mostly functioning
- Now the user-task path is also starting to validate on Mainnet Full

🔹 What comes next this week
- We’ll continue checking more edge cases around the user-task flow
- We’ll also test the dedicated-node path as part of the next baseline pass
- Payment behavior will continue to be monitored as more task paths are exercised

🔹 Current takeaway
- Mainnet Full baseline checks are moving forward
- ephemeral-node user-task E2E with payment worked
- next checks are dedicated-node flow and additional edge cases this week

#Cortensor #DevLog #MainnetFull #L3 #NodeOps #Infra

[Cortensor @cortensor]

Cortensor is starting on @Arbitrum because the rollout needs more than a chain to deploy on.

It needs a path that fits the product flow:

- responsive sessions
- routing and validation
- hosted/API access
- dedicated-node rollout
- L2 first, then Orbit L3

Mainnet Lite starts the controlled path on Arbitrum L2.

Mainnet Full expands toward the fuller native stack on Arbitrum Orbit L3.

That staged path is the key reason.

#Cortensor #Arbitrum #MainnetLite #MainnetFull #AIInfra

[Jonps5 @Jonps51]

@kunagisystems Lol, this guy just checked with chatgpt lmao. I went to the IBM partner site. Is not there. Larp

[Cortensor @cortensor]

🗓️ Weekly Recap – Mainnet Lite Progress, Mainnet Full Prep & Portal Evolution

With Phase #4 wrapped up, this week shifted into Mainnet Lite preparation while continuing parallel groundwork for Mainnet Full* Most of the effort went into infrastructure, Portal V1, and operational readiness.

🔹 Phase #4 – Wrap-Up Complete
- Phase #4 prize processing was completed, closing out rewards for 24 qualified nodes.
- Focus has now fully shifted from Testnet execution into Mainnet Lite preparation.

🔹 Mainnet Lite – Baseline Progress
- Mainnet Lite is now running together with node operators, moving from isolated prep into real operational testing.
- Heartbeat/ping cadence was tuned further to reduce Arbitrum gas costs while maintaining operational usability.

🔹 Mainnet Lite – Router & E2E Progress
- Router domains/DNS are configured for the planned endpoints, with the first two endpoints already live on Mainnet Lite.
- Another dedicated and ephemeral E2E validation pass completed successfully, with router-side testing continuing.

🔹 Mainnet Full – Early Parallel Prep
- Mainnet Full infrastructure continued progressing with chain setup, contracts, bridge flow, explorer, dashboard, indexer, and oracle components all functioning in rough form.
- Router rollout also started, with the first two endpoints online and additional endpoint expansion planned next.

🔹 Portal V1 – Product & Gateway Progress
- Portal continued maturing across auth, API keys, request visibility, admin surfaces, and hosted request flow.
- API Gateway, router pools, and stress testing continued to evolve toward a more production-ready path.

🔹 Portal V1 – Usage & Public Stats
- Token-based usage tracking, public Portal Stats, caching, dark mode, and observability all received another round of improvements.
- Public stats now reflect live environment data and provide a simple public-facing status layer.

🔹 Portal Infrastructure & Backend
- Portal stress testing resumed after Testnet-1a recovery, now focusing on larger prompts and heavier token workloads.
- Early backend work beyond Supabase also began, establishing a longer-term migration path while Supabase remains the current production direction.

🔹 Infrastructure & Contracts
- Testnet/Mainnet RPC separation continued on newly provisioned servers to support both Mainnet Lite and future Mainnet Full.
- Session payment, staking, rate-limit, and session queue contracts were reviewed, hardened, redeployed, and now look good overall with only minor cleanup remaining.

🔹 PyClaw & Product Direction
- PyClaw development continues alongside Mainnet work, with the first public development release still planned as an early iterative snapshot.
- Public messaging also continued aligning the broader stack: Network & Infra → Portal → Corgent → Bardiel → PyClaw as one connected platform.

A productive transition week overall - Mainnet Lite has moved into real operational testing, Mainnet Full groundwork continues in parallel, and Portal V1 keeps evolving from a prototype into a practical hosted product.

#Cortensor #MainnetLite #MainnetFull #Portal #AIInfra #DePIN #PyClaw #Corgent #Bardiel #Arbitrum #L3

[Jonps5 @Jonps51]

@WhiteHouse @RobinhoodApp @vladtenev Trump accounts it is 0x86775f2156A9cDF5884Eb45a6Aa93c1fB6c6F235

[Jonps5 @Jonps51]

@SolvioAgent What is the utility of the token?

[Cortensor @cortensor]

🛠️ DevLog – Mainnet Router Domains Are Set, Next Comes Node Configuration

A quick follow-up on the router setup side.

🔹 Current progress
- The router domains / DNS are now set for both environments:
- https://t.co/koX2H7h1oV
- https://t.co/5YpvALJRYq
- https://t.co/h2hQLVFdRT
- https://t.co/MxGbHoGwO7
- https://t.co/49piKh5C9I
- https://t.co/arZOiGeyfQ
- https://t.co/Ah6YLmky8n
- https://t.co/xh1dAz8XMr

🔹 Environment mapping
- m0 = Mainnet Lite
- m1 = Mainnet Full

🔹 What comes next
- The next step is configuring the router nodes underneath
- That includes config, route/session mapping, and the rest of the endpoint-side setup needed before fuller testing

🔹 Current takeaway
- domains and DNS are now in place
- next comes the actual router-node configuration and mapping work behind them

#Cortensor #DevLog #Router #MainnetLite #MainnetFull #Infra

[Cortensor @cortensor]

🔎 Recap: What Cortensor Network Is and Why It Matters

A quick recap on what Cortensor Network is in the broader stack.

At the simplest level, Cortensor Network is the execution, routing, and trust layer underneath everything else.

It is what makes it possible to:
- run work across nodes
- validate outcomes
- support privacy-aware data handling
- expose usable product layers on top

So from the outside, Cortensor is not just raw distributed capacity.

It is the layer that turns distributed node capacity into something programmable, verifiable, observable, and productizable.

That is why the rest of the stack can exist on top of it.

#Cortensor #AIInfra #AgenticAI #DePIN #Arbitrum

[Jonps5 @Jonps51]

@WallStreetAlfa @curiosvintage @RobinhoodApp 0xa4874f62c8826E19cF8691BCAbd02fe1a0B7401F no it isnt. This is the legit ca

[Cortensor @cortensor]

🛠️ DevLog – Docs V2 Preview Website Is Now Live in Early Form

A quick update on the docs side.

🔹 Current preview
- The new Docs V2 preview is now live:
- https://t.co/JWno6r2HgG

🔹 What it is
- Docs V2 is a cleaner, more structured rewrite of the older docs site
- A lot of the current content was ported from the older https://t.co/7orW4VWLVJ site
- That means some pages may already be accurate, but still need more review, reorganization, and polish

🔹 Current expectation
- This is still an early draft / preview
- It should be treated as a rough public-facing version, not the final fully refined docs experience yet

🔹 What comes next
- We’ll keep iterating on it further during this quarter
- The goal is to keep improving structure, clarity, accuracy, and the overall reading path as the stack and products become more mature

🔹 Current takeaway
- Docs V2 preview is now visible in public
- it is still early and rough
- and it will keep improving through this quarter

#Cortensor #DevLog #Docs #Documentation #AIInfra

[Cortensor @cortensor]

🛠️ DevLog – Docs V2 Preview Is Taking Shape for Q3

A quick note on the new Docs V2 direction.

🔹 What Docs V2 is
- Docs V2 is a cleaner, more structured rewrite of the older Cortensor docs site
- It is being reorganized around the current stack and real user paths, instead of older scattered narratives and experiments

🔹 What is improving
- clearer structure across:
- protocol / contracts
- node roles
- router / API surfaces
- products
- ecosystem
- roadmap
- better cross-linking
- updated diagrams
- clearer operator and developer guidance

🔹 Why this matters
- The older docs still contain a lot of useful raw context
- But they are uneven, partially outdated, and spread across older experiments and storylines
- Docs V2 is meant to turn that into a much cleaner public-facing docs experience

🔹 Current status
- This is still WIP and still rough in places
- Some sections are already useful, while others are still being refined for:
- accuracy
- completeness
- polish

🔹 Timing
- Docs V2 preview will be shared during Q3
- The rough window is between Mainnet Lite and Mainnet Full, as the stack and product surfaces continue becoming clearer

🔹 Current takeaway
- Docs V2 is not just a visual refresh
- It is a more structured rewrite around how the Cortensor stack actually works today
- and the early preview should start becoming visible during Q3

#Cortensor #DevLog #Docs #Documentation #AIInfra

[Cortensor @cortensor]

🛠️ DevLog – Cortensor L3 Is Ending Phase #4 in a Much Stronger Place

A quick recap on where the Cortensor L3 path stands as we move toward the end of Testnet Phase #4.

🔹 Current scale so far
- The L3 path has now processed:
- over 8M total blocks
- over 16.5M total transactions

That gives a much better picture of where the network stands now versus where it started.

🔹 Why this matters
- This phase was not only about keeping the chain running
- It was also about exercising the broader infra path under real usage, repeated task flow, and product-facing traffic on top

🔹 Recovery / infra ops side
- We also had to work through a real recovery scenario during this phase
- That was painful, but it was also useful
- It helped prove more about:
- recoverability
- rebuild / reindex flow
- L3 infra ops readiness
- how the stack behaves under edge cases instead of only normal paths

🔹 Current takeaway
- As Phase #4 comes to an end, the Cortensor L3 path is in a much more robust place
- not just because of raw block / tx count
- but because it has now gone through both sustained usage and real infra recovery scenarios too

#Cortensor #DevLog #L3 #Testnet1a #AIInfra #Arbitrum

[Cortensor @cortensor]

Mainnet Lite comes first for a reason.

A more practical and controlled L2 path on @Arbitrum, built for early hosted access, developer APIs, and real mainnet validation before the fuller stack rolls out.

It is also the earlier demo / playground-style path where the system can be used, tested, and refined under real mainnet conditions before broader expansion.

Q3 2026 has started, and Mainnet Lite is the first mainnet step we are building toward in this phase.

#Cortensor #MainnetLite #Mainnet #Arbitrum

[Cortensor @cortensor]

🛠️ DevLog – Testnet1a Is Back to Normal, Portal Stress Tests Resume Later Today

A quick follow-up on the recent testnet1a recovery.

🔹 Current status
- L3 / testnet1a is back to normal
- All router endpoints are back to normal as well

🔹 Why this matters
- This was a good recovery exercise for us on the infra / ops side
- It gives more confidence that, with the current dataset and recovery path, we can rebuild and recover from this kind of disaster event more cleanly than before

🔹 What’s next
- We’ll keep monitoring things further today
- If everything continues to look stable, we’ll resume the Portal stress tests later today

🔹 Public stats
- Public Portal stats is also reflecting again:
- https://t.co/VwVqjCb383

🔹 Current takeaway
- testnet1a recovery looks successful
- router endpoints are back
- monitoring continues today
- Portal stress testing should resume later today if things keep holding

#Cortensor #DevLog #Testnet1a #Portal #Infra #L3

[Cortensor @cortensor]

https://t.co/DdxMLPpGgp

[Cortensor @cortensor]

Two layers, one direction.

Corgent is the more infra-native trust and execution surface.

@BardielTech is the more product-facing trust and execution layer built on top.

Together, they show how Cortensor can move from raw network capacity into real agentic execution, trust, and product utility.

ERC-8004 references:
https://t.co/AvbrZ1XB4b
https://t.co/3qQd8L6WMn

#Cortensor #Corgent #Bardiel #AgenticAI #AIInfra

[Jonps5 @Jonps51]

@lnsx_io @aeonframework Looking great, update dex please

[Cortensor @cortensor]

First Lite.
Then Full.

Q3 2026 → Mainnet Lite
- built on @Arbitrum L2
- more practical and controlled first step
- earlier dedicated-node-backed rollout
- cleaner hosted and product-facing path first

Q4 2026 → Mainnet Full
- built on @Arbitrum Orbit L3
- fuller Cortensor-native path
- broader long-term network direction
- more complete stack beyond Lite

That is the rollout path as we currently see it.

#Cortensor #MainnetLite #Mainnet #Arbitrum

[Cortensor @cortensor]

🛠️ DevLog – Token Usage Observability on Admin / Ops Now Includes More Model-Level Detail

A quick follow-up on the earlier admin / ops work around token-usage visibility.

🔹 What improved
- The admin / ops side now includes a bit more detail around token usage observation
- That now goes beyond total token volume and prompt/completion mix to include more model-level breakdown as well

🔹 What this helps with
- better visibility into how token usage is distributed across models
- clearer understanding of prompt vs completion share
- better operational read on which model paths are carrying more usage underneath

🔹 Why this matters
- Since Portal usage is moving more toward token-based accounting, the admin / ops side also needs to reflect that at a more useful level
- Model-level token visibility makes the operational picture much clearer than raw request counts alone

🔹 What comes next
- Once these token metrics / graphs are in a better place, we plan to take a subset of them and expose them as public-facing stats / observability surfaces too

🔹 Current takeaway
- token visibility on admin / ops is getting more useful
- model breakdown is now starting to show up there too
- and this is one step toward broader public observability later on

#Cortensor #DevLog #Portal #Observability #APIGateway #AIInfra

[Cortensor @cortensor]

🔎 Recap: Rough Rollout Timeline from Mainnet Lite to Mainnet Full

A quick recap on the rough rollout path so the bigger picture is easier to follow.

🔹 Q3 → Mainnet Lite on Arbitrum L2
- Mainnet Lite comes first during Q3
- The first step is to make sure the base network path is functioning correctly on mainnet conditions
- Then we start deploying and setting up the product/app layers on top of that Mainnet Lite environment

🔹 What gets deployed on Mainnet Lite
- Corgent
- Bardiel
- Portal

These become the first product/testing surfaces on top of the Mainnet Lite path.

🔹 What Mainnet Lite is for
- a controlled mainnet testing ground
- real deployment and setup on Arbitrum L2 mainnet
- real product-path checks
- real usage / testing so we can see what breaks and what needs refinement

So the rough sequence is:
- Mainnet Lite
- then Corgent / Bardiel
- then Portal
- then actual testing usage and follow-up refinement

🔹 Q4 → Mainnet Full on Arbitrum Orbit L3
- Then we do a similar rollout flow again during Q4
- But this time on the fuller Arbitrum Orbit L3 path

That means:
- Mainnet Full first
- then the same broader product/app rollout on top
- then more real usage/testing on the fuller Cortensor-native path

🔹 Current takeaway
The simple framing is:

- Q3 = Mainnet Lite on Arbitrum L2 + product/app rollout on top
- Q4 = Mainnet Full on Arbitrum Orbit L3 + similar rollout on top

So Mainnet Lite becomes the earlier controlled mainnet testing ground, and Mainnet Full becomes the fuller native path after that.

#Cortensor #MainnetLite #MainnetFull #Arbitrum #Portal #Corgent #Bardiel