[ANN] NDL - The coin for Pastafarians - Flying Spaghetti Monster Cryptocurrency!

[number435398]

I think some of my files are getting corrupted somehow.  Anyone have any remote clue as to why my chainparams.cpp file keeps turning into:

Code:

package=xcb_proto
$(package)_version=1.10
$(package)_download_path=http://xcb.freedesktop.org/dist
$(package)_file_name=xcb-proto-$($(package)_version).tar.bz2
$(package)_sha256_hash=7ef40ddd855b750bc597d2a435da21e55e502a0fefa85b274f2c922800baaf05

define $(package)_set_vars
  $(package)_config_opts=--disable-shared
  $(package)_config_opts_linux=--with-pic
endef

define $(package)_config_cmds
  $($(package)_autoconf)
endef

define $(package)_build_cmds
  $(MAKE)
endef

define $(package)_stage_cmds
  $(MAKE) DESTDIR=$($(package)_staging_dir) install
endef

define $(package)_postprocess_cmds
  find -name "*.pyc" -delete && \
  find -name "*.pyo" -delete
endef

As the first few lines of code.  I open it somewhere, don't edit it, and then it turns into that.  Same type of code throughout and all the actual normal c++ code is gone.  These are happening to files I'm not even modifying.

[1714142767]

1714142767

[1714142767]

1714142767

[1714142767]

1714142767

[1714142767]

1714142767

[1714142767]

1714142767

[Chicago]

Hello number435398,

I have been running into really weird compile issues, otherwise I'd have the new wallet good to go.  My flash drive I use to transfer between my main OS and my Linux VM seems to corrupt some files and the compiles fail for weird reasons.  But I've also been working and haven't had time to analyze it to its full end.

Instead of using a flash drive with a Windows filesystem, use a program to transfer the files over the network to your Linux VM.
Were you using NTFS, exFAT or a FAT32 filesystem and were you using the "Safely Remove" feature to be certain all of the files were closed before removing the USB drive? Or instead, were you leaving the USB drive connected and then sharing it with the VM and simply copying the files over between them?

Most people on Windows are familiar with PuTTY and WinSCP.
My favorites are SecureCRT and SecureFX.
Take a look at them next time you want to copy files between Windows and Linux.
There are free trials for SecureCRT and SecureFX.
PuTTY and WinSCP are free.

I think some of my files are getting corrupted somehow.
As the first few lines of code.  I open it somewhere, don't edit it, and then it turns into that.  Same type of code throughout and all the actual normal c++ code is gone.  These are happening to files I'm not even modifying.

I have no idea how depends/packages/libxcb.mk ended up as the contents of your src/chainparams.cpp file.

Best Regards,
-Chicago

[number435398]

I have no idea how depends/packages/libxcb.mk ended up as the contents of your src/chainparams.cpp file.

Yeah, really weird stuff.  It was even corrupting my flash drive's chainparams.cpp in addition to that which was on the VM's hard drive.

I think Noodlyappendagecoin Wallet Version 16.3 is now ready for testing.

[number435398]

Well at least I know the coding on my new wallet is working properly....couldn't get it to accept block 1325000 to save my life.  Then I realized I had told it to fork itself at that block so it rejected our old standard as a result.

What is the consensus on changing the pchMessage code?  Wait?  Test First then Maybe? or No, don't do it at all?

[Chicago]

I'm just waiting on feedback from DaveF after linking him to the new Linux binary.
The peer swarm with the new Network ID has been running great without any interruptions from other coin networks' clients trying to connect and interfere.

If your wallet uses the pchMessageStart from the repository I linked to then it should be able to join the peer swarm too and obtain consensus and validate all of the same blocks.

[number435398]

I'm just waiting on feedback from DaveF after linking him to the new Linux binary.
The peer swarm with the new Network ID has been running great without any interruptions from other coin networks' clients trying to connect and interfere.

If your wallet uses the pchMessageStart from the repository I linked to then it should be able to join the peer swarm too and obtain consensus and validate all of the same blocks.

In the new version of the litecoin core I'm using (16.3), pchMessageStart is only part of initial testing and doesn't appear in the normal non-testing part of the code.

