-
Notifications
You must be signed in to change notification settings - Fork 371
CPS-???? | Linking Off-Chain Identities #1059
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
…rifiable financial records on-chain
Co-authored-by: Ryan <[email protected]>
Co-authored-by: Ryan <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Kammerlo this was triaged at today's CIP meeting, with the introduction mainly getting caught up in formatting inconsistencies with other CPSs and the document specs in CIP-0001 and CIP-9999. Most of that response is already posted at this point.
Our decision was to leave this Unconfirmed and leave detailed review to the coming biweekly period. When you or editors think it's ready, it should come out in the discussion & we'll put it up for Review at the following meeting: with the goal of upgrading this to Confirmed after more review, response & update and then giving it a CIP number.
One thing that came up in the meeting review was an observation that any future versions of the specification were required to maintain consistency with all other previous versions. I think this could make for a good point of discussion going forward: since this would be an unusually strict requirement of versioning and CIPs in general.
Feat/keri cip
We are currently working on different solutions, which involve offChain identifiers to prove that a legal entity is behind a transaction.
For example an organisation with a valid vLEI wants to publish transactions on chain. Finding a way how to tie these identifiers to the transaction will add another layer of trust and accountability.
There are a few possibilities for these identifiers. One latest example of a CF solution is the implementation of KERI within the Veridian Wallet.
A rendered solution is here: https://github.com/Kammerlo/CIPs/tree/master/CPS-%3F%3F%3F%3F