• What is a Blockchain?

• What is a Masternode?

• What is a Spork?

A blockchain is a technology revolutionizing how we store and manage digital information. Initially introduced alongside Bitcoin, the blockchain concept has since evolved beyond financial transactions.

True Blockchain Definition

Imagine a record book that isn't under the control of a single authority but is instead distributed across multiple computers or nodes. Each transaction forms a block, and these blocks are linked in a chain, creating the blockchain. This system's extraordinary capabilities lie in how a cryptographic hash links each block to the previous one. This mechanism ensures that once a block is added to the chain and verified, altering or manipulating the information becomes virtually impossible.

The transparency and integrity add a whole new level of trust to the system. Blockchain technology also eliminates the need for intermediaries, such as relying on central institutions. This is because the blockchain operates on a network where every participant has a copy of the entire blockchain. The decentralized nature opens new possibilities for direct and trustless interactions between participants. In addition to cryptocurrencies, blockchain technology has found applications in various other sectors, including supply chain management, healthcare, voting systems, intellectual property, and many more For example, the integration of other software such as smart contracts, which are emerging with the blockchain bubble, will allow for self-executing agreements where pre-defined rules are encoded within the blockchain itself.

This section provides detailed information about a specific masternode in the blockchain.

" IP Address " Shows the IP where the masternode daemon is currently running. " Status " Indicates whether the masternode is running and connected to the blockchain properly. " Last seen " Displays the last time the masternode was seen on the network; this ping happens every two hours or more. " Pubkey " Shows the wallet address of the masternode. " Protocol " Displays the running wallet protocol of the masternode. " Last paid " Shows the last time the masternode received a reward. To search for specific information related to masternodes on the network, the search box on the left can be used to query the explorer by IP, Status, Pubkey, and Protocol.

A Masternode (MN for short) is a full node in a blockchain network that helps secure the network by consensus and improves the blockchain's functionality.

It operates on a dedicated server with a static IP address while ensuring a high level of availability and reliability. Furthermore, it is only eligible if it meets the required amount of secured collateral.

The MN owner is compensated for contributing to the network's capabilities with a portion of the block reward.

Masternode Specialized Tasks

A Masternode enhances the functionality and security of a blockchain network. They validate and store blocks of transactions, helping to maintain the integrity of the network's ledger and prevent malicious activities like double spending, thus helping to ensure the security and immutability of blockchain data. Masternodes can also help improve the scalability and stability of the blockchain network. By offloading certain tasks and responsibilities from regular nodes, Masternodes help reduce the network load, improve performance, and ensure efficient operation even as the network grows.

Masternode Collateral Requirement

Operating a masternode requires a collateral amount of the cryptocurrency to be locked in a dedicated wallet. This collateral ensures that the Masternode owner has a financial stake in the network and discourages malicious behavior.

The amount of coins in the collateral is always stipulated by the blockchain and is a unique value that must be exactly as requested. The value must be exact, without any deviation, and it must be done in a single transaction. A frequently asked question is whether the collateral allocated in a Masternode is permanently lost. The answer is NO. When you run a Masternode, the coins remain in your wallet. If you decide to stop running the Masternode, the coins become "unlocked" and can be used again without restrictions.

Rewards for Running a Masternode

To reward the Masternode owner for playing such an important role in the network, a percentage of the block reward is delivered directly to the wallet from which the masternode was created (i.e. the wallet with the collateral). When considering running a Masternode as an investment allocation, things like Return on Investment (ROI) are important concepts to understand. ROI is the percentage of initial investment that can be expected to earn back annually. Calculating ROI, in this case, involves several factors, such as the Masternode's collateral, the block reward, and the current number of Masternodes on the network. In general, as more Masternodes participate, the ROI decreases. On the other hand, a decrease in the number of Masternodes literally means a higher ROI. It can be calculated as follows: ROI = (((MN reward per block x number of blocks in a year) / number of MN currently on the network)/ collateral amount)x100 Information on the above points is always provided by the project.

Creating a Masternode

With the help of our unique Masternode Multinode Script, a task that often requires a certain level of technical knowledge has been simplified. This makes it possible for anyone to seamlessly deploy a masternode.

A tutorial on how to easily install and deploy a Masternode using this DECENOMY Masternode Multinode Script can also be found on this website: eploys

The search box can be found in all tabs, allowing for precise queries on the explorer.

After utilizing the aforementioned search box to obtain more information regarding specific block information, or when clicking on the block or hash value presented on block details ( please check Latest blocks guide ) the user will be redirected to a screen resembling the following:

Detailed block info

Section 1 from block info

This board is dedicated to displaying block details, such as the hash and block height, as well as the number of confirmations the block has at the time of the query. Additionally, it includes information on the number of transactions that occurred in that block and the creation date of the block.

Section 2 from block info

This section provides detailed information about the three transactions listed in Section 1. By selecting one of the transaction IDs, users can view its content in more detail. For more detailed information, about how to understand the transactions ID tab, please follow the guide on to learn more )

In this guide, we will explain how to stake our DECENOMY coins.

First of all, let's open our wallet (in our case SAPP). In order for staking to be active, our coins must have at least 600 confirmations (about 10 hours).

A second requirement is that the wallet is unlocked. To do this we can click on the padlock icon at the top right.

Make sure to choose the “Staking only” option!

If you happen to have encrypted your wallet, you will be asked to enter your password and confirm the operation by clicking "OK" as seen below:

Once this is done, the staking icon will activate. To be able to stake, the wallet must always remain open.

If staking is not activated, you can use the getstakingstatus command in the debug console to gain more insight into the root causes of the issue.

We have provided more information on this command, which can be accessed on the page.

On this first screen, we can perform 3 different operations.

• Select the coin we want to use

• Update the script

• Check which coins are installed on the system running this tool

Coins to use

Each coin is referenced by a number so that it can be used. Simply enter the number assigned to each coin in the prompt below and press Enter.

Update the script

This option can be used in case of a script update. The script will assist the user by reading the latest version presented on Github and the version currently installed on the system (the version in use). The user will then be prompted to decide whether to proceed with the upgrade.

Already Installed

This feature provides an easy and fast way to determine which coin wallets have already been installed on the system through previous actions using this script and its own environment base.

One place to manage everything related to multinode.

[1] - List of masternodes in multinode List

This section lists all the multinodes already installed in the system, taking into account the previously selected coin.

The multinode result is always sorted by the alias and then by the masternodeKey.

[2] - Add masternode to multinode List

This option allows you to add new multinode configurations and view those that have already been created or are currently being created.

Section 1

It displays the same information as the previous option for listing multinodes.

Section 2

This is a guide to help you easily understand how to fill out the multinode file.

Section 3

The multinode information must be entered in steps. First, the alias is requested, and then only the masternodeKey is requested. In this last step, the key can be entered manually or generated automatically by pressing the Enter key.

This screen also shows the previously introduced alias as a reference.

[3] - Delete masternodes from multinode list

This is an easy way to delete previously introduced multinode information.

Each line is numbered, making it easier to select the exact information to be deleted. After the selection is made, a confirmation screen is displayed and upon confirmation, the screen is updated with the final information.

One way to backup your wallet is to save a copy of the wallet.dat file on an external device.

First of all, we insert our USB stick into the PC and open our wallet (in our case the SAPP wallet), then go to the bottom left and choose the settings cog.

• 1 Settings

• 2 Wallet Data

• 3 Wallet

As seen in the image below:

Once this is done, as you can see in the image, the backup wallet menu will open, click on the folder icon on the right as in the image below:

After that, a window will open where we can choose the destination for our backup file

• 1 look for our USB stick and click on it to select it

• 2 let's choose a name for our backup

• 3 click on save

If the operation went well, this will appear:

If in case you need to restore your backup, the name to use will be "wallet.dat"

If you select [5] Others, a screen appears with random options that are not suitable for other menus.

[1] - Update this script

