Right, but my point was, I should be able to just send something like

    {'continue_conversation_id': 123, 'message': 'another message?'}

Seems like it would be even less work for the LLM host to just check if ID 123 is still in a cache (and if not, load it from a database) than decoding my request and checking cryptographic signatures. Right now the whole conversation history with blobs functions like a really long ID.