Author: cleanerzkp
Description: Participate in archiving Warpcast content by running this task. Help preserve data and earn SealCoin in this Proof of Concept Hackathon Project. The base bounty per round is 10 SEAL, divided among participants.
Repository URL: GitHub - cleanerzkp/Sealcoin-Warpcast
Image URL: ipfs://bafybeibf6o3xospzjum6r46oweynwbt5vwsk77znkja3fotmgfs24zojni/
Task ID: 9qAs2EqfsGyrUGULQRLTNgfuLbBLU4PFM48N6XFxg76M
KPL Token: KPL Token on Koii Explorer
Sealcoin Warpcast is a pioneering project aimed at archiving valuable content from Warpcast. By running this task, you can help preserve important data and earn SealCoin as a reward. This initiative is part of the Proof of Concept Hackathon Project and aims to demonstrate the potential of decentralized content archiving on the Koii Network.
- Decentralized Archiving: Utilize the Koii Network to securely archive Warpcast content.
- Earn SealCoin: Participants are rewarded with SealCoin based on their contribution to the task.
- Community Driven: Encourages community participation and collaboration.
Runs tests using Jest.
Builds the project and generates the main script: dist/main.js.
Tasks operate within a periodic structure known as 'rounds'. Each round consists of the following steps:
- Perform the Task: Execute the necessary actions for the round.
- Audit Work: Review the work completed by other nodes.
- Rewards and Penalties: Distribute rewards and apply stack slash as necessary.
Rounds are defined by specific time periods, with nodes participating through actions such as uploading data to IPFS, posting CIDs to the K2 settlement layer, and communicating via REST APIs and WebSockets.
For detailed insights into the task flow and its operations, refer to the runtime environment documentation.
Feeling lost at the start? Curious about our template structure or the specifics of certain functions? Wondering how to test your task locally? Interested in learning how to upload data to Spheron via IPFS? Unsure about the process for whitelisting your task or selecting the right cluster? Start with the Development Guide.
Looking to bring better structure to your task? Explore our Task Organizer for better organization.
There are two ways to run your task during development:
-
With
GLOBAL_TIMERS="true"(refer to.env.local.example) - When this option is enabled, IPC calls are made by calculating the average time slots of all tasks running on your node. -
With
GLOBAL_TIMERS="false"- This option allows for manual calls to K2 and disables the automatic triggers for round management on K2. Transactions are only accepted during the correct time period. Instructions for manual calls can be found inindex.js.
Rename the .env.local.example file to .env.local and make the necessary modifications. Here, you can include environment variables that your task requires. This is particularly useful if you're utilizing custom secrets.
- Always ensure your secret files, such as
.envfiles, are secure! Implement a robust.gitignorestrategy. - Continue innovating with Koii!
Should you encounter any issues, don't hesitate to reach out by opening a ticket on Discord.
Our mission is to improve access to decentralized technology, which is why Koii tasks are written and configured entirely in JavaScript (NodeJS 16, to be exact) and support the majority of popular NPM Modules.
For more information, visit koii.network.