uPort/Lobby

Welcome to the uPort lobby!

Mircea Nistor

@mirceanis

But the first interaction is important, as there is no other prior information. It is up to the user to determine trust then.

@smitrajput the credential is not stored on ipfs. It is stored in the local storage of the uPort mobile app, and optionally backed up in an end to end encrypted cloud storage if that is enabled in settings.

Mircea Nistor

@mirceanis

@7-of-9 as far as I know there is no easy way to verify and interpret JWT onchain. Also, it goes against uPort recommendations since it would expose that JWT forever to the world if it's part of a transaction.

But, it should be possible to verify a simpler signature coming from a uPort account, in an onchain authorization scenario.

Mircea Nistor

@mirceanis

Also, the uPort mobile app can sign EIP712 typed data, which can be used as a credential format that is theoretically verifiable onchain. The same privacy concerns apply as with JWT if the signed typed data is part of a transaction though.

Dominic Morris

@7-of-9

Thanks @mirceanis , appreciate your input. My use case is for a ERC1404 security token, specifically in verifying recipient eligibility in the case of an erc20 transfer TX. Here, the EVM/runtime erc1404 would really like to verify the claim(s) for the token recipient, to check that he is authorised to receive the security tokens. Seems to me that on-chain verification of claims is a very key requirement.

Shyam Pratap Singh

@spsingh559

Is there any guide/documentation to build your own uport mobile wallet and stored credentials and share with authority like uportlandia interaction?

Shyam Pratap Singh

@spsingh559

Hi everyone, I would like to know the status of Uport/DAF, can we use this framework for building an identity solution, I have not find documentation regarding DAF except Github. Any help would be appreciated.

Mircea Nistor

@mirceanis

Hi, Shyam.
DAF is the framework we're focusing on now and for the foreseeable future.
It is meant to unify most of the common protocols and formats developed by the W3C and the Decentralized Identity Foundation(DIF) as they relate to Decentralized Identifiers(DIDs) and Verifiable Credentials(VCs).
It is in early development and github is at the moment the best place to get help about it.

Nhan Le

@NLe1

Hi guys,

I am trying to set up uPort with local private Geth client Ethereum network but the best I can try is to follow this github https://github.com/uport-project/private-net-example, but unable to set up because of some JWT problem. Have any of you guys have ever tried this ?

I noticed that the uport-cli is deprecated and there are some use case of this repo that really help in my case

so are uPort going in this direction of supporting the developer's use case which is deploying uPort identities on private network?>

Thanks for reading

Héctor Iván Hernández Castelán

@HeckCas_gitlab

Hey guys! I wanna ask, which is the best way to obtain only the public address of a user, generating to the user a Qr and sending him to scan it to receive public address in my server. I'm currently using the "credentials.createDisclosureRequest" and creating a Qr but in the callbackUrl i dunno how to send it back to the frontend or to the creaQ-Endpoint

Sohrab Quraishi

@sohrabq

hello mates,

i have a problem in uport appmanager website while scanning the QR Code to login it gives the error while formatting outputs from RPC '{"value":{"code":-32002,"message":"rejected due to project ID settings"}}'

could any one help me out please

Ross Bernard Jamaca

@rbjamaca

Where to refer if I wanna do the implementation where credentials get saved to the blockchain?

Ross Bernard Jamaca

@rbjamaca

Hello?

Mircea Nistor

@mirceanis

@rbjamaca please, NEVER save credentials to the blockchain!
Not even encrypted.
It is fundamentally not scalable, it can be very expensive and in many cases it may be a privacy breach and a GDPR violation.

All the work the uPort team has done was to prevent exactly this

Ross Bernard Jamaca

@rbjamaca

I understand @mirceanis . Anyway, while testing some of the examples, i've just noticed that some stuff are not currently working especially about disclosure requests on uport-credentials.

Mircea Nistor

@mirceanis

