Add notaryd

[ariard]

Rolling the ball forward for #5, added a new civkit-notaryd daemon.

[twshelton]

Will this replace AnchorManager (#5) or will notaryd be called from AnchorManager?

[twshelton]

Confirming my understanding of the process flow in pseudo-code

fn notarize(service_payload) -> NostrEventContent {
2. local_store.append(service_payload)
3. attestation = sign(service_payload) // pre-notification?
4. build_merkle_tree // unclear as to process here
5. if local_store.length() >= x; btcx = create_btc_transaction(local_store);
6. broadcast(btcx);
7. return NostrEventContent(attestation);
}

[ariard]

I think the flow is mostly correct with the following feedback:
4. I don’t know yet if the attestation will be committed with a merkle tree or pay-to-contract (i’m thinking to start to standardize bitcoin notarization with bips or something equivalent to have inter-operability of attestations)
5. rather to have create_btc_transaction committed on the size of the store, X should be a time point (block height or unix epoch) though obviously we might have to flush when the store is full before X

[ariard]

Will this replace AnchorManager (#5) or will notaryd be called from AnchorManager?

I’m thinking yes, like notaryd is some boilerplate code to have an AnchorManager (or AttestationManager) receiving the payload and submitting the scriptpubkey to transaction builder.

If you have more feedback, I can address it, otherwise I’m thinking to land #61.

[twshelton]

I agree. Let's land #61 and get the rest of it flushed out.