c08r4d0r's avatar
c08r4d0r 1 year ago
Thanks for pointing out that small pools benefit from less strict mempool policy @Matt Corallo . I hadn't considered that. Do you think Bitcoin core could benefit from moving the social interactions around the repository to nostr? gitworkshop.dev features nostr based pull request and issue management for instance.

Replies (3)

c08r4d0r's avatar
c08r4d0r 1 year ago
@npub1wnlu28xrq9gv77dkevck6ws4euej4v568rlvn66gf2c428tdrptqq3n3wr after realizing that miners who are too small to receive transactions out of band benefit from a permissive relay policy, I'm starting to wonder if DATUM and StratumV2 are the right tools for node operators to express their opinions rather than mempool policy. Perhaps its time to stop calling our nodes "full nodes" if they aren't producing cost effective hash-rate. Whats your take on this?
c08r4d0r's avatar
c08r4d0r 1 year ago
Absolutely! Gitworkshop.dev has improved a lot since Fabian Jahr last checked it out. I think this is a great opportunity to give it another shot.. View quoted note →
c08r4d0r's avatar c08r4d0r
Thanks for explaining whats going on @npub1s33s...252p ! @Bitcoin Mechanic perhaps this is an opportunity to start using `ngit` for social interactions around the bitcoin core repo. Ngit creates nostr events for commits, pull requests and issues and there is a nostr client (gitworkshop) for interacting with these events. Essentially this nostr client acts as a proxy between you and the git server, so you can continue to share a repo with users who are still doing social interactions on github. @npub15qyd...yejr is maintaining this and it has made tremendous progress since the last time a core dev (Fabian Jahr) tried it out. This controversy could be an opportunity to move away from the network effects on GitHub..
View quoted note →