You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
is_valid_cert should take a type implementing Membershipas input
the is_valid_cert impl should directly call the threshold/stake table it needs from Membership (stake_table/success, stake_table/upgrade or da_stake_table/da_success). I think CERT::stake_table and CERT::threshold might be available for this, but maybe these should be on Voteable? haven't fully thought through this
the build_cert function in testing looks fine, but worth a double-check
I might be mixing some things up here, but basically we want to make sure anything directly taking a stake_table or threshold is refactored to only take a Membership, where possible. I think this should be a fairly small refactor but should add a lot of safety
The text was updated successfully, but these errors were encountered:
Delete Memberships and replace functionality. Add some methods to
`Membership` trait to deal w/ collapsing into one type both kinds of
memberships (stake and DA).
* avoid passing membership into `is_valid_cert (see #3918)
* for DA, avoid proxying threshold through `Threshold` trait
* remove `Topic` param from `Membership::new
* Split cert impls by marker (#3891)
* add membership methods to Cert trait
* remove non-existent test from justfile
---------
Co-authored-by: tbro <[email protected]>
See coment #3867 (comment) and zullip discussion.
I might be mixing some things up here, but basically we want to make sure anything directly taking a stake_table or threshold is refactored to only take a Membership, where possible. I think this should be a fairly small refactor but should add a lot of safety
The text was updated successfully, but these errors were encountered: