Pages:
Author

Topic: [NENG]Nengcoin - Litecoin on Steroids - Scrypt for All Miners - page 5. (Read 45944 times)

member
Activity: 1553
Merit: 23
I would say, based on the new error there and v2.0.0 is released,  I think the shorter chain is true chain. We are not going back to old version. It is too much going into new version now.

Soft Forks BIP66 and BIP65 are Enforced on the Chain on v2.0.0

The v2.0.0 was released 2 days ago.  The same code base pre-release  v0.13.3 was pre-released 22 days ago, that was long long time ago.

However, a timestamp attacker attacked the chain around the same day on the v2.0.0 release and v2.0.0 itself enforced BIP66 and BIP65 without BIP34 being enforced.  BIP34 is still planned at 3.9 million block height.   This is the reason for chain split because the wrong chain violated BIP66 and BIP65.  Previously we did not know that BIP66 and BIP65 can be enforced with 75% rule and 95% rule without BIP34 being activated first.

For now, we would urge for all those solo miners on USB ASIC/ASIC to move over to v2.0.0.  For those on v2.0.0 who have difficulty to sync to the same block height as block explorer, please do  "-reindex" to refresh the nodes into correct chain.

We are deciding to move over to new chain and not to look back into old versions on soft forks issue.
member
Activity: 1553
Merit: 23
I think the chain split, we got the reason, BIP66 soft fork is enforced on some of the bad header blocks

