69c2d025-0c48-45c1-8339-2312cd35e7d2 The sub0 hackerspace challenges are designed to get you up to speed with building with Substrate and ink!, whether you’re a complete beginner or already have some chops to show for. How It Works Complete a challenge and submit it to the challenge submission form Your first completed challenge earns you an exclusive sub0 merch pack 🎁 More challenges completed = more chances to win the top prizes Psst: Any workshop activity counts towards a challenge!

had to check the way multix does it on relay chain Screenshot 2024-08-12 at 23.00.19 then had to construct the same call on peoples chain Encoded call data: 0x2901030014b81b76cbf4a9031028a71b14c4740c2970710044cb1e145cbb77948132300d755a2160296c65f838252b9da9f51b9691950ece465e1a71b444d286d91316dd24726ef17b500f436cf596935acac782c71a423d35a959f3e6831f13c34db9d71d427639925d379eb016660a025b9bd639bffa555a4f4e03f4a503fccda32b0d4d683cebcfbd11d233f661f486374fd519d43069406ad06ece972181155341722e000000fc4d756c746978206372656174696f6e20316e747259767a37676d6435395176316e67646377417570563463593844504d6b4d4a4269504132595569565876450000 Encoded call hash:

It's incredibly cumbersome to manage payments and paper work as a multisig entity — to run and crosscheck balance sheets, submit post-event spending reports and stay on track about everything. We should have one place to make it easier to do this simple task. Problem: Paying people and managing post-event follow-ups is a big pain for hackathon managers today in web3. In turn, people get upset when they aren't paid in time which sets a bad precedent for hackathon organizers. A little more on the problem as I've experienced it: We're still using spreadsheets, estimating the market price, jumping from address submitted by email to a dedicated multisig dapp and linking back to Google drives for expense proofs. It's a lot of unessecary steps to achieve something that should be straightforward. To do multiple calls (for e.g. you need to pay 10 different addresses different amounts) you need to construct a utility.batch call using Polkadot JS then submit the call to the multisig, typically a different dapp (e.g. Multix). This UX is not intuitive and could be done in one step instead of needing to switch tabs. It takes time to do all this stuff. And it could be streamlined.

What's the best way to extract extrinsics of a past parachain block from the relay chain's state? For example, I have this information about the block of my parachain. enter image description here Is there a way for me to extract the information that was included in that block? From what I understand, the answer is no because its just a receipt from the PoV function. How much blockspace is being consumed in each parachainInclusion.CandidateIncluded ? Is the same size every time? How much blockspace does a single core actually provide? And how much of it is consumed?

W3F grant to kickstart development Funded by Polkadot community grant in January https://x.com/BagpipesOrg Goal is to be the no-code/ "Zapier for web3". Connect ethereum to Polkadot for eg. Team: Ramsey (Decentration) and Filip (Flipchan) X: https://x.com/BagpipesOrg

Want to take the stage to pitch your idea? Go to https://hackmd.io/@webzero/openpitch/edit to update this page with your name and project :point_down: Note: we'll kick off at 7:30PM, you'll have 5 minutes to explain your idea and 3 minutes dedicated for Q&A. Let's go! e.g. Sacha, Blockspace Devrels

Notes for delivery: how to simulate a bad network #[test] fn custom_node_setup_works() { // build a node with the default network id let default_node = setup_core_builder(); // custom node configuration

This workshop aims to give you a lay of the land of the different smart contract platforms on Polkadot and introduce you to ink! — the native smart contracting language for the Polkadot ecosystem. Note: (to facilitator) spend 2 minutes introducing the workshop plan and quests; about 10 minutes going through the background slides while participants setup their environment; 15 minutes creating a contract, going through it and building it; 5 minutes going over contracts UI; account for time for questions and tangents; time permitting go to quest #2. Learning objectives ✍️ Learn what options you have for building and deploying smart contracts on Polkadot Learn how to get started with ink!Set up your local environment Deploy your first ink! smart contract

Join the Blockspice Uniframe: https://devfolio.co/projects/uniframe-85aa ✅ Patio: https://devfolio.co/projects/patio-station-7ec1 ✅ Contract aid: https://devfolio.co/projects/contractaid-8600 ✅ Decentra jockey: https://devfolio.co/projects/decentrajockey-0e41 ✅ Organicterra ✅ Stealth Command: https://devfolio.co/projects/stealth-command-the-hidden-fronts-1f6f ✅ Honest auctions: https://devfolio.co/projects/hones-auctions-8522 🚀

In this workshop, you'll learn how to launch your own local parachain network and how connecting chains to Polkadot works under the hood. 💪 Workshop plan 🗓️ Learn about the big picture: relay chain binary and parachain binaries; genesis configuration Setup Zombienet to launch a test net Interact with your testnet Stretch goal: configure and run cross-chain tests Quests

A hands-on workhsop on staking and participating in governance on Polkadot with Nova wallet. Agenda Download wallet and send address to receive KSM (~10 minutes) Learn by doing: staking, voting, delegating (30 minutes) Q&A Workshop overview nova-wallet-qr-code

Create tools to help developers build on Polkadot Bounty Description This bounty is open to teams to create tools that improve the developer experience of building on Polkadot. Prize Amount $2,000.00 Number of Projects Awarded 1 Project

Bounty Title UI/UX development: build novel user interfaces for interacting with Polkadot Bounty Category Launch MVP on Testnet or Mainet Bounty Description

Bounty Title Appchain development with the Polkadot SDK Bounty Category Launch an MVP on Testnet or Mainnet Bounty Description

Team Name: Algorealm, Inc. Payment Address: 0xB462F70ACB5e0236316faeCCE8766A3D5672902b (USDT) Level: 2 Project Overview :page_facing_up: Overview SwarmNL is a configurable P2P networking layer designed to be used in distributed system architectures that require data transfer solutions for off-chain communication in a scalable way. It's goal is to provide a lightweight and configurable P2P networking layer for web applications designed to interact with on-chain data.

Hooks example pallet: //! - Pallet hooks to implement some logic to be executed at the start and end of block execution //! (see: [`frame_support::traits::Hooks`]) // This pallet implements the [`frame_support::traits::Hooks`] trait to demonstrate how we could // define some logic to execute in some context. #[pallet::hooks] impl<T: Config> Hooks<BlockNumberFor<T>> for Pallet<T> { // `on_initialize` is executed at the beginning of the block before any extrinsics are

This is largely copy paste from the Basic example pallet refactor. A lot of useful information is contained there which should really be reference documentation. I've taken these out and put them here until we have a process for reference docs. I've tried to organize them under headings to suggest the type of reference docs each piece should live under. // # References // // ## Storage // // pallet::storage attributes allow for type-safe usage of the Substrate storage database, // so you can keep things around between blocks. //

Goals: Mint an NFT collection on Rockmine, the assets parachain on Rococo Launch the UI for users to claim their NFTs Learn the advantages of using a common good parachain for minting a POAP collection Prelude Polkadot and Kusama each have their system parachains for enabling anyone to create their custom NFT collections. There are several reasons why creating NFTs using these chains is a more secure option than minting supplies using smart contracts or using other parachains. But we'll leave that to a separate blog. In this guide we'll learn how to cretae your own NFT collections for a POAP use case. You can learn how to mint single NFTs in this tutorial using singular.app's slick UI. But what if you were running an event and wanted to create POA (proof of attendence) NFTs for your guests?