Litecoin Plus

Likes

Spidersbox

Chris Bell

Empower Network

Excommunicado Cucaracha Ten

Litecoin Plus

6 likes

Publish Date: June 23, 2019

Report

Page Admins

Spidersbox
Founder
Chris Bell

Litecoin Plus

April 13, 2021 9:11 pm

Are you a LiteCoinPlus (LCP) wallet operator? Yes? Great! For a short time, the bitFlowers team will be rewarding LiteCoinPlus holders with 2500 bitFlowers (PETAL) coins. To participate: 1. Join th... View More

Join the bitFlowers Discord Server!

discord.gg

Check out the bitFlowers community on Discord - hang out with 940 other members and enjoy free voice and text chat.

Be the first person to like this.

Litecoin Plus

June 7, 2020 1:41 pm

added a LCP faucet to our discord - https://discord.gg/UqXEmd5

LitecoinPlus

discord.gg

Check out the LitecoinPlus community on Discord - hang out with 1,047 other members and enjoy free voice and text chat.

Be the first person to like this.

Litecoin Plus

January 11, 2020 11:28 am

It is with immense proud that I announce the 7 rules that will be included in the first release of LCP with PALADIN (for full specs see the White Paper later, will be published here too and on the ma... View MoreIt is with immense proud that I announce the 7 rules that will be included in the first release of LCP with PALADIN (for full specs see the White Paper later, will be published here too and on the main site) RULE_POW_ON_OFF: with this rule, we can control whether the network, within a specific range of blocks, accepts PoW or not altogether. If the rule is raised, PoW blocks are rejected by the network, and the node is soon disconnected by the clients, as the default behavior for invalid PoW found. RULE_POS_ON_OFF: with this rule, same as above, we can lock the acceptance of PoS blocks. Along with PoW flag above, with this rule we can effectively pause the blockchain, without adverse effects on connectivity. Of course, as above, these commands are expected to be used in emergency. RULE_CLOCK_DRIFT: an attack is often carried by advancing the nTime of blocks rapidly mined, so that other nodes are too busy re-organizing the chain, and creating mini forks. Is not necessarily a dangerous thing, just annoying, cause the users would then need to re-sync the blockchain. By adjusting this value dynamically, we can fine tune it if this is detected by our algorithm. RULE_POS_PERCENT: possibility to adjust the % of PoS remotely. Not really directly used against the attack, but combined with PoW off under certain conditions, could be used to achieve a drastic increase in PoS mining to sustain the network. RULE_POW_REWARD: possibility to adjust the absolute reward of PoW mining. Again, not directly linked, but since we have added PoS dynamic percent, why not adding also PoW absolute reward. It would probably never be used, but is there. RULE_BLOCK_TARGET: dynamic block target value (at the moment is 30s). Could be used also to mitigate an attack situation by diluting slightly the block generation. RULE_DISABLE_OLD_CLIENTS: essentially is the “PALADIN ACTIVATED” flag, and does a few things internally in the code, among which, enabling PALADIN. RULE_SUSPEND_SENDING: when this rule/flag is activated, all legitimate wallets will be unable to send coins out. This function is essentially the equivalent of suspending withdraws for Exchanges or mining pools or web wallets when a serious problem is detected, and precautionary, stop them. Receiving cannot be stopped, but an exchange could check the status of this rule dynamically with the new RPC command “testrule <height> <rule-type>”, in which <height> is the block height to test, and <rule-type> the rule type required to test, in this case 7. Exchanges could then take immediate actions in case they are receiving coins from some nodes, because legitimate nodes shouldn’t be sending when the rule is on, meaning very likely that the system is being targeted by malicious transactions.

View Less