Skip to content

Commit b41ce20

Browse files
committed
CAD11 error sources
1 parent d0e6311 commit b41ce20

File tree

1 file changed

+5
-7
lines changed

1 file changed

+5
-7
lines changed

cad/011_errors/README.md

Lines changed: 5 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -217,20 +217,18 @@ If a pre-condition is not met, it may then be appropriate to `fail` immediately
217217

218218
## Error Sources
219219

220-
Error sources indicate the region in the network where an error occurred
220+
Error sources indicate the region in the network where an error occurred. These are important mainly because they can indicate responsibility for failure and/or or how to diagnose the problem.
221221

222222
| Source Code | Location of error | Example(s)
223223
| ------------ | -------------------------------- | -----------
224224
| `:CLIENT` | Client library code | Failed input validation
225225
| `:COMM` | Client-Server communications | IO failure, connection failure or timeout
226226
| `:PEER` | Peer handling of user request | Rejected for bad signature by peer
227-
| `:NET` | Consensus network | Transaction rejected in corrupt block
228-
| `:TX` | CVM transaction handling | Invalid public key for account
229-
| `:CODE` | CVM code execution | Invalid public key for account
230-
231-
232-
, probably due to invalid input validation
227+
| `:NET` | Consensus network | Transaction failed to get into consensus
228+
| `:CVM` | CVM state transition handling | Invalid sequence number, `:JUICE` error
229+
| `:CODE` | CVM code execution | `:CAST` error in user code
233230

231+
Error sources are not formally part of the Convex Network / CVM specification, but are important additional information normally returned alongside transaction results. Be aware that a malicious peer could fabricate the error source, so it may be useful to independently validate results.
234232

235233

236234

0 commit comments

Comments
 (0)