[Feat]: Compile paseo-next-v2 genesis (similar to previewnet)
Nobody has claimed this yet.
- Dominant language
- Solidity
- Stars
- 4
- Forks
- 2
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 24
Description
Component
Other
Priority
P1
Summary
Compile paseo-next-v2 genesis (similar to previewnet)
Background - every wipe needs separate deployment to be executed and that happens async and requires coordination, while people can't use platform until all the stars are aligned - config scripts, dotns deployed, bulletin-deploy updated, domains reclaimed, prototypes redeployed
In order to reduce time b/w Wipe <> Platform usable - one point (dotns deployed) we could solve with pre-compiling the dotns into genesis config and ask devops team to bake it into paseo-next-v2 genesis of AH
Proposal
No response
Acceptance criteria
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the paseo-next-v2 genesis setup with the previewnet configuration, then trace the config scripts and dotns deployment steps mentioned in the issue. Confirm with the DevOps team how dotns should be baked into the genesis and define completion as a wipe producing a usable platform without a separate dotns deployment.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- solidity
- Domain
- blockchain, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100