Dincho Todorov

> I have to admit that the concept of preflight allures me - what is the purpose or why do we need it... > > Google says: _GET , POST...

I definitely disagree here. First of all while the dry-run doesn't mutate the node state itself, because ... well .. it's a dry run - it is actually a mutable...

Let's do that before 7.0.0

My general opinion is that the node should not accept a TX if (is known to be) would be then dropped immediately from the pool. I'm not very familiar with...

I agree in general with @ThomasArts as well, however the logic for that validation is already there, but runs on mempool level

I don't think that this is docker specific, this is general UNIX/POSIX process expectations. When you hit CRTL+C you expect the process to stop "immediately" or you (at least me)...

> Turns out that Erlang actually handles SIGTERM these days as equivalent to running init:stop(), so plain `docker stop` will do a clean shutdown. Good to know. I guess the...

Please note: > start interval is the time between health checks during the start period. This option requires Docker Engine version 25.0 or later. That's a bit on the edge...

We use single Dockerfile for now so we can't have an EXPOSE of the port. Documentation can be added indeed in the docker section of the docs.

One more, different field, probably related/same: ``` 2020-03-12T19:37:21.898022983+01:00 ERROR aeternal::loader - Error loading blocks missing field `transactions` stack backtrace: 0: aeternal::middleware_result::MiddlewareError::new at src/middleware_result.rs:14 1: ::from at src/middleware_result.rs:55 2: aeternal::loader::BlockLoader::internal_load_block at...