mesh-security-sdk
mesh-security-sdk copied to clipboard
osmosis-labs
Let's make these better. Some ideas: * Allow per-contract/provider epoch lengths * Better reporting/handling of failed calls (not just log message, but somehow tracked on chain) * Allow someone dropping...
Slashing does reduce the staked amounts. How do we want to handle this in the used max cap and supply offset?
Following with https://github.com/osmosis-labs/mesh-security/pull/192, a new logic for storing delegator data is required in x/meshsecurity module.
Refered to https://github.com/osmosis-labs/mesh-security/pull/201, virtual contract need to check if the ValidatorSlash is tombstoned or not
closes [#89](https://github.com/osmosis-labs/mesh-security/issues/89) ### Description - Add `Restake` custom message to run `InstantUndelegate` function at `mesh-security-provider` module. - Then`Bond` coin to `vault` contract and `Delegate` through `native_staking` contract. ### Note -...
closes [#175](https://github.com/osmosis-labs/mesh-security/issues/175) ### Description - Add `Unstake` custom message to run `InstantUndelegate` function at `mesh-security-provider` module. ### Note - Need to write new e2e test - Follow up PR on...
Follow up https://github.com/osmosis-labs/mesh-security/pull/206
Related to https://github.com/osmosis-labs/mesh-security/issues/176, we need to store the native-staking-proxy contract address with the corresponding consumer chain-id for handling evidence sent from the relayer.
