尚未检测到更新。GitHub 发布版本后会显示在这里。
个人 GitHub 账号下公开仓库的所有者可以登录并验证所有权,自行管理介绍,无需管理员批准。
登录并生成验证文件,在 30 分钟内将其提交到此仓库的默认分支。其他分支或分叉仓库中的文件无效。然后在下方检查文件,即可无需管理员批准直接管理项目。请保留文件以维持管理权限。
如需登录,将前往登录页面。登录后请回到此处,再次点击所选的验证按钮。
在项目文件夹中运行 /nomorevibe verify,即可验证所有权并自行管理介绍。
一分钟完成验证制作者的介绍仅有上面的一句话。 更多详情请阅读仓库 README。 仓库 README ↗
正在加载完整 README。
查看完整 README ↗A single static page for curators of the three Kusama Vision bounties. It fills the child-bounty runbook in from Kusama Asset Hub for whichever bounty and child you select — live state for children that exist, archive state for those that have settled.
→ https://northvanedot.github.io/kusama-vision-bounty-workbench/
Built by a curator of the Proof of Personhood bounty. Not an official Kusama Vision publication.
value and headroom for bounties 0, 1 and 2pallet_multi_asset_bounties::ChildBounty in the live runtime metadataIt never signs, and holds no keys. There is no backend and no wallet connection. Every figure is a chain query you can repeat in Polkadot.js.
Call data is built in-page for the simple calls — increaseValue, checkStatus,
acceptCurator, unassignCurator, retryPayment, closeBounty. The SCALE encoding was
verified byte-for-byte against @polkadot/api output for the same arguments.
fundBounty, fundChildBounty, proposeCurator and awardBounty are deliberately not
built here. They take MultiAddress, H256 and VersionedLocatableAccount arguments —
exactly the argument class the runbook documents an encoding bug for. Build those in Nova Spektr
(the desktop wallet — not Nova Wallet) under Custom operation → Build an operation, or in
Polkadot.js Apps, where the UI encodes them from runtime metadata. That dialog also has a
Paste tab that takes raw call data, so the hex this page emits goes straight in.
Where a call has to go through the parent curator, the page also gives the proxy.proxy
call the multisig submits. Its real argument is a MultiAddress, but only ever the plain
::Id form — a 0x00 tag and the 32-byte curator key the page has just read from chain —
with force_proxy_type set to Governance. Checked byte for byte against @polkadot/api
on runtime 2003002; the page warns if the chain has moved to another runtime.
Steps 2 and 4 list every argument those calls need, ready to copy — the page just won't encode them.
Decode the call data in Polkadot.js Apps → Developer → Extrinsics → Decode and confirm it matches the call and arguments the page displays. The page proposes; Polkadot.js Apps confirms. Do not sign on this tool's word alone.
The page embeds the runbook so it works offline. To regenerate after editing
child-bounty-runbook.md:
python3 build.py
import { ApiPromise, WsProvider } from '@polkadot/api';
const api = await ApiPromise.create({ provider: new WsProvider('wss://kusama-asset-hub-rpc.polkadot.io') });
console.log(api.tx.multiAssetBounties.increaseValue(0, 39990000000000n).method.toHex());
// 0x6209000b009cbee55e24 — compare against what the page emits for the same arguments
console.log(api.tx.proxy.proxy('HfMgvo7Lfuymg9sxii2H747rXdts5be6UfLPp6kXS4cNE9u', 'Governance',
api.tx.multiAssetBounties.closeBounty(0, 0)).method.toHex());
// 0x2a0000e104b438e7893a9f9cbc59e7d057d61a85ed1b88e3a0ebc59733cb89637a5e7c01076206000100000000
pallet-multi-asset-bounties 0.7.0 rust docs
— this is the version Kusama Asset Hub actually runs. The chain reports
spec_version 2003002, which is polkadot-fellows/runtimes v2.3.2, and that release's
Cargo.lock pins pallet-multi-asset-bounties 0.7.0 from crates.io. [T]
Read the version, not just the crate. polkadot-sdk master is already at 1.0.0, and
docs for it are on docs.rs as pezpallet-multi-asset-bounties — a third party's
republish of the newer source. Those docs describe code Kusama is not running yet.
Multi-Asset Bounties Now Live on Westend: Testing and Roadmap — Polkadot Forum, background and roadmap.
This runbook is the failure-mode companion to those: what we hit running the flow on Kusama Asset Hub, not a substitute for the pallet docs.
MIT.