0000 log2_work=56.221875 tx=4488219 date='2022-02-04 09:20:30' progress=0.999822 cache=17.8MiB(136521tx)
2022-02-06 09:38:42 ERROR: AcceptBlockHeader: Consensus::ContextualCheckBlockHeader: a0199a0eeca0a60bc0076d040ac6f7b552eab00c06716a0cb2246421efc03587, bad-version(0x00000002), rejected nVersion=0x00000002 block (code 17)
2022-02-06 09:38:42 ERROR: invalid header received
2022-02-06 09:38:42 ProcessMessages(headers, 162003 bytes) FAILED peer=1
root@vmi695272:~/.nengcoin# tail debug.log
2022-02-06 09:38:21 UpdateTip: new best=10801473901b70171badffbec174ce2ee547e47e57adb4095ff303b17e60922a height=3516599 version=0x20000000 log2_work=56.221875 tx=4488216 date='2022-02-04 09:18:39' progress=0.999822 cache=17.8MiB(136518tx)
2022-02-06 09:38:21 UpdateTip: new best=aa339b13287da6944efd5ba85802ab6d3568ccc46589607ef7caeaa17de1728c height=3516600 version=0x20000000 log2_work=56.221875 tx=4488217 date='2022-02-04 09:19:34' progress=0.999822 cache=17.8MiB(136519tx)
2022-02-06 09:38:21 UpdateTip: new best=4c8c3915eedcd47b31ac9de18a7e805ddfc71e435a1346f1d445c24d2eb48796 height=3516601 version=0x20000000 log2_work=56.221875 tx=4488218 date='2022-02-04 09:19:36' progress=0.999822 cache=17.8MiB(136520tx)
2022-02-06 09:38:21 UpdateTip: new best=43eca76634b523db05f79ad7e9c6e92e1136c9d314c32573d789a4e45ccd0aed height=3516602 version=0x20000000 log2_work=56.221875 tx=4488219 date='2022-02-04 09:20:30' progress=0.999822 cache=17.8MiB(136521tx)
2022-02-06 09:38:42 ERROR: AcceptBlockHeader: Consensus::ContextualCheckBlockHeader: a0199a0eeca0a60bc0076d040ac6f7b552eab00c06716a0cb2246421efc03587, bad-version(0x00000002), rejected nVersion=0x00000002 block (code 17)
2022-02-06 09:38:42 ERROR: invalid header received
2022-02-06 09:38:42 ProcessMessages(headers, 162003 bytes) FAILED peer=1
2022-02-06 09:39:43 ERROR: AcceptBlockHeader: Consensus::ContextualCheckBlockHeader: a0199a0eeca0a60bc0076d040ac6f7b552eab00c06716a0cb2246421efc03587, bad-version(0x00000002), rejected nVersion=0x00000002 block (code 17)
2022-02-06 09:39:43 ERROR: invalid header received
2022-02-06 09:39:43 ProcessMessages(headers, 162003 bytes) FAILED peer=1
root@vmi695272:~/.nengcoin# tail debug.log
2022-02-06 09:38:21 UpdateTip: new best=10801473901b70171badffbec174ce2ee547e47e57adb4095ff303b17e60922a height=3516599 version=0x20000000 log2_work=56.221875 tx=4488216 date='2022-02-04 09:18:39' progress=0.999822 cache=17.8MiB(136518tx)
2022-02-06 09:38:21 UpdateTip: new best=aa339b13287da6944efd5ba85802ab6d3568ccc46589607ef7caeaa17de1728c height=3516600 version=0x20000000 log2_work=56.221875 tx=4488217 date='2022-02-04 09:19:34' progress=0.999822 cache=17.8MiB(136519tx)
2022-02-06 09:38:21 UpdateTip: new best=4c8c3915eedcd47b31ac9de18a7e805ddfc71e435a1346f1d445c24d2eb48796 height=3516601 version=0x20000000 log2_work=56.221875 tx=4488218 date='2022-02-04 09:19:36' progress=0.999822 cache=17.8MiB(136520tx)
2022-02-06 09:38:21 UpdateTip: new best=43eca76634b523db05f79ad7e9c6e92e1136c9d314c32573d789a4e45ccd0aed height=3516602 version=0x20000000 log2_work=56.221875 tx=4488219 date='2022-02-04 09:20:30' progress=0.999822 cache=17.8MiB(136521tx)
2022-02-06 09:38:42 ERROR: AcceptBlockHeader: Consensus::ContextualCheckBlockHeader: a0199a0eeca0a60bc0076d040ac6f7b552eab00c06716a0cb2246421efc03587, bad-version(0x00000002), rejected nVersion=0x00000002 block (code 17)
2022-02-06 09:38:42 ERROR: invalid header received
2022-02-06 09:38:42 ProcessMessages(headers, 162003 bytes) FAILED peer=1
2022-02-06 09:39:43 ERROR: AcceptBlockHeader: Consensus::ContextualCheckBlockHeader: a0199a0eeca0a60bc0076d040ac6f7b552eab00c06716a0cb2246421efc03587, bad-version(0x00000002), rejected nVersion=0x00000002 block (code 17)
2022-02-06 09:39:43 ERROR: invalid header received
2022-02-06 09:39:43 ProcessMessages(headers, 162003 bytes) FAILED peer=1
root@vmi695272:~/.nengcoin# tail debug.log
2022-02-06 09:38:21 UpdateTip: new best=10801473901b70171badffbec174ce2ee547e47e57adb4095ff303b17e60922a height=3516599 version=0x20000000 log2_work=56.221875 tx=4488216 date='2022-02-04 09:18:39' progress=0.999822 cache=17.8MiB(136518tx)
2022-02-06 09:38:21 UpdateTip: new best=aa339b13287da6944efd5ba85802ab6d3568ccc46589607ef7caeaa17de1728c height=3516600 version=0x20000000 log2_work=56.221875 tx=4488217 date='2022-02-04 09:19:34' progress=0.999822 cache=17.8MiB(136519tx)
2022-02-06 09:38:21 UpdateTip: new best=4c8c3915eedcd47b31ac9de18a7e805ddfc71e435a1346f1d445c24d2eb48796 height=3516601 version=0x20000000 log2_work=56.221875 tx=4488218 date='2022-02-04 09:19:36' progress=0.999822 cache=17.8MiB(136520tx)
2022-02-06 09:38:21 UpdateTip: new best=43eca76634b523db05f79ad7e9c6e92e1136c9d314c32573d789a4e45ccd0aed height=3516602 version=0x20000000 log2_work=56.221875 tx=4488219 date='2022-02-04 09:20:30' progress=0.999822 cache=17.8MiB(136521tx)
2022-02-06 09:38:42 ERROR: AcceptBlockHeader: Consensus::ContextualCheckBlockHeader: a0199a0eeca0a60bc0076d040ac6f7b552eab00c06716a0cb2246421efc03587, bad-version(0x00000002), rejected nVersion=0x00000002 block (code 17)
2022-02-06 09:38:42 ERROR: invalid header received
member
Activity: 1553
Merit: 23
One of my short chain got flipped to longer chain naturally, not by human surgery. The longer chain is true chain for now. It makes sense, it has higher diff,
longer chain,  no spike diff involved. Not sure what happened, the chain probably got split somewhere. 

