Ledger Cosmos Call

# Ledger Cosmos Call * Agenda * Intros * Alix @ Ledger - Stargate integration of Ledger * Product Manager for the team * What direction and adaptation is needed * Ge * Gerry @ Ledger * especially active on initial integration * Juan @ Zondax * Team contributing to ledger or cosmos signing to date * ICF funded for continuted Ledger work * user interfacing improvements are incoming * CosmoStation * David * CosmosSTation webwallet & Mobile * booyoun * In charge of development at cosmostation * CosmosJS Library * LEdger integraiton * Keplr * Josh * Chainapsis / Keplr wallet * Chrome Extension and web wallet * Support Ledger * Lunie Light * Denis * Tendermint Inc * Interested in newly scaffolded chains * Confio * Simon Warta * CosmJS, client side libraries interacting with cosmos SDK chains * applied crypotgraphies (Slip10 key derivation) * Signing support in client library for launchpad blcokchains and recently developer connectivei to startage blockchains * Regen * Amaury * Regen has been maintaining the SDK * Familiar with the different sign modes * proto versus aminto * Interchain GmbH * Marko * * Support Ledger team * What is the current state? * There's almost 0% chance of having a new hardware app deployed fo rthe timeline of stargate. If you want to keep using Ledger for foreseeable future we need to keep the same mode as Textual * Legacy mode Amino * Keplr * testing for all amino endpoints are working * Juan * REST endpoints and What kind of payload do you send to a hardware wallet * What kind of payload? * story * any product in the ecosystem was going to be able to create a message, and the device could show key values * that's why text JSON was used * could add one more field and app could show * app was generic * moving to proto, change is REST API to submit, other is what is sent to device to be signed * If you add new fields, it should be OK * protobuf * we could make a cosmos app that reads protobuf, but new aps would have a different proto app schema * need an app for proto app schema * it's not a self describing protocol * Do you need any changes, or are there any changes in the JSON? * current Amino changes won't change * Future changes would be for 0.42.0 for SIGN_MODE_TEXTUAL * How to support ATOM / Cosmos Hub * General discussion about IBC * Ledger Live * focus is to continue supporting legacy ATOM * currently not allocating resources to IBC transfers * Missing feature is actually the verification side on chain * Keplr * use bandaid solution is preferred * Ledger: misunderstanding of what's going on * ledger doesn't support amino, it supports JSON * serialize protobuf to JSON it could be signed? * Needs a spec for protobuf to JSON * What is curently being signed is Amino JSON, it is a JSON dump of Amino * if you were to serialize protobuf as JSON, and it got signed by Ledger, what would happen? * There is no protobuf-JSON signing mode * Amino JSON & protobuf binary are the two signing modes * _could_ support Protobuf-JSON signing mode (an option to SIGN_MODE_TEXTUAL) * textual is a long string of text, ledger UI has a limited length for characters * can't stream 200 characters * IBC message transfer issue, ledger app doesnt' need to change, more of an issue whether the SDK implements the signing mode amino codec. * Simon: the whole space is defined by token transfers. This is a good candidate for a special case and give it priority over the generic case of all future applications. * Options * Coudln't the wallet parse proto, save the protofiles and generate the JSON? Need hardware to be self standing and unsderstand what is being sent * Protobuf-JSON versus SIGN_MODE_TEXTUAL * couldbe a json with one field as the JSON paylod with anothe field for human readble text * KV list instad of text that leads to a compromise how to separate things, delimiters * NEw signing modes * a lot documented around native representation of protobuf documents, loosely specified and not well supported by any library... has it's flaws.. but could be built on top of * might be same amount of work of newly defining * Aaron is the preson to talk to around this topic * Teams * Lunie Light / Tendermint Inc. * Keplr / Josh * CosmoStation / David, * Long Term Strategy * Regen & SIGN_MODE_TEXTUAL * Question * Cosmos versus Cosmos Hub * HD derivation path for the ATOM * they share the same public key on different keys, obfuscated by different addresses * Juan also concerned * Keep only one app in the ledger store? * 3rd number of derivation path could be used for chain * Breaking change on LEdger * When you open ledger and import accounts it defaults to first account, then iterating * Keep the same account, but change the index (4th number) keep it as a hardened derivation * Walelts can specify the derivation path * Best practice and documenting it * every user can derive as they want * they chain doesnt' know * it's a privacy concern * because the public key can be derived * Make a PR on Slip44 * then make a PR on Ledger-Cosmos * Tendermint Ledger question * no need for new tendermint app