
Moderator at @octra , @streamflow_fi @Inertia_fi, fullstack developer, crypto enthusiast, ambassador @PicWeGlobal Zpoineer @ZeusNetworkHQ,
Federal Capital Territory, Nig
Joined October 2013
- Tweets8.1K
- Following2.2K
- Followers750
- Likes8.4K
Pinned Tweet
๐น ๐ฉ๐ถ๐ฑ๐ฒ๐ผ ๐๐๐ถ๐ฑ๐ฒ: ๐ฅ๐๐ป๐ป๐ถ๐ป๐ด ๐ข๐ฐ๐๐ฟ๐ฎ ๐ช๐ฒ๐ฏ๐๐๐ ๐ผ๐ป ๐ช๐ถ๐ป๐ฑ๐ผ๐๐
๐๐ช๐๐๐ ๐๐ค๐ข๐ข๐๐ฃ๐๐จ ๐จ๐๐ค๐ฌ๐ฃ ๐๐ฃ ๐ฉ๐๐ ๐ซ๐๐๐๐ค:
โ ๐๐๐จ๐๐ฉ: github.com/octra-labs/webcli
โ ๐พ๐ก๐ค๐ฃ๐ ๐ฉ๐๐ ๐ง๐๐ฅ๐ค:
git clone github.com/octra-labs/webcli
โ ๐๐ช๐ก๐ก ๐ก๐๐ฉ๐๐จ๐ฉ ๐ช๐ฅ๐๐๐ฉ๐๐จ:
git pull
@octra @octralabs
Safe to disclose: last month Loops identified and we privately reported a critical vulnerability affecting 88% of NOCK supply that could be arbitrarily moved. The patch shipped 5 hours later and was included in 170,000 upgrade. Props to the team for keeping the ecosystem secure!
VINTAGE_JAB retweeted
four steps to decentralization
read the full post ๐
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.
minor improvements to the mainnet are currently being delivered
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.
VINTAGE_JAB retweeted
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
We've added a security policy and enabled GHSA for core repos (currently webcli and lite_node).
All reports go through our Loops pipeline and are transparently mapped to existing timestamped records as shown.
Genuinely new findings may be rewarded if proven useful and reachable.
VINTAGE_JAB retweeted
let's hack
VINTAGE_JAB retweeted
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
VINTAGE_JAB retweeted
๐จ @xavierbosch: "Rodri and Frenkie together could be a HUGE weapon for Barรงa.
Rodri gives you control and protection, Frenkie gives you progression and carries, while Pedri can move higher and decide games closer to goal.
If the chemistry clicks, Flick suddenly has another elite midfield structure instead of relying on the same formula every week."
VINTAGE_JAB retweeted
were quietly finishing up the prototype for octra to work as a priv layer for other networks or apps, test cryptographic proofs and verification took a couple of days (gpu process of building proofs), so we're expecting a couple of updates today. wanted to get definitive confirmation. โ at London, England
VINTAGE_JAB retweeted
Rodri, Pedri and Frenkie are world-class, but if Flick canโt figure out how to use them in big games, weโll keep losing to the big boys. Talent isnโt the problem. Flickโs decisions are. ๐คทโโ๏ธ
VINTAGE_JAB retweeted
Replying to @Kaypoisson1
rodri is not the problem,no 10 is the problem. When olmo played, we had much more control on the midfield. Hansi should play rodri as a single pivot who will drop back and give us defensive protection while pedri and frenkie should play higher up. Fermin isn't the player.
VINTAGE_JAB retweeted
This is How Hansi Flickโs team attacks without Rodri.
Look at that play by Frenkie De Jong
Rodri would have passed sideways in Midfield in the name of keeping possession and Control.
Give me Frenkie and Pedri double pivot please
VINTAGE_JAB retweeted
Barca fans said Frenkie de Jong slows down our game, that he plays too many backward passes, and that we need a more dynamic midfielder who can complement Pedri. Some even wanted him gone. Then we brought in Rodri, who is even slower on the ball, plays just as many sideways and backward passes, and sometimes looks like heโs doing us a favour by being on the pitch. ๐ญ
The moment Frenkie came on, you could feel the difference in our midfield. The tempo changed, the ball moved with more purpose, and we had someone willing to carry possession, break lines, and drive the team forward. His presence was immediately felt, and the game changed.
But apparently, Frenkie was the problem.
VINTAGE_JAB retweeted
Replying to @DacadAli111375 @Kaypoisson1
Don't ever compare Pedri and De jong to that bum Rodri that can't turn and face play always wanting to kill defenders with back passes even when they are marked.
