member
Activity: 1553
Merit: 23
Why are there 2 chains (00: UTC  February 06, 2022) :
- PC wallet(v2.0) and http://cr2big.xyz are at block: 3 520 741
- https://spools.online and https://redpool.pl/ are at block : 3 520 034
So which chain is correct?

Not sure what caused this. But my two nodes,  one on old v1.9.x version wallet reindex from beginning to end, and also the official explorer site node
http://nengexplorer.mooo.com:3001/

all did refresh sync from before the split, then end result is same, the correct chain is now on explorer, same as redpool/spool pool.  In other word, the shorter
chain is the correct chain.  I did see lots of headers' error in log file.  So maybe the longer chain had lots of corrupted headers and block data in corrupted format.
it was going through by some nodes,  but I think the longer chain is wrong chain.  

To verify the truth. I am going to do a third node on v2.0.0, fresh start node, syncing from zero to now. I will see the results tomorrow.
newbie
Activity: 27
Merit: 0
Why are there 2 chains (00: UTC  February 06, 2022) :
- PC wallet(v2.0) and http://cr2big.xyz are at block: 3 520 741
- https://spools.online and https://redpool.pl/ are at block : 3 520 034
So which chain is correct?
hero member
Activity: 2146
Merit: 518
Be careful on trading WNENG
be careful on trading WNENG, Wrapped Nengcoin. Converting WNENG to NENG is usually fine at SXC, 1:1 pegged. However, buying WNNEG is tricky due to the supply shortage at SXC. The price at pancakeswap is decent, close to NENG/DOGE, but make sure check before hand, know what you are doing trading WNENG.

Pancake Swap has gouging price. I refuse to do any business with it. What is NENG? Whang-Chang jackie chan chinese toilet waste. Pop-chop tri-chop doodle-gloop coin that not even pond scum will buy. Care to change the name to a more decent? Does it exist on binance smart chain? As a market-maker guy, I lodge in my pants hefty piles of cash. I could create the future for u. But I wont.
member
Activity: 1553
Merit: 23
Nengcoin v2.0.0 Released - Windows, MacOS, Linux, Android phone, Chromebook, Pi4


Nengcoin core v2.0.0 is released.  This is major release and recommended for all nengcoin users except for solo miners on USB ASIC/ASIC.  Please download new wallet here: https://github.com/ShorelineCrypto/nengcoin/releases/tag/v2.0.0


This version is rebased off bitcoin/litecoin v0.13.3 with full in wallet CPU mining capabilities.  All CPU miners on PC/MacOS/Linux/Android phone/Chromebook/Pi are recommended to use this new wallet.  This wallet is static linked binary wallet so that macOS on x86_64 or M1 chip hardware on latest or older version of OSX all should work with full CPU mining capability when it is used with "cheetah_cpuminer"  miner.

For features and issues of this version, please checkout our prior report at:

https://github.com/ShorelineCrypto/nengcoin/releases/download/pre2.0/NENG_v2.0_Upgrade_Softfork_Proposal.pdf

member
Activity: 1553
Merit: 23
CPU mining domination continues close to 100%. average block is 6 minutes per block mined mainly on PC or android phone
member
Activity: 1553
Merit: 23
NENG base difficulty had a reset hours ago with fast blocks. Then minutes ago, another spike block was mined at difficulty = 244k at block height 3505827

CPU miners will continue to dominate close to 100% again on NENG mining for now until next difficulty adjustment block. It could be a day or 2.



member
Activity: 1553
Merit: 23
spike block mined, CPU mining 100% dominating
a spike block was mined at block height 3504888

