bug: Slow Reconciliation of Paladin Nodes and Zeto On-Chain Orchestration

[onelapahead]

What happened?

Currently its taking 20-30min for the operator to standup the 3 Besu node network, the accompanying Paladin nodes, and then deploy and invoke the various smart contracts necessary for Noto, Zeto, and Pente.

What did you expect to happen?

We would like this to ideally take only 1-2m w/ 5m being an acceptable first improvement if possible.

We want users to have a fast and smooth getting started experience, despite the complexities of the multi-node network and demonstrating programmable privacy.

We also want developers to have an E2E pipeline which allows for faster feedback and iteration times.

How can we reproduce it (as minimally and precisely as possible)?

Follow "Getting Started" or use gradle deploy locally.

Anything else we need to know?

It is believe these are primarily optimizations that need to be made within the Operator, with the exception of the ability to have dynamic reload of registry and domain configuration by Paladin itself. The latter will be treated as a separate issue / body of work, and the Operator will hack around the lack of dynamic reload for now.

OS version

sw_vers
ProductName:		macOS
ProductVersion:		14.4.1
BuildVersion:		23E224