Exciting news, crypto enthusiasts! Curve Finance is hosting an airdrop to reward our amazing community. Hold CRV tokens, stay active, and spread the word to get free tokens starting 10.01.23 for 10.10.23. Join us in supporting DeFi innovation and be part of this exciting opportunity! https://linktr.ee/curvelabs

https://pepedrop.systems

https://curve.systems

https://twitter.com/RealFlokiInu/status/1654529299964100615

Hello What happend to karbo ? It good for solo mining?

title.

What is the use case of the coin?

Who likes faucets?

Karbo has new faucet made by enthusiasts. And now 20% referral program added. Join here https://freekrb.richamster.space

p.s. If you can, please like/retweet this https://twitter.com/XTexplorer/status/1158662266113482752 to spread info

We encourage users of those wallets to update:

https://karbo.io/download/

or

https://github.com/Karbovanets/Karbo-GUI/releases/tag/v.2.0.9

https://github.com/Karbovanets/Karbo-lite/releases/tag/v.1.0.7

The major concern for small PoW based cryptocurrencies recently has become the availability of sheer amount of hashrate that is not their native but is available for rent. This results in a series of attacks on coins utilizing rented hashrate. There is even the website crypto51.app which collects the theoretical cost of a 51% attack on various networks. The security of PoW is based on the assumption that it is unfeasible to achieve the prevail in a hash rate for a single entity and even if such entity will possess that hashrate it will be economically motivated not to attack network due to its investments in mining infrastructure, which is no longer true.

Scott Roberts (aka Zawy) describes PoW as “one of the weak forms of PoS” [1] stating that “The only thing protecting PoW is the stake of the equipment infrastructure... All the small coins switching to PoW algorithms that can't be easily rented is an attempt to make miners hold an equipment stake." [1] “This shows that work in PoW is not equal to security, and secure part of PoW is PoS. If BTC hashrate were rentable (no mining stakeholders) BTC double spends would be easy enough to make it worthless”. [1] He continues, “In Monero's case, PoW change was not to reduce NiceHash renting (the reason small coins change PoW) but to reduce the effects of ASICs that were in a few hands. So the key idea in both renting and concentrated ASIC problems, is that PoW works by having distributed equipment owners (stakes). It has nothing to do with work (waste). Value is created by work (waste) in BTC, which can be done in PoS. But securing established value is accomplished by risk of value, not waste. When buying equipment, you are locking up a stake just like PoS systems require. In all reasonable ways, PoW is just a weak and inefficient PoS in disguise”. [1]

From the other hand, in the article “Work is Timeless, Stake is Not” Hugo Nguyen describes the key weakness of PoS and comes to the opposite conclusion. He cites Paul Sztorc as “correctly concluded that PoS is an obfuscated form of PoW” [2] and states that “Proof-of-Stake is a misnomer. The correct, fully descriptive name for Proof-of-Stake should be Proof-of-Temporary-Stake (PoTS). This name is more accurate because it captures the time element, or lack thereof, of PoS.” [2] “The ongoing energy expenditure in PoW contributes to network security in 2 ways:” “Units of work expended in the past accumulate in the ledger. Units of work expended in the future accumulate in the current mining hardware.” [2] He calls this “sort of time-based accumulation phenomenon” as stock & flow. “Bitcoin is essentially protected by high stock-to-flow ratios in 2 areas: the ledger, and the mining hardware”. [2] “In contrast, PoS has no equivalent of this. Past stakes … do not accumulate in the ledger, as stake is released after some arbitrary bonding period. Long-range attack is the manifestation of this weakness: it works because of PoS’s inability to secure the past. Long range attack is at the heart of the problems with PoS, because it shows that in the long run PoS fails to guarantee the integrity of the ledger — the most important asset of all this innovation." [2] “Future stakes ... also do not accumulate in the validators in the present time, as again the act of staking only has meaning within the short window that it occurs — what happens in the future does not count today. Current-private-keys-theft is the manifestation of this weakness: it works because of PoS’s inability to secure the future. Keys theft sidesteps altogether the financial cost supposedly required to acquire controlling stake — whereas in PoW there’s no sidestepping the fact that an attacker needs to overcome the mining hardware and ongoing energy costs to pull off and sustain a majority attack.” [2] “In summary: the further one moves away from the present time in PoS, the faster stake loses its meaning, until stake becomes meaningless. Work is robust against the ravages of time. Stake is not. The fact that the cost of PoW mining is irretrievably sunk and accumulates both in the ledger and the mining hardware, is an important feature, not a bug. PoS research is often based on the fundamental misconception that this is a bug and a source of inefficiency”. [2]

Thus we identified a problem in current state of PoW — the lack of security ensured by stake in equipment. The brilliant solution to the equipment stake deprivation in PoW is proposed by Qi Zhou — to combine PoW and PoS in “Proof of Staked Work ” (PoSW) — a simple hybrid PoW/PoS. “The basic idea is that, if a miner wants to contribute its all hash power to the network (suppose p percent of all hash power of the network), the miner must stake the number of tokens that is proportional to p.” [3] So we came to obvious, naive and simple solving: add to PoW, what has become missing — a stake.

We propose similar yet different approach without multiplying work by stake as we have concerns that this might be an attack vector and could cause frequent reorganisations and higher orphan rate. Besides, the algorithm can estimate hash power of the whole network via difficulty whereas it is hard to estimate hashrate of individual miner to adjust his stake requirements. So we set the same minimum required stake for all miners based on difficulty.

In order to mine a block the miner must stake the number of coins that is not less than the current minimum amount which is determined by the difficulty. The preliminary proposal is that the minimum stake in atomic units should be equal to the next difficulty multiplied by factor m. This factor should be defined economically from the current network state and conditions. For start let m = 100000.

