hexmani.ac
+11
LICENSE
+11
LICENSE
···+Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:+1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.+2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.+3. Neither the name of the copyright holder nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+32
README.md
+32
README.md
···+**flenser** is an experimental (unserious) piece of software for storing, managing and synchronizing [DIDs](https://en.wikipedia.org/wiki/Decentralized_identifier) using the [did:plc method](https://github.com/did-method-plc/did-method-plc) across a peer-to-peer network.+the current implementation of the PLC is not meaningfully decentralized, and almost all users on the [AT Protocol](https://atproto.com) network rely on this DID method for their identity. the majority of applications on ATproto currently use [plc.directory](https://web.plc.directory), a service operated by [Bluesky Social PBC](https://bsky.social) entirely in the United States, as a source of truth for PLC documents.+due to its status as the most commonly utilized source for PLC identities, it has become a single source of truth for an identity's status, which allows for the operators to arbitrarily change or delete documents without any recourse from other directory operators. while [a list of invalidated operations](https://github.com/did-method-plc/did-method-plc/blob/main/invalidated-op-log.txt) has been published by the operators, it is manually updated and should be taken with a grain of salt.+while there have been [recent pushes](https://docs.bsky.app/blog/plc-directory-org) to move plc.directory to an independent organization, details are still unknown about how the directory will be operated once transferred to the new organization.+if you would like more info on the issues of the current model, [@merkletr.ee](https://bsky.app/profile/did:plc:ezhjhbzqt32bqprrn6qjlkri) has an [excellent article](https://merkletr.ee/fast) on the state of PLC.+this project will build a new server that will be backwards compatible with the current PLC implementation, however with a peer-to-peer system for synchronizing operations between different nodes and establishing a consensus on the state of the network's collective directory.+the properties of how to establish consensus are not finalized, however a target is to have sub-second latency for large-scale amounts of operations per second with byzantine fault tolerant. the current idea is to expand on a [proof of concept](https://codeberg.org/xormetric/didfastpoc) previously created by [@tentacle.expert](https://bsky.social/profile/did:plc:zvinwh7vy4tjegch2hxvopdd).