On larger hives and especially faster hives it would appear that early out thread is checking a little too often. Can this value be modified via qt wallet in the future? Limiting hashing to 23 threads on a 3900x shows that the 24th thread is kept equally busy as any other thread when it's just doing early out checking. Since total time to hash is ~230ms as is maybe early out can be configured to check at time intervals rather than bee internal (or just a higher bee count since time is already pretty low).

The log record could be limited, since when it requesting a template for SHA and for MinX in the same node, since it is mining with both algorithms, the log is filled with this.

2021-05-23 17:24:19 connect() to 104.248.84.57:62456 failed after select(): Connection refused (111)
2021-05-23 17:24:26 connect() to 143.244.44.6:62456 failed after select(): Connection refused (111)
2021-05-23 17:26:45 CreateNewBlock(): block weight: 808 txs: 0 fees: 0 sigops 400
2021-05-23 17:26:47 UpdateTip: new best=000000cb65b36764dada371e021b01259d723f8d3e0732aa9bd55857da4c87ca height=2383 version=0x00000000 log2_work=43.997445 tx=2570 date='2021-05-23 17:26:45' progress=0.999999 cache=0.0MiB(122txo)
2021-05-23 17:26:47 AddToWallet e0c2fea31622885c00db9ac7c87c57c282ce972fbbdf5140e36b9d13ee196f66  new
2021-05-23 17:26:47 ********************* Hive: Bees at work *********************
2021-05-23 17:26:47 CreateNewBlock(): block weight: 808 txs: 0 fees: 0 sigops 400
2021-05-23 17:26:50 BusyBees: No bee meets hash target (3000 bees checked with 3 threads in 3181ms)
2021-05-23 17:26:51 UpdateTip: new best=a36c2351328dd56b4a7e95e961711936c70a2fb3f7492c0ae0c62a7d5d299782 height=2384 version=0x00000000 log2_work=43.997448 tx=2571 date='2021-05-23 17:26:51' progress=1.000000 cache=0.0MiB(123txo)
2021-05-23 17:26:51 ********************* Hive: Bees at work *********************
2021-05-23 17:26:54 BusyBees: No bee meets hash target (3000 bees checked with 3 threads in 2908ms)
2021-05-23 17:26:55 CreateNewBlock(): block weight: 808 txs: 0 fees: 0 sigops 400
2021-05-23 17:27:13 UpdateTip: new best=ba1ff79245af9c97e063bfea83d41f1d21d02cd28ea9d442bca2324373af3cd1 height=2385 version=0x00000000 log2_work=43.997451 tx=2572 date='2021-05-23 17:27:14' progress=1.000000 cache=0.0MiB(124txo)
2021-05-23 17:27:13 BusyBees: Skipping hive check (max Hive blocks without a POW block reached)
2021-05-23 17:27:17 CreateNewBlock(): block weight: 808 txs: 0 fees: 0 sigops 400
2021-05-23 17:28:44 CreateNewBlock(): block weight: 808 txs: 0 fees: 0 sigops 400
2021-05-23 17:28:54 connect() to 143.244.47.85:62456 failed after select(): Connection refused (111)
2021-05-23 17:31:33 socket recv error No route to host (113)
2021-05-23 17:31:44 socket recv error Connection timed out (110)
2021-05-23 17:33:50 connect() to 37.19.197.137:62456 failed after select(): Connection refused (111)
2021-05-23 17:34:40 connect() to 143.244.44.6:62456 failed after select(): Connection refused (111)
2021-05-23 17:35:06 connect() to 95.223.76.26:62456 failed after select(): Connection refused (111)
2021-05-23 17:35:45 CreateNewBlock(): block weight: 808 txs: 0 fees: 0 sigops 400
2021-05-23 17:35:48 connect() to 104.248.84.57:62456 failed after select(): Connection refused (111)
2021-05-23 17:35:49 CreateNewBlock(): block weight: 808 txs: 0 fees: 0 sigops 400
2021-05-23 17:35:50 CreateNewBlock(): block weight: 808 txs: 0 fees: 0 sigops 400
2021-05-23 17:35:54 CreateNewBlock(): block weight: 808 txs: 0 fees: 0 sigops 400
2021-05-23 17:35:55 CreateNewBlock(): block weight: 808 txs: 0 fees: 0 sigops 400
2021-05-23 17:35:59 CreateNewBlock(): block weight: 808 txs: 0 fees: 0 sigops 400
2021-05-23 17:36:00 CreateNewBlock(): block weight: 808 txs: 0 fees: 0 sigops 400
2021-05-23 17:36:02 Potential stale tip detected, will try using extra outbound peer (last tip update: 529 seconds ago)
2021-05-23 17:36:05 CreateNewBlock(): block weight: 808 txs: 0 fees: 0 sigops 400
2021-05-23 17:36:05 CreateNewBlock(): block weight: 808 txs: 0 fees: 0 sigops 400
2021-05-23 17:36:10 CreateNewBlock(): block weight: 808 txs: 0 fees: 0 sigops 400
2021-05-23 17:36:10 CreateNewBlock(): block weight: 808 txs: 0 fees: 0 sigops 400
2021-05-23 17:36:16 CreateNewBlock(): block weight: 808 txs: 0 fees: 0 sigops 400
2021-05-23 17:36:21 CreateNewBlock(): block weight: 808 txs: 0 fees: 0 sigops 400
2021-05-23 17:36:21 CreateNewBlock(): block weight: 808 txs: 0 fees: 0 sigops 400
2021-05-23 17:36:25 CreateNewBlock(): block weight: 808 txs: 0 fees: 0 sigops 400
2021-05-23 17:36:27 CreateNewBlock(): block weight: 808 txs: 0 fees: 0 sigops 400
2021-05-23 17:36:31 CreateNewBlock(): block weight: 808 txs: 0 fees: 0 sigops 400
2021-05-23 17:36:33 CreateNewBlock(): block weight: 808 txs: 0 fees: 0 sigops 400
2021-05-23 17:36:36 CreateNewBlock(): block weight: 808 txs: 0 fees: 0 sigops 400
2021-05-23 17:36:38 CreateNewBlock(): block weight: 808 txs: 0 fees: 0 sigops 400
2021-05-23 17:36:43 CreateNewBlock(): block weight: 808 txs: 0 fees: 0 sigops 400
2021-05-23 17:36:48 CreateNewBlock(): block weight: 808 txs: 0 fees: 0 sigops 400
2021-05-23 17:36:48 CreateNewBlock(): block weight: 808 txs: 0 fees: 0 sigops 400
2021-05-23 17:36:53 CreateNewBlock(): block weight: 808 txs: 0 fees: 0 sigops 400
2021-05-23 17:36:59 CreateNewBlock(): block weight: 808 txs: 0 fees: 0 sigops 400
2021-05-23 17:37:04 CreateNewBlock(): block weight: 808 txs: 0 fees: 0 sigops 400
2021-05-23 17:37:09 CreateNewBlock(): block weight: 808 txs: 0 fees: 0 sigops 400
2021-05-23 17:37:10 CreateNewBlock(): block weight: 808 txs: 0 fees: 0 sigops 400
2021-05-23 17:37:14 CreateNewBlock(): block weight: 808 txs: 0 fees: 0 sigops 400
2021-05-23 17:37:15 CreateNewBlock(): block weight: 808 txs: 0 fees: 0 sigops 400
2021-05-23 17:37:20 CreateNewBlock(): block weight: 808 txs: 0 fees: 0 sigops 400
2021-05-23 17:37:20 CreateNewBlock(): block weight: 808 txs: 0 fees: 0 sigops 400
2021-05-23 17:37:25 CreateNewBlock(): block weight: 808 txs: 0 fees: 0 sigops 400
2021-05-23 17:37:25 CreateNewBlock(): block weight: 808 txs: 0 fees: 0 sigops 400
2021-05-23 17:37:30 CreateNewBlock(): block weight: 808 txs: 0 fees: 0 sigops 400
2021-05-23 17:37:35 CreateNewBlock(): block weight: 808 txs: 0 fees: 0 sigops 400
2021-05-23 17:37:38 tor: Thread interrupt
2021-05-23 17:37:38 torcontrol thread exit
2021-05-23 17:37:38 addcon thread exit
2021-05-23 17:37:38 Shutdown: In progress...
2021-05-23 17:37:38 net thread exit
2021-05-23 17:37:38 UPNP_DeletePortMapping() returned: 0
2021-05-23 17:37:38 upnp thread interrupt
2021-05-23 17:37:38 msghand thread exit
2021-05-23 17:37:42 opencon thread exit
2021-05-23 17:37:42 !!! BeeKeeper: FATAL: Thread interrupted
2021-05-23 17:37:42 scheduler thread interrupt
2021-05-23 17:37:42 Dumped mempool: 5e-06s to copy, 0.002554s to dump
2021-05-23 17:37:42 Shutdown: done

