Pages:
Author

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

newbie
Activity: 96
Merit: 0

Hello friends,

In your opinion Will the value of NengCoin increase?
member
Activity: 1553
Merit: 23
Nengcoin New WhitePaper

Nengcoin new community whitepaper was created and released on Dec 2, 2021 in discord. Here is copy on NENG web page:

https://nengcoin.org/knowledgebase/whitepaper-nengcoin/
member
Activity: 1553
Merit: 23
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.
newbie
Activity: 30
Merit: 0

new pool

system PROP

system SOLO


https://redpool.pl
member
Activity: 1553
Merit: 23
Donation Giveback Event Ended, Community Settlement with SXC
RedRaider10 | [🥉] — Posted this NENG Community Annoucement in Discord

Quote
RedRaider10 | [🥉] — Today at 11:33 AM

u/NENGsters

Hello Fellow Nengsters!

The donation giveback event has ended. Thank you all who have donated and we appreciate your donation!

The Nengcoin Treasury Fund has raised 585,147,583.581 NENG and the funds will be used for future projects like marketing etc.

Through further communication between Dev Hong and SouthXhchange support, we were notified by SouthXchange support that we had a total loss of 6.3 Billion NENG on this 51% attack event and not 4.25 Billion NENG which we had originally thought because 2.05 billion NENG on the account that Dev Hong personally owns from his prior mining and open market purchase was already deducted from this 4.25 billion NENG loss calculation. Dev Hong gladly agrees to contribute this 2.05 billion NENG to our NENG Treasury Fund to cover the 51% hack loss. We were further notified by SXC support that all other members of NENG community will have no hacking loss on trading/deposit/withdraw on NENG and all the prior trades on NENG are honored by SouthXchange with no roll back.

Now that the SXC event is over we will move forward and make sure no 51% attacks happen in the future with this significant security enhancement of v1.9.x hard fork upgrade.

We want to thank all Nengsters for your patience and understanding throughout this tough period!

As always Happy mining & Trading!

#NENGcandoit!

#NENGtothemoon🚀

member
Activity: 1553
Merit: 23
SouthXchange trading on NENG is Back Online
Here we get new reply on Nengcoin (NENG) trading status on SouthXchange exchange:

Quote
#48038 Nengcoin (NENG) Chain Issue Resolved with Checkpoint, Ready for Trading

SouthXchange , said 5 hours ago

Hi Hong Lu,



NENG is back online. Deposits and trading are enabled but not yet withdrawals. We want to monitor the network for a few days first.


Just noticed that yes, Southxchange NENG/DOGE trading pair is already on active buy and sell with decent volumes.
member
Activity: 1553
Merit: 23
Nengcoin 2022 Dev Roadmap Released


Nengcoin 2022 software dev roadmap is released today in detail.  Checkout bitcointalk Ann page on first article. Here is snapshot of section of this:

Roadmap

  • 2021 Q3 -  SouthXchange Listing on NENG and WNENG
                    
    • NENG and WNENG gets listed on SouthXhcange through Community Donations
  • 2021 Q4 -  v1.9.x Hard Fork to Address Security Hack
                    
    • Nengcoin core was upgraded through hard fork  to v1.9.x on v1.9.1 version
    • 51% attack risk is addressed through Nengcoin core v1.9.x branch hard fork
    • Explore Atomic Swap DEX Trading on bitcoin/litecoin based Altcoins
  • 2022 Q1 -  Evaluate v1.9.x, Upgrade Core for Atomic Swap Native DEX Trading
                    
    • Real World Evaluate v1.9.1 version release on Security and Decentralization, Upgrade or Patch if necessary
    • Rebase Nengcoin core on v1.9.x to Litecoin 0.13.3 with New Atomic Swaps Features
    • Explore  Theory of Difficulty Adjustment for Spike/Cheetah diff
  • 2022 Q2 -  Difficulty Adjustment on code for Spike/Cheetah diff - Phase I
                    
    • List NENG to one DEX for Atomic Swap non-Custodian Native Wallet Trading
    • Upgrade Nengcoin core with cheetah difficulty automatically adjusted instead of manual hard forking
    • Maintain Spike difficulty on Fixed Number on Phase I
    • Evaluate and patch/upgrade Core Code on Security and Decentralization if Needed
  • 2022 Q3 -  Difficulty Adjustment on code for Spike/Cheetah diff - Phase II
                    
    • Upgrade Nengcoin core with Spike Difficulty automatically adjusted instead of manual hard forking
    • Evaluate and patch/upgrade Core Code on Security and Decentralization if Needed

