bunch

head of community @octra

[bunch @octrabunch]

encrypted world computer

[octra @octra]

https://t.co/q0FfAyV68y

[alex @octralex]

The work is never ending, but so is the work

[bunch @octrabunch]

@octraintern fr fr

[bunch @octrabunch]

https://t.co/y4qySm9sFL by @varrock

#NewProfilePic

[octra @octra]

a global, permissionless and open “everything exchange” would require:
(1) privacy to bring real world assets onchain;
(2) programmability to trade, lend and borrow against them;
(3) persistent state for assets to stay end-to-end composable

from our (naive) 2022 intro article:

[bunch @octrabunch]

@0xdasha im this boomer

[bunch @octrabunch]

i just can’t stop liking all those blue-white pictures made with octrifier 😭

[bunch @octrabunch]

@varrock peak

[bunch @octrabunch]

@0xtisticangel

[bunch @octrabunch]

@0xtisticangel octra

[octra @octra]

a comprehensive report on octra, its launch strategy, plans, the role of OCT, proprietary hypergraph FHE scheme and what it unlocks, is now out

written by @AvgJoesCrypto, a prominent privacy advocate over at @MessariCrypto

thank you for the coverage!

https://t.co/TRiEmavGSe

[octrascan @octrascan]

👀 someone just bridged in and encrypted 900,000 OCT

🤔 this is probably one of the largest encrypt transaction ever

[octra labs @octralabs]

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

[bunch @octrabunch]

@octralex @octralabs octra

[alex @octralex]

Update: @octralabs will be deploying wrapped OCT and the native bridge on HyperEVM in preparation for listing on Hyperliquid spot markets. We aim to finalize the process this week. Perps will probably take longer and depend on spot volumes, Nova and the Hyperliquid community.

[alex @octralex]

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.

[bunch @octrabunch]

buy > bridge > encrypt > forget

[octra @octra]

speedrunning bridge -> encrypt balance in under 2 minutes

use this simple visual guide to bridge $wOCT on Ethereum to $OCT on octra mainnet and encrypt balance

this instruction is a demonstration of technical process to do so, and not financial advice

[bunch @octrabunch]

FULLY HOMOEROTIC SUMMER

[octra @octra]

formal safety reports are now live on @octrascan and webcli

source bytecode and verifier reports are tied by hashes

programs now show clean warning or error status with proof traces before users rely on them

this addresses a real bug class around value flow signed amounts

[λ @lambda0xE]

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 Standard ML family, which imposes certain obligations on us, we were not planning to announce new features specifically today, but one situation, which is indirectly related to formal verification and more likely belongs to the class of silly bugs in an independent devs's program, made us decide not to wait and to update support right now, especially considering the upcoming availability of lite nodes for everyone who wants to run one, we decided to speed up the process with the latest mainnet beta features

for your convenience we deployed 4 progs and each of which is formally verified- the first program is clean when the second has a warning, the third has a clear stupid bug and the fourth is a standard OCS01 token that is also formally validated and has passed attestation,all programs are valid and compile successfully

fyi: the token standard is not obliged to answer for a dev's mistake when he shoots himself in the foot, but an additional element in the form of formal verification can stop him from making such mistakes. so, here are the 4 programs: clean, warning, clearly broken, and a canonical token standard, each with a full formal verification trace in the corresponding scanner tabs

clean prog: octGcYxnDL8SqkQRzSsewfkXC1uApwhMSTiKP1AAGwPXVmU

has warning:
https://t.co/I4VqjHnGmT

issues:
https://t.co/gzmtcQBNf7

OCS01 token:
https://t.co/hH2f6HLYMI

when a user looks at a program, he no longer blindly believes that "the dev is right", he relies on a formal verification procedure that minimizes the human factor

among other things the scanner now shows the exact validator reward for each epoch, which is a useful feature for economic accounting

ps: the next update concerns the mini-paper (HFHE, pvac and hardness assumptions, cryptography, etc) and will appear in the coming days, together with a major webcli update, .aml docs, and the full formal verification spec, if there is anything interesting, we will inform you in a separate announcement, but for now that's all

thanks all

[octra @octra]

none of these words were in the bitcoin whitepaper