diff --git a/premix/index.html b/premix/index.html index 9d49037e8..c500a9d63 100644 --- a/premix/index.html +++ b/premix/index.html @@ -122,42 +122,31 @@
The top navigation is ordered from left to right like the picture below.
- - -- Usually you will start from left, then move to the right to find out where the bug might located. - If you see red colored text, it means you already found the difference between nimbus and other ethereum - client tracing result. + Work your way through the top-right menu, left to right, to find out where the bug might be located. + If you see red colored text, it means you already found the difference between Nimbus and the other Ethereum + client's tracing result.
- If there is no red colored text in opcode section, it means the bug might be located in transactions section, - or in header section. + If there is no red colored text in the OPCODE section, it means the bug might be located in the TRANSACTIONS section, or in the HEADER section.
- Once you already located the bug, you can use debug.nim located in /premix - to sort things out until there is no more error or it pass block validation. + Once you locate the bug, you can use the ./build/debug tool + to sort things out until there are no more errors and the block passes validation.
- Block with multiple transactions will have triangle pointing downward in the navigation bar. - Usually only the first transaction with red colored text have the problem, but it might affect the rest - of other transactions. In opcode section, the same thing happened, perhaps only the first instruction - with red colored text have the problem, but it will affect the rest of other instructions. + Blocks with multiple transactions will have submenus in the navigation bar. + Usually, only the first transaction with red colored text is problematic, but it might affect the + other transactions. In the OPCODE section, the same thing happens. Perhaps only the first red-colored instruction + is problematic, but it will affect the other instructions.
- In Transactions section, you'll see the transaction kind. - It has three kind: Regular, ContractCreation, and ContractCall. - Each kind will help you locate the bug in Nimbus implementation, they have their own proc. + Transactions in the TRANSACTIONS section are marked as: Regular, ContractCreation, or ContractCall. + Each kind is processed separately by Nimbus, in different procedures.