This option can be used in case of a script update. The script will assist the user by reading the latest version presented on GitHub and currently installed on the system (the version in use). The user will then be prompted to decide whether or not to upgrade. ( The same menu can be accessed directly from the main menu option number 18 )

[2] - File System

Important information about the file system and file location related to the environment base described earlier.

This tab provides a useful function for establishing additional connections to the network, which can improve the connectivity of our wallet.

Clicking the "Node List" button will display information for the addnodes.

This feature can be particularly helpful if your wallet requires better connectivity to the network. For more detailed instructions on how to use addnodes, please refer to our guide following this link

The Latest Blocks and Latest Transactions tabs contain the same information as presented in the Overview tab, in what information is related.

The information displayed in the top squares is the same as Section 2 of the Overview tab, which contains masternode statistics. Similarly, the content of the blocks shown can also be found in Section 3 of the Overview tab.

Detailed block info

Upon selecting a value such as a block height or hash, the user will be directed to the block detail screen. If you would like more detailed information, please follow the guide on .

This option will perform a new installation of the masternode wallet in the system. This action will delete all previous files related to the previously selected coin. A warning screen will be displayed after selecting this option, informing the user about the upcoming steps related to the action.

When selecting [4] Wallet management, a screen will appear with options to fully manage the masternode wallet.

[1] - Update wallet

Similar to the "Wallet statistics" options we checked earlier, the wallet version from Github and the wallet installed in the system will be displayed on the screen before confirming to update the wallet. This method will not destroy the already set masternode; it will only change the binaries related to the wallet and restart the service (not the masternode). Such a process is useful in case of a mandatory wallet release or any other wallet release that needs to be updated.

First of all, we insert our USB stick into the PC. After that, we open the USB stick folder and navigate to the backup file.

Let’s now copy the file

After that, we have to navigate to the wallet data directory located in %appdata% as shown in the picture (Windows 11).

We can now open the coin’s folder we are looking for (in our case Sapphire)

NB The file name must always be wallet.dat so we need to rename the old one first.

In case we have problems connecting our wallet to the blockchain we need addnodes (peers).

In this guide, we will explain in a few simple steps how to add peers to your wallet.

First of all, let's open our wallet (in our case Sapphire)

Now we go to the top right and we will see the configuration file icon (in our case sapphire.conf).

As seen in the following picture

Now click on the configuration file icon to open it.

In case Windows asks us which program we want to use to open it, it is advisable to choose Notepad.

This menu has a dynamic result depending on what is installed in the system. If the coin masternode is not installed, you will be prompted to install it, as shown in the image below.

The master node installation process will display information about the current step. It is unlikely that the installation will get stuck, although the screen may appear frozen or the process may appear to have stopped. It is advisable to wait for some time before abruptly terminating the process. For reference, the complete automated process is shown in the image below.

Once the installation is complete, the coin selection screen for the installation will no longer be available and the coin selection screen will now be this one:

As you move forward in the script, everything is related to the coin selected in the main menu. In this case, it is Sapphire. Moving forward in the script, everything is related to the coin selected in the main menu. In this case, it is Sapphire.

To provide a more detailed understanding of this tool, it would be helpful to explain how the information is organized on the screen. This will make it easier for users to understand the documentation and how to use the script.

Section 1

This refers to the version number of the script that is installed and currently in use.

When selecting [3] Stats Wallet and masternode, a screen will appear with options to choose the desired type of statistics.

[1]- Wallet statistics

A comprehensive overview of all the information needed to keep track of the wallet associated with the masternode.

The Overview tab serves as the landing page for each coin when accessed via a breakdown link. This page contains the essential information required for daily use.

The detailed descriptions of each section, marked and numbered in the image above, will provide a comprehensive understanding of every component.

Section 1

The information provided in this section is easily understandable. It is important to note that there is an option to download the bootstrap for each coin. Simply click on the 'Download' button, and a *.zip file will be transferred to your device. For additional assistance regarding bootstrap, please refer to the bootstrap documentation following

In today's digital age, cryptocurrency exchanges are the gateway to the exciting world of digital assets. Whether you're a seasoned trader or just starting your crypto journey, having a secure and verified exchange account is crucial.

These comprehensive guides are designed to walk you through the essential steps of creating and verifying your Birake account, depositing and withdrawing, and trading.

By the end of this tutorial series, you'll have a verified Birake account, ready to trade, invest, or explore the possibilities that the crypto market has to offer.

Summary

This script was created to manage all coins related to DECENOMY, making it easy to handle masternode multinode installations and maintenance. With this tool, it's possible to:

• Easily manage the masternodes multinode of different coins in each system

• Track the status of your wallet

• Check masternode status with Explorer

This guide is an introduction to acquiring crypto with FIAT. We will first purchase Bitcoin, and then exchange Bitcoin for one of Decenomy's Coins ( e.g. SAPP)

The primary objective of this tutorial series is to provide guidance to individuals interested in getting started with cryptocurrencies but uncertain about where to begin.

Summary

• checkconnection RPC call: This call allows you to test the connectivity of your server with other nodes on the network.

