See individual commit messages. The general theme is that we are moving to routers having a single exit cluster managed by the smart contract with many different participants rather than many exit clusters in their config each managed by a single organization. Practically it was not easy enough to setup an exit cluster and very few people did. Furthermore they mostly joined the existing Hawk Networks managed exit cluster because they wanted failover roaming and didn't care to change the configuration of the pre-built images.
The exit database smart contract when paired with these new changes will allow easy to easily setup an exit and easily join the list of available exits. In short it matches the way we actually use exits rather than the way we thought we might use them years ago.
See individual commit messages. The general theme is that we are moving to routers having a single exit cluster managed by the smart contract with many different participants rather than many exit clusters in their config each managed by a single organization. Practically it was not easy enough to setup an exit cluster and very few people did. Furthermore they mostly joined the existing Hawk Networks managed exit cluster because they wanted failover roaming and didn't care to change the configuration of the pre-built images.
The exit database smart contract when paired with these new changes will allow easy to easily setup an exit and easily join the list of available exits. In short it matches the way we actually use exits rather than the way we thought we might use them years ago.