external/ton
1
0
Fork 0
mirror of https://github.com/ton-blockchain/ton synced 2025-02-14 12:12:21 +00:00
Code Issues Releases Wiki Activity

Fix README

Browse source
This commit is contained in:
EmelyanenkoK 2022-08-08 09:42:23 +03:00 committed by GitHub
parent 8d7f1bba73
commit acba17a025
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 26 additions and 25 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

51
README.md
View file

@ -1,26 +1,27 @@
# TON CatChain
# TON
| Name | Fixed? | Comment |
|------|---|---------------------------------------|
|CA2-01| ✔️ | |
|CA2-02| ✔️ | |
|CA5-01| ✔️ | `hash(payload)` now also covers block data.<br>This behavior is enabled by a flag in config. |
|CA5-02| ✔️ | Size of a block is now limited (16kb).<br>Block height is now limited, and blocks from misbehaviouring nodes are now ignored.<br>See `doc/catchain-dos.md` for details. |
|CA5-03| ✔️ | |
|CA5-04| ✔️ | |
|CA5-05| ✔️ | |
|CA5-06| ✔️ | |
|CA5-07| ✔️ | |
|CA5-08| ✔️ | |
|CA5-09| ✔️ | |
|CA5-10| ✔️ | |
|CA5-11| ✔️ | |
|CAA-01| ✔️ | Fixed in the same way as CA5-01 (hash now covers block data). |
|CAA-02| ✔️ | |
|CAE-01| ✔️ | |
|CAN-01| ✔️ | |
|CAN-02| ✔️ | |
|CAT-01| ✔️ | |
|CAT-02| ✔️ | |
|CAT-03| ✔️ | |
|CAT-04| ✔️ | |
Main TON monorepo, which includes the code of the node/validator, lite-client, tonlib, FunC compiler, etc.
## Updates flow:
* **master branch** - mainnet is running on this stable branch.
Only emergency updates, urgent updates, or updates that do not affect the main codebase (GitHub workflows / docker images / documentation) are committed directly to this branch.
* **testnet branch** - testnet is running on this branch. The branch contains a set of new updates. After testing, the testnet branch is merged into the master branch and then a new set of updates is added to testnet branch.
* **backlog** - other branches that are candidates to getting into the testnet branch in the next iteration.
Usually, the response to your pull request will indicate which section it falls into.
## "Soft" Pull Request rules
* Thou shall not merge your own PRs, at least one person should review the PR and merge it (4-eyes rule)
* Thou shall make sure that workflows are cleanly completed for your PR before considering merge
## Workflows responsibility
If a CI workflow fails not because of your changes but workflow issues, try to fix it yourself or contact one of the persons listed below via Telegram messenger:
* **C/C++ CI (ccpp-linux.yml)**: TBD
* **C/C++ CI Win64 Compile (ccpp-win64.yml)**: TBD