[Chicago]

In the new version of the litecoin core I'm using (16.3), pchMessageStart is only part of initial testing and doesn't appear in the normal non-testing part of the code.

Defined for Mainnet here.
Defined for Testnet here.

[number435398]

In the new version of the litecoin core I'm using (16.3), pchMessageStart is only part of initial testing and doesn't appear in the normal non-testing part of the code.

Defined for Mainnet here.
Defined for Testnet here.

I hate the search option in Visual Studio....said it found it in only one file and I confirmed, yes, that particular variable name is mentioned in chainparams.cpp and is not merely "pchMessage" any longer.  I've also been getting confused as to who was advocating what.  I thought you modified something other than the pchmessage part.  I didn't realize you had effectively forked the network.  With the Flying Spaghetti Monster willing, so far, I'm close to the beta/release (i guess) of my wallet.  I keep noticing small details I'm messing up is all.

[Chicago]

I hate the search option in Visual Studio....said it found it in only one file and I confirmed, yes, that particular variable name is mentioned in chainparams.cpp and is not merely "pchMessage" any longer.  I've also been getting confused as to who was advocating what.  I thought you modified something other than the pchmessage part.  I didn't realize you had effectively forked the network.  With the Flying Spaghetti Monster willing, so far, I'm close to the beta/release (i guess) of my wallet.  I keep noticing small details I'm messing up is all.

Basically, all of the other clients with the same Network ID as Noodlyappendagecoin which had been connecting to the original peer swarm no longer connect with the v0.8.6.2 client.
The other changes you see below with exception of Remove Legacy DNS Seeds and Remove pnSeed Array are merely cosmetic.
The DNS Seeds and pnSeed Array were removed so that the v0.8.6.2 node would not attempt to reach old Litecoin addresses hard-coded into the wallet.
The whole point of it is to prevent unintentional forks.

        - Update Gitian Recipes
        - Upgrade UPnP Support
        - Set Client Version to Noodlyappendagecoin v0.8.6.2
        - Update Copyright Year to 2014-2018
        - Set Checkpoint at Height 1314626
        - Main Network 0x46534d01
        - Test Network 0x46534d02
        - Remove Legacy DNS Seeds
        - Remove pnSeed Array

[dnp]

is whoever running the following aware of the conversation here to hardfork to a new network number (pch) ??

ndl@carpdiem:~$ bin/rc.ndl cmd getpeerinfo|grep addr|grep pools
        "addr" : "188.99.44.158:60623", (dslb-188-099-044-158.188.099.pools.vodafone-ip.de)
        "addr" : "188.99.44.158:49572", (dslb-188-099-044-158.188.099.pools.vodafone-ip.de)
        "addr" : "188.99.44.158:50469", (dslb-188-099-044-158.188.099.pools.vodafone-ip.de)
        "addr" : "188.99.44.158:56194", (dslb-188-099-044-158.188.099.pools.vodafone-ip.de)

[dnp]

i have an iquidus block explorer for Chicago's newnet here:
 http://coins.dognose.net:3010/

i'm still running old code (with my own client patch) on the standard port at coins.dognose.net
and running Chicago's newnet code for the last couple days on a non-standard port.
i would've thought peer discovery would have more connections to that by now, still only have the one specifically configured chicago node...

[Chicago]

i have an iquidus block explorer for Chicago's newnet here:
 http://coins.dognose.net:3010/

i'm still running old code (with my own client patch) on the standard port at coins.dognose.net
and running Chicago's newnet code for the last couple days on a non-standard port.
i would've thought peer discovery would have more connections to that by now, still only have the one specifically configured chicago node...

Honestly, I think maybe 4 or 5 people in the whole world are paying attention.
It doesn't surprise me because difficulty has been and is so low, just enough to almost sustain regular target spacing.

[number435398]

Basically, all of the other clients with the same Network ID as Noodlyappendagecoin which had been connecting to the original peer swarm no longer connect with the v0.8.6.2 client.

I understand.  I didn't realize you had done with your version.

[number435398]

