🌎 cXc.world Beta Pseudo-code 👨‍💻

Architecture for contracts related to cXc.world 🗺🎶 beta.

To Contribute to the pseudo-code

Simply open an issue with your ideas, or send pull requests. If you don't have a Github account, let us know what you see to be improved in the Ideas + Feedback section of cXc's discord.

Find the contracts

• ups.cxc - Receives BLUX / Sol Ups / Big Ups and pays artists BLUX
• soldisk.cxc - Manages Solar Disk registration and recharges

More Stuff

To contribute to smart contract development

Visit the real-contracts if you'd like to help Douglas with his first production smart contract. Contributors to contract code will be paid in PURPLE based on their subjective contribution on contract launch date. You can also elect to be paid a reduced rate in EOS, TLOS or WAX, or request a different compensation.

Pseudo-code conventions used

ACTION action_name(parameters, [needed environment_variable])
- One piece of actionable code

internal ACTION - Unexposed action AKA private function

TABLE [
  column_name
]

|table_name|
|table_name => column_name|

wordstogether and words_together both used (sorry not sorry)

Cross-contract constants

TU = Internal Time Unit calculated from timestamp (All contracts) called timeunit in final code
AUTH_ACCOUNT = "currentxchng", "cxc", "[soldisk, ups,].cxc"

up_type { // ENUM uint8_t 
  SOL = 1,
  BLUX = 2,
  BIG = 3
};

Please note - Function names and variable names change slightly from psuedo-code to real code to account for character limits and conventions.

Informal record of progress

• Completed .hpp file with initial structure
• Added skeleton of ups.hpp
• Moved some functionality (mainly non-public functions) to helpups.cpp
• Moved updating ACTIONS to 'upsert_' functions
• Added upsifter to abstract common functionality to upsifter.hpp
• Completed all updateup() upsert functions (pending testing)

Differences from Purple Explainer

We have had to make some changes for performance. Here's how it will work now.

For more info, read the Soldisk Documentation

• Users must have a Soldisk (renamed from Solar Disk) with at least 1 PURPLE attached.
• Levels now exist on Soldisks
• SOL will now be a regular eosio.token contract, so users can vote by interacting with smart contracts.
• Soldisk is no longer required to Up, but still required to claim SOL
• This means users can trade SOL (unplanned) so we've added a requirement that 20% of SOL received must be used for Sol Ups or the user won't be able to claim more SOL from their Soldisk (Not Finalized)
• There is no 12-hour wait to claim, users can claim up to every Time Unit (5 minutes), and up to the maximum allowed by their level
• Low-level Solar Disks are allowed to claim 1 SOL per time unit passed (not based on max charge). Next-claim reward amount will not increase after daily limit is reached.
• Listeners will be be paid BLUX
• BLUX will be included in default top charts, and Blu Ups considered in reward algorithm, with limits
• Users will be able to trade Soldisk NFTs, but only register one at a time themselves

Updates

This algorithm has been re-engineered to use tables as the mechanism of data storage instead of using NFTs in the process.

Rewriting the contracts in beta-light repo.

Learn more about cXc

P.S. We're also working on our geotribal system contracts tribe.cxc, council.cxc, geo.cxc, stay tuned!