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
btw, the day wasn't wasted, we discovered another bottleneck that required special attention, so we decided to deduce it from a proof-of-concept form, rather than simply as an algorithm and separately decided to prove that after any write, the state remains synchronized among all participants, a quorum requires both thresholds (number and weight of participants) to be met
the learning context itself, based on moving consensus, doesn't change the vote, lock, or finalization phase. this was a rather specific problem, so we decided to formalize it (sorry for the format - the OPD platform will be available in a couple of days, but for now, we're writing the descriptive part manually), so you can take a look at it here: https://t.co/8SB9bCZuIP
the new release marker is now available for validators, pls upgrade as usual:
sh controls/upgrade.sh
sh controls/upgrade.sh --apply
sh controls/stat.sh
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
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.
Our agentic "Loops" infra is getting better: a serious devnet inflation bug was caught immediately upon activation and with no impact on mainnet.
We also ran Loops on friendly privacy/ZK/FHE-adjacent projects, and responsibly disclosed our findings. Write-up coming once safe.
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
What if a superintelligent AI found a way around every rule we set? Could making it believe it was in a simulation be a way to deter it?
@Dr_JohnFletcher and Adi discuss the Simulation Deterrent.
Read more: https://t.co/K9SAo56cQV
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.
Hard at work on (not) Farcaster, ensuring our decentralized communities live on and flourish.
Our team's working on both a brand new browser build for HyperSnap (seen below), alongside a Terminal build for all your agentic needs.
Open beta ASAP. Let's get our home back.
Decentralized social is important.
Yesterday's actions by Farcaster, preemptively banning long-serving community members as an AI decided they "didn't fit the Singaporean citizen model" is frankly insane - and alongside being an example of AI used with the worst possible intentions, it also added to the importance of actual decentralized social.
We're working with our friends within the Farcaster Community (the real one) to lend our dev resources towards ensuring the continuity of the protocol under HyperSnap & Quilibrium, spearheaded by @cass_on_mars.
We believe this symbiotic relationship will be beneficial to both our community at imgnAI, as well as to the Farcaster community - and the large overlap of users active on both of our platforms.
We all believe that decentralization is the way forward - and we want to ensure that we're doing everything in our power to keep decentralized social and its talented pool of builders & creators live and kicking.
>be octra
>start in 2021 as a small self-funded team obsessed with real privacy
>begin with encrypted balances and stealth/private payments with fhe instead of mixers or temporary shields
>build its own proprietary hypergraph FHE (HFHE) tech from scratch instead of bolting privacy onto an existing chain
>expand into a full L1 + encrypted middleware with isolated circles for programs, apps, and private compute
>run public testnet that grew to millions of accounts and over 100m txns
>cancel the fixed-price ICO sale and switch to a community uniswap auction to prioritize broader distribution over a set valuation
>ship mainnet alpha and convert all testnet tokens 1:1 into mainnet assets giving early testers real value
> ship ethereum bridge for private asset movement, and onchain private ai inference experiments and agent friendly tooling
>progressively open-source the stack: webcli, lite_node, amlc compiler, HFHE PoC, and circle examples
>keep shipping frequent updates to the lite node and web client (circles, nested execution, work metering, security) while validators and the network stay live
>turn a private payment idea into a live programmable enceypted network
>stay octra coded
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
octra is the most criminally undervalued digital asset on mother earth; there will be an entire era of cypherpunk reality built on the guarantees of the hypergraph…
we are graced with the early opportunity to watch the founders demonstrate the seemingly endless potential of something so unique and powerful…
to paraphrase the late paul erdős: the market may not be ready for such mathematics…
in the new version of the scan, formal verification, byte and src code, as well as program certs, have become more informative (this is still early alpha, it will change 1000%, but it has become more convenient to work with imo)
example: https://t.co/azhdp4eZc9