►Reach:   The Safest and Easiest DApp Programming Language
▼3 Guide
0.1.3
    ← prev  up  next → 

3 Guide

These guides discuss some key ideas and concepts used through Reach. They aim to teach the "Why" of aspects of some Reach features and discuss the many alternatives available to DApp developers. Indeed, many of these points are relevant to all DApp developers, because the problems appear in all applications.

The following guides are available:

    3.1 Using Reach on Windows

    3.2 How does Reach use version numbers?

    3.3 How does Reach development compare to Solidity development?

    3.4 Do I have to use JavaScript to write my frontend? What about Python, Go, or other languages?

    3.5 How do I add tracing logs to my Reach program?

    3.6 What do the different kinds of consensus transfers mean? publish, pay, race, fork, parallelReduce?

    3.7 How and what to verify

    3.8 Finding and using loop invariants

    3.9 Choosing a deployment mode

    3.10 Non-participation: What it is and how to protect against it

    3.11 Determinism, simultaneity, and choice in decentralized applications

    3.12 Racing non-determinism in decentralized applications

    3.13 Building decentralized abstractions

    3.14 Testing Reach programs in the browser

    3.15 IDE/Text Editor Support

    3.16 Sharing and discovering shared Reach packages

    3.17 How does Reach work?

    3.18 What are Reach’s limitations?

    3.19 Reach’s Roadmap

    3.20 Reach’s Changelog

    ← prev  up  next →