λ

octra labs

@lambda0xE

byzantine general & co-founder @octra

London, England octra.org Joined July 2022

1.8K Following 4.3K Followers 2.8K Posts

Latest posts 5

λ @lambda0xE 13h

build markers are being released, but don't upgrade to the current one yet (even if it's available - we consider them to be for debugging purposes) and wait for the final announcement + currently configuring everything for both networks (devnet and mainnet), so both val configs will be available today, with the devnet a little earlier.

this is the final stage, which includes a complete upgrade of everything, including side services, from scanners to release routes (the mainnet is getting its own separate public branch).

λ Verified account @lambda0xE 20h

"mini-time" of the mini-upgrade has come. what's done?

the past two weeks as always didn't go to waste and we moved the latest relevant parts with minor fixes including our intermediate shit on the fix into Irmin Db (our favorite and most important data storage system),

the work touched all parts - consensus (quorum by weight instead of counting seats, that same infamous sigma algebra of events, validator exclusion for proven violation on the eve of mainnet, among other things now quarantine and node catch up count weight, not the number of node responses, which for the most part were useless, so this crap is also fixed, big work on protecting against network halts, solid improvements to the VM, p2p and Rpc work also got improvements (octra sync target removed from public rpc and available only through local socket), separate work was transferred on our main data storage system - Irmindb (the most powerful in its essence data storage system, equals of which there are none and unlikely to be in the current era, so our moral duty to keep it up to date and update it with our own hands), in total, what's done on it - irmin had a problem with the garbage collector in irmin-pack, we've been running into this problem for a long time and we took it upon ourselves to rewrite some parts and patch it, we made it reliable for a node that runs for months and can crash at any moment, now background gc processes are under full control, as well as many other important things in the work of storage for distributed systems (this work with the new build will also go into a pr for irmindb in their repo)

the release marker will be available in about an hour. first, the devnet will be upgrade, then we will move on to the mainnet. Valiators should prepare btw, thanks eveeryone!

github.com/octra-labs/lit…
View quoted post on X

λ @lambda0xE 20h

"mini-time" of the mini-upgrade has come. what's done?

the past two weeks as always didn't go to waste and we moved the latest relevant parts with minor fixes including our intermediate shit on the fix into Irmin Db (our favorite and most important data storage system),

the work touched all parts - consensus (quorum by weight instead of counting seats, that same infamous sigma algebra of events, validator exclusion for proven violation on the eve of mainnet, among other things now quarantine and node catch up count weight, not the number of node responses, which for the most part were useless, so this crap is also fixed, big work on protecting against network halts, solid improvements to the VM, p2p and Rpc work also got improvements (octra sync target removed from public rpc and available only through local socket), separate work was transferred on our main data storage system - Irmindb (the most powerful in its essence data storage system, equals of which there are none and unlikely to be in the current era, so our moral duty to keep it up to date and update it with our own hands), in total, what's done on it - irmin had a problem with the garbage collector in irmin-pack, we've been running into this problem for a long time and we took it upon ourselves to rewrite some parts and patch it, we made it reliable for a node that runs for months and can crash at any moment, now background gc processes are under full control, as well as many other important things in the work of storage for distributed systems (this work with the new build will also go into a pr for irmindb in their repo)

the release marker will be available in about an hour. first, the devnet will be upgrade, then we will move on to the mainnet. Valiators should prepare btw, thanks eveeryone!

github.com/octra-labs/lit…

github.com GitHub - octra-labs/lite_node: octra network lite node octra network lite node. Contribute to octra-labs/lite_node development by creating an account on GitHub.

λ @lambda0xE 4d

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)

λ Verified account @lambda0xE 6d

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.
View quoted post on X

λ @lambda0xE 6d

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.

λ Verified account @lambda0xE Nov 6

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
View quoted post on X

λ @lambda0xE 6d

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

λ Verified account @lambda0xE Nov 6

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
View quoted post on X