| Time | Item | Who | Notes |
|---|
| Rent for a unit of time → Mercury? | | - During deployment forgeable processes are tagged with a block height for when they 'expire'.
- We process the trace log and mark those produces and consumes that only have forgeable payload - we need this because we are going to disallow sends on forgeable names.
- Plan on computing this in advance that a given payload is forgeable.
|
| 'Proof' of Storage |
| - Owner can post a challenge (key)
|
| Phlogiston for Storage |
| - Second wallet in a deployment for rent.
- Putting a file inside the contract is horribly expensive.
- Deploying a huge contract → pay for storage but not for rent.
- This could encourage everyone to store their contracts as persistent sends. May kill the notion of rent all together.
- This would result in the contract being forgeable and persistent.
|
| Payment of rent/fees for storage |
| - Need to think about what happens with wallets. Is storage for wallets paid up front? Does the wallet pay for it's own storage?
|
| Removal |
|