...
| Question | Outcome | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Does creating Contract Wallets cost Phlogiston? | Yes absolutely. Everything costs | ||||||||||
| Do Contract wallets house only a single contract? | Yes - | ||||||||||
| Who pays the Pholgiston in a contract? Sender or receiver? In Ethereum, the sender always pays. | Could be more sophisticated in the future, for mercury - yes only the sender. | ||||||||||
Do we need to consider ETH→ Phlogiston exchange? Or will ETH need to be converted to Rev? | No | ||||||||||
| How much storage is allocated for a default contract wallet? | Yes - we will have provisioning defaults, but we need to be careful. We want to be sensitive to the fact that these resources will cost.
| ||||||||||
| What is the default minimum amount of Phlogiston needed to transact with a contract wallet? Is there a default? | See above. | ||||||||||
| What happens to transactions that run out of Phlogiston? Do they land up on the blockchain? | Throw an exception. For audit purposes, the fact that it threw the error needs to be on the blockchain. Greg doesn't think that ETH records the out of gas error. Our traces become debugging audit logs. If the continuation gets into the Key value store - then the data doesn't get rolled back. User would obtain inforamtion that they needed to add more gas to continue execution. | ||||||||||
Not Doing
- MutliSig contract wallets. - Stretch goal for Mercury - Nice to have. (we need to decide how critical Multi-Sig wallets are for Mercury)
- No 'watch only' wallets - should be easy to do - try to include it.