| Time | Item | Who | Notes |
|---|
| Mercury release plan |
| |
| 5 minutes | node-0.7 release plan | | - Concern on the churn on decisions related to economics
- Consensus
- Block storage
- Not yet fully specified(to be completed this sprint)
- Feature to be delivered in RNode v0.8
- Network launch updates will be delivered in RNode v0.8. The work below must be done in RNode v0.7 to support
- Request to ticket exposing time in Rholang
- Expose block height and block timestamp
|
| 10 minutes | nodeRNode-0.8.1 release plan | | - Testnet Faucet
- Idea - Deploy against the faucet to receive TESTREV
- Discussion on how/if to use the faucet related to the incentivized test net
- Storage
- Sister to the name registry. There will be a registry for storing files on-chain.
- Economics
- Mateusz is working on it
- Churn on matching impacts work on this
- Client Interface (
| Jira Legacy |
|---|
| server | System JIRA |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 50130123-f232-3df4-bccb-c16e7d83cd3e |
|---|
| key | CORE-1162 |
|---|
|
)- Discussion on what this is and why it's needed
- Pawel Szulc (Unlicensed) to review and provide feedback early next week.
- Looked at Obtaining Data
- Medha edited Obtaining Data page during the conversation
- Discussion how API #3 is significantly more useful than API #2
- Unbonding
- Can also include slashing
|
| 10 minutes | node-0.9 release plan | | - Sharding client software
- Lazy Validator Hedge
- Governance outcomes - Economics
|
| Discussion about block passing across the network |
| |