λPrize 0018#75
Conversation
✅ Validation passedA reviewer will assess against the prize criteria. Automated check. See solution template and TERMS. |
There was a problem hiding this comment.
Looks good. Would bne good to liaise with @jm-clius or @moudyellaz see if any of the "identity stack" plans would be useful here. Meaning should we wait for them to deliver first, or shoudl we publish LP as is.
I would rewrite the usability to make the UI clearer. Eg, I assume the flow is I can share doc xyz to Alice's account (a public or private LEZ account), and alice would "automatically" receive it?
This is also in line with the idea of "deal room" that we want to see.
|
|
||
| ## Overview | ||
|
|
||
| This prize funds a **customer-owned, reusable encrypted document vault** for KYC/KYB and sensitive corporate documents, built end-to-end on the Logos stack with no centralised server. A customer — a **person or a company** — uploads sensitive documents **once** (passport, proof of address, certificate of incorporation, UBO and shareholder documents, board/shareholder resolutions, tax and onboarding documents), stores them **encrypted** in Logos Storage, and later grants a specific recipient — a bank, an exchange, a lawyer — **time-boxed access to selected files or packages**. When the relationship ends, the customer **revokes future access**. No document, and no sensitive metadata, ever leaves the customer's control in the clear. |
There was a problem hiding this comment.
When the relationship ends, the customer revokes future access. No document, and no sensitive metadata, ever leaves the customer's control in the clear.
Not really possible in the digital world, one can always do a local copy when they have access.
There was a problem hiding this comment.
probably bad formulation with ever leaves the customer's control
the idea is about revoking only future access revokes future access
|
It does seem like the Identity track would be useful here, although in terms of roadmap we only plan to have minimal Identity for mainnet. It will entail (by end of Q3):
See summary here Associated external identifiers (e.g. associating wallets, etc.) is only for post-mainnet. I didn't read in detail, but looking at this prize it seems as if a change from wallet-owned vault to λAccount-owned vault in future, shouldn't be too extensive. Given our timelines/priorities, though, I think it will at least be until September before there are useful identity library/primitives for you to use. |
|
thanks @jm-clius ! so, looks like we can proceed with @fryorcraken are you fine with proceeding with this as LP? |
3 participants
No description provided.