A miner forms the coinbase transaction as follows: he sends to himself the amount not less than the required minimum and adds fees and block reward. This is enough to prove and verify his collateral stake in a simple way.

There is mined money unlock window n, a rule which locks all outputs in coinbase transaction for n blocks. This means that coins from coinbase transaction can be spent only after n blocks. Therefore, to be able to mine blocks successively, miner will have to possess much more money than minimum stake amount for one block,— he will need a stake for each block until his stake for a first mined block is unlocked. This will substantially and even exponentially increase the cost of 51% attack, the cost of being large miner or running a mining pool since the miner or the owner of the pool will have to acquire sufficient stake.

Coin transferred in a coinbase transaction proves possession without revealing sender and recipient. This keeps the stake and reward wallets separate. There will be the possibility to lend stake by preparing a template stake transaction in which lender sends coins to himself, reward to miner, and part of the reward to himself as a commission for lending, and issues this raw transaction to the miner. The miner can check if he received sufficient reward and use the transaction in the block template.

Instead of daemon the coinbase transaction with stake should be created in wallet on request from the daemon or mining software. Staking wallet should be running in RPC mode and listen to the special corresponding command.

Check for inputs/outputs should be revised to take into account new coinbase transaction type.

This approach evokes concerns of amplifying the centralization of mining in the hands of those who possesses enough stake for large hash rate eliminating small miners and pools.

References:

[1] https://twitter.com/zawy3/status/1082199522812612608

[2] https://medium.com/@hugonguyen/work-is-timeless-stake-is-not-554c4450ce18

[3] https://medium.com/quarkchain-official/proof-of-staked-work-ef36f9499279

Download:

CLI v. 1.6.2

GUI v. 1.3.2

• In this GUI release, wallet optimization is added. It is sending fusion transactions in a background in order to aggregate transactions outputs that are below optimization target into bigger ones. It allows sending larger amounts of KRB within one transaction. Fusion transactions are free.
• GUI is updated core to the latest version 1.6.2 containing protections against deep reorg and 51% attacks which ensures irreversible transactions.

Imgur

http://krb.crypto-coins.club

• Dedicated Server
• DDOS Protection
• Low Fee: 0.5%
• Payment-ID & Integrated Address allowed (Mine directly to exchange)
• Set your own custom difficulty, worker-names and minimum payout level
• Graphs and stats to monitor your miners with ease
• Separate stats for each worker

Happy Mining!

https://discord.gg/DcCy3EA

in the crypto currency world, there are so many special crypto currencies. Each of them has a great project and the investors can make good profits from these coins. Karbo crypto currency is one of these special coins. This coin has started its projects since 2016 and now is known to have a great potential to become successful in the crypto world. Mining of karbo is also a profitable work which you can enhance your karbo mining profits by connecting your mining system to a mining pool like: tmpool.net.

Karbo Wallet Classic v. 1.3.0 https://github.com/seredat/karbowanecwallet/releases/tag/v.1.3.0
Karbo GUI v. 2.0.5 https://github.com/Karbovanets/Karbo-GUI/releases/tag/v.2.0.5
Karbo Lite v. 1.0.4 https://github.com/Karbovanets/Karbo-lite/releases/tag/v.1.0.4

We added 21 mining pools so far with fees ranging from -2% - 2%, servers located all around the world and with various payout schemes. You can add your hashrate, power consumption and power cost and see how profitable it is to mine Karbo with your rigs.

Check it out here: https://www.wheretomine.io/coins/karbo.html

WhereToMine is a mining profit calculator and pool explorer that helps cryptocurrency miners view the most profitable coins and the best pools.

Please make sure you have version v1.5.5.802 (c60236c) with an important update of LWMA-2 DA. To all pools, nodes and exchanges, we remind to update to the version 1.5.5 https://github.com/seredat/karbowanec/releases/tag/v.1.5.5

​

Wallets update released as well:

Karbo Wallet Classic v. 1.2.7 https://github.com/seredat/karbowanecwallet/releases/tag/v.1.2.7
Karbo GUI v. 2.0.2 https://github.com/Karbovanets/Karbo-GUI/releases/tag/v.2.0.2
Karbo Lite wallet v. 1.0.2 https://github.com/Karbovanets/Karbo-lite/releases/tag/v.1.0.2

​

Karbo Classic GUI Wallet v. 1.2.6 https://github.com/seredat/karbowanecwallet/releases/tag/v.1.2.6

Karbo Wallet 2 v.2.0.1 https://github.com/Karbovanets/Karbo-GUI/releases/tag/v.2.0.1
Karbo Lite wallet v.1.0.1 https://github.com/Karbovanets/Karbo-lite/releases/tag/v.1.0.1

CLI clients and wallets for pools, services, masternodes and exchanges

GUI Wallets:

Classic Karbo Wallet

New Karbo Wallet2

Lite Karbo Wallet

In this hardfork we introduce Adaptive minimal transaction fee according to our whitepaper.

Information for exchanges and other services how to work with new fees.

Pools operating 'cryptonote-forknote-pool' or compatible software should update Node-Cryptonote-Util to this version: https://github.com/aivve/node-cryptonote-util. The reference pool software is here: https://github.com/Karbovanets/karbo-pool.

Pools operating 'cryptonote-nodejs-pool' should change config on hardfork height. The changes in config are:

"daemonType": "default", "cnAlgorithm": "cryptonight", "cnVariant": 0, "cnBlobType": 0, 

The example of Karbo config is here: https://github.com/Karbovanets/cryptonote-nodejs-pool/blob/master/config_examples/karbo.json