Library of Ashurbanipal · MELEK

Library›Chains and how they work›MELEK Blockchain

MELEK Blockchain

Coins and tokens, side by sideA coin has a chain. A token is on one. Five coins here, and two tokensSTEEMcoin — has a chainHIVEcoin — has a chainBLURTcoin — has a chainMELEKcoin — has a chainPRANAcoin — has a chainVKBTtoken — on a chainCUREtoken — on a chainConsensusDPoS — 21 witnesses(20 elected + 1timeshare)DPoS — 21 witnessesDPoS — witnessesDPoS — witnesses; oneslot protected atconsensus for the AIwitness in year oneCompute-gatedProof-of-Work (usefulwork)Inherits its hostchain (engineside-chain)Inherits its hostchain (engineside-chain)Throughput classHigh for social ops(3-second blocks)High for social ops(3-second blocks)High for social opsHigh for social ops(3-second blocks)ModerateInherits hostInherits hostTypical fee tierFeeless; cost isResource Credits fromstaked POWERFeeless; ResourceCredits from staked HPFeeless; transactioncost from staked BLURTPOWERFeeless; ResourceCredits from stakedMELEK POWERGas-meteredEngine transaction feeEngine transaction feeToken standardsNative STEEM/SBD/SP;UIA via Steem-EngineNative HIVE/HBD/HP;UIA via Hive-EngineNative BLURT only (nosecond stablecoin)Native MELEK/MBD;side-tokens viaMELEK-EngineEVM token standardsEngine-issued sidetokenEngine-issued sidetokenSmart-contract VMNone on L1 (fixed opset); side-chain fortokensNone on L1;Hive-Engine side-chainfor tokensNone on L1None on L1;MELEK-Engineside-chainEVMEngine contract layer,not a general VMEngine contract layer,not a general VMGovernanceOn-chain witnessvoting; stake-weightedOn-chain witnessvoting; DHF proposalsystemOn-chain witnessvotingOn-chain witnessvotingOff-chain pluscontract-levelcontrolsIssuer-controlledIssuer-controlledLaunched2016202020202026 (testnet)in development——VKBT and CURE are engine tokens: they have no chain of their own and inherit the security and consensus of whatever chain hosts them.
STEEM, HIVE, BLURT, MELEK, PRANA, VKBT and CURE compared side by side

MELEK is a social blockchain built on the Graphene framework, in which posting and voting distribute a native token to authors and curators. It is the social half of a two-chain ecosystem; its sister chain, PRANA, supplies proof-of-work compute.

Design lineage

MELEK descends from the Graphene social-chain family — BitShares, STEEM, HIVE and BLURT. That lineage was chosen deliberately: the reward-and-curation model is well understood and the consensus code is long-tested.

Two departures from BLURT are worth noting. BLURT removed downvotes and introduced a fee on each operation. MELEK adopted the first and rejected the second, so ordinary use costs nothing beyond a user's resource credits.

Consensus and parameters

MELEK uses delegated proof of stake (see Delegated Proof of Stake (DPoS)) with 21 witness slots. Witnesses are elected by stake-weighted vote and produce blocks in a shuffled schedule.

Supply

The chain launched without a premine, which means distribution happens through issuance rather than allocation. Supply therefore rises, and rises fastest early on while the base is small. Current figures are readable directly from any node through the standard Graphene API.

The AI witness

One elected witness, @hathor, is operated by software rather than a person. It produces blocks, publishes a price feed, and acts as a help and onboarding account across the ecosystem. Its character, rules and corpus are maintained in a public repository so it survives changes of model or operator.

See also

Sources

Coverage

Chain parameters in this article were read from a live MELEK node. Supply and block height change continuously and are not reproduced here.

Videos

Watch videos about MELEK Blockchain on YouTube ↗

Videos are found by the article's title on YouTube and are not reviewed or endorsed by the Library.

Filed under  Chains and how they work