Forking in Algorand Network

Jun 28, 2021
This is a very good question. I’ve written a detailed answer there: Network partitioning - #2 by fabrice Let me know if something is unclear.
The short answer is: there is no risk of forking on Algorand even in case of network partitioning as long as something like 80% of the (online) stake is hone…

When the network stalls, no blocks/rounds are created and no transactions can be committed at all. To make a key registration, you need to make/commit a transaction to the blockchain. So if the network is split 50/50, you just cannot make a key registration at all.

A round takes 4.5s only when …

Also, if you are interested, there is actually a formal proof in Coq (i.e., a proof verified by a computer and not just a human) that the Algorand network never forks even in case of network partitioning. There is a very detailed report there: algorand-verification/report.pdf at master · runtimev…

Stateful Smart Contracts ClearState

Welcome to Algorand!
If you cleared out all the contracts and assets, the minimum balance should be 0.1 Algo. What minimum balance do you get? How did you check it? Can you reproduce the issue on TestNet (on a fresh address) and give the address?

Thank you! I have resolved the issue, it looks like “goal app clearstate” was not sufficient and had to call also closeout. Clearstate cleared the state, it worked, but left the address opted-in, which still required increased minimum balance. Thanks.