The Readme currently states^1 that we will "likely use the transaction-id" as the program-id. But making program-ids deterministic is preferred as it enables programs to exist across multiple chains with the same ID.
While transaction-ids are actually also deterministic, what I'm referring to here is determinism independent of nonce/replay protection, such that a program may be deployed with the same ID no matter how many transactions/actions have been sent by the deployer.
This issue has become stale because it has been open 60 days with no activity. Adding the lifecycle/frozen label will exempt this issue from future lifecycle events.
The Readme currently states^1 that we will "likely use the transaction-id" as the program-id. But making program-ids deterministic is preferred as it enables programs to exist across multiple chains with the same ID.
While transaction-ids are actually also deterministic, what I'm referring to here is determinism independent of nonce/replay protection, such that a program may be deployed with the same ID no matter how many transactions/actions have been sent by the deployer.
How accomplish this is to be determined.