-
It seems that there is an encoding issue for the following:
## ✅ decodeData
```js
ERC725.decodeData(
[
{
keyName: "LSP18RoyaltiesRecipients",
value: "0x001c24871b3…
Hugoo updated
4 months ago
-
### I'm submitting a...
- [ ] bug report
- [ ] feature request
- [ ] question about the decisions made in the repository
- [ ] question about how to use this project
- [x] documentation request…
CJ42 updated
2 months ago
-
Not related to erc725 but may be very useful.
Hugoo updated
5 months ago
-
Instead of working on ERC725 based DIDs (did:erc725:...) move to a higher lever ipid DID (did:ipid:...) based on IPFS and then specify the different public dids from different networks inside DID Doc…
-
There are a lot of people and projects addressing decentralised and self-sovereign identity, from formal specs to apps. We should list them so that we can get a better understanding of the space.
I…
-
At ERC725-alliance talk in Berlin, @ali2251 mentioned we're using `call` in our contracts, which is not reccomended:
I think this is the only case here:
https://github.com/OriginProtocol/origin-pl…
-
NEAR's accounts have few of the features of [DID specification](https://w3c.github.io/did-core) but not all.
We need a NEP that will provide a contract will full specification, a sample implementatio…
-
The queue of pending authorisations should rather be stored on chain - in the identity contract - and not in the relayer. I envisage relayers just providing gas relay service - not storing state.
Has…
-
https://w3c-ccg.github.io/did-spec/
https://identity.foundation/
-
We should add `generateLSP4MetadataJSON` function to generate the JSON from the available fields.
We could add several overloads