to ensure maximum security amid rising industry incidents, we will be spending additional time on formal verification of all modules for the upcoming node release
your patience is appreciated as we work to secure the network
the next batch of mini-updates was just added, we recommend updating webcli as soon as possible
more webcli changes coming this week: accessible github production cycle, less hassle with manual builds, new security improvements, etc.
repo: github.com/octra-labs/webโฆ
stay alert for
a mini update regarding webcli - many security improvements have been added that make it worth updating your version to the latest version (don't delay with the update)
weโre also reinstating the bounty program as an open portal with challenges after receiving good findings from
an important security update has been released, please install the latest version of the web client:
1) export keys
2) delete old client folder
3) download new web client: github.com/octra-labs/webโฆ
4) rebuild
5) import keys
see instructions: docs.octra.org/user-docs/instโฆ
a mini update regarding webcli - many security improvements have been added that make it worth updating your version to the latest version (don't delay with the update)
weโre also reinstating the bounty program as an open portal with challenges after receiving good findings from
This is the right direction. Octra already uses R1CS/Bulletproofs and Pedersen-bound proofs for encrypted balance flows and state transitions, while programs compile to inspectable bytecode with formal verification built in. Private compute should be proof-carrying by default.
Zcash ( and Aleo, Aztec, payy, etc) should double down on formal verification. Anecdotally, advances in coding agents make it straightforward if you have the expertise to write theorems/specs. But the flip side is, advances in AI mean this won't be the last zk bug.
An in-depth overview of the @octra bridge by @DefiLlama Research team is out. It covers how assets can move between public and private states, and not just chains. The bridge is becoming a standalone product, and also part of a broader EVM privacy stack being released gradually.
Two components, one @octra thesis:
> Bridge brings assets from Ethereum into encrypted state
> Circles gives devs a private substrate to build apps inside that same environment
Together, privacy is persistent infrastructure, not an anonymity pool:
defillama.com/research/spotlโฆ
mini update (pre-night devbuild): the devnet and main net RPCs, as well as both scanners, have just been updated, adding support for a very important element - formal verification, as we said earlier, .aml supports native formal verification backed by Coq lang and belongs to the
the upcoming release will open up new opportunities for formal verification auditing directly in @octrascan, where all problems and warnings will be clearly reflected, the full result is immediately available in the corresponding tab
the upcoming release will open up new opportunities for formal verification auditing directly in @octrascan, where all problems and warnings will be clearly reflected, the full result is immediately available in the corresponding tab
an additional optional step is being introduced before deploying programs to @octra - formal verification
the new version of webcli compiler will require formal verification (which can be optionally skipped for now, but it's best not to), the dev will have to write a proof
pre-mini update (dev version, night build): extended feature support at the rpc level has been updated, with program exec, multi exec, value call, large storage, and fhe mul (a function with a recrypt and unlimited operation depth) now available on the mainnet
btw, we've
if youโre experiencing connection or balance display issues, please update your rpc settings to:
octra.network/rpc (mainnet)
devnet.octrascan.io/rpc (devnet)
this will be updated to defaults in the next release
octra stealth transfers do not expose a plaintext senderโrecipientโamount graph.
they spend from encrypted balance, update encrypted state with proofs, and send an encrypted recipient payload.
metadata at the edges still matters: key discovery, claims, timing and app routing
octra stealth transfers are not mixers, nor monero-style ring/UTXO privacy
they rely on encrypted balance state
> hold encrypted value
> spend from it privately
> claim into encrypted balance
> decrypt arbitrary amounts when needed
> compute and compose without revealing state
๐ someone bridged and encrypted 100,000 $WOCT:
octrascan.io/tx.html?hash=9โฆ
the encrypted balance can now be moved arbitrarily within the network, used for programs, circles, apps or inference, or even staked.
โฒ๏ธ btw, the bridging took
a mini-update to webcli that enables rust and aml in circles is already available, you can update and rebuild it now - github.com/octra-labs/webโฆ
weโve also added a few examples:
- public hmtl circle: oct://oct9rofAj2yrS4uaisrZ9yqPwPpYHHCiHzFEGWFNFVGbZhK/index.html
pwd: not