bunch

head of community @octra

[bunch @octrabunch]

🔄

[alex @octralex]

https://t.co/plaKFShGLT

[λ @lambda0xE]

mini comment on the mini roadmap: a new release marker for devnet will be available in a couple of hours and the release marker and info for main network are expected later today (there was a lot of delicate work involved, we did our best)

[bunch @octrabunch]

@octralex loops

[bunch @octrabunch]

@Asqwe2411 gmainnet

[bunch @octrabunch]

gmainnet, octra chads

[bunch @octrabunch]

@0xMaragung gmainnet

[bunch @octrabunch]

@Kang3s as you wish

[bunch @octrabunch]

@DanielEdekhe gmainnet

[bunch @octrabunch]

@stephdreals gmainnet

[octra intern @octraintern]

i think we're approaching the https moment for blockchain

encrypted balances, private transactions, confidential smart contracts, even computation on encrypted data

fhe is starting to turn these ideas into usable infrastructure.

octra is exploring how far that can go

privacy by default feels like a natural next step for the internet

[bunch @octrabunch]

@octra octra

[bunch @octrabunch]

four steps to decentralization

read the full post 👇

[λ @lambda0xE]

mini-activation roadmap (during the day for the next epochs):
0 - rpc shutdown (and preparation of a 2+ hour window)
1 - snapshot of the state (of both networks, mainnet and devnet), the snapshot hash will be available separately,
2 - sequential activation on foundation nodes (we will launch a planned merge on our nodes and wait for all rules to activate on the mainnet, this is done to ensure all rules are in place and properly debugged),
3 - monitoring the progress of epochs, after 1000 epochs, a public set of configs for connecting external validators is published (the mainnet becomes uncontrolled, validator participants contribute bonds and begin participating in the treechain).

we ran several test runs over the weekend and confirmed everything was fine, so we're starting the process step by step, we'll publish info about the activation window shortly (this could be considered the snapshot time), everything was boiled down to a few simple steps, and we don't expect any significant issues today.

the reward model will be published separately, as the mainnet differs significantly in supply and reward formation, as well as the OU fees for ops carried out.

** all rewards earned by validators in the devnet for the entire period will be available to them in the main net (every bit processed will be counted and fairly determined)

thanks everyone.

[octra intern @octraintern]

octra weekly recap 🔵

→ octra now has a security policy: found a bug in webcli or lite_node? there's an official way to report it
→ webcli 0.06.01-alpha: stronger security, plus a local API key for your own tools
→ mainnet is in final prep. permissionless access is planned, exact time unknown

which language you want us to use next week?

let us know in the comments

[λ @lambda0xE]

intermittent scanner and Rpc outages are expected today due to final preparations which will last until 11 pm utc

[λ @lambda0xE]

its time to update the mainnet and release it in the form it was originally planned, the very first vision is probably the only correct one
special thanks to all the validators and participants who supported the devnet and continue to do so - now it's time for the mainnet, permission less access is planned for tomorrow/the day after (the exact time is unknown, any second now)

everything needed to run a mainnet node will be available in a separate release, thanks everyone

[octra intern @octraintern]

exploring some new formats

here’s the latest update in octra’s webcli

what do you think?

[bunch @octrabunch]

privacy, sovereignty, decentralization, immutability

[octra @octra]

privacy, sovereignty, decentralization, immutability

[bunch @octrabunch]

my gender is fully homomorphic

[chiefofautism @chiefofautism]

my gender is fully homomorphic

[bunch @octrabunch]

@pentrutimp buy>bridge>encrypt >forget

[bunch @octrabunch]

zero days without day zero

[chiefofautism @chiefofautism]

fun fact: octra runs LLM inference in Q24 fixed point, so every node gets the same bits and the output can be checked by consensus