I have a solidity function enterEther to send ether to the smart contract like this
function enterEther() public payable {
Receive(msg.value);
balance += msg.value;
}
and i want uPort to call that function. This is my transaction Object. I am using uport-connect library
const txRequest = mycontract.enterEther({
notifications: true,
accountType: "keypair",
networkId: '0x3',
callbackUrl: 'https://uport-connect-demo.herokuapp.com/txcallback',
from: '0x447ea080ad0bc5c14fe82ae4a2581cb8e9de72ea',
value: '0x0111111111111111' })
However when i specify the from field. i don't receive the notification in uPort app to sign this transaction and when i don't specify the from field, i receive the notification but there is no account to send transaction from. help would be very much appreciated.
@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.
@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.