A product calling requestResourceAllocation([BulletInAllowance]) should ultimately result in a claim_long_term_storage call on People chain
(which then XCMs authorize_account to Bulletin and returns the slotAccountKey to the Host). Today this end-to-end path is not wired: packages/host-container/src/createContainer.ts:435 exposes handleRequestResourceAllocation as a NOT_IMPLEMENTED stub, and nothing in the AP layer (packages/host-papp/) triggers the People-chain claim.
People-chain side of the integration is already in place — see paritytech/individuality#893.
Current Host implementations bypass the v0.2 design entirely:
-
useragent-kit signs Bulletin TransactionStorage.store directly with the well-known //Alice dev key — see
crates/host-chain/src/bulletin.rs:55–84 (submit_preimage_at —
queries Alice's nonce at line 64, builds the Alice-signed extrinsic via
build_bulletin_store_extrinsic where the Alice mini-secret is
hardcoded). The entry point submit_preimage_testnet flags this
as "intended for testnet/headless provisioning only. Production hosts should route through a real wallet or service account policy."
-
dotli never overrides handleRequestResourceAllocation at all — it uses the legacy v0.1 handlePreimageSubmit path at
packages/ui/src/container.ts:706, which calls
submitPreimageTransaction(value, getTestSigner()). getTestSigner
hardcodes //Alice with a TODO: "Replace with production signer (People chain XCM authorization + unsigned submission). For testing on Paseo, Alice's account is pre-authorized via
authorize_account."
Note: this gap was identified via a Claude-assisted cross-repo analysis across the products constellation — truapi, triangle-js-sdks, useragent-kit, dotli, dotns / dotns-sdk, playground-cli / playground-app / host-playground / host-api-test-sdk, triangle-e2e, individuality, polkadot-bulletin-chain.
A product calling
requestResourceAllocation([BulletInAllowance])should ultimately result in aclaim_long_term_storagecall on People chain(which then XCMs
authorize_accountto Bulletin and returns theslotAccountKeyto the Host). Today this end-to-end path is not wired:packages/host-container/src/createContainer.ts:435exposeshandleRequestResourceAllocationas aNOT_IMPLEMENTEDstub, and nothing in the AP layer (packages/host-papp/) triggers the People-chain claim.People-chain side of the integration is already in place — see paritytech/individuality#893.
Current Host implementations bypass the v0.2 design entirely:
useragent-kitsigns BulletinTransactionStorage.storedirectly with the well-known//Alicedev key — seecrates/host-chain/src/bulletin.rs:55–84(submit_preimage_at—queries Alice's nonce at line 64, builds the Alice-signed extrinsic via
build_bulletin_store_extrinsicwhere the Alice mini-secret ishardcoded). The entry point
submit_preimage_testnetflags thisas "intended for testnet/headless provisioning only. Production hosts should route through a real wallet or service account policy."
dotlinever overrideshandleRequestResourceAllocationat all — it uses the legacy v0.1handlePreimageSubmitpath atpackages/ui/src/container.ts:706, which callssubmitPreimageTransaction(value, getTestSigner()).getTestSignerhardcodes
//Alicewith a TODO: "Replace with production signer (People chain XCM authorization + unsigned submission). For testing on Paseo, Alice's account is pre-authorized viaauthorize_account."
Note: this gap was identified via a Claude-assisted cross-repo analysis across the products constellation —
truapi,triangle-js-sdks,useragent-kit,dotli,dotns/dotns-sdk,playground-cli/playground-app/host-playground/host-api-test-sdk,triangle-e2e,individuality,polkadot-bulletin-chain.