entangled
entangled copied to clipboard
iotaledger
enTangle'd is an amalgamation of all things Tangle
In #82, I provided a very simple URI parser to parse neighbours URI like `tcp://8.8.8.8:4242` or `udp://8.8.8.8:4242` It is working and sufficient for neighbours but maybe we'll run into more...
> Note that except for a few corner-case differences detailed above, WITHOUT ROWID tables and rowid tables work the same. They both generate the same answers given the same SQL...
Especially for cclient, since it's aimed to operate on small devices, some of which might not have `malloc` We should have some stack based way to allocate memory, we could...
`stor_pack` are currently fixed size, they should either be dynamic or replaced by a proper cursor interface to be able to iterate over all query results without being bounded.
> so one way to get rid of this is to have a recursive data structure and occasionally, after say 10 snapshots, merge the last 5 states into 1 (can...
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...
Metadata
Owner
Metadata
enTangle'd is an amalgamation of all things Tangle