nostr:nprofile1qqsth3eu4eq4qtw667jpzfvxmjh5gg5pp4s25j6hccmue5d8g6c8s3qpz4mhxue69uhk2er9dchxummnw3ezumrpdejqz9mhwden5te0dehhxarj9enx6apwwa5h5tnzd9aqz9rhwden5te0wfjkccte9ejxzmt4wvhxjmcaf8ysx is what signr relates to.

HORNET doesn't interface quite so directly with Nostr and is aimed mainly at creating a replication protocol that allows relays hosting Git repositories to sync with each other... at least, that's my rough understanding of it. nostr:nprofile1qqs9njktmqadt322myw6eag6f8qxuzl0wv9vpe7zxkn0d73fhy3s7qspr3mhxue69uhkummnw3ezumt4w35ku7thv9kxcet59e3k7mgprpmhxue69uhkc6t8dp6xu6twvaex2mrp0yhxxmmdqy08wumn8ghj7mn0wd68yttjv4kxz7fwv3jhyettwfhhxuewd4jsc3t90n and others in the project know more about that side of it, I'm just doing the cryptography/tooling for the Git interfacing.

HORNET will be applicable to Nostr itself, though, since it will enable the compact representation of nostr accounts and the means to selectively synchronise their activity across relays.

I'm not sure exactly where we are at on the timeline, I have only really just joined this and taken on this task because I'm quite comfortable with coding and cryptography systems, hashes and EC signatures.

I am starting on integrating this CLI tool into Git so it can automatically sign commits now.