You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
add XCM support to Bulletin Chain (hopefully someone from XCM team could help with that);
decide whether we want to use utility pallet there;
make sure that we only accept bridge transactions from whitelisted relayers;
do not register any rewards at Bulletin Chain, because tokens have no economic value there;
add bridge support to substrate-relay;
prepare something similar to Branislav setup (zombienet + binaries + document) to launch Polkadot + Polkadot Bridge Hub + Bulletin Chain (and another system parachain later) locally.
send some test message directly from Polkadot BH to Bulletin Chain (unless other Polkadot parachain is ready).
Follow up tasks: make actual PRs to Polkadot.BH once it is deployed.
A list of live unresolved problems:
we need to know real dispatch weight of the message. Bulletin chain uses immediate dispatch, so we need to decode the message (and calls) and use XCM weigher for estimating dispatch weight for message delivery transaction (Add bridge dispatcher and exporter zdave-parity/polkadot-bulletin-chain#33).
All development should happen in master and then backported to the polkadot-v.1.0.0-audited branch (and
polkadot-staging
eventually).Tasks that would allow us to test it locally:
decide whether we want to use utility pallet there;substrate-relay
;Follow up tasks: make actual PRs to Polkadot.BH once it is deployed.
A list of live unresolved problems:
The text was updated successfully, but these errors were encountered: