Update regarding progress toward January milestones:
Over a dozen unique fields have been mapped to custom types that can be used in creating attestation schemas for events on Potlock. Eight additional schemas have been developed that can be used to reference objects and events during the donation process. We have also begun creating a scoring system to integrate relevant attestations into a trust or impact evaluation algorithm for both individual contributors and projects registered on Potlock.
Hyperfiles Potlock Integration - Main Page
Potlock Impact Evaluation Flow
Potlock Attestation Schemas & Fields
Potlock Impact Scoring System
Potlock Attestation Framework For Impact Evaluation
Attestation schemas are currently being deployed to attestations.near instead of potlock.hyperfiles.near. In the future, schemas may be registered to a fork of socialDB with custom permissions (e.g. to enable optional non-revocability).
Additionally, tremendous progress has been made to complete Near Attestation Service (NAS). This will enable anyone to easily create new schemas and publish attestations with a UX similar to Ethereum Attestation Service.
Hyperfiles is exploring implementations of the attestation primitive that leverage the unique benefits of the Near account model and open social graph. These include collaborative type definition, categorization, and use of types in standardizing references (attestations). Implementing conditional logic on top of attestation schemas traditionally requires independently deployed resolver contracts to validate the content of an attestation before granting a user permission to publish a related object using the schema in question. This makes it hard to deploy schemas with conditional logic and creates a large amount of redundant effort by schema deployers whose needs could be addressed by a basic resolver toolkit to choose from.
Thinking about how to make reusable/composable attestation “schema resolvers”:
- Resolver factory contracts: e.g. allow users to deploy custom “attester resolvers” where users specify an allowlist of accounts that can use a schema they deployed
- BOS feed components that render “attestations” meeting specific conditions (e.g. Near social posts mentioning @Potlock using the hashtag #isMilestone or #isProgress).
We’re developing a suite of reuseable and composable resolver components instead of single-use resolver contracts. The goal is to pre-populate NAS with optional “resolver components” that users can select from and input relevant parameters (e.g. allowlist, deposit required, etc) directly while creating schemas.
On-chain updates have been posted at:
Notable accomplishments include expanding the Hyperfiles type library, Hyperfiles documentation, and improving Near Attestation Service (NAS).