On Dec 18, 2017, at 1:49 PM, David McClain <dbm@refined-audiometrics.com> wrote:

seems to be a problem with the use of TRANSFER here:

(defun process-coin-server-request (stream)
(let ((request (read stream)))
(case request
(transfer (process-transfer-request (cdr request) stream))
(execute (process-execute-request (cdr request) stream))
(blocks (process-blocks-request (cdr request) stream)))))

Also redefines BLOCK and so we probably need to declare shadowing at the top.

My bad, totally slipped my mind.

Not sure what the quickload stuff was trying to accomplish, but my resident version of Ironclad kept shadowing anything imported by quickload. No SHA3 digest in my resident version, so I replaced it (for now) with the bleeding edge version from GitHub. That worked, as far as I can tell.

Yes, I tend to use the most recent versions of your library, but given it’s crypto library it might be good you upgraded.

Actually had to compile buffer twice in order to get past the TRANSFER error (not sure why that even works?) but the system appears to be hung waiting for some kind of network connection. Perhaps you could give us a usage hint?

My mistake on not doing a clean compile before releasing; most of this was made interactively and I haven’t gotten around to writing a full app target in my LW.