feat: stabilize public error mapping (#1380) - #1385
Conversation
…g#1380 public error mapping
|
Thanks for linking issue #1380. This PR currently adds only the intent document and does not implement public error mapping. Please add the implementation and focused golden-vector tests proving existing codes remain stable, new codes are unique and documented, unknown/out-of-range values decode safely, and all public entrypoints are covered. Please include CI validation evidence in the follow-up PR. |
|
Hello @greatest0fallt1me, I have implemented the stable error mapping as requested. I added the Note: I noticed there are existing compilation errors in the test suite from previous commits on this branch (e.g., Payout Routing
|
|
Hello @greatest0fallt1me, I've pushed an additional commit to resolve test suite compilation issues and fix unused result warnings in the newly added golden-vector tests. CI validation should now be able to run and pass correctly. Let me know if there's anything else you need! |
Summary
Closes #1380
This draft pull request establishes initial scaffolding and architecture intent for stabilizing public error mappings in Predictify contracts.
Proposed Implementation Plan
Acceptance Criteria Checklist
Payout Routing
0xF46C9F6d70C50BF81ef3588AB523a90a594a2F89GCL6OXAMLD75BMTINA6EMRUDWK5THQUSHMYNLSNBCJAPZJHNYJTUNIBC