.derupt-core-yyyymmdd
Users call their own .derupt-profile which then calls .derupt-core-yyyymmdd
The core maybe require or receive upgrades/updates from time to time, for that we follow a simple date based naming convention to track versions.
General:
.derupt-core-yyyymmdd contract is for handling public message & action logic.
.derupt-core-yyyymmdd contract receives calls from .derupt-profile contracts and proceeds to process them accordingly.
Warning:
users should deploy a
.derupt-profile
contract in app before using core features.users should call
.derupt-profile
users should not call
.derupt-core-yyyymmdd
(nor logging contracts)users should only enable 1 extension per 1 key function at a time (eg up to 6 active extensions at a time)
Key Functions Process Transactions Overview:
What happens in a process depends on the function the user is calling.
gift-message:
transfer
of a variable sip-010 token is called during this process.send-message:
mine
cryptocash is called during this process.like-message:
transfer
cryptocash is called during this process.dislike-message:
stack
cryptocash is called during this process.favorable-reply-message:
mine
&transfer
cryptocash is called during this process.unfavorable-reply-message:
mine
&stack
cryptocash is called during this process.
The 6 key functions and arguments in the .derupt-core-yyyymmdd
contract:
Last updated