Previous to this change, were those identities uploaded on uport's very own mainnet?
@Rachel5514Cho_twitter This is an old article explaining how uport digital identity infrastructure is helping before uportDIDs were migrated to Ethr-DIDs https://medium.com/uport/zug-id-exploring-the-first-publicly-verified-blockchain-identity-38bd0ee3702.
@HABIMANAROGER6_twitter You can specify the network by providing the network_id. this is explained in a portion of this article https://medium.com/uport/uport-on-any-ethereum-blockchain-c54368a12e8c
Is the https://appmanager.uport.me/ working? I cannot see my apps. It just shows me a message "Searching for your apps…
Reading the public blockchain. This may take a moment." and never comes back.
Reading the public blockchain. This may take a moment." and never comes back.
I have tried clearing the caches, using Incognito mode. Although the application is running fine but app manager doesn't show my apps.
Is anyone else facing the same issue?
https://uportlandia.uport.me/ is doing a good job at demoing SSI based auth and data sharing.
I've studied the source code behind it a bit, but still couldn't find an answer to this question: is there any standard which specifies the data formats and protocols used? E.g. in order to request "date of birth", what's the machine readable name of that attribute and what does the request need to look like? There's https://github.com/uport-project/uportlandia/blob/develop/src/constants/config.js, but it doesn't mention if the exact data structures used there are "self invented" or implementing some (draft) standard.
I've studied the source code behind it a bit, but still couldn't find an answer to this question: is there any standard which specifies the data formats and protocols used? E.g. in order to request "date of birth", what's the machine readable name of that attribute and what does the request need to look like? There's https://github.com/uport-project/uportlandia/blob/develop/src/constants/config.js, but it doesn't mention if the exact data structures used there are "self invented" or implementing some (draft) standard.
I found https://www.iana.org/assignments/jwt/jwt.xhtml, but that seems not to be what's used
Also, I'm aware of attempts to create a standard for "did auth". Is uPort involved in that standardization? Is there any draft standard which uPort is implementing or about to implement?
@d10r As per my understanding. Credentials are very customisable, maybe someone here has a better knowledge of it but take a look here https://developer.uport.me/credentials/createverification and how the date is used in creating a credential. and i, myself is looking for the perfect answer for this question. So a date can be just a simple string like "19th FEB 2020" which can be put inside a claim field or it can be formatted. whats important is how you make use of those values in your smart contracts and DApps
How does uPort derive the keys and addresses? I tried to follow the logic but got stuck at "RNUportSigner.d.ts" because I can't see where that code comes from. (I've tried using other things like uport-credentials and MyEtherWallet and they give a different address when I put in my seed. uPort mobile says it's using mainnet, but is it using a derivation path different from m/44'/60'/0'/0 ?)
@Taimoor10 it's all easy as long as I only want my Apps to interact with each other. But for interoperability, it's important to speak the same language.
According to that doc (thx for the link), it's at least partially based on OpenID claims spec. I hope that in the future there will be convergence with projects like Hyperledger Aries,Kantara Initiative, IHAN Blueprint etc.
As I currently see it, uPort does a great job at building tooling and approachable demos.
It's not so clear to me if uPort is well integrated into standardization efforts. The space still seems to be quite fragmented.
@d10r you are right. It says here https://developer.uport.me/messages/sharereq that claims are somewhat based on OpenID-Connect and it would be great if uPort improves their documentation and make these things clear. There is certainly need for it
@Taimoor10 @d10r yes, that spec is indeed based on OpenID-connect.
At the moment there is no final standard regarding credential request/replies but uPort is working towards interoperability.
This will also mean that legacy protocols will be unmaintained when that happens.
I see many potential bugs being discussed here, many without resolution.
Generally it's better to post these on github.
The uPort team, unfortunately, doesn't have the resources to man this lobby too often, leaving people without answer.
Discussions are still very welcome, of course, but if you suspect there's a bug somewhere it fits better as a github issue.
Is there any code for sign ETH transaction use UPort credentials? https://developer.uport.me/credentials/transactions is not work for me.
@passionofvc, it's impossible to know what does not work for you. Please share abundant details about your setup and error messages to increase your chances of getting help.
Ideally, post the snippet of code that is failing and error details as an issue on https://github.com/uport-project/uport-credentials/issues .
Don't forget to remove any private keys from code before posting.
Ideally, post the snippet of code that is failing and error details as an issue on https://github.com/uport-project/uport-credentials/issues .
Don't forget to remove any private keys from code before posting.
@mirceanis I create sample use https://developer.uport.me/credentials/transactions but send error happened when I approved the request, show network provider is invalid,
@mirceanis Is there any app run as UportID can use local truffle,Ganache node, local ipfs to save hash data, local transport push event service (chasqui) to debug how credentials work? UportId(mobile) has many build in https://id.uport.me/req/ https://ipfs.infura.io:5001/api/v0/add.
hello everybody .. I hope this is the right place to get some entry level information .. i'm coming from a little experience made on SSI on Hyperledger Indy .. now trying to wrap my mind about how concepts of Indy maps on uPort .. is there any up-to-date document that may assist me?
I guess the signing account of the TX in question would need to be authorised by the identity owner to read the data, that is understood in principle. But is it even possible at all to do "on-chain" stuff like this in uPort? All the examples I could see talked about doing this with JWT, HTTP, JS, etc. -- not Solidity.
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.
But, it should be possible to verify a simpler signature coming from a uPort account, in an onchain authorization scenario.
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.
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.
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.
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