Contract dupe(5) is okay. We need to fine tune the memory size of the containers.
Measuring deploys → we should measure it internally. Ethereum users will be interested in the number of deploys.
After a successful deploy, the user won't get results back until the block is proposed. Once the block is proposed, the user will see their transaction within a block.
This is a measure of transaction latency
We need to manage stakeholder expectations around the issue of latency and finalization
DECISION - not to include in the deploy demo for test net, and be able to speak to when the question comes up at the conference
Pawel Szulc (Unlicensed): create an integration test for the contract dupe(2) - to ensure correctness for the contracts.
Michael Birch (Unlicensed) add demo wallet contract to Git Hub (Rholang examples). Consider separating so there can be contract for creation separate from the transaction contract