• mnping RPC call`: This call allows you to send a ping message to your masternode and receive a pong response. It helps you verify that your masternode is online and responsive.

• We begin by navigating to "buy crypto" from the top menu bar. From the dropdown menu, we have various methods to do this, including bank deposit and credit or debit card. we will be using the latter in this tutorial.

• Next, you will be presented with options to specify how much you want to spend, in which currency, and which cryptocurrency you want to purchase. For now, let's purchase 100 euro worth of Bitcoin.

Introduction

In the realm of cryptocurrency networks, the evolution of masternode systems is a critical juncture where operational efficiency and network stability converge. The traditional masternode model's sudden adjustment of collateral values at a specified block number has posed challenges, resulting in considerable network instabilities. Abruptly dropping the existing masternodes with old collateral values and waiting for new masternodes with updated collateral leads to significant disruptions in the network’s continuity.

The disruptive impact arises from the network's need to cleanse the entire masternode list, causing pauses in operations until the list repopulates. This process introduces considerable instability, impacting the reliability and functionality of the network. Moreover, it creates significant stress and uncertainty for masternode operators, affecting their ability to adapt within the set timeframe.

Proposed Feature: Enhancing Masternode Stability with Collateral Window

The current masternode system undergoes critical changes in collateral values at specific block numbers, precipitating significant network instabilities. The sudden alteration results in the removal of existing masternodes with previous collateral values, prompting a waiting period for the introduction of new masternodes with updated collateral. This process disrupts network continuity, introducing considerable instability and stress among operators.

In response to these challenges, the innovative Masternode Collateral Window feature has emerged. This solution facilitates the setup of new masternodes with adjusted collateral values seven days before the deadline. This extended window aims to alleviate the stress on masternode operators, providing ample time for adjustment and minimizing disruptions to the network.

The development of this feature involves a meticulous reconfiguration of the masternode setup process. Implementing the Masternode Collateral Window entails refining the masternode software to allow operators to update collateral values within the specified window. Extensive testing and validation are essential to ensure the stability and compatibility of the new feature within the network's framework.

The Masternode Collateral Window represents a significant step towards a more stable and stress-free masternode ecosystem. This development aims to significantly reduce network instabilities, providing operators with a smoother transition period for collateral adjustments ultimately fostering a more resilient and predictable network.

Conclusion: Advancing Masternode Stability with Collateral Window

The Masternode Collateral Window brings a critical shift in the masternode ecosystem by extending the collateral adjustment timeline. This innovation significantly diminishes stress and network instabilities by allowing operators a seven-day window to adapt their collateral values. The implementation of this feature demands meticulous adjustments and thorough testing. Ultimately, this advancement promises a more stable, operator-friendly, and predictable masternode network, emphasizing a smoother transition and reduced disruptions in the system.

One of the main functions of the masternode system is to distribute rewards to the masternodes (MN) that secure and support the DECENOMY network. The rewards are generated by the block creation process and are allocated to a specific MN at each block. However, the question of selecting which MN will receive the reward in each block is not trivial. Different methods can have different implications for the fairness and efficiency of the reward system.

Challenges and limitations of the voting mechanism

The previous inherited method of selecting the reward recipient is based on a voting mechanism. Each MN in the network casts a vote for another MN that it thinks should receive the next reward based on the criteria of the last paid value. The last paid value is an estimate of when an MN was last paid, calculated by counting the number of votes that it received from other MNs. The MN that receives the most votes in a given block is selected as the winner and receives the reward.

However, this voting mechanism has some drawbacks and limitations.

• It relies on the assumption that all MNs are online and voting correctly, which may not always be accurate. Some MNs may be offline, malfunctioning, or maliciously voting for themselves or other colluding parties.

• It does not account for the actual time when an MN was paid but only for the number of votes it received. This means that sometimes an MN may lose a reward round because it received fewer votes than another MN, even though it was truthfully waiting longer to be paid.

• It does not provide a clear and consistent way to measure the last paid value of an MN across different nodes in the network. Different nodes may have different views of the voting history and may disagree on which MN was paid and when.

Masternode Payment V2 is a blockchain-driven approach

The masternode payment v2 is a new feature that addresses these issues and replaces the old voting mechanism entirely. Instead of using votes to select the reward recipient, it uses a simple and objective rule: it pays the MN that is waiting longer to be paid.

• To determine which MN is waiting longer to be paid, it uses blockchain data as the source of truth. The blockchain records every payment that is made to an MN in a particular field called payee.

• The masternode payment v2 scans the blockchain from the most recent to the oldest block and looks for this field to identify when an MN was paid. It then assigns a last paid value to each MN based on its last payment's block height (or number).

This way, it can accurately and objectively determine which MN has been waiting longer to be paid and select it as the next winner.

Advantages of Masternode Payment V2

The masternode payment v2 has several advantages over the old voting mechanism.

• It does not depend on any external factors such as network connectivity, node availability, or voting behavior. It only relies on the blockchain data, which is immutable and verifiable by anyone.

• Reflects the actual time when an MN was paid, not just the number of votes that it received. This ensures that every MN has a fair chance to receive a reward based on its waiting time, not on its luck.

• Provides a consistent and transparent way to measure the last paid value of an MN across different nodes in the network. Every node can easily calculate and verify this value by scanning the same blockchain data.

The masternode payment v2 is a major improvement for the masternode system and for the DECENOMY coins. It simplifies and streamlines the reward system, increases its fairness and efficiency, and reduces its complexity and potential for errors. It also makes DECENOMY coins more attractive and competitive as a cryptocurrency that rewards its users for securing and supporting its network.

Introduction

Revolutionizing Masternode Hosting for Decentralization

In the dynamic landscape of cryptocurrency networks, the evolution of masternode systems plays a crucial role in shaping their efficiency and security. This document introduces a groundbreaking feature aimed at transforming the masternode ecosystem, allowing a single full node to host multiple masternode instances.

The advent of multi-instance hosting marks a significant shift, alleviating operational complexities and lowering barriers for masternode operators. This innovation incentivizes the cost-effective management of several masternodes on a singular server, reducing the technical overhead and encouraging broader participation.

Beyond operational efficiency, this feature indirectly fosters network decentralization by enabling easier access and management of masternodes. By simplifying the process of hosting multiple masternodes on private servers, this advancement contributes to a more diverse and resilient network structure.

This document outlines the technical aspects, benefits, and the pivotal role of this feature in promoting a more accessible, cost-efficient, and decentralized masternode ecosystem.

Proposed Feature: Multi-Instance Hosting for Masternodes

This feature introduces a transformative shift in masternode systems by enabling a single full node to host multiple masternode instances, promoting a more accessible, decentralized, and self-sovereign network architecture.

Allowing a single full node to manage multiple masternodes concurrently significantly reduces technical complexities and operational costs. Operators can efficiently manage several masternodes on a private server, enhancing cost-effectiveness and operational efficiency.

Additionally, this advancement indirectly incentivizes decentralization and self-sovereignty by encouraging increased participation. Simplifying the process of hosting multiple masternodes on private servers not only fosters network diversity but also empowers operators, providing greater autonomy and control over their masternode operations.

The technical implementation involves refining the full node software to accommodate multiple masternode instances effectively. Comprehensive testing is imperative to ensure stability, security, and optimized performance within the network.

Ultimately, the implementation of multi-instance hosting aligns with the overarching goal of fostering a more accessible, cost-effective, and self-sovereign masternode ecosystem. This feature significantly reduces operational barriers and promotes decentralization and self-sovereignty, strengthening the network's overall structure and accessibility.

Conclusion: Advancing Decentralization through Multi-Instance Masternode Hosting

The introduction of multi-instance hosting for masternodes marks a pivotal leap in redefining the landscape of cryptocurrency networks. This innovative feature enables a single full node to manage multiple masternode instances, ushering in a more accessible, efficient, and self-sovereign ecosystem.

At first glance, consolidating multiple masternodes on a single server may seem to incentivize centralization. However, this overlooks the nuanced impact of prior practices. Formerly, the forced hosting of one masternode on a single server created a false impression of decentralization, as numerous masternodes were hosted on one server, each operating under different IP addresses and processes.

The newly introduced multi-instance hosting breaks away from this false decentralization paradigm. By significantly reducing the barriers of entry to host multiple masternodes, this feature paves the way for a more genuinely decentralized network. Lowering technical complexities and operational costs encourages individual investors to host masternodes in their private facilities, thereby democratizing masternode ownership and promoting a diversified network structure.

The democratization of masternode ownership not only empowers a more diverse range of stakeholders but also fosters a more resilient and decentralized network structure. Operators gain greater control and autonomy, reinforcing the concept of self-sovereignty within the masternode ecosystem.

Implementation of multi-instance masternode hosting necessitates meticulous testing and refinement to ensure network stability and performance. In essence, this feature's true impact lies in democratizing and decentralizing masternode ownership, leading to a more robust, inclusive, and genuinely decentralized masternode ecosystem.

Context

A blockchain explorer is a web based tool that enables users to search and view the transaction history of a particular blockchain network in a user friendly way. It provides a graphical interface for accessing and analyzing all the transaction data stored on the blockchain.

The explorers play a vital role in analyzing the health and transaction history of a blockchain network. They offer a comprehensive and transparent view of the network's transactions, allowing users to track and trace the flow of cryptocurrency across the network. This makes them an essential tool for researchers, investors, and anyone interested in understanding the inner workings of a blockchain network.

Main Link

Breakdown Link to direct access to each coin explorer

/coin

Note: change the path parameter (coin) to a Decenomy ticker coin always in CAPS example: https://explorer.decenomy.net/SAPP

Summary

Since this script serves the needs of all DECENOMY coins, the first screen of it is based on the selection of the coin we want to manage. Only after the previous step, more options are available, always taking into account whether the coin is already installed in the system or not. Full option availability only after the coin is installed.

- Main Menu

-

• • List of masternodes in multinode list

What is a Fork?

A fork in the context of blockchains is when changes are made to the blockchain's protocol which usually results in two separate versions of the blockchain.

Because blockchains are often updated to ensure security and embed new features, there is the need to be on the lookout for instructions on how to update your wallet if it's mandatory.

Failing to respond promptly to upgrades can result in your wallet being associated with the incorrect blockchain.

Possible Scenario your Wallet might be Forked

For example, you might have activated staking for a Decenomy coin, and in a short period, you realize you have received an outrageous amount of staking rewards.

In such an instance, there is a possibility your wallet might have been forked. This means your wallet is on the wrong chain and these rewards earned are useless. Once the issue is resolved, these rewards will not show in your wallet as they aren't real.

Verifying a Wallet Fork

Once you suspect a wallet fork, the following steps will help you to confirm if it's truly a fork. We will use SAPP for demonstration purposes.

• Open your wallet and go to "SETTINGS", then select "Debug". Next, you choose "Information" from the dropdown menu. We then navigate to the "Blockchain" section on the left side of the screen.

• The information of interest is: 1. Current number of blocks: 2360341 2. Last block hash: 616851ded4d975e3dc331a0ecf894bd5814a4b27aaf5e46118bd1adf8e8b8b0d

On the SAPP explorer, we compare the "Current number of blocks" and "Last block hash" from the wallet to ensure they match.

If we confirm the block hashes of both the wallet and the explorer are the same, then our wallet is on the right chain. However, if the hashes are different, then it indicates a fork.

NB: In some cases, it is preferable to use previous blocks in our wallet as bases for the comparison. This is because new releases have self-fork management and the explorer takes a while to index. This causes a difference in the hashes when using the most recent block.

To check the hash of a specific block in our wallet, we do this instead:

• Open your wallet and go to "SETTINGS". Next, we choose 'Debug' and then 'Console"

• We use the command getblockhash with the block number we want its hash. e.g., getblockhash 2360331

We get a response with the hash as shown in the image below:

We then have to compare the hash to that of the explorer to see if they match

Resolving a Fork

• Go to "SETTINGS" in your wallet. Select 'Debug' and then 'Wallet Repair'. Scroll down to the end

• First, we start by selecting the "Rewind blockchain to last week" option

• If it doesn't resolve the issue, we then proceed with the "Rewind blockchain" option. Hopefully, that should put your wallet on the right chain.

This is important to ensure that your wallet is up to date with the latest security features, bug fixes, and other improvements.

In this guide, we will explain how to update a wallet:

Let's start by opening the wallet, in this case, Sapphire, to verify the wallet version located at the bottom left of the wallet window.

We can check for updates through our official channels (Twitter, Discord, website, or directly on GitHub)

After we have verified that there is an update (in some cases the updates are mandatory otherwise the wallet will stop working) we have to download the latest version. For Sapphire, you can locate it on GitHub using the following link:

https://github.com/decenomy/sapp

To access the latest version on GitHub, simply copy and paste the GitHub address into the address bar, as shown in the image below:

Once you are on GitHub, Click on the RELEASES link as shown in the image below:

This screen will appear:

Apparently, the latest version is v1.5.2.1, which differs from our current wallet version (v1.5.2.0).

Now, we need to select the appropriate version for our operating system, which, in this instance, is Windows. For Windows, you should choose the file named 'SAPP-1.5.2.1-Windows.zip'.

Once the file has been downloaded, we can go back to our wallet to close it.

Once this is done, go to the download folder and extract the zip file which contains the new version of the wallet as in the image below:

Once the file has been extracted we can copy "sapphire-qt" and paste it into the Sapphire wallet folder on our computer. This will replace the previous version.

An easy way to locate the Sapphire wallet folder is to find the "Sapphire Core" shortcut on our desktop. Right-click on the icon and select "Open file location" as seen in the image below:

Upon selection, you will be directed to the correct folder where you should paste the 'sapphire-qt' file. Confirm the replacement of the file, and you're all set to proceed.

Now you can start your wallet, which has been updated and is now ready for use.

The search box can be found in all tabs, allowing for precise queries on the explorer.

After utilizing the aforementioned search box to obtain more information regarding a specific transaction ID, or when clicking on the transaction value presented on block details ( please check Search by Block and/or Hash guide ) the user will be redirected to a screen resembling the following:

Detailed Tx ID info, case 1

This screen displays comprehensive and detailed information about the events that took place in this specific block, on this specific transaction.

Section 1 from Tx ID info, case 1

This section provides cross-information about the transaction ID, including the block height to which it belongs, as well as the hash and time of that particular block height.

Section 2 from Tx ID info, case 1

The " Sending Address " indicates that it was a reward transaction created, taking into consideration the nature of the coin, POS/MN. The " Recipients " section indicates that the address receiving the 280 SAPP was a stake reward, while the address receiving the 520 SAPP was a masternode reward. Further confirmation of these values is explained in the next section.

Section 3 from Tx ID info, case 1

To provide some context for the information presented, it's important to briefly explain the staking process. In this process, a certain amount of inputs with a specific value are ready to stake a block. Once staked, the input that earns the reward is compounded with its previous amount and the stake reward value.

In the " Input Details " section, it's indicated that the input with an amount of 11214 SAPP was staked in this block. After the stake, the same input with the same address now has a compounded value of 11494 SAPP, as shown in the " Output Details " section.

It's worth noting that in some cases, a wallet can stake and split one input into multiple inputs, as seen in the example presented in the following board.

The wallet in this case staked with an input of 44699 SAPP and compounded it into a new input. At the same time, it split this new input into four others.

By referring to sections 2 and 3, it is always possible to gain insight into the reward value that a stake and a masternode receive, as well as what happens when an address stakes.

Detailed Tx ID info case 2

This type of transaction is a breakdown of a coin transfer and is not related to any reward earned from a masternode or stake.

The " Sending Address " indicates that the transaction used a combination of 5 different wallet addresses to transfer the desired value. As for the "Recipients" address, it appears that the user wanted to transfer precisely 5112 SAPP to one address while sending the remaining amount of 1.9078 SAPP to another address. It is important to note that this value already takes into account the deduction of transaction fees.

DECENOMY coins are based on a central blockchain coin development known as the DECENOMY Standard Wallet (DSW). The work for DSW is done and collected in a main repository at https://github.com/decenomy/DSW In a process referred to as rollouts, a code merge is delivered to each DECENOMY coin repository once a certain amount of new features and/or improvements have been collected. Additionally, in the event of a bug being discovered on one of the blockchains, the fix is introduced to the corresponding blockchain and then delivered to the DSW main code.

It is important to note that DSW is not intended for use as a wallet or coin but rather serves as a base code that can be utilized for programming purposes. As the code is open source, the DECENOMY team encourages contributions from the community, including new features, fixes, or bug reports, through the creation of an issue or pull request on the DSW Github repository. Details of each coin can be found in the following list

• Azzure (AZR)

This guide will walk you through the steps needed to buy Decenomy coins on Birake.

This is the third tutorial from the series How to Buy Decenomy Coins on Birake. We assume you have successfully created and verified your Birake account by now. And most importantly funded your account.

• From the top menu go to

1. Exchange

2. Then Show Markets

• Once this is done, a search bar will open where we can filter by entering a coin name. In this case, we input SAPP (Sapphire).

• Now click on the SAPP market to enter the market page with the buy and sell orders.

• Now we can proceed with the purchase. We have 0.00076163 BTC available and can buy SAPP for this value in the SELL ORDERS table.

• Now we need to click on the rows of the SELL table until the total of our order is equal to or greater than our Bitcoin balance. In our case, the second row of orders in the table gives us a total higher than our Bitcoins available.

• So you have to click on the available balance to buy the equivalence of SAPP with our BTC balance.

1. Click on the Balance

2. Click on BUY

• Now a window will open confirming the operation. Then click CONFIRM to place your order.

In this guide, we will explain various useful VaultWatch features and provide instructions on how to utilize them.

Let's go to the web page

To locate your desired coin, simply enter its name into the search bar. For the purpose of this tutorial, we will use SAPP as our demonstration coin.

Click on the coin's name to go to the next page

Once this is done, we can see the basic information of the coin (e.g. links and some technical details) as shown in the image below:

We will focus on staking and show you the main tools offered by VaultWatch.

Account Creation

• To start with, let's navigate to Binance from Google. Always ensure you have the correct URL.

• For added security, it's recommended to visit

In case there are any synchronization problems with your wallet, it is useful to know how to use a bootstrap (i.e. an archive containing the blockchain files). It is highly recommended to backup your wallet.dat file before making these operations. If you don't know how please refer to our guide “How to make a backup on a USB stick” Done this, if your wallet is open you have to close it.

So now let's go to the site as in the image:

After that, we choose in the bar at the top the coin that interests us (in our case Sapphire), and we click on the link in the table below as in the image:

This takes you to the overview page of the coin in question. In our case, we got sent to the landing page of the SAPP coin.

NB: Alternatively, you can access the overview page of any Decenomy coin by choosing "Overview" from the menu on the far left of your screen.

The installation of the files provided by this script has been done properly, taking into account the best security practices. As a result, the files are not installed at the root level, as is common with similar tools. Instead, each instance of the coin installation will create its own user ID on the Linux system files, with the coin name serving as the identifier for the deployment location of the respective coin blockchain files. Please note the exact file locations using the coin sapphire as an example.

First, let's open our wallet (in this case Sapphire). After this, as we can see in the image below, there is a padlock icon that is used to encrypt our wallet.

It is important to encrypt our wallets to ensure greater security for our coins.

Now let's click on the padlock icon and the following window will open. We recommend that you put a secure password that is not already used elsewhere.

It is important to take care not to lose this password because without the password it will no longer be possible to access funds.

Then we click the "OK" button

A further confirmation screen will open and we will click the ENCRYPT button.

In this guide, we will explain how to use Crypos.io for shared masternodes.

Now let's go to our browser and type crypos.io in the address bar.

Then we register or log in if we are already registered.

Now that we are logged in, click on shared masternode in the left menu.

Once this is done, a page will open where we can choose the coin that interests us (in our case we choose Sapphire).

Then click on the Buy Share button.

Before proceeding (as we will see shortly) it will be necessary to provide the receive address of our wallet, where our rewards will be sent if they are not all reinvested.

Prior to that, you will be required to set up two-factor authentication (2FA).

So now let's go to our wallet and from the receive menu we copy our address.

At the time of making this guide, the minimum amount required to participate in a shared masternode is 200 SAPP. Click on the "add payment address" button to access the input field.

Now we can paste the address previously copied in the field and click on the "save" button:

Choose the "Deposit SAPP" option as we are going to be transferring the SAPP from our personal wallets.

In the next step, we can see the address to which we have to deposit our SAPP. There is also some information on our deposit below the deposit address.

Use the drop-down menu to specify the percentage of your reward you will want to reinvest.

Now we send from our wallet to the address we see on Crypos, the coins we intend to invest.

The coins will be credited after 10 confirmations.

After reaching the 10 confirmations, we will see our masternode by clicking on the profile icon at the top right corner and then selecting my masternodes.

Now click on the "details" button.

On the next page, we can see the following information.

• Coins in shares (The coins we have invested)

• Coins value (The dollar value of our investment at the current price)

• 24h revenue (Expected returns in 24h)

• Overall revenue (The value of our earnings)

Below we can see the list of masternodes in which our coins are invested.

We can withdraw our funds at any time by clicking the icon highlighted in the image at the bottom right.

By going to our wallet we can check our received rewards.

How to stake on a VPS

In this guide, we are going to explain how to stake on a VPS server.

This guide is for advanced users and assumes that you know how to safely use an Ubuntu server.

We assume that you will run all the commands as root user.

First, we need to connect to our server via SSH and download the wallet we want to install, from our official links on GitHub.

In this case, we have chosen KYAN.

The wallet links can be found at https://github.com/kyancoin/KYAN/releases

We choose the Linux version and copy the link.

To download the wallet we use wget command.

wget https://github.com/kyancoin/KYAN/releases/download/v1.0.0.1/KYAN-1.0.0.1-Linux.zip

We now extract the archive using unzip command (if the command is not available you can run apt install unzip) unzip KYAN-1.0.0.1-Linux.zip

Now we copy the KYAN executables in /usr/local/bin folder to make them available as system command

cp kyanite* /usr/local/bin/

Let’s start the KYAN daemon and encrypt the wallet.

kyanited -daemon

kyanite-cli encryptwallet “YOUR-PASSWORD-HERE”

We can now create a system service to make sure our wallet will always run. nano /etc/systemd/system/kyanite.service

This command will open nano text editor where we paste the following.

[Unit]

Description=KYAN service

After=network.target

StartLimitIntervalSec=0

[Service]

Type=forking

Restart=always

RestartSec=10

User=root

ExecStart=/usr/local/bin/kyanited -conf=/root/.kyanite/kyanite.conf -datadir=/root/.kyanite

ExecStop=-/usr/local/bin/kyanite-cli -conf=/root/.kyanite/kyanite.conf -datadir=/root/.kyanite stop

[Install]

WantedBy=multi-user.target

We can now exit nano and save (ctrl+x, y, enter).

To apply the change we run this command systemctl daemon-reload

Now we need to setup the kyanite.conf file, we use nano again

nano /root/.kyanite/kyanite.conf

Paste the following lines in it:

daemon=1 server=1 rpcuser=kyanite rpcpassword=YOUR-RPC-PASS rpcallowip=127.0.0.1

staking=1

Save and exit nano.

The configuration is now complete and we can start the kyanite service and generate a new address.

systemctl start kyanite.service

kyanite-cli getnewaddress

While we wait for the wallet synchronisation we can transfer our funds to the address we just generated.

As the last step we need to unlock our wallet for staking. kyanite-cli walletpassphrase “YOUR-PASSWORD-HERE” 99999999999999 true

N.B. Coins need 600 network confirmations to start staking

You can verify staking status using the command below

kyanite-cli getstakingstatus

All the fields must return “true”

It is highly recommended to delete terminal history when we enter sensitive information like wallet passwords. It can be done simply using history -c command.

This guide explains how to optimize staking and solve the most common problems.

We open our wallet (in our case SAPP), and let's make sure staking is active.

Staking optimization

When staking, the larger the address balance the more will be earned. However, when we receive a reward, the coins are spent and it is necessary to wait for 600 confirmations to be available again for staking (mature)

It is therefore useful to divide the coins into different inputs through the setstakesplitthreshold command.

Whenever a successful stake is found, the stake amount is split across as many outputs (each with a value higher than the threshold) as possible.

E.g. If the coin stake input + the block stake reward is 30280, and the split threshold is 3400, the corresponding coinstake transaction will have 9 outputs (of 3400 SAPP each).

It is also possible to set the split value from the UI, Settings→Options→Wallet

Another useful command to know is setautocombinethreshold. Periodically the wallet will look for 'dust' in your addresses, and combine them up to the number of coins set in the configuration setting.

The command setautocombinethresholdtrue value will enable a feature that will automatically combine all staking / masternode rewards you receive into one input, up to the amount that you specify with the value.

So, if you want your minimum input size to be 5000 SAPP via the user interface, then you would want to follow the steps below:

1. Go to 'Settings' from your wallet

2. Select 'Options'

3. Choose 'Wallet' from the dropdown menu

4. Check the 'Autocombine threshold

Once done, any inputs less than 5000 will be swept into a new input, repetitively until the combined threshold is exceeded.

Once that threshold is exceeded, the grouping begins with another input. Your wallet MUST be unlocked when a reward is received for this to take effect.

Common problems

We can check the staking status in detail with the following command getstakingstatus

Below is an explanation of the result of the command.

• "staking_status": true|false, (boolean) whether the wallet is staking or not

• "staking_active": true|false, (boolean) whether the wallet is active or not

• "staking_enabled": true|false, (boolean) whether staking is enabled/disabled in sapphire.conf

For staking to be active, the first six values must necessarily be "true". Below we explain how to solve the most frequent problems you might encounter.

• haveconnections: if false, you don't have connections to the coin network. Make sure you have internet access, consider the port being blocked or bad connectivity.

• walletunlocked: if false, click the lock icon in the top right, select staking only, and enter your passphrase.

• mnsync: if false, wait 20 minutes. If still false, consider deleting mncache.dat and mnpayments.dat files from the data directory.

That’s everything you need to know about staking.

Earlier in the series on how to buy Decenomy coins with FIAT, we covered the account creation and verification process on Binance, and how to purchase Bitcoin (BTC) with your bank card.

Next in this series, we provide clear and concise steps to buy Decenomy coins after you've acquired Bitcoin on Binance. Without wasting much time, let's dive straight into the tutorial.

• In order to buy Decenomy Coins we now need to withdraw the Bitcoin on Binance to Birake exchange.

• After clicking 'Withdraw,' you'll be taken to the withdrawal page. Here, you may notice that you're on the 'Withdraw Fiat' page.

• To switch to 'Withdraw Crypto,' simply select the 'Withdraw Crypto' option located at the top right. Should you wish to withdraw fiat in the future, just simply switch back.

• At this point, we can see BTC is already selected as the coin we want to withdraw.

• We can also select Bitcoin from the network dropdown. However, at the moment we don't have a BTC address we want to withdraw, so we need to set up an account on Birake Exchange. Kindly refer to on Birake.

• Once you have your new Birake account verified, click on "Deposit/Withdraw" from the top menu to access the deposit page.

• From here we now need to select BTC from the dropdown list. Always double-check to ensure the correct coin is selected, as transactions cannot be reversed.

• Now we can see the BTC address to deposit to. We can select "Copy Address" or highlight the address and copy it. Ensure the complete address is copied

• Now that we have the address copied we can go back to Binance and paste it in there.

• Then double-check we still have Bitcoin selected as the network.

• Next, we can input how much we want to withdraw. In this case, we will select "MAX".

• You can then see the amount we will receive when we scroll down.

• Review the transaction and click on 'Continue' when you are sure.

• Complete the security verification requirements to proceed

• After satisfying the security verification requirements, you will receive a confirmation window indicating that your withdrawal is pending review. Click on "Completed" to finish the withdrawal process.

• You will then be returned to the withdrawal page, down the bottom, you can see the transaction is being processed and awaiting confirmation.

• The time it takes for the transfer to happen can vary greatly with Bitcoin. Usually, if sent from Binance, you will get an email confirming it has been completed.

• After a while, we can go back to Birake and we can see the Bitcoin has arrived.

Once you have the Bitcoin credited to your Birake account, refer to .

We demonstrate how to exchange Bitcoin for Sapphire (SAPP). The same procedure can be applied to other Decenomy coins.

Birake Account Creation Process

• Head over to https://trade.birake.com/

• Click on "Create Account / Login" from the top menu bar.

You will be redirected to the account creation page where you will have to fill out the form with:

1. Your desired Account Name

2. Email address

3. The password is already generated. You just have to copy and paste it into the "Confirm password" field.

4. Select the three checkboxes to confirm you agree to the terms. Then click on the "Create an accoun

We advise you to keep your password safe to avoid any difficulties accessing your account. Please store your password securely.

Birake KYC Verification Process

After successfully creating an account, it will be necessary to verify it with an identity document. This will enable you to deposit and withdraw funds.

• Click on the profile icon at the top right corner of the screen and choose "Verification" from the list.

• Existing users are also required to undergo a new KYC process with the new provider. Please click on the 'RESEND' button, and an email will be sent containing a link to complete the KYC process.

• To initiate the KYC process, you will be required to verify your phone number.

• Following that, you will receive an SMS on the provided phone number containing the KYC link. Ensure that you complete the process directly on your phone, as copying and pasting the link into your browser may not work.

• On the subsequent page, please agree to the privacy consent and click on 'Continue.'

• Select the 'Capture my ID' button to photograph the front page of your National ID card.

• Repeat the process for the back of your ID card by clicking on the 'Capture my ID' button.

• After the ID verification, you will have the opportunity to review your ID details. While most fields will be automatically generated, it is crucial to verify their accuracy. If any information is incorrect, you will be able to make the necessary changes.

• Check the checkbox to confirm your agreement with the consent policy once again. When you are certain that your details are accurate, click on the "My details are correct" button.

• Next, you will be required to finalize the face verification process by recording a selfie video.

• Once you have finished the KYC process, you will be notified with a success message confirming your verification.

Accounts are usually verified within 2 - 3 mins. When your account is verified you will be able to make a deposit.

In this quick and easy tutorial, we'll walk you through the steps to deposit and withdraw your assets on the Birake exchange platform. Let's get started!

Deposits

• While logged in to your account, navigate to the top menu bar and select "Deposit / Withdraw". We are going to use Bitcoin (BTC) for demonstration.

You will be sent to the deposit and withdrawal page. From there we choose

1. BTC from the drop-down menu

2. Select Deposit

3. And copy the address provided

We can now send our Bitcoins to the newly copied deposit address.

After about a few minutes we will have our Bitcoins on Birake, as we can see from our Current balance:

Withdrawals

• To initiate a withdrawal, you need to go to the deposit and withdrawal page from the main navigation menu. In this case, we will be using Sapphire (SAPP) for demonstration.

• Select SAPP from the dropdown menu

• After choosing SAPP,

1. Click on WITHDRAWAL

2. Then Click on WITHDRAW NOW

On the bottom left of our window is where we have our current balance.

• Now let's open our Sapphire wallet

1. Click on Receive

2. Copy the address

• Once the address has been copied, we return to Birake.

1. Click on AVAILABLE (to withdraw the full amount available)

2. Paste the address previously copied from our Sapphire wallet

3. Click WITHDRAW

• We confirm and wait for the withdrawal request to be processed.

• We will then check our Sapphire wallet in a while to confirm receipt.

DSW stands for Decenomy Standard Wallet and is a cryptocurrency platform part of DECENOMY, a project network that shares the same wallet codebase and blockchain infrastructure, enabling cross-chain interoperability and governance among the DECENOMY projects. DSW is a PIVX fork based on DASH, which is also based on Bitcoin. One of the features that DSW supports is changing collateral values for masternodes, opposite to DASH and PIVX where the collateral is constant.

Fixed collateral value variation and their disadvantages

Masternodes are special nodes that provide services to the network. To run a masternode, one must lock a specific amount of DECENOMY coins as collateral. The collateral amount is currently determined by a fixed table specifying the collateral value for each block height range. However, this fixed system has some disadvantages, such as:

• It does not reflect the dynamic changes in the market conditions and user preferences, which may affect the supply and demand of DECENOMY coins and masternodes.

• It does not allow for fine-tuning of the collateral amount to achieve an optimal balance between risk and reward for masternode operators and investors.

• It may create barriers to entry or exit for masternode operators, who may need to acquire or dispose of a large number of coins to meet the collateral requirements or the assembly of an abnormal number of masternodes.

To overcome these limitations, a new feature called Dynamic Collaterals is proposed.

Introducing Dynamic Collaterals

Dynamic Collateral is a feature that will change the collateral value at every 100000 blocks, based in:

• evaluation of the current coin supply,

• a predefined target percentage of the supply locked in masternodes,

• desired number of masternodes in the network.

The idea behind Dynamic Collaterals is to adjust the collateral amount according to the market conditions and the network needs, ensuring a balance between supply and demand, security, and decentralization.

How Dynamic Collaterals Work

The change in collateral value will be limited by a minimum percentage and a maximum percentage, for example, if we have a percentage range of 10% and 20% means that in each collateral change the value will change only within that range or not at all. The changes are also valid for supply reduction in cases when a certain quantity of coins gets burned within the running period. These changes are also limited in terms of value steps, they will only change in steps of 1000 coins. The moment that this calculation takes place is on the block created 7 days before the collateral change, giving time for the investor to adjust their masternodes accordingly for the next epoch.

For example, suppose that:

• the current coin supply is 1 billion DSW,

• the target percentage of locked supply in masternodes is 70%,

• the desired number of masternodes is 2880, which means that each masternode should receive a reward every alternate day (assuming 60 seconds per block).

Then, the collateral amount can be calculated as follows:

Collateral = (Coin Supply x Target Percentage) / Desired Number of Masternodes Collateral = (1 billion x 70%) / 2880 Collateral = 243055 DSW

This means that to run a masternode, one needs to lock 243000 DSW coins as collateral (rounded down to a multiple of 1000 coins). This amount will be valid for 100000 blocks, after which it will be recalculated based on the new coin supply, target percentage, and desired number of masternodes.

Suppose that after 100000 blocks:

• the coin supply has increased to 1.3 billion DSW due to new minting,

• the target percentage and desired number of masternodes remain unchanged.

Then, the new collateral amount can be calculated as follows:

Collateral = (Coin Supply x Target Percentage) / Desired Number of Masternodes Collateral = (1.3 billion x 70%) / 2880 Collateral = 315972 DSW

This means that to run a masternode, one needs to lock 315000 DSW coins as collateral (rounded down to a multiple of 1000 coins). However, since this amount exceeds the maximum percentage change of 20%, it will be capped at 291600 DSW (243000 x 1.2); in this case, 291000 DSW coins a multiple of 1000 coins. This amount will be valid for another 100000 blocks.

The Benefits of Dynamic Collaterals

• It allows for more flexibility and adaptability of the network to changing market conditions and user preferences.

• It encourages more participation and investment in masternodes by adjusting the collateral amount to an optimal level that balances risk and reward.

• It creates more opportunities for masternode operators, who can benefit from price fluctuations and arbitrage possibilities.

Dynamic Collaterals is still a work in progress and a small component of the overall DECENOMY vision and may require further research and testing before implementation. However, it is an exciting and promising feature that may bring more value and utility to the DSW platform and the DECENOMY network.

Let's open our wallet (in this case Monk)

The collateral has increased from 4000 to 8000 Monk and apparently from the masternodes menu our masternode is missing.

We need to unlock the old collateral (the previously blocked 4000 coins transaction).To do this we go to

• Send

• Coin Control

Now a window will open, as we can see in the image the masternode transaction is labeled with a padlock icon.

We have to right-click on it and choose "Unlock unspent" from the list to unlock it.

Now we need to send a new 8000 Monk transaction to ourselves.

So

• Click on Receive

• Generate a new address

• Modify the label (we use the name of the old masternode again in our case MN1)

• Let's copy the address

Now let's go to the menu

• Click "send"

• Paste the address

• Insert precisely 8000 in the amount

• Click send

Now we click send to confirm the sending of the funds.

Now let's go back to the home screen and we can see that the payment to ourselves is confirmed after 6 confirmations (about 6 minutes).

Now let's go to the Debug Console and click on it.

The debug console will open where we have to enter the command below:

• getmasternodeoutputs

Press enter to get the following information

• hash of the transaction

• outputidx

Let's go to masternode.conf and click on it.

This will open Notepad and we will need to replace the following:

• hash of the transaction

• outputidx

From the console we copy

• hash of the transaction

• outputidx

Let's replace them in Notepad. We the save the file after the changes and restart the wallet.

From the home screen

• Click on masternodes

• Click on the three dots and choose start

Now that the collateral is up to date, our node is ready!

Cryptocurrency networks, fueled by their underlying technologies, are in a perpetual state of innovation. Masternodes, critical in their functionality, play a significant role in ensuring the integrity and security of these networks. Recently, discussions have been made proposing a groundbreaking shift - implementing a progressive collateral model for masternodes.

Introduction

Coin Info

• GitHub • Wallet Download • Bootstrap • Explorer 1 • Explorer 2

EBF system is still in the work-in-progress phase

Enhanced Blockchain Features (EBFs) refer to functional extensions of a regular UTXO-based blockchain, such as Bitcoin. Comparable to Ethereum contracts, EBFs are stateful and Turing complete, providing the ability to compose functionalities that complement and strengthen the regular stateless UTXO model. However, it is noteworthy that EBFs should not be authored or released by the general public since they will extend and interact with vital components of the blockchain. Such crucial components include the capacity for generating new coins, thereby rendering EBFs a high-security standard and sensitive element. EBFs amalgamate the practicability and determinism of a blockchain's UTXO model with the strengths of natively developed Turing complete functionalities.

Structure

Enhanced Blockchain Features (EBF) infrastructure comprises multiple platforms, each designed to accommodate a set of interrelated additional functionalities. Each platform comprises contracts with various methods, each being assigned specific and unique tasks. It is critical to ensure that each method is fully deterministic and adheres to the principles of single responsibility and separation of concerns to enhance the efficiency and reliability of the EBF platform. By adhering to these principles, the EBF platform can offer a stable and dependable environment for executing contracts, thereby ensuring the security and stability of the blockchain ecosystem.

Messaging

To invoke a contract method on an Enhanced Blockchain Features (EBF) platform, an EBF message must be issued. These messages are expressed as OP_RETURN script transaction outputs on regular transactions. To distinguish them from regular OP_RETURN scripts, EBF messages are identified by starting with an OP_RETURN opcode and two checksum bytes.

Digital signatures are utilized to ensure the authenticity and integrity of EBF messages. The signatures are generated using the sender's private key, and executed against the entire transaction, thereby preventing a replay attack and preventing the need for a nonce field. In this manner, the EBF platform ensures that the same message cannot be used to modify the blockchain multiple times.

The following fields describe the EBF message generic envelope:

Message Processing

The processing of EBF messages involves several steps. First, the transaction containing the EBF message must be validated according to the blockchain rules. This includes checking that the inputs are valid and that the sender has the necessary funds to cover the transaction fees. Once the transaction is validated, the EBF message is extracted from the OP_RETURN output script.

Next, the EBF message is deserialized, and the contract method specified in the message is located. The contract method is then executed, and any necessary state changes are made to the blockchain. This may involve modifying the balances of accounts or updating the state of smart contracts.

It is essential to note that EBF messages are executed deterministically, and any state changes must be consistent with the blockchain's current state. This ensures that the blockchain remains secure and that all nodes in the network can reach a consensus on the current state of the blockchain.

Due to blockchain technology's decentralized nature, blockchain network blocks may be subject to reorganization. Consequently, each contract method deployed on an Enhanced Blockchain Features (EBF) platform must have a robust process to handle reorganization events and restore the contract to its prior state in such an event. In the context of the EBF platform, a reorganization refers to a mechanism that restructures the blockchain network in response to a network-wide consensus failure, ensuring the integrity and consistency of the blockchain. The reorganization process is critical in enabling the EBF platform to maintain a reliable and secure environment for executing contracts, minimizing the risk of failure, data loss, inconsistency, or corruption during a blockchain reorganization.

In summary, the processing of EBF messages involves validating transactions, extracting and deserializing EBF messages, locating and executing contract methods, making necessary state changes to the blockchain, and preventing replay attacks through the use of transaction signatures.

Block Processing

The validation of transactions constitutes a critical step in processing blocks within the EBF infrastructure. Upon adding a new block to the blockchain, it is imperative to ascertain the validity of the transactions contained within it and to ensure they conform to the regulations stipulated by the EBF platform. This validation procedure comprises a comprehensive review of the EBF messages and the digital signatures embedded within them, an examination of the transaction inputs and outputs, and a check to ensure the absence of double-spending and invalid EBF states. The nodes within the network undertake the validation process and participate in the consensus protocol, arriving at a collective agreement on the veracity of the transactions within the block. Upon successful validation, the transactions are appended to the block and propagated to the other nodes within the network. The block processing mechanism within the EBF infrastructure closely resembles that of the conventional blockchain, with the additional layer of EBF validation superimposed upon it.

The proper execution of smart contracts constitutes another pivotal aspect of block processing on the EBF infrastructure. Smart contracts represent self-executing software programs that operate on the blockchain and automate the execution of predetermined rules and conditions. This feature is deemed essential for the EBF platform, as it facilitates the integration of more sophisticated features that can interact with the network in real-time. The execution of smart contracts entails the validation of the input data that is passed through messages, the execution of the underlying code, and the updating of the contract state. The nodes within the network undertake the task of executing smart contracts, where they execute the contract code and arrive at a consensus on the updated contract state.

State management

State management is another crucial aspect of block processing on the EBF infrastructure. State refers to the current state of the blockchain network, which includes the balances of accounts, the state of contracts, and the current state of the consensus protocol. State management involves updating the network state based on the transactions included in the block and the execution of smart contracts. Nodes in the network perform this process by maintaining a copy of the current state of the network and updating it as new blocks are added to the blockchain. State management plays a vital role in ensuring the consistency and integrity of the blockchain network by ensuring that the current state of the network reflects the latest valid transactions and contract executions.

Welcome to DECENOMY Documentation We strive to provide comprehensive support for various features and tasks in the POS/MN space through our informative articles, which include text, video, and pictures, to ensure clarity and ease of understanding.

Our documentation is a continuous effort and will be constantly updated and expanded as we deem it necessary to include more helpful information. Please use existing categories for efficient searches:

This guide assumes you have an account and the coins needed to start a masternode in your local wallet. As soon as you log into ihostmn.com you will find yourself on the dashboard.

You will need to deposit a small amount via Paypal or cryptocurrency, to pay the monthly fees of your masternode (necessary to pay the hosting service offered by ihostmn.com) . Click on "Fund account" in the left menu to proceed.

Once the payment has been made, the funds will be immediately available in your account.

We can now click in the left menu on the “Masternode hosting” link. You will see all the coins available on the website, in our case we have chosen to run a MONK masternode. You can search MONK or any other coin using the search bar on the top.

Required

• Masternode collateral Valid collateral amount related to the current block as well as each blockchain specification. Please review the information presented on this website in the section. Within each coin information, the collateral values are listed below on the Rewards Breakdown

Being a public API, there is no need to use any kind of authentication.

API v1 reports plain text. API v2 reports more info in detail.

API v1 Endpoint URL

https://explorer.decenomy.net/api/v1/coins/coin/

Path parameters v1

Query parameters v1

Example query v1

Example response v1

API v2 Endpoint URL

https://explorer.decenomy.net/api/v2/coin/

Path parameters v2

Query parameters v2

Example query v2

Example response v2

Coin Info

• GitHub • Wallet Download • Bootstrap • Explorer 1 • Explorer 2

Coin Info

• GitHub • Wallet Download • Bootstrap • Explorer 1 • Explorer 2

Introducing Last Paid V2

One of the features of the masternode system is the ability to track when a masternode (MN) was last paid. This information is helpful for determining the order of payments and the expected time until the next payment. However, the previous standard method of calculating the last paid value of an MN has some flaws and inaccuracies that can affect the fairness and efficiency of the payment system. The last paid v2 is a new feature that aims to solve these problems and improve the accuracy and reliability of the last paid value.

Challenges and limitations of the standard version

The previous standard method of calculating the last paid value of an MN is based on the number of votes that an MN receives from other MNs in the network. The inherited masternode system uses a voting mechanism to select which MN will receive the next payment. Each MN casts a vote for another MN that it thinks should be paid next based on various criteria, such as the last paid value, the protocol version, and the collateral age. The MN that receives the most votes in a given block is selected as the winner and is elected to be paid.

However, this voting mechanism has some drawbacks and limitations.

• It relies on the assumption that all MNs are online and voting correctly, which may not always be accurate. Some MNs may be offline, malfunctioning, or maliciously voting for themselves or their possible colluding partners.

• It does not account for the actual time when an MN was paid but only for the votes it received. This means that sometimes an MN may lose a payment round because it received fewer votes than another MN, even though it was truthfully waiting longer to be paid.

• It does not provide a clear and consistent way to measure the last paid value of an MN across different nodes in the network. Different nodes may have different views of the voting history and may disagree on which MN was last paid and when.

Introducing a Blockchain-based solution

The last paid v2 is a new feature that addresses these issues and replaces the old voting mechanism entirely. Instead of using votes to determine when an MN was paid, it uses the blockchain itself as the source of truth.

• The blockchain tracks and records every payment made to an MN in a field called payee.

• The last paid v2 algorithm scans the blockchain from the most recent to the oldest block and looks for this field to identify when an MN was paid.

• It then assigns a last-paid value to each MN based on the block height of its last payment.

This way, it can accurately and objectively determine which MN was waiting longer to be paid and select it as the next winner.

Advantages of Last Paid V2

The last paid v2 has several advantages over the old voting mechanism.

1. It does not depend on external factors such as network connectivity, node availability, or voting behavior. It only relies on the blockchain data, which is immutable and verifiable by anyone.

2. It reflects the actual time when an MN was paid, not just the number of votes it received. This ensures that every MN has a fair chance to receive a payment based on its waiting time, not popularity, influence, or luck.

3. Provides a consistent and transparent way to measure the last paid value of an MN across different nodes in the network. Every node can easily calculate and verify this value by scanning the same blockchain data.

The last paid v2 is a significant improvement for the masternode system and for DECENOMY coins as a whole. It enhances the accuracy and reliability of the payment system, increases its fairness and efficiency, and reduces its complexity and potential for errors. It also makes DECENOMY coins more attractive and competitive as a cryptocurrency that rewards its users for securing and supporting its network.

Coin Info

• GitHub https://github.com/decenomy/BECN • Wallet Download https://github.com/decenomy/BECN/releases/latest • Bootstrap https://explorer.decenomy.net/bootstraps/BECN/bootstrap.zip • Explorer 1 https://explorer.decenomy.net/BECN • Explorer 2 https://becn.flitswallet.app/

Tutorials

• Wallet Guide • Masternode Guide • Masternode Setup Guide ( non multinode )

Social

• Twitter • Discord • Telegram Channel • Telegram Group

Price, Staking and Masternodes Statistic

• CoinMarketCap • Coingecko • Vaultwatch • Masternode Online

Coin Specs

• PoW Algorithm: X11KVS • Premine: 1,700,000 BECN • PoW Blocks: 1 - 1000 • PoS Blocks: Starting from 1001 • Block Time: 60 Seconds • Maturity: 100 Confirmations • Prefix: BECN adresses start with the lower case letter "b" • Ports: 36552 (p2p) / 36553 (rpc)

Rewards Breakdown

Sporks are a feature that offers a way of implementing upgrades or changes to a blockchain network without requiring a hard or soft fork. Sporks allow the network to switch between the old and new rules at a specific block height or time, depending on the consensus of the nodes.

Sporks are different from forks, which are permanent changes to the network that require all nodes to upgrade or risk being left behind on an incompatible chain. Sporks are also different from soft forks, which are backward-compatible changes that do not require nodes to upgrade but may reduce their functionality.

How do Sporks work?

Sporks work by allowing cryptocurrency developers to change some network parameters without requiring all nodes to upgrade their software. Sporks are literally switches that the developers can turn on or off using a special private key. Sporks can activate new features, fix bugs, or adjust network settings.

What are the Benefits of Sporks?

• They allow for faster and smoother network upgrades without disrupting the network's normal operations.

• They give the developers more flexibility and control over the network parameters and features, allowing them to adjust them according to the changing needs and demands of the users.

• They reduce the risk of network splits or chain reorganizations when nodes disagree on the validity of blocks or transactions.

Some Examples of Cryptocurrencies using Sporks

• Dash is a digital currency that uses sporks to activate new features such as InstantSend and PrivateSend without disrupting the network.

• Zcash is a privacy-focused cryptocurrency that uses sporks to control the activation of network upgrades such as Sapling and Heartwood.

• PIVX is a fork of Dash that also uses sporks to implement changes and improvements to the network. PIVX stands for Protected Instant Verified Transactions and aims to provide fast, secure, and private transactions.

Coin Info

• GitHub • Wallet Download • Bootstrap • Explorer 1 • Explorer 2

Coin Info

• GitHub • Wallet Download • Bootstrap • Explorer 1 • Explorer 2

This documentation page provides an overview of the improvements that are being made to the DSW wallets.

New Features