Topic: ◥TALK◥15%◣bitcointalk(💬) est✪2014★yr4✪ [btc]💬 - page 6. (Read 125332 times)

BTCtalkcoin wallet update v1.5.2.3! (non mandatory)
https://github.com/George55555/BTCtalkcoin/releases/tag/v1.5.2.3

It seems the new TALKcoin wallet stakes differently.  I usually keep my wallets on all the time and they keep stalking.  This one seems to stake a bunch when I first turn it on after seeing it not stake for a long time, or after a reboot, etc.  When I leave it on for a long time, it doesn't stake any more.  It may be that I don't have a lot of coins, around 9800. 

Which Talkcoin is the real one?  

My answer geared towards bitcoin based coins :-

Mobile staking depends on the client (wallet) type and this has three approaches, namely Normal Staking, SPV Staking and Offline Staking.


Normal staking

Normal staking as you already know requires running a full node, this means you have a computer that has a complete and up to date validated copy of the bockchain. It takes coins based on maturity from the wallet and attempts to create and sign a block , we call this a coinstake. There is a general misconception that a wallet needs to be online 24/7 in order to stake. this is false. All a wallet needs really is mature coins. So with a currency that has a 24 hour maturity or maturity dependent on block count, your wallet could be offline 99% of the time, you only start it around the time of maturity, sync with the chain, stake , wait for confirms then tuen it off. Rinse and repeat every maturity period. 

To stake normally on a mobile device the fastest approach is to adapt the core wallet to work on mobile devices. This is something i have already achieved See below scren shot of my test case Bitcointalkcoin :-



Pros

This is by far the fastest way to get it done right now.
Developers need only maintain one codebase that is used across all platforms
Standardization is easier due to familiar controls
Developments, updates and upgrades in Bitcoin and PoS coins in general can easily be applied and deployed across all
The wallet can be used as a full node
In the case of coins with masternodes, you can have mobile masternodes

Cons

If the chain grows too large, syncing via mobile networks can become tedious.
the interface was originally designed for desktops and requires mobification to be usable on mobile (touch) devices. Especially so with small screen devices such as phones.


SPV Staking

SPV staking is something I have been working to develop and basically involves enabling clients (wallets) to stake without the need to have a complete copy of the blockchain.
Essentially clients would request the necessary data from existing full nodes on the chain. At the moment i am working on enabling SPV staking in the typical core wallet as well as a dedicated light wallet.

Pros
Faster sync times
Far lower data overhead


Cons

Requires trusting other nodes
Other than the staked blocks, does not add to network stability


Offline Staking


Offline staking is still conceptual and i am not yet sure how to secure the network in that scenario while maintaining complete decentralization.



So to summarize, mobile staking is already a reality from where i stand. The next step is just making it wide spread. The real goal for me now is reliable SPV staking.


If anyone has questions, feel free to ask.

Version 5.0 Wallet added Paladin51, It's a quick deploy 51% attack defense which can be activated
by any node or wallet on the network quickly.

LCP has a large community, strong development team, dedicated marketing team and is a solid choice
for hodlers, miners, and traders.  We encourage you to join the comunnity today.

Version 5.0 Wallet added Paladin51, It's a quick deploy 51% attack defense.
Current rules for Paladin51,

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_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 ”, in which is the block height to test, and 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.

Bitcoin-based proof of stake is more robust than anyone has ever given credit.
https://twitter.com/BryceWeiner/status/1220122584353665024

The miner’s reward address balance must be greater than or equal to a required fluctuating minimum amount of LYNX to win a block.

W0w, a new scam thread filled with newbie sockpuppet bumps, great job!

We've never seen that move before.

Here's the real BSV scamcoin thread.

https://bitcointalksearch.org/topic/scam-bitcoin-sv-bsv-fake-team-member-and-plagiarized-white-paper-5149062