This repo houses the EOS smart contracts which run the Everipedia Network on the EOS network. See the technical whitepaper for conceptual functions, categorization, modularization, and theory.

The currently deployed tag is 1.0-final. Note that the master branch contains breaking changes to accommodate the new CDT (Contract Development Toolkit).

Brainpower

Voting on article edit proposals generates stakes of IQ tokens for a period of 21 days. Voting up or down article edit proposals stakes IQ for the amount of the vote. Proposing an edit stakes 50 IQ as an anti-spam measure.

How to Test Your Implementation

If you want to test your implementation of the Everipedia smart contracts, you can use the following command:

sh cd test.test.sh

Running this command will execute your test script and ensure that everything is working smoothly. It’s a good practice to verify that the smart contracts interact correctly within the EOS ecosystem.

Understanding the Code with an Analogy

Think of the Everipedia Network as a library. Each article in this library is like a book on a shelf. Every time someone wants to change something in a book (like a correction or an update), they need to propose an edit. This is similar to a voting process where library members decide whether the change is beneficial.

The IQ tokens represent the reputation points of the library members. They need to invest 50 IQ tokens when they want to propose an edition, similar to placing a deposit to ensure that they are serious about their suggestions. Members also earn these IQ tokens when their edits to the books are approved by others through voting, just like gaining credits for helping to improve the library.

In this scenario, the smart contracts act as the library’s rules. They govern how books can be edited, how votes can be placed, and how IQ tokens are distributed, ensuring that everything operates smoothly and fairly.

Troubleshooting Tips

• If your tests don’t run as expected, double-check your script file (test.test.sh). Ensure it is executable by using the command chmod +x test.test.sh.
• Verify that your EOS environment is correctly set up and running; sometimes, issues can stem from environmental misconfiguration.
• Refer to the technical whitepaper for guidance on theoretical frameworks and potential pitfalls.

For more insights, updates, or to collaborate on AI development projects, stay connected with fxis.ai.

Final Thought

At fxis.ai, we believe that such advancements are crucial for the future of AI, as they enable more comprehensive and effective solutions. Our team is continually exploring new methodologies to push the envelope in artificial intelligence, ensuring that our clients benefit from the latest technological innovations.