Andreas C. Osowski
Andreas C. Osowski
Expected result (or similar): ``` >>> iota.TryteString(b'ABABZZDD99').as_bytes() (30, [55,178,248,107,12,0]) ``` Actual result: ``` >>> iota.TryteString(b'ABABZZDD99').as_bytes() Traceback (most recent call last): File "iota.lib.py/iota/codecs.py", line 147, in decode + (self.index[second] * len(self.index))...
(rel #679) At the moment, there is not a global list of static command name strings (e.g. for "attachToTangle"). We should add such a list of static exports to `cclient/serializer/json`...
For PRs, we should have a bot that checks the binary size changes as well. I believe there are some public github projects that have suchs bots running automagically (rust?)
At the moment for absorb/squeeze the caller is required to provide the full input (or output) trit arrays even though we're processing them in chunks of 243 trits at a...
Right now, we are using the reference impl which is rather unoptimised & slow... This issue will mean modifying the buildfile in https://github.com/iotaledger/rules_iota to take toolchain targets into account.
- [ ] cIRI - [ ] tanglescope Do we also want to support Docker? See https://docs.bazel.build/versions/master/be/pkg.html#pkg_tar for context
Provide a configurable (LRU?) cache to cache transactions in memory so we don't have to roundtrip to storage regularly. In general, all transactions should be loaded through this cache -...
_Originally posted by @ifullgaz in https://github.com/iotaledger/entangled/pull/399_
We should develop a set of tests that check whether an implementation of IOTA conforms to the rules. Related: https://en.wikipedia.org/wiki/Technology_Compatibility_Kit As part of this, we'll probably also have to write...