Which port # should I use for my conf file to connect?

When i try

./litecoincash-cli createbees 1 false MDwASjngYWi4XAххх

it return

{"result":null,"error":{"code":-64,"message":"Error: If specifying a honey address, it must be legacy format (TX_PUBKEYHASH)"},"id":"curltest"}

But when i try without honey address bee created success

-- Describe the issue --

Creating bees with a honey address outside your wallet does not give error, however it does not provide any block rewards to that address.

-- What behavior did you expect? --

An error that address is not in your wallet, since honey rewards cannot be sent to other addresses.

-- What was the actual behavior (provide screenshots if the issue is GUI-related)? --

Create bees is successful with a transaction ID returned.

-- How reliably can you reproduce the issue, what are the steps to do so? --

1. Open two wallets, generate legacy address from first wallet.
2. Open second wallet that has enough LCC to create bees, open console and type:

createbees 10 true XXXXXXXXXXXXXXXXXXX

Where XXXXXXXXXXXXXXXXXXX is the legacy address created in step 1.

-- What version of LitecoinCash Core are you using, where did you get it (website, self-compiled, etc)? --

0.16.0.5 / 0.16.0.6 from repository

Issue appears on windows QT wallet when opening wallet. From what I can tell, if I close the wallet with TX in the mempool it will crash after re-opened until TX are processed or mempool.dat is removed.

