Configurable block format  #18

Activity

1. liamaharon

   added

   enhancementNew feature or requestNew feature or request

   on Aug 15, 2023
2. weichweich commented on Sep 21, 2023

   

   weichweich

   on Sep 21, 2023

   Last edited by weichweich

   More actions

   trying to gauge how common it is for parachains to use something other than node_primitives::Block.

   Awesome project, looking forward to integrate this into KILTs release process!

   Our Spiritnet uses a u64 as block number. So I would need to adjust the block definition.

   But we also build our own tool that automates the release process a little more and tests some specific things for us as well. So I'm thinking to use this project rather as a dependency than a CLI tool. Which also looks easy enough to do thanks to the split in CLI and core. 🚀

   ❤️React with ❤️1Reacted by liamaharon
3. liamaharon

   added

   good first issueGood for newcomersGood for newcomers

   on Sep 21, 2023
4. liamaharon commented on Sep 21, 2023

   

   liamaharon

   on Sep 21, 2023

   ContributorAuthor

   More actions

   Awesome project, looking forward to integrate this into KILTs release process!

   Thank you!

   Our Spiritnet uses a u64 as block number. So I would need to adjust the block definition.

   Got you. In the immediate term, you could fork the project and make necessary adjustments to the block format.

   Medium term, it should be straight forward to adjust the inherent provider so that it also supports configuring the block format.
5. rockbmb

   added this to the Introductory work milestone on Jan 20, 2026