# R&D Summit Lisbon 2022 Agenda
Link to video in (For Jakub and Luigi):
https://meet.google.com/dix-hjoz-zeg?authuser=0&hs=122&ijlm=1644757693372
Start time 9:00am
## Top Questions
1. What should IOTA look like in 5 years?
> IOTA as the settlement layer
3. How do we do coordicide?
> aBFT DeCoo with Angelo/Wolfgang first, Coordicide piece by piece, project Nova is the first piece, a dep. graph will be created soon :tm: to define what will be implemented soon in the existing node software (iterative development on top of Hornet/Bee). TIPs will be defined for these features. aBFT will buy us time to finish the GoShimmer prototype.
5. How do we solve the shared security problem?
> We agree l1 validators need to validate root committee as well, We agree rollbacks on L1. There are possibilities (current best guess is implementing enforced expiration feature to alias governer, can be a iterative protocol upgrade so we don't need it in Stardust) but needs way more discussions. We need more involvement
7. What actions do we need to take today?
> aBFT, Assembly additional eyes, Angelo kicked out of GoShimmer -> ISCP, dep. graph for Coordicide, incentives/UX needs to be looked at for Coordicide. Mana5 as access mana needs to be investigated. Have to see who still uses Chronicle and requirements, what would be a suitable replacement. ZK workgroup forming, feeless narative sync with comms. Ganache like tool/docs needs to be created. Narrative private tangles (only for dev, not deployment, no support). Stronghold narrative. Investigate node plugin setup for plugins that work in both Hornet and Bee (gRPC/mqtt). PoI stardust. Get rid of NFT booster narrative and adjust/kill NFT drop. Staking UTXO TIP. Communicate Shimmer narrative (staging network, no feature drift), discuss with board to not announce things before a bigger group of engineers/researchers approve. Firefly plan for token migration Shimmer, protocol upgrade TIP. Streams/Identity follow up session to align if it still makes sense in this form/priority. Any product build needs to at least conform to one of the four basic principles of a DLT (see "Why use a DLT" below, ask Billy if needed), create manifesto for R/E core principles.
### Why use a DLT
- Proof of the current state | Must be on the ledger, probably in an alias
- Proof of mutation of state | Must be on the ledger, probably in an alias | There is a an exception for "add only data bases"
- Proof od existence of data (i.e. PoI) can be in a transaction or message (the latter is cheaper)
- Proof of availability (is this super important? Does it make sense in congestion? Doe streams make sense? Degrades with multiple layers: but it could make sense for a private tangle)
## Not discussed in much detail, needs follow up
- Deprecating old network migration (stopping coo on old network, other centralized form that works with aBFT, sc maybe?) (Follow up by Hornet team, Andrea, Wolfgang, test with Legal and board)
## More specific questions we want answered
- Is the current IOTA 2.0 reasonable?
Yes, but... open questions need to be answered, it needs to be done incrementally and fully specced/with TIPs so they can be implemented in existing node software.
- What problems does IOTA 2.0 solve (how and why is it better than existing approaches)?
Parallel processing, fast confirmation, accessible writing, freedom (like a pizza), because decentralization!!1
- How do we go from IOTA 1.5 to coordicide?
Iteratively through TIPs, implemented in Hornet/Bee after aBFT, on Shimmer first.
- Long term sharding strategy?
Through L2 - Short term ISCP, mid term TangleTrees, long term, let's see...
- Is IOTA as a data protocol ("data on the Tangle") feasible? Going deeper into the data-only use-cases. Revisiting fundamental assumptions and strategic choices for the protocol
Refer to the 4 principles of DLT
- revisiting "feeless" narrative
Token provides access to the settlement layer, should be communicated/corrected.
- analysis of validator incentives: why would somebody run a node?
Provides (write) access to the network, mana rewards
- How projects across the board align with our vision? What projects should be repurposed / dropped? Commonality of intents.
See action points above, existing projects need to be tested with the 4 principles of DLT
- Why should folks hold IOTA tokens?
To gain access to the network/constrained resources of the DLT
- Why should anyone use the IOTA network?
The 4 principles of Coordicide,
Parallel processing, fast confirmation, accessible writing, freedom (like a pizza), because decentralization!!1
# Detailed agenda
Time indications are max. time allocated per subject, main focus on introductions and explainations + decision making where we can. If we need more time we should schedule follow up sessions for after the summit with the people that should be part of that conversation.
## Premeeting Discusission Topics
Week before the summit to prepare for the conversation topics:
- Design Principles of Coordicide (Billy) (Monday)
- State of coordicide (Andrea + Jonas) (Tuesday)
- State of Smart contract and assembly (Dave/Evaldas) (Wednesday)
- View from MA (Thursday)
- The state of Stardust (Levi, confirmed) (Friday)
## Day 1: Where do you see yourself in 5 years from now?
- Morning:
- R&D Vision discussion and sync (https://hackmd.io/4QZeP-ipTQS_tQ-S5Z-RqA), where do we see ourselves in 5 year - 4h (Moderated by Dave)
- Afternoon:
- How are peple going to use the tangle: what is data?
- What are the requirements/assumptions about the protocol
- Feelessness
- Beer:
- You like DAGs?
- Incentives for running a node
- INS?
Deliverables:
- Agreed upon vision document from R&E perspective
- Conclusions from discussions about data on IOTA, feelessness, protocol requirements/assumptions
## Day 2: Coordicide
- Morning
- Discussion: Is IOTA 2.0 reasonable? (Moderated by Jonas and Andrea)
- Afternoon
- DeCoo discussion - 2h (Moderated by Wolfgang)
- The path to Coordicide (Iterative building on top of existing mainnet or a completely seperate release), migration - 2h (Moderated by Luca)
- Beer:
- Long term sharding strategy
Deliverables:
- A step by step plan from now to Coordicide/further on, as agreed upon by consensus (medium future roadmap). Coordicide blocks well defined and sequence of porting them.
- How exactly is the process going to look like?
## Day 3: Smart contracts, other stuff/wrap-up
- Morning:
- ~~Smart contracts: how to approach and work towards solving the shared security problem - 3h (Moderated by Dave)~~
- Shimmer, how to approach (launch plan, staking, inflation, Assembly on Shimmer) - 3h (Moderated by Max)
- Afternoon
- Wrap up: Summary and what do we do now? (Moderated by Dave)
- Beer:
- How to work better together
- R&D community interaction and expectation management
- Re-evaluation of projects, does everything still make sense?
- Streams, Identity, Chronicle, etc
- EBSI
Deliverables:
- Written summary for the IF about this days discussions and wrap-up
- Written down action items coming from the afternoon conversations
# Reading List
- **Consensus in IOTA 2.0:** https://docs.google.com/presentation/d/1_FSL5OL0ERTiX0ADy3G-3icuXrpDwRUnFiSxTens3X4/edit#slide=id.ge5ea09baaf_0_293 (video version https://youtu.be/DfR09NvgSyg)
- **Fast Conflict White Flag and AW based Milestons:** https://docs.google.com/presentation/d/1mYUxHUQ8SylFDD3wkbNlNrsywebXoJVin9oZusoMBmI/edit#slide=id.g11329c94115_0_443
## Premeeting presentations
- **Design principles of Coordicide:** https://docs.google.com/presentation/d/1Fr5pla5ID4VYYE11-OX_O7oQ8lmbfrUTW83y1PXjoIw/edit#slide=id.g10fed621c93_0_508
- **State of Coordicide:** https://docs.google.com/presentation/d/1DNqYKXbfxBEkGVhblA7Yf5PxIiojKwuVJbjsZKfYTOY/edit?usp=sharing ([recording](https://iotafoundation.slack.com/files/UBL39TU2X/F031P42ACLX/2022-02-08_09-03-46.mp4))
- **Stardust presentation** https://docs.google.com/presentation/d/1waxIklP4WawtQrAv8YLUBOSAz1wK6Zf3ZTxX1ECgfoE/edit?usp=sharing
- Read the TIPS! https://github.com/iotaledger/tips/pulls
- **Data Use Cases on IOTA:** https://docs.google.com/presentation/d/1ebHR_vvXBEoBzsUMeAysFsl_c28eGnjpzLbFR7CRP1E/edit#slide=id.g1108f710cdb_0_0