default

That's what I am doing. Removed the folder each attempt as well as `~/.starport`. Tried downgrading to starport `v.0.15.1` and get a slightly different error now. `error while running command...

Hmm, same error :/. ``` XXX@~/go/src/github.com/test-[]$ starport app github.com/test/test error while running command /tmp/nodetime: : exit status 4 ```

Is there potentially any bad cached build state from prior runs that could cause this? I tried removing everything in `~/.starport` and doing a fresh install each time. Also tried...

Only other thing I can think of is my linux distro - I'm running a system76 laptop. They have their own ubuntu based linux distro (pop os).

Will just run in a vanilla ubuntu VM :+1: , thanks for the quick responses guys!

> at a high level i'm super in support of this idea, however I think its prob best as its own spec. If we add this to the relayer incentives...

Ethan talks about the issues generalizing `parity/trie` (also an issue with eth trie) to the ics23 proofing format. https://github.com/confio/ics23/issues/65#issuecomment-1031851018 OTOH, if we continue to use ics23 within 02-client I don't...

Is it correct that `Prefix/Suffix` can be generalized for > 2 child nodes? For example we could support any `N` number of child nodes: ``` prefix = variable length prefix...

For the [base16 modified merkle trie](https://github.com/paritytech/trie) used by parity, each node has up to 16 children. Go `parity/trie` impl [here](https://github.com/ChainSafe/gossamer/tree/development/internal/trie) for reference. It looks like the following would be appended...

Would it make sense to type switch at a higher level over different types of tree structures -> proof types? E.g. generic merkle/verkle etc. Every non generalizable structure could be...