2022 Q4 -  NENG to the Moon?

member
Activity: 1553
Merit: 23
Checkpoint Patch v1.9.1 Released - Community Announcement

From discord announcement channel:

Quote
RedRaider10 | [🥉] — Today at 8:32 PM
@NENGsters
Hello Fellow Nengsters!!

The v1.9.1 version NENG core software release works great as it fixed bugs in prior release. However NENG blockchain is currently in limbo as there are  two chains competing with each other with no clear winner on v1.9.1 version.  Two chains limbo issue forbid NENG to be listed at SouthXchange listing for trading and cause confusion in NENG community.



After many meetings and talks between NENG leaders, we have decided to go with the checkpoint method. The checkpoint method is where one chain is picked on code and is chosen to be the true chain in the blockchain and making the other chain obsolete. Checkpoint method has been tested and verified as the best course of action to alleviate this issue once and for all. The release will still be the same version (v1.9.1), the only difference is that it will have the readme_checkpoint.txt file. It is highly recommended for all members to re-download the v1.9.1 checkpoint version to get rid of the chain syncing issue. Moving forward we will also contact SouthXChange to resume NENG trading once they have re-downloaded the v1.9.1 checkpoint version.

As always Happy Mining!

#NENGcandoit!
#NENGtothemoon
member
Activity: 1553
Merit: 23
ShorelineCrypto exchange can not visit?

For shorelinecrypto (SLC)  exchange issues, please follow SLC bitcointalk Ann thread and also their discord channel there, there was major announcement made yesterday:

https://bitcointalksearch.org/topic/m.58414124

Discord:
https://discordapp.com/invite/jZMyhKm
full member
Activity: 407
Merit: 101
ShorelineCrypto exchange can not visit?
member
Activity: 1553
Merit: 23





really.................. so... you screw with the difficulty to you can try to make a CPU mineable scrypt coin..... THEN... the chain doesn't form a chain because the difficulty of the blocks being solved is too low and causing it to throw an error...........................you have no idea what you are doing.. all you had to do was change the amount it will vary during a diff reorg. ...  and change the frequency it will reorg the diff from every n blocks to every block...... OR stop screwing with it to try and gain an advantage


bug is bug.  but you are criticizing the coin design high level.  Nengcoin original design was 80:20 split between ASIC miners and CPU miners,  ASIC miners (including USB ASIC) get 80% of all block reward, CPU miners (PC + android) get 20%.   v1.9.x with new security upgrade will change the split, but intention of dev team is always to insure that majority of block reward goes to ASIC miners (including scrypt USB ASIC in this group).

NENG has more than 3 years of history,  CPU mining for nearly 3 years,  mobile mining on Android for more than 1 year.  So this is not what you think. The coin is working fine.  Sure bug causing syncing issue was serious issue, but the patch fixed this.
member
Activity: 1553
Merit: 23
ShorelineCrypto exchange trading on Nengcoin (NENG) has resumed after several days of suspension.  NENG wallet withdraw also resumed.
jr. member
Activity: 30
Merit: 1
Full Node Syncing Problem

This issue apply for all full nodes,  solo miners or pool miners etc. 

Posted byu/Sokka2015
3 hours ago
Live node problem
Hello Nengsters!

There was an issue regarding node syncing and it has been resolved. For those having node syncing problems check block explorer and put some addnode using live-node board, do "dead chain" procedure as usual in our reset times if needed if the node can not sync.

Block Explorer link: http://nengexplorer.mooo.com:3001/


-----------------------------------------------------------------------------
honglu69
·
just now
For those nodes miners that do not have any clean chain data available from another node, do this below to re-sync from beginning to end to get correct chain:

./nengcoind -reindex

To speed up syncing and target correct nodes source, you can max out for only two connections, any two with correct blocks and addnode in "nengcoin.conf" file and delete other nodes to insure no interference from other wrong nodes:

------------

upnp=1

maxconnections=2

addnode=71.234.69.93:6377

addnode=185.182.8.67:6377

addnode=209.145.50.223:43768

----------




really.................. so... you screw with the difficulty to you can try to make a CPU mineable scrypt coin..... THEN... the chain doesn't form a chain because the difficulty of the blocks being solved is too low and causing it to throw an error...........................you have no idea what you are doing.. all you had to do was change the amount it will vary during a diff reorg. ...  and change the frequency it will reorg the diff from every n blocks to every block...... OR stop screwing with it to try and gain an advantage
member
Activity: 1553
Merit: 23
Nengcoin v1.9.1.4 Released - Linux on Arm Device

v1.9.1 bug fix to fix v1.9.x full node syncing issue.

Full version tag: "v1.9.1.0-randomSpike-v1.9.x"

Web Guide for Raspberry Pi 4:
https://github.com/ShorelineCrypto/nengcoin/tree/master/doc/Raspberry_Pi_4


Linux on Arm device (such as Rasberry Pi 4) wallets on 64 bits or 32 bits Arm (arm64 and armhf) wallet download:
https://github.com/ShorelineCrypto/nengcoin/releases/tag/v1.9.1.4

This is major release and all new and existing NENG members are required to upgrade wallet.  The old version of wallet will not sync either due to hard fork or due to minimum work bug.

member
Activity: 1553
Merit: 23
How to Sync Node Fast with bootstrap file


bootstrap file is particularly helpful to sync fast over past 3 years NENG blocks.  Here is one copy of bootstrap from dev:
https://drive.google.com/file/d/1t9o4KiAIpnCccascB8Lij4HHR0pZmdLR/view?usp=sharing


For desktop Windows10/MacOS/Linux/Chromebook,  you can simply place this file under data folder,  keep  "wallet.dat", "nengcoin.conf" files only and delete all other files and then sync blocks from disk directly.

This would work very well for android phone as phone syncing NENG node is very slow due to weak Android arm CPUs on single thread.  Perform this in Android Userland app linux command line:

Code:
pip install gdown
cd
echo   export PATH=${HOME}/.local/bin:$PATH  >> .bashrc
.  .bashrc

gdown https://drive.google.com/uc?id=1t9o4KiAIpnCccascB8Lij4HHR0pZmdLR

mv bootstrap.dat ~/.nengcoin/


You can now start NENG wallet in Userland App ubuntu or debian command line and sync NENG full node within a few hours.
member
Activity: 1553
Merit: 23
Nengcoin v1.9.1.0 Released - Win/Linnux/Mac Wallets


Nengcoin v1.9.1.0 released with a bug fix on v1.9.x full node syncing problem

Windows and Linux binary wallets with upgrade instructions:
https://github.com/ShorelineCrypto/nengcoin/releases/tag/v1.9.1.0

MacOS wallet will be uploaded later to the same link above. Update: MacOS wallet and installation script has been uploaded to above link

This is major release and all new and existing NENG members are required to upgrade wallet.  The old version of wallet will not sync after block height 3243060 or some other block height either due to hard fork or due to full node syncing minimum work bug.

For ROOT CAUSE tech analysis on this bug, check out this report:
Root Cause Analysis on Full Node Syncing Trouble on v1.9.x Hard Fork

https://bitcointalksearch.org/topic/m.58358297

or

https://www.reddit.com/r/nengcoin/comments/qntqls/root_cause_analysis_on_full_node_syncing_trouble/
member
Activity: 1553
Merit: 23
Root Cause Analysis on Full Node Syncing Trouble on v1.9.x Hard Fork
11/6/2021
Hong Lu,   Dev of Nengcoin


Since our v1.9.x hard fork on Oct 31 2021,  Nengcoin blockchain has been struggling for full nodes syncing.  It seems to have formed many little chains without forming a real major chain. We initially thought this was due to "bad node", but we think we found the issue. It is not a "bad node" issue, the latest software release has bug, we call it "Minimum Work Bug".

Too Little Proof-of-Work Error

The debug.log file typically has this error recently when it rejects the obvious longest chain (like the on on block explorer):
 
Code:
ERROR: ProcessBlock() : block with too little proof-of-work

Although Nengcoin core has difficulty adjustment changes with new introduction of "cheetah diff" for CPU/Mobile miners, and "Spike diff" for preventing 51% attacks, the basic concept of bitcoin longest chain rule never changed, the Nengcoin core largely cloned after Litecoin core v0.8.x branch, which itself cloned from bitcoin core v0.8.x.  This error itself is strange enough.  If there is bad node, well whoever agree with NENG core algo and have the bitcoin longest chain on math should win and other chains on bad node should just be orphaned. In other word,  in concept of bitcoin/litecoin blockchain world,  chain should not get stuck by this.


Code on this error
Here is code from NENG source code that will print out this error:
https://github.com/ShorelineCrypto/nengcoin/blob/MinWorkBug/src/main.cpp#L2618

This error was result of condition of this function "ComputeMinWork",  by going through this function and many real cases that block get stuck, we think we found root cause of this issue.  Indeed, we believe the  v1.9.0.0 code has software bug that caused this recent chaos on Nengcoin blockchain.

Trouble 1 -  Failed on Difficulty Range on Cheetah Blocks

On the function "ComputeMinWork", it has an assumption that block difficulty should just be no more 4x increase or decrease because that is how it works on bitcoin or litecoin.  Each difficulty adjustment may cause difficulty drop, but no more than 1/4 of previous difficulty period.  Nengcoin is different, we know it can have CPU cheetah block that has difficulty that is significantly below this 4x range up or down.  We know that NENG difficulty can have a sharp reset, the difficulty drop a lot.

We have this fix on this issue:
https://github.com/ShorelineCrypto/nengcoin/commit/c4332786c5263474aea3b102955b084328e1404c

Trouble 2 - Checkpoint block selection that can fail Min Work Check

Another common trouble that we observed has nothing to do with cheetah difficulty on cheetah blocks.  We went through this code on  "ComputeMinWork" and realized that it checks difficulty from the last checkpoint block and enforce a rule that minimum work is no less than 1/4 adjustment for each period.  In bitcoin and litecoin, that is correct math because difficulty can only be adjusted up 4x or downward to no less than 1/4.   But this is not true understanding of Nengcoin blockchain.  We know NENG sometimes can do a reset, and the difficulty can drop to very low levels from high levels, thus breaking this no more 4x, no less 1/4 rule.

We have a fix on this issue,  in that we should not set a checkpoint on high difficulty block, we should just pick a block on cheetah difficulty to avoid this pitfalls: https://github.com/ShorelineCrypto/nengcoin/commit/d68d0e543249040774f45c448af0a43e728dffbb

The above fix should work because  block height 3244063  has only difficulty of 0.0391.  The Nengcoin code can continue enforcing no more than 1/4 drop on each period, but the chain is not likely to drop that below cheetah diff, therefore the fix should just work.

Checkpoint in bitcoin world is no longer favored because checkpoint essentially is a control by software side, by dev.  Nengcoin is like bitcoin/litecoin/dogecoin and we believe that dev should not have that much control on this issue.  In that sense, we are not likely to use checkpoint in software release frequently, and we only use checkpoint when a major hard fork is released.  The Nengcoin full node syncing will rely mainly on bitcoin longest chain rule to decide who is the winner, who is loser on blockchain mining competition.  Because of philosophically not favoring checkpoint technology on this blockchain, picking a cheetah diff as infrequent security measure is a quite reasonably good fix on this issue.


member
Activity: 1553
Merit: 23
New information on this v1.9.x wallet full node syncing issue

we are looking to perform a software patch on this, because this may be a software bug related issue causing the syncing problem.   

Nengcoin diffculty adjustment modified GetNextWork function to have extra cheetah diff (for CPU/Android miner) and spike diff on top of bitcoin style difficulty adjustment, other code was unchanged, this could be reason for the issue not able to syncing nodes into chain. Details:


