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) – at London, England
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.
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
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
intermittent scanner and Rpc outages are expected today due to final preparations which will last until 11 pm utc – at London, England
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
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 – at London, England
mb they have some talent- beyond just being pro-kremlin? many are apolitical and write good code – at London, England
20
3,372
λ retweeted
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
– at London, England
hi everyone, webcli has been updated, a lot has been done, we're counting it as version 0.06.01-alpha.
the cryptographic surface has been strengthened, as has security (this doesn't mean we've closed everything; we're working on it and it's far from finished),
anyone working with the dev net and planning to interact with the mainnet should update and test FHE ops on the devnet (this is perhaps one of the most important parts), working with circles, and more, we've also added access via an API key to automate some processes and make it easier if you're building a tool for some reason, access to the key is in the "settings" tab, so pass the key in the request header of your app - "Authorization: Bearer <api key>"
fyi: : webcli must be running, the api is only available on your puter, kep the key private.
webcli should be rebuilt, and also importantly - please keep a previous copy of webcli src in close access to your hands for some compatibility tasks (this will potentially be necessary).
thanks everyone.
github.com/octra-labs/webcli
hi everyone, webcli has been updated, a lot has been done, we're counting it as version 0.06.01-alpha.
the cryptographic surface has been strengthened, as has security (this doesn't mean we've closed everything; we're working on it and it's far from finished),
anyone working with the dev net and planning to interact with the mainnet should update and test FHE ops on the devnet (this is perhaps one of the most important parts), working with circles, and more, we've also added access via an API key to automate some processes and make it easier if you're building a tool for some reason, access to the key is in the "settings" tab, so pass the key in the request header of your app - "Authorization: Bearer <api key>"
fyi: : webcli must be running, the api is only available on your puter, kep the key private.
webcli should be rebuilt, and also importantly - please keep a previous copy of webcli src in close access to your hands for some compatibility tasks (this will potentially be necessary).
thanks everyone.
github.com/octra-labs/webcli – at London, England