- Get Started
- Framework
- Get Started
- Framework
Service Proofs as Edge Attributes
Service proofs verify that a transaction has been successfully completed between a buyer and a provider. In the Local Protocol, these proofs can take the form of pin exchanges, location proofs, or other evidence of service completion. Service proofs enhance the reliability of the transaction graph, ensuring that rewards are allocated for users performing real transactions and not fake transactions.
When available, service proofs can be integrated into the graph value calculation, increasing the weight of the corresponding edge for the transaction, making it more valuable to the network.
Service Proofs in the Adjacency Matrix
Each edge in the graph has a weight representing the cumulative fees or value from transactions between producer and buyer . When a service proof is available, we adjust the edge weight to reflect the increased confidence in that transaction:
where is the boost provided by the service proof.
Alternatively, in terms of the adjacency matrix , we update the entry:
This adjustment increases the significance of the edge in the calculation of EC.
Impact on Eigenvector Centrality and Rewards
By increasing the weight of the edge , both nodes and receive a higher EC score due to their strengthened connection. This boost is again propagated through the network.
Higher EC scores translate into increased graph values and , which are used to calculate block rewards. Therefore, providing service proofs directly benefits the involved parties and indirectly enhances the trustworthiness of their neighbors.
In the next EC calculation, both and will increase more than they would have without the proof. This results in higher rewards for both parties and increases their attractiveness as transaction partners in the network; transacting with high EC nodes boosts ones own EC.
Key Concepts#
- Transaction Verification: Confirms that services have been provided as agreed.
- Graph Integration: Boosts graph value, aligning rewards with verifiable transactions.
Next Steps#
Next, we discuss why modeling proofs in Local Protocol is more cost effective than opinionated or narrow DePIN architectures, and argue that DePIN requires Local Protocol to unlock new use cases that are limited by the availability or cost of proofs. We do this by modeling proofs as probabilities.