From now on to next reset, CPU mining on PC or android phones are likely to dominate mining 100% on NENG
member
Activity: 1553
Merit: 23
tested on x86_64 version of macOS Monterey, latest macOS version, Nengcoin new wallet indeed works well. M1 chip same macOS version is likely to work too.
member
Activity: 1553
Merit: 23
v2.0 macOS Wallet working in MacOS Big Sur
Just compiled v2.0 macOS wallet with static linked libraries. This means that the new verson macOS wallet should work in all macOS versions, from Catalina to Big Sur or Monterey. The binary wallet was compiled on x86_64 hardware, because macOS M1 chip on arm CPU also support x86 binary, this wallet should work on new macOS M1 chip too.

Screen shot of Nengcoin NENG wallet running in big sur, probably for the first time:
https://www.reddit.com/r/nengcoin/comments/sbeux5/v20_macos_wallet_working_in_macos_big_sur/

Here is pre-release for macOS wallet. The version tag and some URL link is wrong. But the official release on 2.0.0 will be same as this pre-release on codes:https://github.com/ShorelineCrypto/nengcoin/releases/tag/rebase0.13
member
Activity: 1553
Merit: 23
NENG v2.0 Features, Soft Forks, Atomic Swap

Hong Lu, Developer of Nengcoin & Cheetahcoin
1/23/2022


  • NENG v2.0 Release in Weeks
  • Significant Improvement on Syncing, Wallet User Experience
  • Faster Node Syncing, Ban on Bad Nodes
  • 50 million NENG Limit Removed, Better Handling on Stuck Transaction
  • Soft Forks Comparison with Bitcoin/Litecoin/Dogecoin
  • Censorship Resistance Decentralization with DEX Trading on Atomic Swaps
  • Issue for Solo Miners on USB ASICs/ASICs

Full Text:

https://github.com/ShorelineCrypto/nengcoin/releases/download/pre2.0/NENG_v2.0_Upgrade_Softfork_Proposal.pdf
member
Activity: 1553
Merit: 23
Recommended CPU Mining on NENG in PC/Phone - Dual Mining

The below discord channel recent conversation touched on NENG CPU/Mobile mining best practice and profitability

Quote
raeZur logic — 01/15/2022
@honglu69 - thank you - I've been CPU mining with the cheetah_cpuminer on neng - but noticing that it is not really mining all that much - not like CHTA - so wondering if I should just abandon the idea - if it's not really worth CPU mining. Is the ideal blocktime 1 min or what? I have my cpuminer interval set at 240s.. should I adjust it?
honglu69 — 01/15/2022
for CPU mining NENG, yes, the reward is much less.  The current recommended approach is "dual mining" both NENG + CHTA, so the main profit is CHTA, NENG is extra.  There are reasons for NENG profit to be much less. mainly the cheetah effect is much weaker on scrypt,  many cheetah blocks are mined not by CPU, but by ASIC miners on solo or pool mining mode.  100% dedicated CPU mining NENG on PC or phone may not be worth it for now.
the NENG side wait time is 2 minutes,  after two minutes, "cheetah_cpuminer" will kick in and start mining on CPU.  dual mining works because many times the CPU is idle.  It mines NENG while CHTA is idle,  or mines CHTA while NENG is idle on CPU.
interverval is same as CHTA,  say your phone has 8 CPU, here is recommended command in phone for NENG in another screen session:
    python  main.py --interval 10 --cpu 6
8 CPU,  leave 2 CPUs for NENG/CHTA wallet to sync and other system tasks,  use only 6 CPUs for CPU mining NENG.   same command for NENG or CHTA on different folder of  "cheetah_cpuminer".     My neng folder on phone is "cheetah_cpuminer",  my CHTA folder is "cheetah_cpuminer_chta" folder, both run in same phone, on different screen sessions
in rare cases, sometimes both CHTA and NENG are kick in mining together, when that happens, my phone uses 4 CPU mining NENG, 4 CPU mining CHTA, that is OK for short period.  Most of time, they do not mine together, therefore dual mining gets more profit on CPUs on phone or PC.
raeZur logic — 01/15/2022
Thank you for the explanation. 🙂
member
Activity: 1553
Merit: 23
SouthXchange added NENG/LTC Trading Pair

