Defining features to be implemented
Closed this issue · 3 comments
To support Rosetta API, we need to do the following tasks.
- Porting rosetta-sdk-go to Klaytn (related to duplicate symbol error)
- Porting rosetta-ethereum and modifying it to Klaytn
2-1. library replacement
2-2. Modify the logic for Klaytn
2-3. Modify utilities for Klaytn - Set test environment configuration
3-1. Ready for Dockerizing
3-2. rosetta-cli setting value setting
3-3. Create mock file
3-4. Generating test data for Klaytn
The tasks other than the rosetta API implementation are as follows.
- Modify the license wording
- CI/CD settings
From what I've figured out so far, there doesn't seem to be anything additional to implement in the Klaytn platform source code. However, in the process of implementing the rosetta API, it may be necessary to additionally implement it on the Klaytn platform.
Based on the scope of work listed above, we estimate that the Rosetta API implementation will take around 6 weeks.
cc @aeharvlee
@kjhman21
To support Rosetta API, we need to do the following tasks.
- Porting rosetta-sdk-go to Klaytn (related to duplicate symbol error)
- Porting rosetta-ethereum and modifying it to Klaytn
2-1. library replacement
2-2. Modify the logic for Klaytn
2-3. Modify utilities for Klaytn - Set test environment configuration
3-1. Ready for Dockerizing
3-2. rosetta-cli setting value setting
3-3. Create mock file
3-4. Generating test data for Klaytn
The tasks other than the rosetta API implementation are as follows.
- Modify the license wording
- CI/CD settings
From what I've figured out so far, there doesn't seem to be anything additional to implement in the Klaytn platform source code. However, in the process of implementing the rosetta API, it may be necessary to additionally implement it on the Klaytn platform.
Based on the scope of work listed above, we estimate that the Rosetta API implementation will take around 6 weeks.
cc @aeharvlee
@jimni1222 Nice work. Thanks!