[BLIP-10] Upgrade Core

[zacparker41]

Upgrade Core

Upgrade core package components for standards compliance. Zac Parker (@zacparker41)

---

Abstract

The core package has not been materially updated since December 17, 2020. Since then, the Baseline Protocol standard has been published and there has been significant R&D which has resulted in a software stack capable of satisfying enterprise demand in a manner that is standards compliant. In the interest of being compliant with the standard, it is a high priority to propagate those changes to the core package.

Motivation

Standards compliance, production systems.

Specification

The following packages represent the core protocol specification:

Previous Package	New Package	Reference	Description
api	api	https://github.com/provideplatform/baseline	The linked repo will be open source on or about 1/15 upon kickoff of the OASIS Provide Open Project
--	consensus	forthcoming
contracts	contracts	forthcoming
messaging	messaging	forthcoming
persistence	middleware	https://docs.provide.services/api/quickstart/baseline/product-middleware-integration
privacy	privacy	https://github.com/provideplatform/privacy
--	registry	https://github.com/provideplatform/ident
types	types	forthcoming
--	vault	https://github.com/provideplatform/vault

---

Test Cases

Documentation forthcoming.

Reference Implementation

Documentation forthcoming.

Security Considerations

Documentation forthcoming.

[skosito]

I'm curious to read a bit about significant r&d mentioned in the abstract. As a dev, it would be interesting to me to get a better feeling about enterprise demands, could you please point me to place where you documented it? Thanks

[skosito]

Also, one more question, should we use provide stack as reference or simply use baseline standard and update packages according to standard docs?

[kthomas]

Also, one more question, should we use provide stack as reference or simply use baseline standard and update packages according to standard docs?

Provide stack with standard swagger API reference will work nicely.

[GoldenBit0]

1/10/22 Core Devs:

• Propose group review of the Core (existing and new)
• Next steps: Sonal create working group and schedule first session, create new channel
• Timeframe: start in Jan

[GoldenBit0]

1/24/22 Core Devs:

• PR will be created and reviewed in next Core Devs session

[GoldenBit0]

2/7/22 Core Devs:

• PR will be created and reviewed in next Core Devs session

[GoldenBit0]

3/7/22 Core Devs: @kthomas please update

[GoldenBit0]

3/21/22 Core Devs: @kthomas please update

[kthomas]

Updating coming @GoldenBit0 ...

The didkit work is being merged into main this week across the stack and we will be propagating standards-related items up finally.

Thanks to the entire community for its patience as we have navigated the new PRVD-OASIS launch and how it relates to Baseline. Excited to share the updates live with the team at the next core devs meetup.

[GoldenBit0]

4/4/22 Core DEvs: @kthomas status changed to roadblock, awaiting update in core dev call or PR for review

[GoldenBit0]

5/2/22 Core Devs: @kthomas awaiting update in core dev call or PR for review

[kthomas]

Coming with PR! By next coredevs.

[GoldenBit0]

6/13/22 Core Devs: @kthomas any updates?

• Marking as icebox

[fleischr]

There was some progress on this in the BRI-1 branch Phillip last updated in august. There's an open PR under his name. We'll need to apply a few more updates from Phillip's last commits.

[fleischr]

I've done more analysis on this effort. I have a sheet of individual work items code / documentation wise that can be paced out in step with migration of BRI-1 repos from the provideplatform org to prvd-oasis.