Gougoubi Activate And Stake Risk LP
Use this skill for the combined execution flow: activate first, then add risk LP.
Use This Skill When
- - The user wants to activate a proposal and add risk LP in one run.
- The user wants fixed risk LP per condition.
- The user wants to repair missing activation or missing LP on a small scope.
Do Not Use This Skill When
- - The user only wants result submission. Use
gougoubi-submit-real-results. - The user only wants reward claiming. Use
gougoubi-claim-all-rewards. - The user only wants condition creation. Use
gougoubi-create-condition.
Input
CODEBLOCK0
Defaults:
Pipeline
Step 1: Validate input and resolve proposal.
Step 2: Ensure there are enough usable committee voters. Auto-join committee with minimum stake when required.
Step 3: Enumerate conditions by scope.
Step 4: For each selected condition:
- - If status is
CREATED, vote to activate. - Wait until the condition is
ACTIVE. - Add risk LP exactly once unless the user explicitly asked to top up.
Step 5: Return per-condition activation and LP results.
Checkpoints
- - Do not add LP before the condition is
ACTIVE. - Keep activation failures and LP failures separate.
- Continue past single-condition failures and report them.
Output
CODEBLOCK1
Failure:
CODEBLOCK2
Project Scripts
- - INLINECODE9
- INLINECODE10
- INLINECODE11
Script Entry Points
- - Preferred combined entry: INLINECODE12
- INLINECODE13
- INLINECODE14
- Use
--dry-run before execution when installing or validating this skill in a new environment.
Boundaries
- - Never add LP to an inactive condition.
- Do not top up existing LP unless the user explicitly asks.
- Keep the workflow idempotent where possible.
Gougoubi 激活并质押风险 LP
使用此技能执行组合流程：先激活，再添加风险 LP。
使用此技能的场景
- - 用户希望一次性完成提案激活和添加风险 LP。
- 用户希望每个条件有固定的风险 LP。
- 用户希望在小范围内修复缺失的激活或缺失的 LP。
不使用此技能的场景
- - 用户仅需提交结果。请使用 gougoubi-submit-real-results。
- 用户仅需领取奖励。请使用 gougoubi-claim-all-rewards。
- 用户仅需创建条件。请使用 gougoubi-create-condition。
输入
json
{
proposalAddress: 0x...,
riskLpPerCondition: 100,
scope: all|only-created|single,
conditionIndex: 0
}
默认值：
- - scope=all
- riskLpPerCondition=100
流程
步骤 1：验证输入并解析提案。
步骤 2：确保有足够的可用委员会投票人。必要时以最低质押自动加入委员会。
步骤 3：根据 scope 枚举条件。
步骤 4：对于每个选中的条件：
- - 如果状态为 CREATED，投票激活。
- 等待条件变为 ACTIVE。
- 仅添加一次风险 LP，除非用户明确要求追加。
步骤 5：返回每个条件的激活和 LP 结果。
检查点
- - 在条件变为 ACTIVE 之前不要添加 LP。
- 将激活失败和 LP 失败分开处理。
- 跳过单个条件失败并报告。
输出
json
{
ok: true,
proposalAddress: 0x...,
activatedCount: 0,
riskLpAddedCount: 0,
activated: [],
riskLpAdded: [],
activationFailed: [],
riskLpFailed: [],
warnings: [],
nextActions: []
}
失败情况：
json
{
ok: false,
stage: validation|resolve-proposal|join-committee|activate|add-risklp|confirm,
error: reason,
retryable: true
}
项目脚本
- - scripts/pbft-activate-and-add-risklp.mjs
- scripts/pbft-join-and-activate-all-conditions.mjs
- scripts/pbft-add-risk-lp-to-proposal.mjs
脚本入口点
- - 推荐组合入口：scripts/pbft-activate-and-add-risklp.mjs
- node scripts/pbft-activate-and-add-risklp.mjs --help
- node scripts/pbft-activate-and-add-risklp.mjs --dry-run
- 在新环境中安装或验证此技能时，执行前请使用 --dry-run。
边界条件
- - 切勿向未激活的条件添加 LP。
- 除非用户明确要求，否则不要追加现有 LP。
- 尽可能保持工作流的幂等性。
