Request For Proposals: Soliciting Engineering Implementation Scopes of Work for CosmWasm implementation on Regen Ledger (Regen Network)
**RFP Context: **
A proposal recommends adopting CosmWasm on Regen Ledger. In anticipation of this vote passing, the Regen BuilderDAO is initiating the process of soliciting scopes of work from engineering teams for this implementation.
_Proposals may submit for some or all of the engineering work. _
Implementation Scope:
Upgrade Regen Network from Cosmos SDK v0.46 to Cosmos SDK v0.50 (via a stepped upgrade of v0.47)
Audit and approve the Cosmos SDK upgrade
Adopt CosmWasm via add x/Wasm
Create bindings to Regen Ledger’s modules
Expected Implementation Timeline:
2-3 months
**Scope of work: Submission requirements **
Proposals must separate CosmosSDK v.050, CosmWasm, and auditing/testing into 3 separate estimates.
Proposals must include a timeline for implementation for each sub-proposal (SDK, CosmWasm, audit, etc.).
Proposals must include a total cost of implementation, not to be exceeded.
Proposals must detail challenges for the implementation, and how they will be addressed.
Proposals must include a single point of contact for discussing the proposal.
Proposals may be submitted by either individuals or entities.
Proposals must describe the functional requirements.
Proposals must describe any assumptions that affect the scope to be implemented.
I will surface questions relating to this RFP as they come up …
Question: What is the order of the upgrade implementation?
Answer: Regen Ledger is on Cosmos SDK v0.46. The Cosmos SDK upgrade is first to SDK v.047, then stepping up into SDK v0.50. After v0.50 is implemented, then CosmWasm will be added.
The RFP review committee is pleased to announce the contractors for the Cosmos SDK 0.50 upgrade and CosmWasm integration of Regen Ledger.
**Community Updates: **
We will post subsequent updates on the timeline and work progress in this discussion, once the engineering work has begun.
Contractor Selection criteria:
The RFP review committee has carefully reviewed all RFP submissions, and has chosen to prioritize submissions where engineering teams:
have an existing or past working relationship with RND’s engineering team and the Regen Ledger codebase
the timeline for completion of the work is expedient
team’s experience with these upgrades on other blockchains
team’s willingness to accept Regen tokens as payment
Engineering team:
Primary engineering scope of work: Robert Zaremba (former RND team member, Cosmos SDK)
Current Challenges, reported by Robert:
I had few problems with peer dependencies and the orm package which is integrated in Regen in “alpha” stage. I don’t think we will get it ready by Feb 12 - there are problems with orm. You are the first chain using it and it’s in alpha stage and there are conflicts with Cosmos SDK v0.47.
code is migrated, need to work on the tests, ecocredits aren’t done yet
tons of duplicated code in the repo makes the work harder - could be simplified and reduced; created problems
ORM challenge - testing - refuses to start because of contract with ORM - discussing with Aaron Craelius how to handle alpha version of ORM; not much development generally around ORM, so there are bigger issues than just this upgrade -choosing to not shift the code; causes conflict with run-time related to protocol buffers with the 0.47 SDK -
two solutions: (1) revise the decision with ORM (previous code decisions) - causes more migration work (2) go from alpha to beta OR fork the code base ; waiting on Aaron to advise before taking actions - expecting next week
code is migrated to 0.47 already
changes needed in how app with run due to this, can get started with the code review
next steps:
start code review
ORM decisions
testing of code library is in progress (simulation tests, etc.)
CosmWasm integration:
changes required are prepared in the branch -configuration, options
CosmWasm will be fast once v0.47 is adopted via governance
Reported some problems to Marco at SDK team:
some SDK code was untested, had to tell Cosmos SDK core team - they have some fixes to deal with regarding migrations
JeanCarlo Updates:
-reading through the code, setting up environments, will provide an assessment of how long the review will take
best guess at v0.47 timeline:
ORM is the outlier, so we can’t provide a clearer estimate until that is resolved; this work isn’t trivial
2 weeks for testing is still the estimate
potentially still a month before an upgrade proposal