Hello again,
I am in the process of building a cryptocurrency trading agent. I have posted some stuff about this before (see here : Marc Goossens - Revolut6).
I have received some criticism about the use of Python script nodes to ‘talk’ to the API.
I would like to have a go at replacing these by KNIME nodes.
But the API insists the messages I send to it are signed by the Ed25519 standard.
I have asked K-AI for help and this is wat it tells me:
KNIME does not have a native node for calculating cryptographic hashes or digital signatures (such as Ed25519) directly. For your use case (Ed25519 signing and base64 encoding), you should use a Python Script node, as this functionality is not available in standard KNIME nodes. …
Does anyone have any brilliant ideas ?
One thing that occurs to me is to ‘build’ a new Node for this, but this is far out of my comfort zone - and my workflow ‘as is’ with the Python nodes does the job.
The key advantage of KNIME is that it allows users (especially those who aren’t programmers) to follow and understand processes in a deterministic way. It also enables them to quickly understand and diagnose problems and identify hallucinatory behaviors.
Visual programming, among other things, allows us to maintain a critical perspective and avoid certain probabilistic biases.
If we draw an analogy with the living world, inbreeding inevitably leads to the degeneration of a species. Probabilities of probabilities lead to the same result (inbreeding), especially when these probabilities are increasingly influenced by economic or even moral considerations.
One idea would be to create a node (a simple and deterministic operation) to generate hashes using different keys as parameters, which are used in cryptocurrency chains. This would allow the community to work on trading agents using different cryptocurrencies and at least remain sovereign.