reach-lang VS Formality

Here is a link to their website https://reach.sh/ . Check out their documentation, discord (great community), and they have videos on youtube as well!

I'd highly suggest looking into Reach language (reach.sh). It's a smart contract language based on javascript that has the ability to deploy on ethereum, algorand, and conflux blockchains (i'm sure they will add more at some point). It's a lot simpler to learn than solidity for instance.

https://reach.sh there are also sdks available for Java, JavaScript, Python, go

Pokerand.io is built from the ground-up using Flutter, a UI software development kit created by Google. The Smart Contract, which handles deposits, withdrawals, authentication, and maintains player balances on-chain, is built using the Reach.sh smart contract platform (https://reach.sh/). The Reach contract will be published as an open-source project on GitHub, along with simple NodeJS programs to manually reproduce Deposits and Withdrawals of tokens.

reach.sh is...

When this was first released someone commented "RIP reach" and I assumed the contracts were written with reach.sh

The second point is somewhat invalid. Aside from pyteal, which compiles python to teal smart contracts, there is also Reach which is JavaScript to teal.

If you want a game where there are smart contracts and moves are recorded on the blockchain then either I suggest to wait for Cardano sidechains to itself with smart contract languages which are a bit easier (e.g. https://github.com/reach-sh/reach-lang) or simply develop in Solidity on Milkomeda sidechain with MetaMask.

In this article, we will cover a tutorial on how to build and deploy your decentralized Application on 4everland. For this case, we will be using react js and 4everland will be used to manage our front-end. The Application will use the Ethereum network and it will be written in Reach, a dApp programming language that is simple to learn and has a Javascript syntax.

If you want to look at some examples of smart contracts implemented in a higher level language, there's reach, which is Js based, which compiles to various chain vms including avm. Their GitHub has numerous example smart contracts that I found useful. Their docs & walkthroughs are also good to get you started thinking the right way. You may even consider it for implementation if you're comfortable with JS. It also provides compile time assertions that double check your code for things like "value X should only be visible to participant A" which I found great as a concept.

Also, my current work is using Kind as a foundation, the purpose of this language is exactly what you have asked for, give a check on https://github.com/uwu-tech/Kind.

Kind has a "how I learned to stop worrying and love the `Type:Type`" vibe. That doesn't make it invalid as a proof language. It just inverts the priority: instead of consistency being the default and expressivity being opt-in (as in Agda, with the `type-in-type` pragma), it is expressive by default, and consistency is an opt-in. I strongly believe that is the right way. We plan to add opt-in termination (thus consistency) checkers, it is just not an immediate priority, but the language is completely ready for that. About `Type in Type` specifically, keep in mind that there are consistent, interesting type theories that feature `Type in Type`. So it isn't problematic in itself, and removing it seems wrong.

About erasure, you can flag an argument as computationally irrelevant by writing `` instead of `(x: A)`. So, for example, in the [Vector/concat.kind](https://github.com/uwu-tech/Kind/blob/master/base/Vector/con...) file, `A`, `n` and `m` are erased. As such, the length of the vector doesn't affect the runtime. As a good practice, you may also write `f` instead of `f(x)` syntax for erased arguments, but that is optional.

> TL;DR -- I think the language looks nice, and the compile to JS (from what I read of the Formcore source) looks to be well done. Also, the docs that are present are well presented in a non-academic way that I find pretty readable.

Thanks for the kind words. We put a lot of effort on the compilers and, while there is still a lot to improve, I'm confident they're ahead of all the other languages, by far.

Kind is a functional, general-purpose programming language featuring theorems and proofs. It has the smallest core, a pretty solid JavaScript and Scheme compiler (seriously, check how clean is the generated kind.js), and a syntax that is a middle ground between Haskell and TypeScript, in an attempt to make it more accessible.

I'm writing CONTRIBUTE.md right now.