The most fleshed out part of the plan so far is some of our ideas for supporting 2nd layer “lite accounts” (implemented via a HAF app).
That sounds interesting, especially since you said it would come "relatively quickly". :)
Let's also see how much they can do, these lite accounts. You already said that's something you guys still discuss for the initial release.
I consider Lite accounts to be one of the key feature for creating a highly decentralized 2nd layer for Hive. It will let Hive users interact with unrelated Hive and offchain apps with a single identity.
Will they at some point be able to interact with L1 via smart contracts, or do you believe L1 should be off-limits for L2 lite accounts?
By design, they will always remain unable to directly affect the 1st layer. This is an important safety feature for the first layer. But it will always be possible to "port" proven, desirable functionality from the 2nd layer to the 1st layer. And a 1st and 2nd layer account can be "linked" via a common private key.
That sounds interesting. I tried to think if there would be a use case for the common private key, other than linking the two accounts together. Since L2 can't influence L1, but vice versa could potentially happen, if L2 allows it, I wonder how that can be used.