This page serves as a living document to explore how a Cosmos chain (here Inco Network) can be dual-secured by using EigenLayer restaked ETH. Context TODO: what is Inco, what is Eigen, why dual stake. This blog post is a good intro. Goals Use both INCO and ETH to secure the Inco appchain. As far as possible, use the same infrastructure for Inco's bridging. A third consideration is that the Inco validators will additionally run a MPC network for the FHE decryption key. However, due to the current difficulties with slashing in a MPC network, we can omit this consideration in this document.

import github.com/google/uuid // msgServer is the server-side (blockchain node) implementation of // a blockchain transaction handler. type msgServer struct{ // store has access to the blockchain state, which is a key/value store // (which will be merkelized) persisted on disk. store *Store }

Date: March-April 2023 Auditors: Amaury (https://github.com/amaurym), Facundo (https://github.com/facundomedica) Introduction SIGN_MODE_TEXTUAL is a new string-based sign mode that is targetted at signing with hardware devices. It is specified in ADR-050. In 2022-2023, the Cosmos SDK team led a working group with Agoric, Confio, StrangeLove and Zondax to implement SIGN_MODE_TEXTUAL. As part of its Quality Assurance process, this working group is conducting an internal audit to identify potential security issues, inefficiencies and non-compliance to the specification. This document describes the results of the internal audit.

import github.com/google/uuid // msgServer is the server-side (blockchain node) implementation of // a blockchain transaction handler. type msgServer struct{ // store has access to the blockchain state, which is a key/value store // (which will be merkelized) persisted on disk. store *Store }