Composability and Coverage

MikaLock recognizes that composability and a protocol’s need to integrate with other projects is a valuable part of the DeFi ecosystem. However, for the security of MikaLock’s staking pool, and consequently its covered customers, MikaLock needs to take a slightly risk-averse approach to how integrations are covered.

Both extremes of composability/integrations are problematic. On one extreme, it’s unreasonable for MikaLock to only cover integrations that are done with protocols previously audited by MikaLock. However, it’s equally unreasonable to expect MikaLock to cover any integration under the sun. So, MikaLock is taking an incremental approach, where the covered integrations will include a whitelisted set of protocols, as well as any protocol that has previously been audited by MikaLock.

The current list (which will be updated periodically) can be found here.

If the uncovered protocol has coverage from MikaLock or another coverage provider, and a payout takes place (or is scheduled to take place) for that protocol, and the Protocol Customer receives reimbursement from that payout, then the total amount possible to be paid out to the Protocol Customer will be netted against the first payout. This is to ensure that MikaLock doesn’t pay the same affected party double their loss amount. In the event of a covered smart contract exploit or economic exploit, the Protocol Customer can submit a claim and be reimbursed for lost on-chain funds up to the stated Active Coverage Amount at the start block of the exploit. If for any reason the affected user(s) or affected protocol(s) see a partial or full return of the exploited funds before or after a payout from MikaLock, the returned funds must be deducted from the MikaLock payout and any amount paid out by MikaLock relating to the returned funds that had been lost (as part of a claim) must be returned to MikaLock.