The New Noodlyappendagecoin Wallet (BETA) is now available!!!

https://github.com/number435398/Noodlyappendagecoin-project

Two windows versions, one with the new PCH value (NDLY), one with the old, for people to try out.

BACKUP YOUR WALLET.DAT FILE FIRST!

Do NOT mine on the new pch value yet.  Or if you do, don't expect to keep the coins.  Too much weird stuff going on right now and its the explorer that seems to be the best source and the explorer is still on the original pch code.

If this is successful and I have everyone's support, the version w the new PCH code could be the new version of the wallet without any additional modifications required on my part.

This is a BETA!  Bear that in mind!

[number435398]

The Noodlyappendagecoin Wallet 16.3 (BETA) has several new details:


THIS IS A BETA!  BE CAREFUL!

-Old NDL paperwallet addresses are no longer importable through the console, though it does seem to work with old wallet.dat files just fine.

-You can see a visual list of nodes in the console and right click to ban them as you see fit

-Support for BIP34,BIP65, and BIP66 will initiate at block 1365000 (approximately November 17-20, 2018)

-Support for BIP68, BIP112, BIP113, SegWit (BIP141, BIP143, BIP147) deployment to begin November 22, 2018 (subject to network consensus)

-Potential change of the pchMessageStart to "NDLY"

-"HD" Private Key Generation code has been added but not enabled

-Wallet no longer supports in-wallet Mining

-Wallet no longer supports "Stratum" mining

-Wallet now supports "Long-polling" mining (this typically requires that you will have to specify the address to which the mining amount will be sent to; a new address will no longer be auto generated)

-Noodlyappendagecoin balance can be shown in Noodlyappendagecoins, Noodles, and tips. (1 NDL, 1/10 NDL, 1/100 NDL)

-All transactions now require a payment of 0.001 NDL/kb (and is clearly displayed in the "Send" tab)

-Probably other things I can't think of right now.

[dnp]

-Wallet no longer supports in-wallet Mining

-Wallet no longer supports "Stratum" mining

deal breaker. the only two ways i mine. especially in-wallet cpu mining because any ASIC will overwhelm the current network size.

and dont give me that "avoiding false-postiives from antivirus software" bullpucky. altcoins have been surving that issue for
years now. THAT problems likes with the antivirus vendors and people should not raise their asses up to accomodate AV
lazy heuristics.

[number435398]

You just have to use

-Wallet no longer supports in-wallet Mining

-Wallet no longer supports "Stratum" mining

deal breaker. the only two ways i mine. especially in-wallet cpu mining because any ASIC will overwhelm the current network size.

It just means you have to use a miner that supports longpolling.  Cpuminer is one of the ones that can do that.  Its possible your current external mining program likely supports longpolling, so you aren't losing that mining method.  Which miner are you using?

[dnp]

It just means you have to use a miner that supports longpolling.  Cpuminer is one of the ones that can do that.  Its possible your current external mining program likely supports longpolling, so you aren't losing that mining method.  Which miner are you using?

i use in-wallet cpu mining for NDL to avoid overwhelming the network.
i have a stratum-only daemon providing interface to all the altcoins i support at coins.dognose.com
i do not run external standalone mining software, my asic boxes talk to the stratum daemon ports using the software their
manufacturer provides internally to the box.

i'm already using nearly 19gig of a 24gig linux system supporting all the various mining tools, daemons, explorers, database
interfaces, etc. i dont intend on running more software just to support NDL, i still want to support several other
older altcoins. my system cannot support more crap running.

i also simply do not have the time to do this sort of juggling act. coins.dognose.net will have to cease NDL support.

[number435398]

i also simply donot have the time to do this sort of juggling act. coins.dognose.net will have to cease NDL support.

I was unaware that it was that significant.  This is a beta and part of that beta process is discovering these things before it goes fully live.  I'll will prioritize stratum support.

[dnp]

THIS IS A BETA!  BE CAREFUL!

side issue:
 have you modified the  messages from this new code to use various permutations of Priate Talk and FSM references?

the FUN aspect in the coin, imho, is critical to its acceptance.