Reach is great. As the CEO, I know I may be biased. But there are 1.3 billion reasons you should be biased too. Let explain why you as USERS should care that the blockchain apps you use (and the NFTs you buy) are built in @reachlang. 🧵 ALERT
1/ Reach is game-changing for #blockchain developers. It’s MUCH easier to learn and lets you build sophisticated #dApps in 2-4 weeks (versus months of trying to learn the low-level smart contract code), but users shouldn’t really care about that.
2/ Sure, it may give developers more time to build/enhance your favorite features, but you just care that an app does what you want (and doesn’t lose your money in the process).
3/ The reason you, as users, should ask every single blockchain project if they build their apps in @reachlang is SAFETY. In 2021 alone, $1.3B was lost to hacks.
Reach was built with YOUR safety in mind. Here’s how Reach protects YOU, the user...
Reach was built with YOUR safety in mind. Here’s how Reach protects YOU, the user...
4/ When developers build in Reach, they’re forced to think of the entire workflow of an application; not just inputs in a smart contract. This helps protect against cybersecurity attacks from unexpected places.
5/ We’ve also automated formal verification. Formal verification has been around almost as long as computers themselves. It is used when there are billions of dollars at risk (sound familiar?). It’s used in financial algorithms, hardware manufacturing, and rocket launches.
6/ The problem is that formal verification is VERY costly and requires very specialized skills to perform. It’s not uncommon for the cost of verifying an application to exceed 100x the cost of building it. But Reach is anything but common...
7/ When developers build an app in Reach the compiler creates multiple formal proofs to verify the app will do EXACTLY what they intend. Formal proofs turn the entire app into a math problem and verify the results in every potential reality.
8/ The platform automatically verifies the application is free from entire categories of safety issues. Developers can check for specific vulnerabilities by adding simple assertions to the code. The expertise of a team of PHDs is at their fingertips the moment they hit compile.
9/ This happens each time the code is complied, formally verifying each updated version of the application. Formally verifying every update is just not feasible in applications that are not built #inReach it would be too costly & time-consuming
10/ But safety doesn’t stop at the compiler. @reachlang also protects you directly in your browser. Every Reach application verifies the contract you’re interacting with is exactly the contract your interface thinks it is. If it is not, then it will just fail.
11/ Without this check, it’s possible for a rogue developer to upgrade smart contracts without your knowledge or sneak a bad contract into a pool of good ones to steal your money.
12/ Of course Reach isn’t a silver bullet. There’s no guarantee if you use Reach nothing will ever go wrong. BUT it does make things exponentially safer. Wearing a seat belt doesn’t guarantee you’ll survive a car crash, but it drastically increases your odds.
13/ I hope this helps explain why your money is so much safer when you use apps written in @reachlang. Question is: which apps are those? We’re already building the safest, most user-friendly DEX in @HumbleSwap. @xbacked, @Dequency_io, and @XTZ_ESPORTS are also building #inReach
14/ Reach is being used to build @YieldlyFinance new NFT Marketplace and future bridges from @Algomint_io. Call me “crazy” or “risk-averse”, but I don’t put money in contracts written by hand and I don’t drive without a seat belt. #buckleup #blockchain #crypto #NFT
• • •
Missing some Tweet in this thread? You can try to
force a refresh
