List.fold_left
458 subscribers
116 photos
4 videos
9 files
622 links
lambda0xe notes
Download Telegram
This media is not supported in your browser
VIEW IN TELEGRAM
ā¤4🄰2
we're testing a new circuit for high speed ring validation over encrypted state (pre proof is faster than finality, seamlessly with the OVM), quite interesting results are obtained
1ā¤10🤔2
the majority of txs come from devs
1ā¤8🤩2🤔2
in the new version of the scanner, formal verification, byte and src code, as well as program certs, have become more informative (this is still early alpha, it will change 1000%, but it has become more convenient to work with imo)
šŸ”„9ā¤6🤔3
List.fold_left
https://trufae.github.io/parla/
this + deployment in octra circle
1ā¤5šŸ”„4🤔2šŸ‘Ž1
a story about a small experience working with frontend scammers who did not perform any work, took advantage of trust and tried to receive salaries just like that, without results - as a lesson and experience for those who are currently involved in hiring.

previously we had two frontend developers working for us who were hired more than a year ago, both russians and both named Dmitry. now these two freelancers are traveling through private messages and telling fairy tales about unfair dismissal without a golden parachute having popped up. about 200 thousand dollars was spent on them while practically no work was done. their names - Dmitry Vachugov (resident of Serbia, citizen of Russia), the second - Dmitry Lazarev (russian).

all that they did - an unfinished blog, a bad explorer and several more processes that they did not finish.
their method of fraud is simple - sit on a fixed rate, do nothing, and if do something - then non-working code or generated, and the main part of the work of these people - receiving salary (which is above the market). Vachugov received - about 3000 euros per month (the damage suffered at the hands of the fraudster amounted to approximately 56+ k dollars), Lazarev about 10 thousand dollars per month (the damage suffered at the hands of the fraudster amounted to approximately 120+ k us dollars), both did not pass internal compliance, but due to rapid development we did not have time to deal with these people and hoped for their integrity, as it turned out in vain, because they perceived the friendly attitude as weakness and decided to simply steal salaries doing nothing at that and using bureaucracy.

now some from the community may receive complaints submitted as if they are poor and uncounted and they were not paid, which is a lie. if they write to someone of you, or come crying that their scam did not work - ask for interest, whether they can show the results of their work and how much money came to them.

bottom line: scammers in the field of hiring are progressing, but do not become smarter. they calmly violate contracts, do nothing and demand salaries, spoil the atmosphere in the team. therefore it is necessary to separate the team of like-minded people from vile freelancers who, taking advantage of remote work and trust, get employed in several companies for full salary, and then cry that they were deceived.
1šŸ‘9😭8šŸ™ˆ3šŸ¤”2🤔2
releasing the latest hand made bits to improve fault tolerance (the upgrade will be required on weekends), as well as a portal with all changes and the proposal log, which stands out for its activation rules, the name has been coined -OPD (octra protocol document), everyone will be able to participate in proposals for changes.

OPDs are needed to structure all the changes and separately highlight explanations of why they have been made in the first place, and to propose a discussion.
šŸ‘14ā¤4🤔3
btw, the day wasn't wasted, we discovered another bottleneck that required special attention, so we decided to deduce it from a proof-of-concept form, rather than simply as an algorithm and separately decided to prove that after any write, the state remains synchronized among all participants, a quorum requires both thresholds (number and weight of participants) to be met

the learning context itself, based on moving consensus, doesn't change the vote, lock, or finalization phase. this was a rather specific problem, so we decided to formalize it (sorry for the format - the OPD platform will be available in a couple of days, but for now, we're writing the descriptive part manually), so you can take a look at it here: https://gitlab.octra.org.uk/octra/libv_litecore/-/blob/c49de45cf49ebbc2e5c0697eb956cbcada5845e7/formal/coq/polc_cache.v

the new release marker is now available for validators, pls upgrade as usual:
sh controls/upgrade.sh
sh controls/upgrade.sh --apply
sh controls/stat.sh
1ā¤13🤔2