search

holochain-open-dev / holoom

Tools for weaving blockchain data into holochain
2 stars 1 forks source link

Make trusted authors configurable at runtime #31

Closed 8e8b2c closed 4 weeks ago

8e8b2c commented 2 months ago

Currently the network specifies a singular respected oracle at genesis via dna props. This needed be the case, since the views of all the attested data within the network could have the opportunity to state which authors they respect.

8e8b2c commented 2 months ago

Aside, this will greatly simplify the deployment process because the lair-keystore won't have to exist before the network. Furthermore this would allow old authorities to retire, and new ones to join.

8e8b2c commented 2 months ago

User story:

A user knows of a set of evm contracts they wish to interact with, that are gated by a particular evm signer. They want to use signing offers that they know to belong to the specified signer. As long as the user is able to access the desired contract transaction, they do not care who the signer decided to trust in order to legitimise it. (They may still want to see who is trusted out of curiosity, but ultimately since is the signer who has the final word, it for the signer to specify who they trust.)

Setup:

A frontend is configured to list rainlang contracts gated by particular signer(s), alongside the signing offer counterparts. (The signer's offers in effect specify the entry node of relevant trust graphs.) To make it convenient for signing offers to be fetched in a manner that satisfies the user that they are genuine offers for the relevant signer, offers could be linked against the signers evm address, with a validation rule that checks for an evm signature to ensure the creator of the offer wasn't made bad some other malicious agent.