Our Personal Data Server from scratch! tranquil.farm
oauth atproto pds rust postgresql objectstorage fun

Decentralized ledger with did-plc-bft #15

open opened by erlend.sh edited

There’s a wip extension of PLC which aims to make it fully decentralized, called did:plc:bft.

Emerging specification and reference implementation by @gbl08ma.com in progress here: https://tangled.org/gbl08ma.com/didplcbft

PLC implementation isn’t the responsibility of a PDS per se, but it is however up to the PDS implementer to decide whether to support an alternative did-method. I know you tranquil folk like to be on the cutting edge, so I’m putting this issue up for public deliberation.

me and lewis talked about this exact thing in DMs just a bit before @gbl08ma.com posted the most recent update about the project and we are both in agreement that we want to support did methods other than just did:web and did:plc. and specifically that we want to push methods that improve on the status quo over those two (ie. did:webvh, did:plc:bft, a more developed version of xormetrics fastpay inspired poc and whatever other methods people might find it worth while to experiment with)

personally i think it would be nice to eventually (optionally) embed nodes for some of these into tranquil itself but support for making accounts with them will certainly come first and still be a good step.

I just want to clarify that didplcbft is not meant to be a new DID method but instead an alternative way to "interact" with did:plc identifiers, with the (very unlikely) long term possibility of it becoming what did:plc is (pending an update to the did:plc spec so that plc.directory is not the only canonical API endpoint, of course).

Should I get to the point where there's a functioning didplcbft network online (which would still defer authority to plc.directory), then, in principle, all any piece of software will have to do in order to "support didplcbft," is allow for did:plc identities to be resolved/updated through an endpoint other than plc.directory. This is something you might want to support regardless of didplcbft existing: I believe other (non-P2P-based) unofficial PLC mirrors already exist, and it is nice when people can elect to use them.

id argue that plcbft functions differently enough from current plc that it constitutes a new method albeit a plc compatible one that I hope eventually becomes what plc is. but yes i understand its meant to be transparent and act just like any other did:plc server from an API point of view. and i believe we already have support for setting a custom plc server so we're covered there.

i meant more as a general thing we want to look into additional did methods like webvh as well.

plcbft just also represents a significant step in more or less exactly the direction ive wanted plc to take for a while now! so i want tranquil to offer as much support for it as possible. perhaps with a builtin or bundled plcbft node or anything else that might help amass a significant stake in the network.

sign up or login to add to the discussion
Labels

None yet.

assignee

None yet.

Participants 3
AT URI
at://did:plc:ad5bwszsc5m5jpj2sfa6uzjk/sh.tangled.repo.issue/3mdkw2nye6522