You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Nostr Integration update will bring about full nostr integration into the protocol.
The goal of this update is to increase the censorship resistance of the protocol, by:
1.) Establishing the identity and reputation of the server (which can be staked), and
2.) Decentralizing the delivery of proofs to the server (to eliminate client censorship), and
3.) To broadcast the proofs and attestations of the server (to eliminate server censorship)
The following tasks need to be completed:
The formulas for calculating the cid, acct_id, dpid, and wid hashes must be nostr compatible.
Each of these records must have a nostr-compatible signature issued by the platform.
Each of these records (should) delegate their identity based on the key-rotation of the server.
The Proposal API should include a field for specifying nostr relays.
The Server API should have endpoints for publishing a nostr note for any given record.
The server API should deliver nostr-compatible receipts when submitting statements to the CVM.
Also, research must be done on how to best listen to the nostr network and receive messages in a verifiable way. One idea would be an agreement to poll a certain set of relays at a certain interval, in order to service a contract. The relays would act as an inbox for messages, and an independent source to verify that the messages were received.
This thread is for discussing the nostr integration update. Feel free to ask any questions.
The text was updated successfully, but these errors were encountered:
The Nostr Integration update will bring about full nostr integration into the protocol.
The goal of this update is to increase the censorship resistance of the protocol, by:
1.) Establishing the identity and reputation of the server (which can be staked), and
2.) Decentralizing the delivery of proofs to the server (to eliminate client censorship), and
3.) To broadcast the proofs and attestations of the server (to eliminate server censorship)
The following tasks need to be completed:
cid
,acct_id
,dpid
, andwid
hashes must be nostr compatible.Also, research must be done on how to best
listen
to the nostr network and receive messages in a verifiable way. One idea would be an agreement to poll a certain set of relays at a certain interval, in order to service a contract. The relays would act as an inbox for messages, and an independent source to verify that the messages were received.This thread is for discussing the nostr integration update. Feel free to ask any questions.
The text was updated successfully, but these errors were encountered: