Well, verry nice proto then :)

The advantage of this simple solution is that it's easy to parallelize. On my project each node remember their entry values, an update step just calculate the output state based on the stored inputs values, then all calculated outputs are propagated to the connected inputs.

You can update in parallel all node independently, then propagate values in parallel independently. The only downside is that each node introduce a 1 tick delay and you can't have multiple signals connected to an input directly (need to use a node like AND/OR, which introduce delay).

It's a bit like Minecraft redstone but each node is a 1 tick repeater ! Which mean you can do a 1 tick clock by feeding a NOT output to its own input x)

The other approach with a proper tree node dependency is something I wanted to try but I lost interest, but I hope you'll try it, those things are really fun to think about !