In regards to formal verification of the actual code written in smart contracts, what kind tooling can we expect? Is there some ability to use K to do such things? Are refinement types (since Charles said dependent types are not/they are using System F omega if I recall) going to be part of Plutus with the compiler supporting that? Or (which I assume is unlikely) is it going to be possible to use Coq or some other proof assistant with program extraction straight to Plutus?
Somebody from twitter commented the following:
The limitation with Cardano is that offline transactions are not yet supported by the released wallets. Not being able to sign transactions offline means true institutional cold storage is not yet possible.
What it means exactly is that you need to be able to export an unsigned transaction, take it to a computer that's never been (or will be) connected to the internet, load your private key, sign the transaction, bring the signed transaction to an online wallet, and broadcast it.
If you cannot do that, then you cannot move your crypto without exposing your private keys to a online computer which significantly reduces security guarantees about the custody.
Paper wallets simply refer to private keys (or mnemonic seeds) written down on a piece of paper. It doesn't imply anything about the ability to load those private keys onto an offline computer and sign exported transactions.
INCENTIVES AND DELEGATION TEAM The details below reflect the work taking place on incentives in Cardano. The information is taken from a presentation on staking given by Lars Brünjes, IOHK Director of Education, earlier in 2018, and shows the general direction of the research though there will be refinements and additions as the work progresses.https://staking.cardano.org/Read the paper: Reward Sharing Schemes for Stake Pools.https://arxiv.org/abs/1807.11218Read the blog post on Staking: Stake Pools in Cardano.https://iohk.io/blog/stake-pools-in-cardano/Read the blog post on Sybil Attacks: Preventing Sybil Attacks.https://iohk.io/blog/preventing-sybil-attacks/Read the technical specification: Delegation Design Spec.https://github.com/input-output-hk/fm-ledger-rules/tree/master/docs/delegation_design_spec
pro-tip:You can use replit to share snippets of Cardano WASM code with other people to easily answer developer questions like “how do I generate addresses for a mnemonic”https://repl.it/repls/IndolentWarmheartedDehardwarization
Also, even tho the encoding structure is the same, but the derivation schemes for path indexes are very different, so it's not like V2 is V1 minus the encoded path. They are completely separate address spaces, hence the difference in number of mnemonics between wallets
we don’t provide this for two reasons1) Allowing for 12-word input would confuse a lot of Daedalus users trying to migrate to Yoroi2) We don’t want to encourage users to enter their hardware mnemonic into Yoroi since this turns their cold storage into a hot wallet
no but you can turn 24 words into a private key if you know how to program (example here but I don’t recommend typing in mnemonics into a website https://repl.it/repls/IndolentWarmheartedDehardwarization )
No way, as the generated entropy; of which the mnemonics are based on; is hashed and/or BPKDF2-d and/or HMAC-Blake2b-d etc. (depends on the wallet's imp) uses one way functions. And that (sometimes called master secret) and it's derivatives are the keys.
So essentially all you need to do is now create a new shelley testnet wallet..and keep the priv key/mnemonics safe and offline ..and use new wallet only from there on...your mainnet funds should not be affected or leaked if you havnt shared 12 word seed