I hereby claim:
- I am exulansis on github.
- I am exulansis (https://keybase.io/exulansis) on keybase.
- I have a public key ASCx94FDHSHrw3Eb969HQhIkJu4UXf9UUqz-feF1DtoeYAo
To claim this, I am signing this object:
0x20e730cb137412f723f5c6c340cd444fcd0cb98c |
``` | |
agile-security | log info in agile-idm-web-ui: token info found by. for user id agile!@!agile-local and for client id AGILE-OSJS and with expiration 1507803979895 and scope ["1"] | |
agile-security | log info in agile-idm-web-ui: user found by user id agile!@!agile-local and id agile!@!agile-local | |
agile-security | log info in agile-idm-core: api: creating promise for creation of entity and setting owner to user executing the request | |
agile-security | log info in agile-idm-core: api: creating promise for creation of entity with owner agile!@!agile-local | |
agile-security | log info in agile-idm-core: api: creating promise for reading entity | |
agile-security | log info in agile-idm-core: error status code 404 error message: read entities with pk {"id":"agile-data-59df35f585c0a9002cd1ab91","type":"/client"} not found | |
agile-security | log info in agile-idm-core: attempting to validate entity of type /client and data is : {"name":"agile-data-59df35 |
pragma solidity ^0.4.19; | |
contract Donation { | |
address owner; | |
event fundMoved(address _to, uint _amount); | |
modifier onlyowner { if (msg.sender == owner) _; } | |
address[] _giver; | |
uint[] _values; | |
event deployed(address _a, address _creator); | |
function Donation() public { | |
owner = msg.sender; |
I hereby claim:
To claim this, I am signing this object:
I hereby claim:
To claim this, I am signing this object:
The did:jolo
method spec can be found here. A simple diagram illustarting the identity creation flow (using the Wallet) can be found here.
In order to create and interact with Jolocom identities, the Jolocom Library and SmartWallet (links to source code posted below) can be used. Some additional software components can make developing / debugging (also linked below) a bit easier.
At Jolocom we model verifiable credentials using W3C Verifiable credential specification, aside from some very recent spec modifications. Below you can see an example of a credential, serialized as JSON-LD, stating that the did did:jolo:ffcc8f84fae1b6ad253561d7b78167a661d72f58e86e60dbd04cd9b81096cdbe
is associated with the email address [email protected]
. You might notice that the subject, issuer, and signer of the credential, are the same identity. This can be effectively referred to as a self signed, or self issued, credential.
{
"@context": [
"https://w3id.org/identity/v1",