# Aca-py update with BcGoc

### Docs

https://docs.google.com/document/d/1YamSGM2FX34uXp4otWeHH976pyxN4Jaz59llypOf_kY/edit#

https://docs.google.com/presentation/d/18c6tFDMrqnRPVIMHbqI6xbSoKMaicxspfApqVT2FKkI/edit#slide=id.gae843b0b89_0_2

## Json-ld and BBS+ support

* 1rst phase : Support for "plain" JSON-LD over the current issue credential/present proof RFC's 0036/0037 (or RFC 0453/0454)

* Expose via admin API endpoints just to add and verify linked data proofs. Usefull when implementing Rest full base API's. See https://github.com/w3c-ccg/vc-http-api

:::info
* What whould be the differences between using direct v1 ? vs v2
* libindy-request-presentation and libindy-cred-offer-0 ?
* Credential storage -> Aries askar
:::

* 2nd phase : Support of BBS+ and DIF presentation exchange data format
:::info
Using RFC 0453/0454 as a protocol ?
:::

https://gataca-io.github.io/verifier-apis/

## Universal resolver and did:ethr base on EIPS-1056

### Universal Resolver

- Integrate universal resolver as a default fallback when not native did resolver available

- Universal DID SaaS is working on DIDComm binding to DID resolvers (Aries RFC 0124). Will be included in the open-source version ?

### Support DID:ETHR base on EIPS-1056 on issuance

- most probably did methods base on https://github.com/ethereum/EIPs/issues/1056 so we can align with the European Blockchain Services Infrastructure did:ebsi)
- Universal Registrar ?