mesh-security
mesh-security copied to clipboard
osmosis-labs
`ConsumerPacket::AddValidator` requires the tendermint pubkey, and we will need that information to implement slashing. However, that information is not available in the CosmWasm queries we have access to. We need...
TODO: - [x] Slashing behaviour / impl. - [ ] MS V1 limitations / design decisions. - [ ] Osmosis price oracle contract. - [ ] ...
When unbonding from a tombstoned validator, we need to make sure if there's the need to unbond funds from the blockchain staking module or not. This is because some blockchain...
Verify with the Cosmos SDK that zero max-cap means / implies **no bonded amounts**. If that's not the case, send `Unbond` messages for each bonded tokens in the case max-cap...
Some follow-up IBC issues: - [ ] External Staking IBC `TransferRewards`: Add events. - [ ] Staking protocol over IBC: Ideas about using values in success ACKs to double check...
Would be great if we could publish a @mesh-security/types NPM package on every release.
We currently use a `ConsumerPacket::DistributeRewards` packet to send the tokens from consumer to distribute to the stakers on the provider. We need to review the semantics of that. First, we...
Builds on #89 but making the vault even closer to native staking. **Situation**: I have 1000 vesting $OSMO, which I could stake normally on one validator. It is currently not...
This may well be chain-specific and definitely requires a custom module (integration) on the provider side, but we should provide a design as well as at least one sample implementation...
As I understand, slashing is: The staking contract (the creditor) is getting slashed for x% (accumulated slashing can never exceed max_slash%). Then he has to forward information to the vault...