Sadly we don't have the bandwidth to maintain the full uPort stack anymore.
All of our efforts are now focused on the Veramo framework ( https://github.com/uport-project/veramo ) and the libraries that uPort has donated to the Decentralized Identity Foundation.

If you are just starting out, it would be a good idea to check out https://veramo.io instead of relying on the uport-credentials / uPort mobile combo.
It is not yet a full replacement for the uPort stack (and I'm not sure if it will ever be a 1:1 mapping there) but the goal is to provide a standards-compliant, multi-platform framework for decentralized identity and verifiable credentials that can also interoperate with other projects and efforts in this space.

Ross Bernard Jamaca

@rbjamaca

Thank you for pointing me to the right direction. I'll give veramo a try.

yiannakpavy

@yiannakpavy

I apologize for being naive, but are there fees associated with creating a uPort identity? Everything I have read claims that these fees are payed by a fueling server, and that the uPort identity is the address of the proxy contract on the Ethereum chain (mainnet?). Can anyone offer some clarification?

Mircea Nistor

@mirceanis

Hi, @yiannakpavy. It's not naive :) Indeed uPort was using this model in the first version, but that has changed a long time ago.
The latest versions of uPort no longer use a proxy contract to represent an identity.
Instead, any ethereum address is considered an identity (see https://github.com/decentralized-identity/ethr-did-resolver).
Since these addresses can be created without interacting with the blockchain, it means that creating an identity is free.
If one needs to update the identity, then a transaction is required and that will cost some gas.
The smart contract on which this is based (https://github.com/uport-project/ethr-did-registry) allows a third party (like a fueling service) to pay for the transaction if the right signature is provided by the identity for which it posts.
This mechanism later got the name of meta-transaction.

That being said, please read my previous note about the state of the uPort stack: https://gitter.im/uport-project/Lobby?at=60422bb8823b6654d285dcc5
Please take a look at https://github.com/uport-project/veramo as this is where all the development work is being focused now.

yiannakpavy

@yiannakpavy

@mirceanis Thank you for the clarification and all the info! I think my confusion still lies in the notion of creating an Ethereum address without interacting with the chain. Does the address persist on the blockchain when created? Also, is the old version of uPort (using proxy contract as the identity) still being used/available? With respect to Veramo, is there a uPort-equivalent platform/app in development that encompasses SSI, eg, managing identities and credentials? (I apologize for bombarding you with questions)

yiannakpavy

@yiannakpavy

@mirceanis Sorry to bother, but I had a few follow-up questions. When you say a transaction is required to update the identity, is this analogous to updating the DID doc of the identity with attestations/attributes? Does uPort still support updating a uPort-specific decentralized registry (e.g., via the Registry Contract) that maps a uPortID to off-chain, disclosed data (e.g., via IPFS)? I'm trying to better understand the use cases supported here, e.g., on- vs. off-chain transactions, and how/when the blockchain is used.

yiannakpavy

@yiannakpavy

To supplement the discussion above, it looks like the current uPort application still implements the Proxy Contract. See https://github.com/uport-project/specs. Is that correct?

yiannakpavy

@yiannakpavy

And one last series of questions (sorry about not just creating a thread), how is key recovery implemented without the Proxy Contract and Controller Contract? Is everything backed into ethr-did-registry contract methods now? Also, is Serto now that overarching platform (that was uPort) that leverages the Veramo project?

Mircea Nistor

@mirceanis

ok.. I will try to answer as much as I can.

an ethereum address is computed by hashing a secp256k1 public key and taking the last 20 bytes of it. No interaction with the chain is necessary. You can create a keypair on your computer, hash the public key, take the last bytes and there you have it.
The address can be queried on chain but nothing will come up. If you go to etherscan and look for it, it will just show up as any other address that has no transactions associated.
the ethr-did-registry, when queried for a non-existent address will just return back the address.
the old uPort version is no longer used, nor available.. You may try to build it from source but you will run into many many issues that nobody can fix.
in the more recent model (the only one that still matters) updating the identity means updating the DID document with attributes that later get interpreted as public keys or service endpoints in the did document. Attributes on-chain are a big no-no.
Please take time to go through the links I have posted about ethr-did, as there are many more details about how did documents are built.
the current uPort application does not still implement the Proxy model. I'm not sure where you find that mentioned without a deprecation message.

yiannakpavy

@yiannakpavy

Thanks, man. That's helpful. Is this concept of a central registry (for off-chain look up) still alive? As a general user, why would I ever need the central registry?

E.g., why would I ever need to do anything on-chain that is related to identity (and/or attributes)?

(that's likely a stupid question, but again, I'm a total noob)

Mircea Nistor

@mirceanis

again, on-chain attestations are not recommended.
on-chain identity management, in the ethr-did model means posting public keys that can be used to sign on behalf of an identity

yiannakpavy

@yiannakpavy

but can't that be achieved off-chain, as well? E.g., isn't that how I would disclose an attestation to a private party?

Mircea Nistor

@mirceanis

Of course, most things can be achieved off-chain. The chain is only used to update public key information (that can be used to verify those off-chain attestations).
To update those keys on behalf of an identity, you have to have control of the identity, and that is what the ethr-did-registry smart-contract ensures.

If you have more questions about these things, please post them on https://github.com/uport-project/veramo/discussions
There are more people there that can answer.

yiannakpavy

@yiannakpavy

OK, will do. Thanks again for the help!

Mircea Nistor

@mirceanis

you're welcome!

please understand. uPort is no longer maintained :(

yiannakpavy

@yiannakpavy

Right on. Thanks for the clarification. There's so much academic/technical literature out there (from as recent as last year) that provides technical analysis of the old version, so that's why I was getting confused. For what it's worth, I'm trying to gain understanding from both a developer AND user standpoint, hence some of my questions are from an identity holder's perspective.

Mircea Nistor

@mirceanis

got it. I'm curious, where this literature is :)

yiannakpavy

@yiannakpavy

One example: https://www.researchgate.net/publication/339836401_Self-Sovereign_Identity_Systems_Evaluation_Framework

yiannakpavy

@yiannakpavy

Also, just a point of clarification, is Serto now the overarching SSI platform, and it implements Veramo?

Mircea Nistor

@mirceanis

oh.. I was editing one previous answer to answer that and it got lost (I'm a noob at gitter).
Serto uses veramo to do most operations but I'm not sure if it has all the properties of an SSI platform.

yiannakpavy

@yiannakpavy

OK, cool. The https://www.serto.id/ site implies ownership of Veramo, so I was just curious. Also the headline on the top of the website seems to imply as much, "uPort is now Serto".

Mircea Nistor

@mirceanis

We're close collaborators, different teams formed from a mix of older members of uPort. Used to be under one umbrella, hence the listing of all the open source libraries and veramo. "uPort is now Serto" refers to the brand.
Veramo focuses on the lower level tech, multi-platform, keeping close to standards, modular framework.
Serto provides services that leverage Veramo, in a nicer package than the raw framework.

yiannakpavy

@yiannakpavy

Ah, that's makes sense. Man, I can't thank you enough for the discussion. I really appreciate you taking the time to help!

Mircea Nistor

@mirceanis

You're welcome!

See you on GitHub :)

Where communities thrive

People

Repo info

Activity