.

[λ @lambda0xE]

the cryptographic proto is fully active on the dev net, the proof form is optimized by 2x (tests can be observed live btw), the entire surface is accessible, enc, dec, stealth txs, claims, etc, and at the VM level, the HFHE proof form (pvac version) is fully operational:
https://t.co/vUvZzoR0o8 (you can see an example here and on our dev addr in the history, and the payload is available via rpc and in the raw record)

* an important thing before migration, in order to use these features, you will need to upgrade your webcli tomorrow evening

[. @gstaadvc]

@lambda0xE @iams4444 shavua octra

[The Innovation Game (𝔦, 𝔦) @tigdoesthings]

Hi folks, a quick update from us.

TIG has a busy few months ahead, with key projects and plans moving forward.

So we’re moving our Community Calls to every other Friday, giving the team time to focus on the work and bring more to the table when we meet.

See you at the next one. It’ll be worth it.

[λ @lambda0xE]

use circles in octra to host private resources, apps, data, etc, there will be nothing to steal, and there is no such concept as exit nodes

[λ @lambda0xE]

hack yourself before other do (the policy we ourselves adhere to).

fyi: an automated fuzzing search engine based on slop generators (by @octralex) found critical crap in ALL projects we've ever interacted with (since there's already context), some have been fixed, others haven't been revealed yet and may not be, given the mixed reactions.

what a time to be alive

[λ @lambda0xE]

a new unscheduled release is now available for vals. please upgrade your nodes (a lot has been done on recovery and sync + an old bug from an earlier implementation at the vm level has been fixed) *

* the node could process the same epoch twice, and the root at that moment was different, when building and checking proposals at the consensus level, it was specified as 32 raw bytes (the earliest implementation from the end of 2024),and when using the epoch from the head, it was transmitted as a 64-hex string, so the bug was found during pre-release main net testing for mem compatibility of different program envs

upgrading is easy -
sh controls/upgrade.sh
sh controls/upgrade.sh --apply
sh controls/stat.sh
https://t.co/7EP5FWd1ej

[The Innovation Game (𝔦, 𝔦) @tigdoesthings]

Work in progress. More soon.

[Cassie Heart @cass_on_mars]

they genuinely think you're stupid.

the API didn't have a bug. it was intentionally made read only for banned and non-yes-voting users. The API literally returned a response that stated the reason of your read-only status. When software literally prevents you from doing things, and tells you the reason explicitly was something they put into effect, there is no world in which you can call that a "bug". Those APIs are _still_ read only for users that voted no or were banned. No idea if non-voting users can use it now.

You would know these things already, if they hadn't banned users that have called this out. I saw @jchaskin22 asked about this on farcaster, but of course, responding would be of minimal benefit, as they filter out my replies on their client. So tagging you here so you have direct confirmation from someone who has concrete knowledge of what happened from the other side.

[The Innovation Game (𝔦, 𝔦) @tigdoesthings]

We've now open-sourced the code for a mining pool that runs on TIG.

Want to run your own? Fork it. Give it a name. Set your own rules. Open it to whoever you like.

The pool assigns benchmarks to members' machines, submits their work under the pool's TIG account, tracks credits and collateral on Base, and handles settlements and withdrawals. Most of the groundwork is done. The rest is up to you: hosting, branding, payout model, fees and spending caps.

What's the point? For those new here, pools help smaller benchmarkers balance their factors across challenges. More pools mean more people can take part, and healthier competition across the network.

That's why we're putting the code out there so anyone can build on it. No need to start from scratch.

Pool server: https://t.co/xjZW61aj8c

Member client: https://t.co/irz4NCvKYI

MIT licensed. Still in development, so expect some bugs.

[Cassie Heart @cass_on_mars]

Quorum Mobile update is out
TestFlight: https://t.co/lOCjeEdvz6
Android: https://t.co/bJbL5G9mIA

[Fuzzy @FuzzyFoxNation]

👋 $QUIL

[Brix Bounty Farm @brix_farm]

2026 vibes

[Cassie Heart @cass_on_mars]

The new owner of farcaster, @balajis, has banned me from their side of the fork.

Absolutely incredible work.

So anyway, we're doing the hard fork of farcaster and would love to hear name ideas for our non-cancerous side.

Spinning up an emergency group chat:
https://t.co/dmpGdZJUT5

[0xio @0xio_xyz]

0xio Desktop 0.5.2 is now available on MacOs and Windows

Turn your menu bar into a privacy-powered wallet
Download: https://t.co/oGVnSIZGpo

[alex @octralex]

https://t.co/plaKFShGLT

[alex @octralex]

Octra does not actually need a new CLI, it is natively agentic.
Any agent can build webcli, derive keys, fund a wallet, encrypt, deploy programs and circles and even run nodes. The RPC scheme is complete, our own fleet runs on public code.
Easily the most agent friendly network:

[dasha @0xdasha]

narratives come and go, vision originates and stays

[octra @octra]

we've been saying, octra is where agents *choose* to live

[. @gstaadvc]

@lambda0xE octra

[λ @lambda0xE]

the new upgrade is already available, it includes important updates for fault tolerance as well as an addition for resource compute protocol, which was previously unavailable in the lite node but has been moved from the bootstrap build to achieve more natural and seamless decentralization, activation will be in 1 day, there is time to update (as previously said, this is no longer a major update on top of consensus, but a module within the runtime), the upgrade as always with a single list of commands:

sh controls/upgrade.sh
sh controls/upgrade.sh --apply
sh controls/stat.sh

ps: if the message "installed ... pending" appears, leave the node running, do not restart it in a loop.

regarding the build - marker 32, source f7637a7e, and you need to update to 1688734, consider this the final update, further only applied upgrades.

we've also migrated the earliest work on formal verification from 2021, so you can do some dev-archaeology, among other things( if you have the time)

thanks everyone.
https://t.co/7EP5FWd1ej