Observed on two different windows 10 pro machines. One with a 3800x and one with a 3900x cpu. Logging showed nothing other than it simply stopped logging mid statement (usually right after it starts getting peers). When the issue is present I can restart the wallet as many times as 5 times with it crashing each time. These machines are fairly quick and that could have something to do with the problem. Wallet is encrypted and requires password for hivemining... which i stopped doing immediately to rule out hivemining start as a possible crash mechanism.

There seems to be 1 hivemined block for every 2 pow blocks. ( for the whole hive, not just in a specific wallet )

It should be a 1 : 1 ratio.

The 2 : 1 ratio in favor of pow blocks seems to be always the same.

I believe this is not intended, and is a bug.

Where i can find info about RPC API Beehive with fullnode ubuntu ?

I recently sent out 3 bee orders to the hive and i believe they were sent at the same time according to the information displayed in my litecoincash core, although the first 2 orders were about 10 minutes apart before my 3rd order

Maybe about a hour or 2 later my system was not shutdown properly which lead to the litecoincash folder being corrupted

I was able to recover my wallet with -salvagewallet and then rebuild the blockindex

My 1st and 2nd bee order was fine

However my 3rd order was missing with the transaction list before my wallet was corrupted showing it being taken from my account balance but after i reclaimed my wallet the bees are not in my hive even though the litecoincash was deducted from my balance

Now after salvaging my wallet only my first 2 bee orders are present in transaction history

How should i proceed?

Where are my precious bees?

Also when will a multi-wallet feature like bitcoin core has be added?

-getinfo should format everything into the old format. It does nothing currently.

This is an error report for the litecoincash core install on a VPS, i was hoping it would install correctly however the test failed...

FAIL: test/test_litecoincash
============================

Running 271 test cases...
test/main_tests.cpp(30): ^[[1;31;49merror: in "main_tests/block_subsidy_test": check nSubsidy == nPreviousSubsidy / 2 has failed [0 != 1192]^[[0;39;49m
unknown location(0): ^[[4;31;49mfatal error: in "rpc_tests/rpc_ban": std::runtime_error: JSON value is not an object as expected^[[0;39;49m
test/rpc_tests.cpp(266): ^[[1;36;49mlast checkpoint^[[0;39;49m

^[[1;31;49m*** 2 failures are detected in the test module "LitecoinCash Test Suite"
^[[0;39;49mFAIL test/test_litecoincash (exit status: 201)

How should i proceed?
Please advise...

Hi all,
There is a possible null pointer dereference issue found by Qihoo360 CodeSafe Team.
Details as bellow:

Function State() could return null pointer:

After calling this function in line 521, the returned pointer is directly dereferenced without checking against:

Cheers
Qihoo360 CodeSafe Team

hi
I am one of the solo miners of the LCC
I'm a mine with my own NOMP
I used a uNOMP before the new update of the wallet, And I got a few Blocks
But in the new version of wallet, we have to use the NOMP
Since I'm using a new version of the wallet
So far, I have found 2 blocks, both orphans
I think this is a problem with the new version of wallet and i cant download Previous version
After finding my first orphaned Block, I reset the server (NOMP)
But just a few hours ago, I found a second Block, the orphan
I use my old laptop as a server
If I find an orphan again, I will announce here
can i have link for download previous version ( LitecoinCashCore:0.15.0.1)

getnetworkhiveinfo[honey_pot] returns 13440000000000 where honey pot is 1344000.0000000

I have programmed code to divide by 10000000 but would be more accurate if included decimal.

--Suggestion to update litecoinca.sh website

--mobile wallet

Remove atomicdex wallet (inactive)
Add komodoplatform.com wallet (active)

Remove upgrade track 0.16.3 already active for a long time, no necessary.

--Exchanges: Live

Remove (inactive) - stex, instaSwap, extracts and atomicDex
Add (active) - freiexchange.com and yobit.net (yobit despite not being able to withdraw lcc has trading)

Mining Pools

Remove (inactive) - bsod.pw, ww25.gomine.pro, gos.cx, prohashing.com, mining-coins.com
Add (active)- miningpoolstats.stream, p2p-spb.xyz:5557/static, coinxpool.com, pool.mecrypto.club, pool.phalanxmine.com/site/all_coins?coin=LCC

Other Services

Remove (inactive) lcc.tokenview.com, blockfolio.com/coin/LCC_2
Add (active) poolbay.io/crypto/1218/litecoin-cash

Connect:Community

Change logo Twitter

Wallet

Active a wallet electrum (activate fast)

Greetings to the entire Litecoincash community. The project has great potential.

I am finding that when attempting to send a transaction with 7 or more decimals the send fails.

Is anyone else experiencing this?

Is there anything I can do to allow decimals greater than 6?

It is possible to multi-thread the hive bee's hashes iteration loop, making the bee's hashes check time a lot faster, giving an unfair advantage to those with such a modified wallet.

I have given the code to Tanner.

I am getting the below error when performing a make when using the latest git. Any ideas why?

./uint256.h:48:24: note: no known conversion for argument 1 from ‘CTxDestination {aka boost::variant<CNoDestination, CKeyID, CScriptID, WitnessV0ScriptHash, WitnessV0KeyHash, WitnessUnknown>}’ to ‘const base_blob<160u>&’
./uint256.h:48:24: note: bool operator!=(const base_blob<256u>&, const base_blob<256u>&)
./uint256.h:48:24: note: no known conversion for argument 1 from ‘CTxDestination {aka boost::variant<CNoDestination, CKeyID, CScriptID, WitnessV0ScriptHash, WitnessV0KeyHash, WitnessUnknown>}’ to ‘const base_blob<256u>&’
Makefile:5869: recipe for target 'libbitcoin_server_a-pow.o' failed
make[2]: *** [libbitcoin_server_a-pow.o] Error 1
make[2]: Leaving directory '/home/wallets/litecoincash/src'
Makefile:9690: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/home/wallets/litecoincash/src'
Makefile:736: recipe for target 'all-recursive' failed

Hi all,
There is a sizeof issue found by Qihoo360 CodeSafe Team.
Details as bellow:

the argument of macro 'FLATDATA' is charstrval which is a pointer defined here:

in the expand of macro 'FLATDATA' here:

Can you guys confirm this?

Cheers
Qihoo360 CodeSafe Team

Logging this here as there is no other avenue of contact with LCC devs.

Exchanges no longer connected to the wallets. Appears to have stopped around 25/26 September

I've seen a few pools drop LCC off ASICBoost as it's not compatible.

Is there a specific reason or is intentional that LCC isn't compatible...

Thanks

Hello. Just a test from my wallet. 1st tx sent fine. 10lcc
2nd tx says it sent, but doesn't exist. of course this was the balance of my wallet. where are the coins?

{
"account": "",
"address": "Ce6ZhX8e2Zyn4wPCTW5MswDW1wfQjpAn7t",
"category": "send",
"amount": -2240.0000000,
"vout": 1,
"fee": -0.0001370,
"confirmations": 0,
"trusted": true,
"txid": "a4100e6d86072ac09360f86c76573bd420961e3c013d8ea41c71f228f9348227",
"walletconflicts": [
],
"time": 1536366454,
"timereceived": 1536366454,
"bip125-replaceable": "no",
"abandoned": false
}
]