00:06:51 <br-m> <hinto> > The daemon should generate a symmetric secret on startup. Then have an endpoint where it issues new nonce every single request, returning a MAC-ed message with a challenge, timestamp, deadl
00:06:51 <br-m> <hinto> > ine, and difficulty target.
00:06:51 <br-m> <hinto> @jeffro256:monero.social if the daemon is holding onto these messages until the deadline there would have to be a limit on how many can be held, right?
00:12:55 <br-m> <hinto> Is there anything that prevents other nodes from inserting messages and doing nothing?
02:07:26 <br-m> <jeffro256> @hinto: The daemon wouldn
02:07:47 <br-m> <jeffro256> n't be holding onto the messages, just used nonces