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!
Topic: [ANN] NDL - The coin for Pastafarians - Flying Spaghetti Monster Cryptocurrency! - page 16. (Read 125161 times)
October 27, 2018, 07:58:28 PM
October 27, 2018, 05:20:52 AM
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.
October 27, 2018, 02:56:44 AM
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...
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.
October 27, 2018, 02:24:06 AM
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...
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...
October 27, 2018, 02:13:03 AM
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)
October 27, 2018, 02:11:21 AM
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
- 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
October 27, 2018, 01:52:38 AM
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.
October 27, 2018, 12:53:51 AM
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.
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.
October 26, 2018, 10:23:27 PM
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.
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.
October 26, 2018, 04:14:57 PM
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?
What is the consensus on changing the pchMessage code? Wait? Test First then Maybe? or No, don't do it at all?
October 26, 2018, 12:12:00 AM
Quote
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.
October 25, 2018, 12:02:47 AM
Hello number435398,
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 have no idea how depends/packages/libxcb.mk ended up as the contents of your src/chainparams.cpp file.
Best Regards,
-Chicago
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.
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
October 24, 2018, 05:40:42 PM
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:
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.
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.
October 22, 2018, 05:48:59 AM
i just recompiled the un-modded source i downloaded oct.16 and get the same error at the same line number.
it had the new pch value so i assumed i found the correct source.
so, what source location should i download?
also, could -txindex be a potential issue? its needed to support iquidus block explorer.
or maybe i somehow corrupted my block files, although a -reindex didnt fix it.
oh well, next weekend it is. 60 hour work weeks suck.
it had the new pch value so i assumed i found the correct source.
so, what source location should i download?
also, could -txindex be a potential issue? its needed to support iquidus block explorer.
or maybe i somehow corrupted my block files, although a -reindex didnt fix it.
oh well, next weekend it is. 60 hour work weeks suck.
Hi dnp,
60 hour weeks aren't great at all!
Sources are here.
I started a new test here, compiling with GCC v7.3.0 and with txindex=1 in the noodlyappendagecoin.conf and watched as it sync'd over the network.
I'm not sure how you may have corrupted your block files since I am not looking over your shoulder, but it is entirely possible.
After this node sync'd, then I stopped it and started it again to look for your error but everything started normally.
Best Regards,
-Chicago
October 22, 2018, 04:38:26 AM
i'll try again next weekend with a fresh download.
Hi dnp,
Sounds good, let me know if there is anything I can help with to make things easier.
Eventually, when nodes are seeded on the new peer swarm, I'll add some updates into src/net.cpp and we can discuss who wants to run the DNS Seeder code.
Once src/net.cpp has a few hard-coded addresses in the pnSeed array and after there is a working DNS Seed, then the chain should march on until there is some future upgrade.
Best Regards,
-Chicago
i just recompiled the un-modded source i downloaded oct.16 and get the same error at the same line number.
it had the new pch value so i assumed i found the correct source.
so, what source location should i download?
also, could -txindex be a potential issue? its needed to support iquidus block explorer.
or maybe i somehow corrupted my block files, although a -reindex didnt fix it.
oh well, next weekend it is. 60 hour work weeks suck.
October 22, 2018, 04:22:53 AM
i'll try again next weekend with a fresh download.
Hi dnp,
Sounds good, let me know if there is anything I can help with to make things easier.
Eventually, when nodes are seeded on the new peer swarm, I'll add some updates into src/net.cpp and we can discuss who wants to run the DNS Seeder code.
Once src/net.cpp has a few hard-coded addresses in the pnSeed array and after there is a working DNS Seed, then the chain should march on until there is some future upgrade.
Best Regards,
-Chicago
October 17, 2018, 11:32:30 PM
Great project! I really like.
But why just sit and wait for the development of this project, when you can wait and participate at this time in the bounty program of an excellent project? https://t.me/InnovaMinex
But why just sit and wait for the development of this project, when you can wait and participate at this time in the bounty program of an excellent project? https://t.me/InnovaMinex
October 22, 2018, 04:16:58 AM
Notably, the src/main.cpp line cited in your assertion error does not match up here. Your code suggests SetBestChain is defined starting in line 1802 while in the code I've shared it is declared in line 1784.
i do mod the source before compiling, however i do not put mods into main.cpp
i probably fumbled something although it did run fine as compiled for a couple days.
i'll try again next weekend with a fresh download.
October 21, 2018, 12:09:27 PM
Not to put pressure on the people who are working on the client, but I think we need a new one now.
New client and instructions were posted this past week.
As stated a few weeks ago, I don't have a machine I can compile on. Unless I missed it (entirely possible) you just posted a windows exe file. The explorer is on a Linux box.
I'll throw up a windows VM and get your client and the bootstrap and go from there.
Give me a day or two and it should be be back and synced.
-Dave
I posted a Linux binary last night.
You can download it here.
I tested it as working under Ubuntu 18.04 LTS.
Jump to: