Might be good to establish some best practices for common blockchain / smart contract scenarios.
- Given that contracts are immutable, how can we release new versions? Maybe using a proxy contract that only points to the latest revision?
- How can we schedule future executions?, Maybe by attaching a reward for whomever executes this contract at a certain date?
- "bit" - easy CLI wallet with commands similar to Git. e.g.,
bit clone <wallet>
,bit add <balance>@<friendwallet>
,bit commit -m "Sending <balance> to <friend>
,bit push
. Important to have lots of autocomplete and help - see Keybase for a good CLI example.
- Rich media for websites that display in exchange for browser mining. e.g., a complex Bloomberg chart embedded in a website that's only displayed after the user contributes a micropayment in the form of processor cycles.