Resolves conflicts across governance-dao, oracle-verifier, and risk-pool that arose from upstream merging several other bounty PRs (execution audit trail, cross-validation, geographic weighting, fee tiers, LP collateralization/vesting) after this branch was created. Error enum variants that collided on the same discriminant were renumbered so both sides' variants coexist; StorageKey/event/type additions from both sides were kept side by side. Also fixes pre-existing breakage on main uncovered only once the merge made the full workspace buildable, unrelated to issues Parashield-Protocol#382/Parashield-Protocol#383/Parashield-Protocol#385: - governance-dao: `Proposal` literals were missing the `verification_callback`/ `execution_verified` fields added by the execution-audit-trail feature, the `is_vetoed` field used by `veto_proposal` was never added to the struct, and `Error::ProposalVetoed` was referenced but never defined. - oracle-verifier: `StorageKey::GeoWeight` was used by the geo-weighting feature but never added to the enum; the region-aggregation path never set `AggregatedData`'s confidence-interval fields; `get_reputation_weighted_confidence` exceeded Soroban's 32-character contract function name limit. - risk-pool: `LpPosition` literals were missing the `insurance_enabled`/ `insurance_paid` fields added by the LP-insurance feature. - claims-processor: `Claim` literals were missing the identity-verification fields; a `get_claim(&env, ..)` call didn't match its by-value signature; an installment-schedule update had a borrow conflict. - risk-pool/claims-processor: `Option<CustomStruct>` fields (`vesting`, `installments`) don't round-trip through soroban-sdk's XDR (ScVal) conversion once any crate's `testutils` feature is active anywhere in the build graph (a build-graph-wide feature, not a per-crate opt-in) -- `cargo test` therefore could not compile even though `cargo build` did. Switched both fields to `Vec<T>` (0/1 elements), which soroban-sdk does support generically; updated the small number of call sites. - claims-processor/src/test.rs had two test functions whose bodies were interleaved with fragments of unrelated tests, left over from an earlier, unrelated commit's mechanical rewrite (b1e5fda) of this file; restored both from the last commit where they were correct. claims-processor/src/test_integration.rs and src/test_advanced.rs from that same commit have similar corruption (e.g. a module-level attribute stranded mid-file) that is left unresolved -- claims-processor is untouched by any of this branch's three issues, and reconstructing its test suite is a separate, unrelated cleanup. `cargo test --quiet` at the workspace root will still fail on that crate until it receives its own fix.

Uh oh!

[Enhancement] No risk pool reinsurance mechanism #382

Description

Activity

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions