Topic: [ANN] NDL - The coin for Pastafarians - Flying Spaghetti Monster Cryptocurrency! - page 17. (Read 125323 times)
October 21, 2018, 11:02:44 AM
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.
October 21, 2018, 11:01:07 AM
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
What is the linux executable file that you're using from the compile?
October 21, 2018, 10:26:09 AM
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
October 21, 2018, 09:47:35 AM
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.
October 21, 2018, 09:11:38 AM
Yep, I am seeing the same thing. The few nodes that the block explorer are connecting to that are good NDL are all at the same spot.
Did someone mining fork off or is there another issue?
Not to put pressure on the people who are working on the client, but I think we need a new one now and then you can do regular releases over the next few weeks / months / whatever till all the new features are in.
But, I am not a programmer or developer so I have no idea if that is going to be a bigger task or not.
-Dave
Did someone mining fork off or is there another issue?
Not to put pressure on the people who are working on the client, but I think we need a new one now and then you can do regular releases over the next few weeks / months / whatever till all the new features are in.
But, I am not a programmer or developer so I have no idea if that is going to be a bigger task or not.
-Dave
October 21, 2018, 07:52:17 AM
Chain stopped again with no connection; I do have block number 1321888 at abt 22:00 pm UTC yesterday ... seems to fit to Daves blockexplorer, that also stopped then.
So far I didn't test Chicagos work, I simply have not enough time at the moment.
n.
So far I didn't test Chicagos work, I simply have not enough time at the moment.
n.
October 21, 2018, 12:46:52 AM
Hello dnp,
The "network" primarily has been the node I published earlier in the week and one Windows 7 node which is connected with it.
About 10 hours ago, I rebooted my hypervisor and had forgot to restart the Windows wallet so that there would be at least one connection to the other node.
I've started it back up and also ran another test with the updated code on Ubuntu 18.04 LTS and it is syncing now too.
I see you're not exactly running my build. There are some key differences in your output compared to what is produced by the published code.
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.
There are some other notable differences during startup I have highlighted above from your post.
Here is what a debug.log startup sequence looks like with the code I have shared.
The sources in the repository are nearly identical to the original code published in 2014.
The changes are all cleanly visible in the commit history.
I have also prepared a Linux binary.
You may find it on the releases page of the repository here.
Please note it too is linked with Berkeley DB v5.3.
This is a transparent and serious attempt to repair the network and to prevent unintentional forks due to the error reports and failures shared here last weekend.
In terms of inspecting the changes to the original code and seeing what was modified is exactly what was advertised - I think the commits make this possible for most people quite easily.
I was motivated to do the work because it would have a serious impact on the health and longevity of the Noodlyappendagecoin network.
Best Regards,
-Chicago
it's a fresh wallet.dat too, it ran okay earlier in the day and was all caught up with the one node at that time.
The "network" primarily has been the node I published earlier in the week and one Windows 7 node which is connected with it.
About 10 hours ago, I rebooted my hypervisor and had forgot to restart the Windows wallet so that there would be at least one connection to the other node.
I've started it back up and also ran another test with the updated code on Ubuntu 18.04 LTS and it is syncing now too.
I see you're not exactly running my build. There are some key differences in your output compared to what is produced by the published code.
Code:
testcoins@carpdiem:~$ rc.ndl2 start
nice --adjustment=2 /usr/local/bin/noodly2d-0862 -port=24021 -rpcport=12022 -txindex
testcoins@carpdiem:~$ Noodlyappendagecoin server starting
noodly2d-0862: main.cpp:1802: bool SetBestChain(CValidationState&, CBlockIndex*): Assertion `pfork != NULL' failed.
2018-10-20 17:49:08 Noodlyappendagecoin version v0.8.6.21-unk-dnp (Oct 20 2018, 13:17:03)
2018-10-20 17:49:08 Using OpenSSL version OpenSSL 1.0.2p 14 Aug 2018
2018-10-20 17:49:21 nFileVersion = 80621
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.
There are some other notable differences during startup I have highlighted above from your post.
Here is what a debug.log startup sequence looks like with the code I have shared.
2018-10-21 05:09:48 Noodlyappendagecoin version v0.8.6.2 (2018-10-16 00:37:04 -0500)
2018-10-21 05:09:48 Using OpenSSL version OpenSSL 1.0.1 14 Mar 2012
2018-10-21 05:09:48 Default data directory /home/ubuntu/.noodlyappendagecoin
2018-10-21 05:09:48 Using data directory /home/ubuntu/.noodlyappendagecoin
2018-10-21 05:09:48 Using at most 125 connections (1024 file descriptors available)
2018-10-21 05:09:48 Using 6 threads for script verification
2018-10-21 05:09:48 init message: Verifying wallet...
2018-10-21 05:09:48 dbenv.open LogDir=/home/ubuntu/.noodlyappendagecoin/database ErrorFile=/home/ubuntu/.noodlyappendagecoin/db.log
2018-10-21 05:09:48 Bound to [::]:40021
2018-10-21 05:09:48 Bound to 0.0.0.0:40021
2018-10-21 05:09:48 scrypt: using scrypt-sse2 as built.
2018-10-21 05:09:48 init message: Loading block index...
2018-10-21 05:09:48 Opening LevelDB in /home/ubuntu/.noodlyappendagecoin/blocks/index
2018-10-21 05:09:48 Opened LevelDB successfully
2018-10-21 05:09:48 Opening LevelDB in /home/ubuntu/.noodlyappendagecoin/chainstate
2018-10-21 05:09:48 Opened LevelDB successfully
2018-10-21 05:09:48 LoadBlockIndexDB(): last block file = 0
2018-10-21 05:09:48 LoadBlockIndexDB(): transaction index disabled
2018-10-21 05:09:48 Initializing databases...
2018-10-21 05:09:48 45e34031cd491ea08d7224b91435c465cd40e0837642d6cfd1cccad93122e901
2018-10-21 05:09:48 45e34031cd491ea08d7224b91435c465cd40e0837642d6cfd1cccad93122e901
2018-10-21 05:09:48 4fc0120077bbf01025690bb2b924f60729b43be8e63888c1be84d6efdeb48c74
2018-10-21 05:09:48 CBlock(hash=45e34031cd491ea08d7224b91435c465cd40e0837642d6cfd1cccad93122e901, input=010000000000000000000000000000000000000000000000000000000000000000000000748cb4deefd684bec18838e6e83bb42907f624b9b20b692510f0bb770012c04f18dac452f0ff0f1e3a6c1a00, PoW=0000040936beff57487bfa2a3705ead129933e72e57eaff1789ec4155e5fb358, ver=1, hashPrevBlock=0000000000000000000000000000000000000000000000000000000000000000, hashMerkleRoot=4fc0120077bbf01025690bb2b924f60729b43be8e63888c1be84d6efdeb48c74, nTime=1388632600, nBits=1e0ffff0, nNonce=1731642, vtx=1)
2018-10-21 05:09:48 CTransaction(hash=4fc0120077bbf01025690bb2b924f60729b43be8e63888c1be84d6efdeb48c74, ver=1, vin.size=1, vout.size=1, nLockTime=0)
CTxIn(COutPoint(0000000000000000000000000000000000000000000000000000000000000000, 4294967295), coinbase 04ffff001d0104404e657720596f726b2054696d65732033312d31322d32303133203a20536f205 6616c7561626c652c20497420436f756c6420416c6d6f7374204265205265616c)
CTxOut(nValue=50.00000000, scriptPubKey=040184710fa689ad5023690c80f3a4)
vMerkleTree: 4fc0120077bbf01025690bb2b924f60729b43be8e63888c1be84d6efdeb48c74
2018-10-21 05:09:48 Pre-allocating up to position 0x1000000 in blk00000.dat
2018-10-21 05:09:48 SetBestChain: new best=45e34031cd491ea08d7224b91435c465cd40e0837642d6cfd1cccad93122e901 height=0 log2_work=20.000022 tx=1 date=2014-01-02 03:16:40 progress=0.000001
2018-10-21 05:09:48 init message: Verifying blocks...
2018-10-21 05:09:48 block index 86ms
2018-10-21 05:09:48 init message: Loading wallet...
2018-10-21 05:09:49 nFileVersion = 80602
2018-10-21 05:09:49 Performing wallet upgrade to 60000
2018-10-21 05:09:49 keypool added key 1, size=1
.
.
.
2018-10-21 05:09:49 keypool added key 101, size=101
2018-10-21 05:09:49 keypool reserve 1
2018-10-21 05:09:49 keypool keep 1
2018-10-21 05:09:49 wallet 633ms
2018-10-21 05:09:49 init message: Loading addresses...
2018-10-21 05:09:49 ERROR: CAddrman::Read() : open failed
2018-10-21 05:09:49 Invalid or missing peers.dat; recreating
2018-10-21 05:09:49 Loaded 0 addresses from peers.dat 0ms
2018-10-21 05:09:49 mapBlockIndex.size() = 1
2018-10-21 05:09:49 nBestHeight = 0
2018-10-21 05:09:49 setKeyPool.size() = 100
2018-10-21 05:09:49 mapWallet.size() = 0
2018-10-21 05:09:49 mapAddressBook.size() = 1
2018-10-21 05:09:49 upnp thread start
2018-10-21 05:09:49 dnsseed thread start
2018-10-21 05:09:49 Loading addresses from DNS seeds (could take a while)
2018-10-21 05:09:49 0 addresses found from DNS seeds
2018-10-21 05:09:49 dnsseed thread exit
2018-10-21 05:09:49 net thread start
2018-10-21 05:09:49 addcon thread start
2018-10-21 05:09:49 opencon thread start
The sources in the repository are nearly identical to the original code published in 2014.
The changes are all cleanly visible in the commit history.
I have also prepared a Linux binary.
You may find it on the releases page of the repository here.
Please note it too is linked with Berkeley DB v5.3.
i'm also a bit unclear, it this simply a 'test' network or a serious attempt at hardforking everyone over to the new pch value?
This is a transparent and serious attempt to repair the network and to prevent unintentional forks due to the error reports and failures shared here last weekend.
In terms of inspecting the changes to the original code and seeing what was modified is exactly what was advertised - I think the commits make this possible for most people quite easily.
I was motivated to do the work because it would have a serious impact on the health and longevity of the Noodlyappendagecoin network.
Best Regards,
-Chicago
October 20, 2018, 12:54:06 PM
so, playing with Chicago's modified ndl
when i (re)start the daemon today i get
it's a fresh wallet.dat too, it ran okay earlier in the day and was all caught up with the one node at that time.
i'm also a bit unclear, it this simply a 'test' network or a serious attempt at hardforking everyone over to the new pch value?
when i (re)start the daemon today i get
Code:
testcoins@carpdiem:~$ rc.ndl2 start
nice --adjustment=2 /usr/local/bin/noodly2d-0862 -port=24021 -rpcport=12022 -txindex
testcoins@carpdiem:~$ Noodlyappendagecoin server starting
noodly2d-0862: main.cpp:1802: bool SetBestChain(CValidationState&, CBlockIndex*): Assertion `pfork != NULL' failed.
2018-10-20 17:49:08 Noodlyappendagecoin version v0.8.6.21-unk-dnp (Oct 20 2018, 13:17:03)
2018-10-20 17:49:08 Using OpenSSL version OpenSSL 1.0.2p 14 Aug 2018
2018-10-20 17:49:08 Default data directory /home/testcoins/.noodlyappendagecoin
2018-10-20 17:49:08 Using data directory /home/testcoins/.noodlyappendagecoin
2018-10-20 17:49:08 Using at most 20 connections (1024 file descriptors available)
2018-10-20 17:49:08 Using 8 threads for script verification
2018-10-20 17:49:08 init message: Verifying wallet...
2018-10-20 17:49:08 dbenv.open LogDir=/home/testcoins/.noodlyappendagecoin/database ErrorFile=/home/testcoins/.noodlyappendagecoin/db.log
2018-10-20 17:49:08 Bound to [::]:24021
2018-10-20 17:49:08 Bound to 0.0.0.0:24021
2018-10-20 17:49:08 init message: Loading block index...
2018-10-20 17:49:08 Opening LevelDB in /home/testcoins/.noodlyappendagecoin/blocks/index
2018-10-20 17:49:09 Opened LevelDB successfully
2018-10-20 17:49:09 Opening LevelDB in /home/testcoins/.noodlyappendagecoin/chainstate
2018-10-20 17:49:09 Opened LevelDB successfully
2018-10-20 17:49:21 LoadBlockIndexDB(): last block file = 2
2018-10-20 17:49:21 LoadBlockIndexDB(): last block file info: CBlockFileInfo(blocks=375533, size=84622739, heights=939774...1315306, time=2017-05-26...2018-10-20)
2018-10-20 17:49:21 LoadBlockIndexDB(): transaction index enabled
2018-10-20 17:49:21 LoadBlockIndexDB(): hashBestChain=4f108d0f34539f50645e193d211a5e63f2fd5ce3eee88f3fee926fd22678c528 height=1315306 date=2018-10-20 17:45:15
2018-10-20 17:49:21 init message: Verifying blocks...
2018-10-20 17:49:21 Verifying last 288 blocks at level 3
2018-10-20 17:49:21 No coin database inconsistencies in last 289 blocks (289 transactions)
2018-10-20 17:49:21 block index 12854ms
2018-10-20 17:49:21 init message: Loading wallet...
2018-10-20 17:49:21 nFileVersion = 80621
2018-10-20 17:49:22 wallet 230ms
it's a fresh wallet.dat too, it ran okay earlier in the day and was all caught up with the one node at that time.
i'm also a bit unclear, it this simply a 'test' network or a serious attempt at hardforking everyone over to the new pch value?
October 18, 2018, 04:30:33 PM
omg, and I thought ... not to mention.
We are not stable, as we are writing. ...
I am sure this has to be solved.
the day weed becomes legal in this country the internet goes to pot
worse than drugs is only reality. :-)
https://www.youtube.com/watch?v=qhnFl3Y2FVI&index=8&list=RDnbjnS_RTj_o
n.
October 17, 2018, 09:29:14 PM
omg, and I thought ... not to mention.
We are not stable, as we are writing. ...
I am sure this has to be solved.
the day weed becomes legal in this country the internet goes to pot
October 17, 2018, 07:08:40 PM
dnp's coins.dognose.net server is down.
I hope nothing bad happened.
n.
I hope nothing bad happened.
n.
TekSavvy Assistance
@TekSavvyCSR
Many customers on the Cable network around Ontario may be experiencing a issue with the service.
This is impacting all customers that are using Third Party Internet Access providers on
the Rogers infrastructure. We will update all customers when we know more information. -BP
thankfully i also have lightweight DSL with my fibre television service
i can go out, but nobody gets in.
omg, and I thought ... not to mention.
We are not stable, as we are writing. ...
I am sure this has to be solved.
n.
October 17, 2018, 06:41:18 PM
TekSavvy Assistance
@TekSavvyCSR
Many customers on the Cable network around Ontario may be experiencing a issue with the service.
This is impacting all customers that are using Third Party Internet Access providers on
the Rogers infrastructure. We will update all customers when we know more information. -BP
https://youtu.be/s_Whz9yapTc?t=70
-Dave
it's a very good inside view of Rogers Cable network support
October 17, 2018, 06:30:58 PM
TekSavvy Assistance
@TekSavvyCSR
Many customers on the Cable network around Ontario may be experiencing a issue with the service.
This is impacting all customers that are using Third Party Internet Access providers on
the Rogers infrastructure. We will update all customers when we know more information. -BP
https://youtu.be/s_Whz9yapTc?t=70
-Dave
October 17, 2018, 06:20:28 PM
dnp's coins.dognose.net server is down.
I hope nothing bad happened.
n.
I hope nothing bad happened.
n.
TekSavvy Assistance
@TekSavvyCSR
Many customers on the Cable network around Ontario may be experiencing a issue with the service.
This is impacting all customers that are using Third Party Internet Access providers on
the Rogers infrastructure. We will update all customers when we know more information. -BP
thankfully i also have lightweight DSL with my fibre television service
i can go out, but nobody gets in.
October 17, 2018, 03:04:22 PM
dnp's coins.dognose.net server is down.
I hope nothing bad happened.
n.
I hope nothing bad happened.
n.
October 16, 2018, 06:41:52 AM
October 16, 2018, 04:33:52 AM
I've been taking the "Network ID" as the pchmessage code. Perhaps they are not the same thing.
The Network ID is the first four bytes of every block.
Wire protocol is little-endian.
The pchMessageStart is the same as the Network ID.
October 16, 2018, 04:29:01 AM
Nevertheless, this seems important: Are you on the same chain as our blockexplorer (daves work)?
http://explorer.noodlyappendagecoin.net/
http://explorer.noodlyappendagecoin.net/
Yes, same chain.
The hash at height 1314626 from the FSM bootstrap.dat in the new peer swarm matches the hash on the explorer.
be76cac6a6c69b2eedbb2972722ffdbb5e18a0b83a5f59f9cc5cb5adc992bfc6
Divergence begins at 1314626 +1 because obviously I couldn't magically upgrade software remotely for everyone around the planet.
Best Regards,
-Chicago
October 16, 2018, 04:23:09 AM
(...)
There is one full node only and it is not mining.
addnode=23.253.205.134
addnode=[2001:4801:7825:102:be76:4eff:fe10:3d29]
If you would like to participate, just run the new code and start your miner.
I am hoping this solves the network problems we discussed over the weekend and acts as a stop-gap until we perform another network upgrade to implement BIP 34 and BIP 66.
This interim client should make things easier on future development so there are less exceptions written into the code.
This interim client is not meant to hinder other development efforts.
This client is a clean break from the v0.8.6.1 network.
There was approximately a 12 hour difference between the snapshot at height 1314626 and this public release.
If I picked the wrong fork of the chain, let me know and we can do this experiment again with another chain.
I selected this chain because it is the one which His Holy Noodliness's code identifies with in the peer swarm.
Best Regards,
-Chicago
There is one full node only and it is not mining.
addnode=23.253.205.134
addnode=[2001:4801:7825:102:be76:4eff:fe10:3d29]
If you would like to participate, just run the new code and start your miner.
I am hoping this solves the network problems we discussed over the weekend and acts as a stop-gap until we perform another network upgrade to implement BIP 34 and BIP 66.
This interim client should make things easier on future development so there are less exceptions written into the code.
This interim client is not meant to hinder other development efforts.
This client is a clean break from the v0.8.6.1 network.
There was approximately a 12 hour difference between the snapshot at height 1314626 and this public release.
If I picked the wrong fork of the chain, let me know and we can do this experiment again with another chain.
I selected this chain because it is the one which His Holy Noodliness's code identifies with in the peer swarm.
Best Regards,
-Chicago
Will look at it these days, I am very happy that thoughts and efforts do come up these days!
Nevertheless, this seems important: Are you on the same chain as our blockexplorer (daves work)?
http://explorer.noodlyappendagecoin.net/
If yes, I have got a few ideas too, what we can do to secure that this remains to be the right side of the ndl-blockchain.
:-)
Geez,
n.
October 16, 2018, 03:21:15 AM
Quote
In my experiment, I set the Network ID to FSM1.
It wasn't too much effort to render a linear bootstrap.dat using the new Network ID.
It wasn't too much effort to render a linear bootstrap.dat using the new Network ID.
I've been taking the "Network ID" as the pchmessage code. Perhaps they are not the same thing.
Jump to: