# SPARKs SPARKs are integral to the PairedWorld ecosystem, providing a practical solution to enhance and monetise reputation without losing it. As fungible ERC-1155 tokens, they are pivotal in organising and encouraging participation in [Meet-ups](/whitepaper/participation/meet-ups.md) the critical social connection and community events within the PairedWorld ecosystem. SPARKs are [distributed at regular intervals](/whitepaper/token-ecosystem/sparks/issuance.md) to SOUL token holders, emphasising the merit-based nature of our ecosystem. This allocation, done at no charge, rewards active participation and facilitates more vibrant and interactive community Meet-ups. SPARKs also offer flexibility through their transferability. They can be exchanged in secondary markets, promoting active user participation and engagement within our network. The application of SPARKs is both straightforward and impactful. To organise or attend a Meet-ups, a single SPARK is burned, symbolising a meaningful contribution to the community. This mechanism encourages active involvement, fosters a sense of community ownership, and aligns with our core mission of building a more equitable, cooperative, and interconnected world. **Usage** SPARKs must be burned to schedule or attend a Meet-ups. Only one SPARK is needed and can be used per event. If the Meet-ups is visible and listed on the [in-app](/whitepaper/w3meet-mobile-dapp.md) schedule, the SPARK can be burned in advance as an RSVP for an extra reward bonus. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.paired.world/whitepaper/token-ecosystem/sparks.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.