mirror of
https://github.com/vacp2p/roadmap.git
synced 2026-01-10 08:08:06 -05:00
chore: update existing sc commitments and add new ones for Q3 (#177)
This commit is contained in:
r4bbit
@@ -21,8 +21,8 @@ Codex aims to extract all funds related logic of the `MarketPlace` contract into
|
||||
### Review Vault contract
|
||||
|
||||
* fully qualified name: `2025q1-vault-integration:review-vault-contract`
|
||||
* owner:
|
||||
* status: 5%
|
||||
* owner: r4bbit
|
||||
* status: 100%
|
||||
* start-date: 2025/04/01
|
||||
* end-date: 2025/04/15
|
||||
|
||||
|
||||
@@ -1,14 +1,14 @@
|
||||
---
|
||||
title: Formal Verification Tools Research
|
||||
tags:
|
||||
- "2025q2"
|
||||
- "2025q3"
|
||||
- "sc"
|
||||
- "ift"
|
||||
draft: false
|
||||
description: Look into alternative formal verification tools and their integration with the existing smart contracts.
|
||||
---
|
||||
|
||||
`vac:sc:ift:2025q2-fv-tools-research`
|
||||
`vac:sc:ift:2025q3-fv-tools-research`
|
||||
|
||||
Look into alternative formal verification tools and their integration with the existing smart contracts.
|
||||
|
||||
@@ -20,7 +20,7 @@ Look into alternative formal verification tools and their integration with the e
|
||||
|
||||
### Research alternative tools
|
||||
|
||||
* fully qualified name: `2025q2-fv-tools-research:research-alternatives`
|
||||
* fully qualified name: `2025q3-fv-tools-research:research-alternatives`
|
||||
* owner: r4bbit
|
||||
* status: not started
|
||||
* start-date: 2025/04/01
|
||||
90
content/sc/ift/2025q3-sc-learnup-sessions.md
Normal file
90
content/sc/ift/2025q3-sc-learnup-sessions.md
Normal file
@@ -0,0 +1,90 @@
|
||||
---
|
||||
title: Smart Contracts LearnUp Sessions
|
||||
tags:
|
||||
- "2025q3"
|
||||
- "sc"
|
||||
- "ift"
|
||||
draft: false
|
||||
description: Monthly learn up sessions about anything smart contracts related.
|
||||
---
|
||||
|
||||
`vac:sc:ift:2025q3-sc-learnup-sessions`
|
||||
|
||||
Monthly learn up sessions about smart contract development, protocols, security and alike.
|
||||
|
||||
## Description
|
||||
|
||||
The smart contract service unit is running a monthly learn up session about protocols,
|
||||
Ethereum Improvement Proposals (EIPs) and similar topics related to smart contract development and security.
|
||||
The goal is to learn more about the Ethereum ecosystem and to discuss the presented topics with the team and anyone else who wants to join.
|
||||
|
||||
By organizing these presentations and having discussions that are open to the entire IFT organization,
|
||||
the smart contracts team fosters a culture of knowledge sharing and continuous learning across teams,
|
||||
improving cross-project collaboration.
|
||||
|
||||
## Task List
|
||||
|
||||
### Smart Contracts LearnUp Sessions 2025 Q3
|
||||
|
||||
* fully qualified name: `2025q3-sc-learnup-sessions:2025q3`
|
||||
* owner: r4bbit
|
||||
* status: not started
|
||||
* start-date: 2025/07/01
|
||||
* end-date: 2025/09/30
|
||||
|
||||
#### Description
|
||||
|
||||
Organize learn up session on a monthly basis and ensure meetings are recorded and provided to the IFT.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- [ ] Recording of the sessions
|
||||
|
||||
### SC LearnUp Session 2025/07
|
||||
|
||||
* fully qualified name: `2025q3-sc-learnup-sessions:2025-07`
|
||||
* owner: r4bbit
|
||||
* status: not started
|
||||
* start-date: 2025/07/01
|
||||
* end-date: 2025/07/31
|
||||
|
||||
#### Description
|
||||
|
||||
Run a learn up session about topic of choice related to smart contract development to present and discuss with the team.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- [ ] Recording of the session
|
||||
|
||||
### SC LearnUp Session 2025/08
|
||||
|
||||
* fully qualified name: `2025q3-sc-learnup-sessions:2025-08`
|
||||
* owner: r4bbit
|
||||
* status: not started
|
||||
* start-date: 2025/08/01
|
||||
* end-date: 2025/08/31
|
||||
|
||||
#### Description
|
||||
|
||||
Run a learn up session about topic of choice related to smart contract development to present and discuss with the team.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- [ ] Recording of the session
|
||||
|
||||
### SC LearnUp Session 2025/09
|
||||
|
||||
* fully qualified name: `2025q3-sc-learnup-sessions:2025-09`
|
||||
* owner: r4bbit
|
||||
* status: not started
|
||||
* start-date: 2025/09/01
|
||||
* end-date: 2025/09/30
|
||||
|
||||
#### Description
|
||||
|
||||
Run a learn up session about topic of choice related to smart contract development to present and discuss with the team.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- [ ] Recording of the session
|
||||
|
||||
29
content/sc/ift/2025q3-security-audits.md
Normal file
29
content/sc/ift/2025q3-security-audits.md
Normal file
@@ -0,0 +1,29 @@
|
||||
---
|
||||
title: Security Audits
|
||||
tags:
|
||||
- "2025q3"
|
||||
- "sc"
|
||||
- "ift"
|
||||
draft: false
|
||||
description: Participating in security audit contests to get better at building secure applications.
|
||||
---
|
||||
|
||||
`vac:sc:ift:2025q3-security-audits`
|
||||
|
||||
Participating in security audit contests to get better at building secure applications.
|
||||
|
||||
## Description
|
||||
|
||||
In the long-term,
|
||||
we want to be able to conduct security audits in-house for both,
|
||||
IFT projects and third-party projects.
|
||||
To get there,
|
||||
we need to practice and learn from the best.
|
||||
We aim for participating in one security audit contest this quarter,
|
||||
if the circumstances allow it.
|
||||
Urgent work related to IFT projects take precedence over this.
|
||||
|
||||
## Task List
|
||||
|
||||
List of security audits and contests the team participated in.
|
||||
|
||||
@@ -5,15 +5,44 @@ tags:
|
||||
- vac
|
||||
---
|
||||
|
||||
|
||||
## Possible commitments for Q4 and beyond
|
||||
|
||||
- Karma token airdrop via ENS name
|
||||
- EIP collaboration with finance (vaults with advanced access control)
|
||||
- SN L2 native bridge yield extension deployment on testnet/mainnet
|
||||
|
||||
|
||||
## 2025q3 `vac:sc:`
|
||||
---
|
||||
|
||||
### `ift:`
|
||||
|
||||
- [ ] [[sc/ift/2025q3-sc-learnup-sessions]]
|
||||
- [ ] [[sc/ift/2025q3-fv-tools-research]]
|
||||
- [ ] [[sc/ift/2025q3-security-audits]]
|
||||
|
||||
### `status:`
|
||||
|
||||
- [ ] [[sc/status/2025q3-consulting]]
|
||||
- [ ] [[sc/status/2025q3-maintaining-status-contracts]]
|
||||
|
||||
### `status-l2:`
|
||||
|
||||
- [ ] [[sc/status-l2/2025q3-native-bridge-eth-yield-management]]
|
||||
- [ ] [[sc/status-l2/2025q3-native-bridge-dai-yield-management]]
|
||||
|
||||
|
||||
## 2025q2 `vac:sc:`
|
||||
---
|
||||
|
||||
### `ift:`
|
||||
|
||||
- [ ] [[sc/ift/2025q2-sc-learnup-sessions]]
|
||||
- [ ] [[sc/ift/2025q2-security-audits]]
|
||||
- [ ] [[sc/ift/2025q2-fv-tools-research]]
|
||||
|
||||
### `status:`
|
||||
|
||||
- [ ] [[sc/status/2025q2-sn-native-bridge-yield-bearing-module]]
|
||||
- [ ] [[sc/status/2025q2-sn-native-dex]]
|
||||
- [ ] [[sc/status/2025q2-maintaining-status-contracts]]
|
||||
|
||||
@@ -0,0 +1,56 @@
|
||||
---
|
||||
title: SN L2 Bridge DAI Yield Management
|
||||
tags:
|
||||
- "2025q3"
|
||||
- "sc"
|
||||
- "status-l2"
|
||||
draft: false
|
||||
description: Implement yield generation in the Status Network native bridge for bridged DAI.
|
||||
---
|
||||
|
||||
`vac:sc:status-l2:2025q3-native-bridge-dai-yield-management`
|
||||
|
||||
Implement yield generation in the Status Network native bridge for bridged DAI.
|
||||
|
||||
## Description
|
||||
|
||||
Once ETH yield management is implemented and working,
|
||||
the next step is to implement yield generation for bridged DAI.
|
||||
This commitment is about implementing yield generation for bridged DAI using the DSR module of MakerDAO.
|
||||
|
||||
|
||||
## Task List
|
||||
|
||||
|
||||
### DSR integration
|
||||
* fully qualified name: `2025q3-native-bridge-eth-yield-management:dsr-integration`
|
||||
* owner:
|
||||
* status:
|
||||
* start-date: 2025/07/01
|
||||
* end-date: 2025/07/30
|
||||
|
||||
#### Description
|
||||
|
||||
We've implemented the necessary abstractions and proxies to allow for yield generation in the native bridge.
|
||||
The next step is to integrate the DSR protocol as a yield provider for the bridge.
|
||||
Part of this task is implementing deposits and withdrawals via the bridge.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- [ ] Commits/PRs that implement and integrate the DAI yield provider
|
||||
- [ ] Tests that verify the functionality of the DAI yield provider integration
|
||||
|
||||
### Yield distribution
|
||||
* fully qualified name: `2025q3-native-bridge-dai-yield-management:yield-distribution`
|
||||
* owner:
|
||||
* status:
|
||||
* start-date: 2025/07/01
|
||||
* end-date: 2025/07/30
|
||||
|
||||
#### Description
|
||||
|
||||
Implement the necessary changes to send and distribute the generated yield to the splitter contract on Status Network.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- [ ] Commits/PRs that implement the yield distribution logic
|
||||
@@ -0,0 +1,57 @@
|
||||
---
|
||||
title: SN L2 Bridge ETH Yield Management
|
||||
tags:
|
||||
- "2025q3"
|
||||
- "sc"
|
||||
- "status-l2"
|
||||
draft: false
|
||||
description: Implement yield generation in the Status Network native bridge for bridged ETH.
|
||||
---
|
||||
|
||||
`vac:sc:status-l2:2025q3-native-bridge-eth-yield-management`
|
||||
|
||||
Implement yield generation in the Status Network native bridge for bridged ETH.
|
||||
|
||||
## Description
|
||||
|
||||
After laying the groundwork for yield generation in the Status Network native bridge,
|
||||
the next step is to leverage the existing architecture to implement yield generation for bridged ETH.
|
||||
This commitment is about implementing yield generation for bridged ETH using the Lido protocol.
|
||||
|
||||
|
||||
## Task List
|
||||
|
||||
|
||||
### Lido integration
|
||||
* fully qualified name: `2025q3-native-bridge-eth-yield-management:lido-integration`
|
||||
* owner:
|
||||
* status:
|
||||
* start-date: 2025/07/01
|
||||
* end-date: 2025/07/30
|
||||
|
||||
#### Description
|
||||
|
||||
We've implemented the necessary abstractions and proxies to allow for yield generation in the native bridge.
|
||||
The next step is to integrate the Lido protocol as a yield provider for the bridge.
|
||||
Part of this task is implementing deposits and withdrawals via the bridge.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- [ ] Commits/PRs that implement and integrate the Lido yield provider
|
||||
- [ ] Tests that verify the functionality of the Lido yield provider integration
|
||||
|
||||
### Yield distribution
|
||||
* fully qualified name: `2025q3-native-bridge-eth-yield-management:yield-distribution`
|
||||
* owner:
|
||||
* status:
|
||||
* start-date: 2025/07/01
|
||||
* end-date: 2025/07/30
|
||||
|
||||
#### Description
|
||||
|
||||
Implement the necessary changes to send and distribute the generated yield to a splitter contract on Status Network.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- [ ] Commits/PRs that implement the yield distribution logic
|
||||
|
||||
@@ -31,7 +31,7 @@ another contract has to be deployed that provides the necessary data.
|
||||
|
||||
* fully qualified name: `2025q2-karma-rln:slash-karma`
|
||||
* owner: r4bbit
|
||||
* status: not started
|
||||
* status: done
|
||||
* start-date: 2025/05/21
|
||||
* end-date: 2025/06/31
|
||||
|
||||
@@ -73,7 +73,7 @@ It should also be possible to add new tiers.
|
||||
|
||||
* fully qualified name: `2025q2-karma-rln:implementation`
|
||||
* owner: Ricardo
|
||||
* status: not started
|
||||
* status: 80%
|
||||
* start-date: 2025/05/21
|
||||
* end-date: 2025/06/31
|
||||
|
||||
|
||||
@@ -8,7 +8,7 @@ draft: false
|
||||
description: Maintain and improve existing Status smart contracts as requested.
|
||||
---
|
||||
|
||||
`vac:sc:status:2025q2-sn-native-bridge-yield-bearing-module`
|
||||
`vac:sc:status:2025q2-maintaining-status-contracts`
|
||||
|
||||
Maintain and improve existing Status smart contracts as requested.
|
||||
|
||||
|
||||
@@ -5,18 +5,21 @@ tags:
|
||||
- "sc"
|
||||
- "status"
|
||||
draft: false
|
||||
description: Implementing a yield-bearing module for the Status Network Native Bridge.
|
||||
description: Design and implement architecture to enable yield generation in the Status Network native bridge.
|
||||
---
|
||||
|
||||
`vac:sc:status:2025q2-sn-native-bridge-yield-bearing-module`
|
||||
|
||||
Implementing a yield-bearing module for the Status Network Native Bridge.
|
||||
Design and implement architecture to enable yield generation in the Status Network native bridge.
|
||||
|
||||
## Description
|
||||
|
||||
The native bridge of Status Network needs to be extended by a module that allows for generating yield on the bridged assets.
|
||||
The general idea is that users lock their assets in the L1 bridge contract and the bridge module deposits them to yield-bearing protocols.
|
||||
The yield is regularly harvested and distributed on the L2.
|
||||
The native bridge of Status Network needs to be extended,
|
||||
such that it allows for generating yield on the bridged assets.
|
||||
The general idea is that users lock their assets in the L1 bridge contract and the bridge deposits them to yield-bearing protocols.
|
||||
The yield is then regularly harvested and distributed on the L2.
|
||||
This commitment is about laying the groundwork for this feature,
|
||||
by designing and implementing the necessary interfaces and base contracts.
|
||||
|
||||
## Task List
|
||||
|
||||
@@ -24,42 +27,41 @@ The yield is regularly harvested and distributed on the L2.
|
||||
### Research and Design
|
||||
* fully qualified name: `2025q2-sn-native-bridge-yield-bearing-module:research-design`
|
||||
* owner: r4bbit
|
||||
* status: 60%
|
||||
* status: done
|
||||
* start-date: 2025/04/01
|
||||
* end-date: 2025/04/30
|
||||
|
||||
#### Description
|
||||
|
||||
This task is about researching the existing bridge protocol to get a better understanding of how it works and how the yield-bearing module can be integrated.
|
||||
In addition, we need to discuss with Linea if they want to implement the "modularity" of the bridge themselves,
|
||||
or if that should also be done by us.
|
||||
The goal is to have a clear plan on how to implement the yield-bearing module.
|
||||
This task is about researching the existing bridge protocol to get a better understanding of how it works and how it can and should be extended to allow for yield generation.
|
||||
In addition,
|
||||
we need to collaborate with the Linea team to understand what their requirements are.
|
||||
The goal is to have a clear plan on how to implement the fundamental architecture.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- [ ] Design document explaining how the yield-bearing module will be integrated into the bridge protocol
|
||||
|
||||
### Module implementation
|
||||
### Fundamental Architecture Implementation
|
||||
|
||||
* fully qualified name: `2025q2-sn-native-bridge-yield-bearing-module:implementation`
|
||||
* owner:
|
||||
* owner: andrea
|
||||
* status: not started
|
||||
* start-date: 2025/05/01
|
||||
* end-date: 2025/05/30
|
||||
|
||||
#### Description
|
||||
|
||||
After we've created a proper plan on how to implement the module extension for the bridge,
|
||||
After we've created a proper plan on how to implement the basic architecture and interfaces,
|
||||
the next step is to actually implement it.
|
||||
Here it's important that the module will be implemented upstream in the linea mono repository.
|
||||
Testing and verification of its functionality is also part of this task and will happen in that repository as well.
|
||||
Testing and verification of its functionality is also part of this task and will happen as the fundamentals are implemented.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- [ ] Yield-bearing module implementation (link to PR in Linea mono repository)
|
||||
- [ ] Implementation of agreed architecture and interfaces for eth bridging
|
||||
|
||||
### Status Networtk Testnet Deployment
|
||||
* fully qualified name: `2025q2-sn-native-bridge-yield-bearing-module:testnet-deployment`
|
||||
### Status Networtk Devnet Deployment
|
||||
* fully qualified name: `2025q2-sn-native-bridge-yield-bearing-module:devnet-deployment`
|
||||
* owner:
|
||||
* status: not started
|
||||
* start-date: 2025/06/01
|
||||
@@ -67,22 +69,9 @@ Testing and verification of its functionality is also part of this task and will
|
||||
|
||||
#### Description
|
||||
|
||||
Once the module is implemented, we will deploy it on the Status Network testnet for further testing.
|
||||
Once the fundamental architecture is implemented, we will deploy it on the Status Network devnet for further testing.
|
||||
We should spend a significant amount of time testing the module with other team members to ensure that it works as expected.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- [ ] Deployment of the module on Status Network testnet
|
||||
|
||||
### Status Networtk Mainnet Deployment
|
||||
* fully qualified name: `2025q2-sn-native-bridge-yield-bearing-module:mainnet-deployment`
|
||||
* owner:
|
||||
* status: not started
|
||||
* start-date: 2025/06/31
|
||||
* end-date: 2025/06/31
|
||||
|
||||
#### Description
|
||||
|
||||
After successful testing on the testnet, we will deploy the yield-bearing module on the Status Network mainnet.
|
||||
|
||||
- [ ] Deployment of the module on Status Network mainnet
|
||||
- [ ] Deployment of base architecture on Status Network devnet
|
||||
|
||||
@@ -12,6 +12,9 @@ description: Implementing a native DEX for the Status Network.
|
||||
|
||||
Implementing a native DEX for the Status Network.
|
||||
|
||||
**This commitment has been removed. The Status Network team has decided to outsource the work to a 3rd party team.**
|
||||
|
||||
|
||||
## Description
|
||||
|
||||
The Status Network needs a decentralized exchange (DEX) to allow users to trade tokens in a trustless manner.
|
||||
|
||||
33
content/sc/status/2025q3-maintaining-status-contracts.md
Normal file
33
content/sc/status/2025q3-maintaining-status-contracts.md
Normal file
@@ -0,0 +1,33 @@
|
||||
---
|
||||
title: Maintainin existing Status smart contracts
|
||||
tags:
|
||||
- "2025q3"
|
||||
- "sc"
|
||||
- "status"
|
||||
draft: false
|
||||
description: Maintain and improve existing Status smart contracts as requested.
|
||||
---
|
||||
|
||||
`vac:sc:status:2025q3-maintaining-status-contracts`
|
||||
|
||||
Maintain and improve existing Status smart contracts as requested.
|
||||
|
||||
## Description
|
||||
|
||||
Smart contracts for Status that have already been implemented and deployed might still need maintenance.
|
||||
This includes upgrading systems or fixing bugs that might be discovered after the contracts have been deployed.
|
||||
|
||||
The Smart Contracts team commits to providing maintenance service for existing smart contracts,
|
||||
such as:
|
||||
|
||||
- Status ENS
|
||||
- Status Communities Contracts
|
||||
- Status Staking Protocol
|
||||
- Status Voting DApp
|
||||
|
||||
## Task List
|
||||
|
||||
There are no concrete tasks associated to this commitment.
|
||||
As requests come in,
|
||||
they will be addressed by our team.
|
||||
|
||||
22
content/sc/status/2025q3-status-consulting.md
Normal file
22
content/sc/status/2025q3-status-consulting.md
Normal file
@@ -0,0 +1,22 @@
|
||||
---
|
||||
title: Status Smart Contracts Consulting
|
||||
tags:
|
||||
- "2025q3"
|
||||
- "sc"
|
||||
- "status"
|
||||
draft: false
|
||||
description: Provide input and feedback related to smart contract solutions.
|
||||
---
|
||||
|
||||
`vac:sc:status:2025q3-status-consulting`
|
||||
|
||||
Provide input and feedback related to smart contract solutions.
|
||||
|
||||
## Description
|
||||
|
||||
The Smart Contracts team will provide consulting services to the Status team on various topics related to smart contract development.
|
||||
|
||||
## Task List
|
||||
|
||||
There are no concrete tasks associated to this commitment.
|
||||
|
||||
Reference in New Issue
Block a user