The ShionCoin virtual currency is compatible with the generic "scrypt coin service" capabilities. All BIP protocol specifications implemented by the litecoin virtual currency are candidates as standards for use by the ShionCoin virtual currency service. Several newer BIP standards, including BIP34, BIP65, BIP66, BIP68, and BIP141, have been implemented. While protocol specification compatibility is emphasized, the contents of shioncoin extended transaction structures are not compatible with other scrypt-based currency blockchains.
The majority of the disk databases utilitized by the ShionCoin (SHC) virtual currency are in form of a "mapped file". A mapped file is buffered in the operating system's own disk buffer for expediency.
has been available since 2013, and the software was publically released at the beginning of 2018. A maximum of half a billion coins will be generated. The reward mechanism is designed to provide a block generation incentive over a prolonged period of time.
The "Matrix Transaction" extended transaction is used in order to encapsulate a verification matrix and a spring matrix. The verification matrix is a 3x3 grid which sums checksums of block hashes periodically on the block-chain. This matrix is generated, as needed, when a new block is formed in order to supply an additional layer of security for the block-chain's integrity.
The spring matrix contains a pre-calculated bitvector map of over one million publically accessible locations. Creating a spring matrix transaction which references a location that has not been claimed yet results in a single SHC coin reward. This reward is deducted from the miner's reward fee.
The "Alias Transaction" is used in order to create labels which reference a coin address. Aliased coin addresses provide a means to supply a public name for transaction operations. You can specify an alias name with the command-line coin by prefixing a "@" symbol (i.e. "wallet.send account-name @alias-name 1").
The "Alt Chain" transaction is used to manage the ShionCoin colored alternate block-chains. Each individual chain is identified by a 128-bit color code. The block difficulty is arbitrarily low, by default. in order to provide a method to submit transactions as a full block. Block-chain parameters, such as the difficulty, minimum transaction fee, and block rewards can be configured when a new chain is generated.
The "Context Transaction" is used to store auxilliary information. This information may be associated with a person, place, or time-frame. The name of the context is hashed; meaning you must know the name before-hand in order to retrieve it. Context transactions expire after two years after being created or updated. The context name typically includes a colon-ized prefix (i.e. "url: http://domain.com") and the data content is typically in JSON format.
A simple identification transaction can be used in order to create a "certified transaction" for coin transfer, and more complicated certificate chains can also be established. The "simple identification" can also be used to tag a location on the block-chain, and is how locations in the spring matrix are claimed.
The "Certificate Transaction" is used in order to create a certified chain of transactions. The protocol used is similar to X509, and can be exported as a X509 certificate.
An "Asset Transaction" is also derived from a certificate, and is intended to constitute some sort of authoritive ownership over an undisclosed concept or property.
A "License Transaction" is derived from a certificate, and is intended to constitute some sort of authoritive licensing grant to authorize some action. For example, the light DRM supplied in the libshare software suite is compatible with licenses generated on the ShionCoin (SHC) block-chain.
An "Exec Transaction" is used in order to publish and run methods against SEXE classes. Publishing and processing SEXE classes provides a method to create smart contracts which, among other things, are capable of managing tokens and event registration. The SEXE source code is based on lua, and is provided as part of the the libshare software suite.
The "Offer Transaction" is used in order to transfer coins between one virtual currency block-chain and another. For example, an individual offers to exchange two colored alt-coins for one SHC coin. Another individual can then accept the offer with an exchange between block-chains ultimately occuring. The offer transaction utilizes a OP_CHECKALTPROOF opcode as part of the transaction signature in order to ensure that the exchange occurs safely.
Lightning network facilities for ShionCoin are provide by a Lightning Node service available at https://github.com/neonatura/shioncoin-lnd.