[GUEST ACCESS MODE: Data is scrambled or limited to provide examples. Make requests using your API key to unlock full data. Check https://lunarcrush.ai/auth for authentication information.] #  @polk_gov Polkassembly Polkassembly posts on X about to the, kindly, xcm, payout the most. They currently have XXXXX followers and XXX posts still getting attention that total XXX engagements in the last XX hours. ### Engagements: XXX [#](/creator/twitter::1467468062236430338/interactions)  - X Week XXXXX +540% - X Month XXXXXX -XX% - X Months XXXXXXX +77% - X Year XXXXXXX +414% ### Mentions: X [#](/creator/twitter::1467468062236430338/posts_active)  - X Months XXX +100% - X Year XXX +63% ### Followers: XXXXX [#](/creator/twitter::1467468062236430338/followers)  - X Week XXXXX +2.90% - X Month XXXXX +17% - X Months XXXXX +28% - X Year XXXXX +200% ### CreatorRank: XXXXXXXXX [#](/creator/twitter::1467468062236430338/influencer_rank)  ### Social Influence **Social topic influence** [to the](/topic/to-the), [kindly](/topic/kindly), [xcm](/topic/xcm), [payout](/topic/payout) **Top accounts mentioned or mentioned by** [@polkadot](/creator/undefined) [@polkgov](/creator/undefined) [@kusamanetwork](/creator/undefined) [@web3foundation](/creator/undefined) [@gavofyork](/creator/undefined) [@drw3rk](/creator/undefined) [@bifrost](/creator/undefined) [@playmythical](/creator/undefined) [@moonbeamnetwork](/creator/undefined) [@polkadex](/creator/undefined) [@cerenetwork](/creator/undefined) [@pendulumchain](/creator/undefined) [@gldncalf](/creator/undefined) [@billlaboon](/creator/undefined) [@filippoweb3](/creator/undefined) [@polkadotinsider](/creator/undefined) [@paritytech](/creator/undefined) [@lolmcshizz](/creator/undefined) [@chaosdao](/creator/undefined) [@hydradx](/creator/undefined) ### Top Social Posts Top posts by engagements in the last XX hours "⚠Urgent: Following the AssetHub migration a few of treasury.spend proposals: #1798 #1796 #1794 #1793 #1790 #1788 #1806 were affected by a one-time XCM compatibility issue. We apologise to the teams impacted and are reaching out to coordinate resolution. These proposals may need to be re-submitted; we kindly ask the community to support them again. Full details:" [X Link](https://x.com/polk_gov/status/1998033477703491848) 2025-12-08T14:14Z 9165 followers, 10.6K engagements "To clarify: these proposals weren't created during the migration itself. The issue is that the XCM V3V4 upgrade changed how treasury.spend parameters must be structured. OpenGov treasury proposals have a 28-day decision period before execution. So proposals created shortly after migration only reached execution phase weeks later when the version mismatch became apparent. We sincerely apologise for the inconvenience caused here and are actively working with the affected teams directly to implement the needed" [X Link](https://x.com/polk_gov/status/1998278726166163500) 2025-12-09T06:29Z 9162 followers, XXX engagements "The move to XCM v4 happened earlier and that part is already stable. What surfaced now was a one time compatibility edge case triggered specifically by the AssetHub migration not an ongoing version issue. A few of the proposals created during the transition window ended up with mixed V3 and V4 parameters that only failed at execution time on the migrated runtime. We have fully corrected the pre-image generation logic and reached out to all affected teams" [X Link](https://x.com/polk_gov/status/1998279375423410523) 2025-12-09T06:31Z 9156 followers, XXX engagements "Critical Update: The treasury payout issue has been identified as a runtime-level gap in XCM version handling. The Polkadot Fellowship is working on a fix expected late December. Affected proposals won't need resubmission. Payouts will be claimable once the upgrade is enacted. Details:" [X Link](https://x.com/polk_gov/status/1998433810250334565) 2025-12-09T16:45Z 9174 followers, 8137 engagements
[GUEST ACCESS MODE: Data is scrambled or limited to provide examples. Make requests using your API key to unlock full data. Check https://lunarcrush.ai/auth for authentication information.]
@polk_gov Polkassembly
Polkassembly posts on X about to the, kindly, xcm, payout the most. They currently have XXXXX followers and XXX posts still getting attention that total XXX engagements in the last XX hours.
Engagements: XXX #
- X Week XXXXX +540%
- X Month XXXXXX -XX%
- X Months XXXXXXX +77%
- X Year XXXXXXX +414%
Mentions: X #
- X Months XXX +100%
- X Year XXX +63%
Followers: XXXXX #
- X Week XXXXX +2.90%
- X Month XXXXX +17%
- X Months XXXXX +28%
- X Year XXXXX +200%
CreatorRank: XXXXXXXXX #
Social Influence
Social topic influence to the, kindly, xcm, payout
Top accounts mentioned or mentioned by @polkadot @polkgov @kusamanetwork @web3foundation @gavofyork @drw3rk @bifrost @playmythical @moonbeamnetwork @polkadex @cerenetwork @pendulumchain @gldncalf @billlaboon @filippoweb3 @polkadotinsider @paritytech @lolmcshizz @chaosdao @hydradx
Top Social Posts
Top posts by engagements in the last XX hours
"⚠Urgent: Following the AssetHub migration a few of treasury.spend proposals: #1798 #1796 #1794 #1793 #1790 #1788 #1806 were affected by a one-time XCM compatibility issue. We apologise to the teams impacted and are reaching out to coordinate resolution. These proposals may need to be re-submitted; we kindly ask the community to support them again. Full details:"
X Link 2025-12-08T14:14Z 9165 followers, 10.6K engagements
"To clarify: these proposals weren't created during the migration itself. The issue is that the XCM V3V4 upgrade changed how treasury.spend parameters must be structured. OpenGov treasury proposals have a 28-day decision period before execution. So proposals created shortly after migration only reached execution phase weeks later when the version mismatch became apparent. We sincerely apologise for the inconvenience caused here and are actively working with the affected teams directly to implement the needed"
X Link 2025-12-09T06:29Z 9162 followers, XXX engagements
"The move to XCM v4 happened earlier and that part is already stable. What surfaced now was a one time compatibility edge case triggered specifically by the AssetHub migration not an ongoing version issue. A few of the proposals created during the transition window ended up with mixed V3 and V4 parameters that only failed at execution time on the migrated runtime. We have fully corrected the pre-image generation logic and reached out to all affected teams"
X Link 2025-12-09T06:31Z 9156 followers, XXX engagements
"Critical Update: The treasury payout issue has been identified as a runtime-level gap in XCM version handling. The Polkadot Fellowship is working on a fix expected late December. Affected proposals won't need resubmission. Payouts will be claimable once the upgrade is enacted. Details:"
X Link 2025-12-09T16:45Z 9174 followers, 8137 engagements