Upon request from NENG community through dev support ticket,   Southxchange has added litecoin trading pair today. Here it is:
https://main.southxchange.com/Market/Book/NENG/LTC


Happy Trading NENG!
member
Activity: 1553
Merit: 23
need exchange

SouthXchange, active trading there.

Request for allowing wallet withdraw is sent to SXC, still waiting for their decision, hopefully soon. But deposit NENG into SXC, selling NENG for doge, withdraw doge is never a problem for weeks now.  Buying NENG has some issue as the wallet at SXC withdraw is still not allowed to private wallet.  For now, it is headache for buyers, but sellers are fine now for exchange.

Update on Jan 5: Withdraw on NENG is allowed at SouthXchange support
Just got response from SouthXchange support in discord,  all NENG Nengcoin  trading deposit/withdraw are back to normal. withdraw was just allowed on NENG today, confirmed by me.

WNENG Wrapped Nengcoin is normal on trading/withdraw/deposit too.
full member
Activity: 407
Merit: 101
need exchange
member
Activity: 1553
Merit: 23
First CPU Cheetah Block Mined on Rebased 0.13.3 Alpha Wallet
Today marks major milestone for Nengcoin core code rebasement into litecoin v0.13.3 with CPU internal miner restored. Lots of dev road blocks have been resolved and bugs fixed.

* (1) First patch of restoring internal miner on rebasement failed, it restored SHA256 instead of scrypt from bitcoin core code base. mined cheetah block failed and rejected.

* (2) Second patch code restored scrypt mining replacing SHA256 properly, but mined cheetah blocks were orphaned yesterday. It turns out the alpha code had bugs on parameters which failed to transit the newly mined blocks outside to other nodes.

* (3) The 3rd patch try today has a major success. Using "cheetah_cpuminer", below screen shot is the output of below command:


Code:
~/nengcoin_0.13.3_linux_arm64$ ./nengcoin-cli listtransactions

Below are the two blocks mined in 16 core 64 bits android phone insider Userland app. The top block was the first Cheetah block mined on rebased litecoin/bitcoin 0.13.3 core code base with internal miner restored. The bottom block was second CPU cheetah block mined right after 30 block height .

Block explorer on the first block mined:

http://nengexplorer.mooo.com:3001/block/d99cef916b45714d91eba5a14011be23cd4a7d78949a3c8f48bd4f6430f9f8fa

Screen shot of the two blocks on the wallet:
https://www.reddit.com/r/nengcoin/comments/rwfpgw/first_cpu_cheetah_block_mined_on_rebased_0133/
member
Activity: 1553
Merit: 23
Dev Update on v0.13.3 rebase Upgrade - 2021/2022 Holiday Weeks

Made a lot of progress on the dev work over the holiday weeks , testing and debugging and coding all are ongoing on the plan based on "Nengcoin dev roadmap 2022".   The current immediate task is to migrate and upgrade Nengcoin core code to bitcoin/litecoin core 0.13.3 version.  The NENG wallet  alpha version  was compiled and is working after rebasing NENG core code into litecoin core 0.13 branch.  Tested so far initially:  NENG blockchain syncing, receiving and sending coins are all working.  You guys can tell that some of nodes have "NengCore0.13.3" version tag which are dev nodes testing there.

Internal wallet mining functions are restored and patched from earlier bitcoin/litecoin versions.   CPU mining on cheetah_cpuminer works, but no block mined yet. The initial patch ported SHA256 mining into Nengcoin.  The current github "rebase0.13" branch as of today port the scrypt algo mining and removed sha256.
Stay tune for more dev updates in the future.
member
Activity: 1553
Merit: 23
Nengcoin Node Selector

You want to find more nodes, or sometimes your connection has too much poor nodes connections and you only want to connect to nearby fast nodes for the purpose of better
result for mining,  here is tool that can help you, developed by our member discord ID @spaces.are.evil :

https://nengcoin-node-selector.vercel.app/
Pages:
Jump to: