wandor

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. – at London, England

from zero to one - devnet was updated at epoch 1500000 (much better than we expected), there were some delays that should be resolved with the new release (existing validators should upgrade, the release marker is already in place). among other things, we moved a lot of tests that we don't usually add to releases, but decided to slowly add them for the sake of culture and convenience of validators and devs who directly work with the code, so that they don't waste time writing covering tests. another thing i'd like to point out is that main net is catching up quickly with all the fixes successfully implemented in dev net, the next release will include configs for connecting to main net, so validators will be able to start working with the main network as well. want an upgrade? it's simple, run these commands from your existing node checkout + using the same user that runs your node: sh controls/upgrade.sh --diagnose sh controls/upgrade.sh --apply sh controls/upgrade.sh --diagnose * remember the days when upgrading took several iterations and a ton of approvals? that's a thing of the past now. btw, if you have a spare graphics card or a cluster of GPUs, now's the time to create a symlink for your future mainnet node because you'll have something to fill it with (private inference on steroids has already been tested and debugged). ps: a major webcli update is also on the way, thanks to everyone for their support and help. – at London, England

an update regarding webcli: many cryptographic primitives have undergone changes aimed at enhancing security. the cryptographic interface has been expanded to include new required functions - such as key switching and refreshing - and improvements have been made to the handling of ciphertexts, the bridge, and other components. an informative feature has also been added to visualize the ciphertext data structure as an interactive L-map, this allows to view noise levels, new layers, and more. the cryptographic primitive interface has become more complex, and legacy balances now require explicit re-encryption and key switching for security reasons. this update is currently available on devnet and will be supported on main net in a few days, following additional security verification. the entire cryptographic workflow is now seamlessly available, the next update will be a full lite node designed for quick startup (details in the next announcement). strongly recommended to update to the latest version, thanks everyone. github.com/octra-labs/webcli – at London, England

the largest dev net update is currently underway, support for direct GPU computing for resource-sharing circles has been added to nodes as part of the development of on-chain state inference mechanics we plan to complete this tomorrow afternoon (this will deserve a separate article) thanks everyone – at City of London, London

in the PoC version of PVAC-HFHE, the recrypt function contained a blank for the next bounty, which was already revealed to us (even though we didn't ask for it), so we decided to make a new one, and this and a few other small things will simply be patched, and for the bounty, we will prepare a new interesting challenge*, which will be published a little later, with a new release of webcli** (with an update to the proof system) and pvac (secure recrypt) * bounties are becoming more interesting and richer, and include not only cryptography, but also testing hypotheses on hostile behavior within the ledger, VM, circle outline, etc ** it may seem like there are a number of problems right now, but that's not the case, bc the network has already been updated, but the public repo hasn't caught up yet, this will be completed today – at Hackney, London