Usually, bitcoin longest chain rule will slip and orphan one chain and merge into main chain quickly.  However, something is wrong obviously on NENG now.  Here is my wallet vs explorer chain,  both were synced this morning, now it is forked into two chain.  Debug.log file on this with conf enforcing 2 nodes only connected:
Code:
2021-11-05 01:03:36 connected 185.182.8.67
2021-11-05 01:03:36 send version message: version 70002, blocks=3245543, us=0.0.0.0:0, them=185.182.8.67:6377, peer=185.182.8.67:6377
2021-11-05 01:03:36 receive version message: /Satoshi:1.9.0/: version 70002, blocks=3245633, us=71.234.69.93:60108, them=185.182.8.67:6377, peer=185.182.8.67:6377
2021-11-05 01:03:36 UPnP Port Mapping successful.
2021-11-05 01:05:34 received block 13853f1ca7f585fa8a30fbc863cc04dea3903b943e839c39839775621ef4a8b8
2021-11-05 01:05:34 ERROR: ProcessBlock() : block with too little proof-of-work
2021-11-05 01:05:34 Misbehaving: 185.182.8.67:6377 (0 -> 100) DISCONNECTING
2021-11-05 01:05:34 disconnecting node 185.182.8.67
2021-11-05 01:05:35 trying connection 192.168.86.98:6377 lastseen=426687.3hrs
2021-11-05 01:05:35 connect() failed after select(): Connection refused
2021-11-05 01:05:37 trying connection 185.182.8.67 lastseen=0.0hrs
2021-11-05 01:05:37 connected 185.182.8.67
2021-11-05 01:05:37 send version message: version 70002, blocks=3245543, us=0.0.0.0:0, them=185.182.8.67:6377, peer=185.182.8.67:6377
Essentially,  two chains there connected by conf file  connect=185.182.8.67
Explorer 185.182.8.67 has 3245633 blocks,  this desktop node has 3245543.  Most likely by bitcoin longest chain rule, explorer has bigger work, should be  good,  the other chain should be orphaned.  But it did not.
The log file saying "ERROR: ProcessBlock() : block with too little proof-of-work"
the node is saying the block explorer has too little work,  misbehaving,  ban this  IP.  Usually nodes get banned. In this case in conf file   connect=explorerIP ,  banned and then reconnect, then banned again.

This may be a software issue or some of bug that needs to be fixed. Not sure how to resolve this now.
In the coming weekend, I need to dig through code, to see what his error "ProcessBlock() : block with too little proof-of-work",  for now it is just muddle through.  For now,  not ideal solution, just make the explorer node as "official" blockchain for SLC trading purpose,  not good, not great solution.  But we have to muddle through this until it is fixed on code.  It may be a software issue.
member
Activity: 1553
Merit: 23
Why is it so hard to mine a block right now? (CPU and Asic)

The chain has syncing problems since the hard fork.  Many bad nodes there (old versions)  preventing syncing (like orphan correct chain).  Obviously the explorer blockchain is bitcoin longest chain ruled based result,  the syncing has some math issue due to bad nodes there.

Even on same versions,  many miners are mining their own chain, not forming into one chain only yet. We are trying and communicating in discord now.  SO the issue is really a full node chain syncing problem, rather than a mining issue.  

When you mine a dead chain, sure you mined reward will be orphaned later.

Another factor, diff is bit too low, NOw is CPU mining range.  There are more penalty on ASIC (including USB ASICs) when diff is too low.

When ASIC get stuck for more than 2 minutes, only (or mostly) CPU miners on PC or android can move the chain. However, due to node syncing issue,  most of android phone miners are offline, not up to latest block.  No CPU miners,  one block get stuck could take half to 1 hour to be mined by a handleful of small CPU miners on "cheetah_cpuminer" tool
member
Activity: 1553
Merit: 23

Latest snapshot of good node,  no conf/wallet.dat, but including all other files in data folder. Recommended for x64 Linux + Windows10,  not recommended for android phone:

https://drive.google.com/file/d/1lCT2XZRTlPXsOGvxhZatt444mpCImofF/view?usp=sharing

for  Android phone, current easiest is to use snap shot to sync a local copy of wallet on windows10 or desktop Linux on x64, well connected on same block as explorer,  then do below syncing, removing all other files, keep wallet.dat and nengcoin.conf  with content below:

Code:
pcuser=yourrpcuser
rpcpassword=yourrpcpassword
rpcport=6376
rpcallowip=127.0.0.1
server=1
daemon=1
connect=192.168.86.115
192.168.86.115 is your local copy of good node IP, (replace with your IP), whatever your local environment desktop Windows10/Linux is.
Pages:
Jump to: