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

[nxtraordinary]

"Somebody" created a fork (at least one) with connection to different networks

1299965


1300462


Which one is right, alas?


n.

I've been fiddling with the litecoin wallet and had set some BIP checkpoints at 1300000, so maybe I inadvertently facilitated that fork on accident while testing, idk.  I doubt it.  Which fork has the most work?

"Which fork has the most work?"


Your fork, if you simply do use more force, Mr number man.


n.

[number435398]

"Somebody" created a fork (at least one) with connection to different networks

1299965


1300462


Which one is right, alas?


n.

I've been fiddling with the litecoin wallet and had set some BIP checkpoints at 1300000, so maybe I inadvertently facilitated that fork on accident while testing, idk.  I doubt it.  Which fork has the most work?

"Which fork has the most work?"


Your fork, if you simply do use more force, Mr number man.


n.

Haven't been mining, been programming the wallet

Originally, I was merely hypothesizing that my wallet behaving strangely may have helped to split the network between two people who were mining, who were not me.

[number435398]

Okay guys, seriously, we need to start talking about this.  We may need a soft fork, if not a hard fork for the new version of the wallet I'm making.  Due to the addition of various BIPs that we need to be traded; these may cause blocks to be....not understood by old wallets due to the new protocols.  I don't know for sure, as I've only been focusing on getting it working so far.  Curious as to what block we want these new things to go into effect (so as to give everyone time to adopt the new one).  Its possible that that wont be required, but either way, I want to plan a particular block to make it easier for everyone, just in case.

[Landakhitam]

Spent a few hours looking into this.  Its not simple.  I'm concerned that such modifications may exceed my abilities.  It looks like its best to just start over again with a litecoin wallet and built it back up for NDL.

You're on the right track.

Though if you're planning to rebase, going to v0.10.4 is definitely not aiming high.
You'll want at least v0.13.0 where the internal miner is removed so that anti-virus software doesn't flag the wallet and delete it on people.

Could do some sort of master node setup, though idk how to do the programming for that.  With any coin, if you catch it soon enough, you could roll back the blockchain too.  Prioritize the chain with the trades.  Then again, that's also why I updated the code to include a hard coded checkpoint.

[number435398]

Spent a few hours looking into this.  Its not simple.  I'm concerned that such modifications may exceed my abilities.  It looks like its best to just start over again with a litecoin wallet and built it back up for NDL.

You're on the right track.

Though if you're planning to rebase, going to v0.10.4 is definitely not aiming high.
You'll want at least v0.13.0 where the internal miner is removed so that anti-virus software doesn't flag the wallet and delete it on people.

Could do some sort of master node setup, though idk how to do the programming for that.  With any coin, if you catch it soon enough, you could roll back the blockchain too.  Prioritize the chain with the trades.  Then again, that's also why I updated the code to include a hard coded checkpoint.

You updated the NDL code to include a hard coded checkpoint?

[nxtraordinary]

Chain stopped with 8 Connections to the network.

Although NOT synchronizing since 5 hours and since block 1302731 and at upjumping difficulty of 0.23986077.
So, also our blockchain explorer stopped at that point 5 hours ago!

http://explorer.noodlyappendagecoin.net/

At the moment no one can mine the coin for whatever reason, despite on a fork.

I mean - yes of course its a piracy coin, but whats that now?

The chain - at least a part of the chain - is again standing still, and also because of pretty high last given difficulty of 0.23986077 at block height 1302731, it seems plausible that there is "somebody" mining on a fork of ndl as there are these further - not syncing - connections and PoW is wanted to be high - to build a high-rated own chain.
If not on a fork, this buddy at least went in with big hash-power and left the network again after a few hours of fun.
 

So, this now simply kicked out the standard wallets of ndl this night which already got problems since a few days.

For us always this stupid alert "URGENT: Alert key compromised, upgrade required" did appear.

(Same thing happend at Nyancoin a year or so ago, it does not mean anything but leads to more confusion in the network).


n.

[nxtraordinary]

OK i am throwing in my asic, to get chain moving again, obviously it was only that greedy grip by big lonely hashpower for a blitz-attack again, that stopped the whole network.
Some people never learn in life.

Action seems to be connection to that wallet, as this account got a million after the stop, that has been verified now, hours later, where I saw it, a few minutes ago, at block height 1302736.


http://explorer.noodlyappendagecoin.net/address/NUR1r1tmhkF6dSbzty26sBeVLJ95nT9oLv


n.

Heres a documentation of that attack from last night again (much more amount of coins that beloved pirate ☠️ would get if simply one laptop runs silently through the night), also this time he did it again over about only two hours, after that, he went out, and network broke down;
especially look at the time stamp, then you see what did happen:

Latest Transactions
Show
entries
Block   Hash   Recipients   Amount (NDL)   Timestamp
1302731   88759b6387f2c6f6c568d7c20ccaad71119e7f01d563ceed7c6b5c947b6b2831   1   2500.00000000   Sat, 06 Oct 2018 03:01:32 GMT
1302730   83fd0471d2fc493188486bf0898acfd3ddef67176a4b117f118e77db68898139   1   2500.00000000   Sat, 06 Oct 2018 00:44:19 GMT
1302729   c420a1a452f9ed0f45d0bc3ff92be0f370b9ac80d54760cd96440154a1ad5b6c   1   2500.00000000   Sat, 06 Oct 2018 00:18:03 GMT
1302728   61dc83dcc79169c41358dfff6622ff1fbd2871dcd2cbe1dca22fbe9e713b091f   1   2500.00000000   Sat, 06 Oct 2018 00:17:38 GMT
1302727   f6ba1212fe3746753b1741361c6af98c042c226c30943b86e64d037c1c37f915   1   2500.00000000   Sat, 06 Oct 2018 00:17:36 GMT
1302726   bcfe35a197638bb33863eb5f8fc743ae9e6046f309a7d02af4a88bb6f5fa6911   1   2500.00000000   Sat, 06 Oct 2018 00:16:49 GMT
1302725   de8b1b8f211e3f09f4e19829c542b9f29c5e5c2d4b997e8eac3bd9df5b1b7dc0   1   2500.00000000   Sat, 06 Oct 2018 00:16:42 GMT
1302724   39f73153f091dbc20855a7a2bfd06abec1b60255404a53b824c1ad96c419478d   1   2500.00000000   Sat, 06 Oct 2018 00:15:58 GMT
1302723   49c66777188cccd99be4557098cbbbb7f924bc6777e3171929a117c0c04f9158   1   2500.00000000   Fri, 05 Oct 2018 23:31:01 GMT
1302722   d407a93c59c537222d97390b236c4610656a7b212ee14b6426da18f81820c714   1   2500.00000000   Fri, 05 Oct 2018 23:30:27 GMT
1302721   d456eada1f9fd9793f1d8716f4fbc0d7557f77131821e579ebf1fc5f892244a5   1   2500.00000000   Fri, 05 Oct 2018 23:29:19 GMT
1302720   02f8639d90722a4ba4e68fb29779a3b5d9ddda8c748ebc9071c343f6a4efc0af   1   2500.00000000   Fri, 05 Oct 2018 21:24:57 GMT
1302719   90e2176b36a13f8029adb7d921c6d8253b46cc3a452b9bd49603bad9dc86ce55   1   2500.00000000   Fri, 05 Oct 2018 21:24:52 GMT
1302718   94b9880491af885c42017c83edf305d53526795fac3c90d94b2b13f73575354d   1   2500.00000000   Fri, 05 Oct 2018 21:24:47 GMT
1302717   5551ac7bb997bc5712910e793c96d0842331fd043e93af839a54952dfc4541f2   1   2500.00000000   Fri, 05 Oct 2018 21:24:45 GMT
1302716   3f3feda3310efd659fe03e7bcd1fbe68cde06dd1520285b6320148a5441618f0   1   2500.00000000   Fri, 05 Oct 2018 21:24:44 GMT
1302715   c63b20104e69147945256b602673da9c9eb457a6a10279dfc9485785afbf7d70   1   2500.00000000   Fri, 05 Oct 2018 21:24:43 GMT
1302714   ab928fc8ccb58291c32fa0527088a787cde3522b809baa2792b5fe63168f7f52   1   2500.00000000   Fri, 05 Oct 2018 21:24:40 GMT
1302713   fe31576b884ac6c0a52567d10907e1f363091e21319d47461747a6a9c67ee77d   1   2500.00000000   Fri, 05 Oct 2018 21:24:38 GMT
1302712   df3384a0bc676f00e4be24086d06feaa9ea3d202f6711b1b281ef2e4199ca5b6   1   2500.00000000   Fri, 05 Oct 2018 21:24:37 GMT
1302711   ce4c8bdf9a1b8f243e69a03c75601556dfc37e7e223209705ac454b1ad713ba6   1   2500.00000000   Fri, 05 Oct 2018 21:24:22 GMT
1302710   033131125f1b84b69c77ad4ae7555fb8a2bb5f100424563094d410ddd9491409   1   2500.00000000   Fri, 05 Oct 2018 21:24:18 GMT
1302709   6556b2501fa8829be070ae8977c9468a15f8397fba29e6c83d13d2afe5c0d967   1   2500.00000000   Fri, 05 Oct 2018 21:24:13 GMT
1302708   d2a3f9acf699d6e41ca2ff368c82febaab51990769dc62e6533cefbeaa3049ef   1   2500.00000000   Fri, 05 Oct 2018 21:24:13 GMT
1302707   0953b7ef38c81bf50a57bf83e7467d57595c04582efecdd1da0e66c480fffb7e   1   2500.00000000   Fri, 05 Oct 2018 21:24:13 GMT
1302706   8759ffacb2f034693df20fd9ed999fbd105c7f5e3e67df36cef34bea2206cb0b   1   2500.00000000   Fri, 05 Oct 2018 21:24:02 GMT
1302705   18491a0d0ff9ba36ff27d2f2d8c3893263b0c4e7fa3ce9389a182c0addb9ba14   1   2500.00000000   Fri, 05 Oct 2018 21:23:57 GMT
1302704   1f84a8041a2827992fb0fdd2735db43d45043547b2d875320d7c6e39b3f88eb2   1   2500.00000000   Fri, 05 Oct 2018 21:23:51 GMT
1302703   7afc2ff05578150f65ec3cda0dad8404d3bed4e3ba1ece468300061942574c1a   1   2500.00000000   Fri, 05 Oct 2018 21:23:44 GMT
1302702   247a39cd4fca3d981aee56a5d8d10429b0122fe2467acdc18dcd323ca6a02509   1   2500.00000000   Fri, 05 Oct 2018 21:23:33 GMT
1302701   c7441675edabd890968938f9e5d86b6fce5f1d475adc36fb430b3949fcc5fee0   1   2500.00000000   Fri, 05 Oct 2018 21:23:32 GMT
1302700   11a31213229f26cec2bc7b2ddce4200d2584051bce5234fce50869d068287249   1   2500.00000000   Fri, 05 Oct 2018 21:23:31 GMT
1302699   005cf3e8afda156936a59dc106cfa39207966262a1abe6996e30073284edcb52   1   2500.00000000   Fri, 05 Oct 2018 21:23:27 GMT
1302698   33cceb2f4a8ec36b3abc2ab066d0797c2a1ce2aaafa4735f60069170b6668eea   1   2500.00000000   Fri, 05 Oct 2018 21:23:26 GMT
1302697   7ff8fb420f9298b2302197a749057c6a37c5357766e4cc711cd35ea965c83e81   1   2500.00000000   Fri, 05 Oct 2018 21:23:26 GMT
1302696   5ffb8bc83f168a5fe68f73e7cb27864c7b9b5247fb1a908b76e9267d8f357a0c   1   2500.00000000   Fri, 05 Oct 2018 21:23:24 GMT
1302695   228798e37c118cfc53d6316c5a8db1793dca2fe069cbecfd15b543eaa7e52318   1   2500.00000000   Fri, 05 Oct 2018 21:23:24 GMT
1302694   ae841f4abdf47d5e396f3f2624f408fb2e0c611098ec3c44a65ebdb3b04684cb   1   2500.00000000   Fri, 05 Oct 2018 21:23:19 GMT
1302693   e3fdfbaccd8f0d2f67134cc97a378f4497132f002125e265fec99986549f52ed   1   2500.00000000   Fri, 05 Oct 2018 21:23:09 GMT
1302692   be6248e50225aa5f527b4057f32e65390f63e206cd833b97060f7087e18625ee   1   2500.00000000   Fri, 05 Oct 2018 21:23:08 GMT
1302691   dadf6cd89a972723d373c8d8dee66ff7a3e64b02a233f081aad772a6884515d6   1   2500.00000000   Fri, 05 Oct 2018 21:23:06 GMT
1302690   f3852fd4f6cdb1e5a4db22673a5dc467390c404904afda9c7282f9e704d47a8c   1   2500.00000000   Fri, 05 Oct 2018 21:23:04 GMT
1302689   9f75d6ad3e17ce520c949af6ed5b08cae19cd3f2c7d0c6b2aef2ce87212177a0   1   2500.00000000   Fri, 05 Oct 2018 21:23:02 GMT
1302688   5a74e61237db3f562aa05945e49e953bc91a6fd0563542b7c6b849875695e60a   1   2500.00000000   Fri, 05 Oct 2018 21:23:00 GMT
1302687   19f2a50c413f105697bd2f9cf82e9e3685a01c0078bca3b7218ddbd5d89d4c86   1   2500.00000000   Fri, 05 Oct 2018 21:22:59 GMT
1302686   3541b8364adfff47128fb4ef00fba316a79a449aaa340996a41e759e7579aa32   1   2500.00000000   Fri, 05 Oct 2018 21:22:51 GMT
1302685   6150548a0c87efc65ec0d23072e8c0e2311311af38bbf569f282d25746a35454   1   2500.00000000   Fri, 05 Oct 2018 21:22:49 GMT
1302684   1c0f7f311fe2ac2f73b709d450a035b2f4d64a5bb265820889ae932c48a39bb8   1   2500.00000000   Fri, 05 Oct 2018 21:22:46 GMT
1302683   0ba31a985bdb9c92d2ecb76cf9a3e587dd536489b3f181ea9feae71781c93ac9   1   2500.00000000   Fri, 05 Oct 2018 21:22:45 GMT
1302682   5c4a195a596498ff4c8b659f98d2743be050277628417ad508303cfedff074cc   1   2500.00000000   Fri, 05 Oct 2018 21:22:42 GMT
1302681   0c4210e6056bbc249a64334481f2ab88dad342606fe1d3ee6224580d85722f28   1   2500.00000000   Fri, 05 Oct 2018 21:22:41 GMT
1302680   5ac6d54d44c9e3b27d06e6097ac396b09454b044236fc09ec7402f9827c5c175   1   2500.00000000   Fri, 05 Oct 2018 21:22:37 GMT
1302679   52f591d3ac9f56df83665150f1612a4d6405260bcaf419fb5151c04d963e362c   1   2500.00000000   Fri, 05 Oct 2018 21:22:33 GMT
1302678   5482c6a571c06901d880974ed040239274a0c8a5362dd22ca4df38e2396ae8b4   1   2500.00000000   Fri, 05 Oct 2018 21:22:32 GMT
1302677   3256de1f8ef954acfef35ff6c18504739a370280e547a3fe7904139129632d19   1   2500.00000000   Fri, 05 Oct 2018 21:22:21 GMT
1302676   44ff4f40d92508df4c3ade79a9e465d392df28d341a9baadae2dbaae2041d619   1   2500.00000000   Fri, 05 Oct 2018 21:21:52 GMT

etc ...

[nxtraordinary]

Blockexplorer doesn't show, but now its at 1302779, only one block away from next cycle.

Yeah, at least I can count to 60!   


n.

[number435398]

When NDL was created, the following network code was used:

Code:

pchMessageStart[0] = 0xfb;
pchMessageStart[1] = 0xc0;
pchMessageStart[2] = 0xb6;
pchMessageStart[3] = 0xdb;

The problem is that matches the Litecoin network, and several other alt coin networks.  What that means is if our wallets get an IP address for one of those coins, it'll add it and consider it to be an NDL node.  The only way to change that is to change the values of that code.  But that also means all old wallets not coded as such will not be able to connect.  

If I can ensure the block explorer can handle that, I may be applying a code change to the next wallet.   Any thoughts, objections?  Considerations?  Everyone would have to either move to the new wallet or update the actual source code in whatever wallet they were using.  I'm considering using:

Code:

pchMessageStart[0] = 0xfd;
pchMessageStart[1] = 0xc2;
pchMessageStart[2] = 0xe8;
pchMessageStart[3] = 0xfe;

I really need your guys' feedback on this as it will affect all of us.  Positive or negative, I really need your feedback.

[number435398]

as mentioned before, a DEcentralized Dexchange would be more cool and noodlier

Hey what's up?

I've been down this road a bit -- and wanted to share the following.
NoodlyAppendageCoin will need to do a network upgrade in order to participate in DEX.

Basically, the v0.10.4 Bitcoin code gets the job done as it brings SuperMajority for BIP 66 and BIP 65.

It is BIP 65 which enables DEX.

Best Regards,
-Chicago

What more do you have on that?  I've nearly completed upgrading to Bitcoin and Litecoin version 0.16.3.  What exactly do you mean by "network upgrade"?

[Chicago]

as mentioned before, a DEcentralized Dexchange would be more cool and noodlier

Hey what's up?

I've been down this road a bit -- and wanted to share the following.
NoodlyAppendageCoin will need to do a network upgrade in order to participate in DEX.

Basically, the v0.10.4 Bitcoin code gets the job done as it brings SuperMajority for BIP 66 and BIP 65.

It is BIP 65 which enables DEX.

Best Regards,
-Chicago

What more do you have on that?  I've nearly completed upgrading to Bitcoin and Litecoin version 0.16.3.  What exactly do you mean by "network upgrade"?

Hello,

So the "network upgrade" means features have been integrated by the block version changing through SuperMajority or otherwise via a softfork.

For example, BIP 34 would have its enforcement hash defined here:
https://github.com/bitcoin/bitcoin/blob/49e34e288005a5b144a642e197b628396f5a0765/src/chainparams.cpp#L80-L81

There are also remnants of where BIP 66 becomes active.
https://github.com/bitcoin/bitcoin/blob/49e34e288005a5b144a642e197b628396f5a0765/src/chainparams.cpp#L83

Similarly you will find a remnant of where BIP 65 becomes active.
https://github.com/bitcoin/bitcoin/blob/49e34e288005a5b144a642e197b628396f5a0765/src/chainparams.cpp#L82

Other parts of the network upgrade are where BIP 9 softforks would start.

For example, CSV.
https://github.com/bitcoin/bitcoin/blob/49e34e288005a5b144a642e197b628396f5a0765/src/chainparams.cpp#L97

Or SegWit.
https://github.com/bitcoin/bitcoin/blob/49e34e288005a5b144a642e197b628396f5a0765/src/chainparams.cpp#L102

==========

If you inspect the same src/chainparams.cpp file in the 0.13 branch's last release you will see the only specific block height with regards to network upgrades which must be hard-coded is for the version 2 block enforcement with BIP 34.

https://github.com/bitcoin/bitcoin/blob/v0.13.2/src/chainparams.cpp

 -- and in that file you would be able to set nStartTime / nTimeout for the BIP 9 softfork activation for CSV and SegWit -- which left unmodified will never upgraded on this network and otherwise would be marked "failed" in the getblockchaininfo output because  the triggers for them are for 2016 - 2017.

Best Regards,
-Chicago

[number435398]

You just reminded me to set the segwit up, thanks .  I'd like to release my new version tonight, but there's always something, right?  So any info on how to ensure people can still solo mine?  Or has that been disabled?  Can't get it to work.

[Chicago]

You just reminded me to set the segwit up, thanks .  I'd like to release my new version tonight, but there's always something, right?  So any info on how to ensure people can still solo mine?  Or has that been disabled?  Can't get it to work.

The internal miner was removed with v0.13.0.

It was removed because too much anti-virus software was interfering with people downloading the wallets and flagging them as cryptocurrency miners.

Try mining with https://github.com/tpruvot/cpuminer-multi.git if you want a CPU miner.

[Chicago]

It would also seem changing the difficulty adjustment algorithm to Dark Gravity Wave v3 would be immensely helpful.

[number435398]

You just reminded me to set the segwit up, thanks .  I'd like to release my new version tonight, but there's always something, right?  So any info on how to ensure people can still solo mine?  Or has that been disabled?  Can't get it to work.

The internal miner was removed with v0.13.0.

It was removed because too much anti-virus software was interfering with people downloading the wallets and flagging them as cryptocurrency miners.

Try mining with https://github.com/tpruvot/cpuminer-multi.git if you want a CPU miner.

That's what I mean.  I'm trying an external miner program and its complaining that its not getting a response.

It would also seem changing the difficulty adjustment algorithm to Dark Gravity Wave v3 would be immensely helpful.

I'm really hesitant to do that right now.  I'm concerned that might be a bit too big to apply without getting more of an explicit consensus.  Not to mention the difficulty and the result of delaying the release of the new wallet.  I'll think about it though.

[number435398]

Still working on the wallet.  Current problem; transactions aren't showing up (both coinbase and regular).  They show on the explorer, but not the wallet.  Once I get that worked out, it may be ready for release.

[number435398]

Okay, turns out the transactions aren't showing up because when I create a "new" address for the wallet, it creates an address, but doesn't record the private key....can't even dumpprivkey the private key on it.  I don't know what's going on with that as I didn't change anything like that from the litecoin code.  Anyone have any ideas?

[Chicago]

Did you set the Main network PUBKEY_ADDRESS in src/chainparams.cpp to 53 and the SECRET_KEY to 181?
Did you set the Test network PUBKEY_ADDRESS in src/chainparams.cpp to 117 and the SECRET_KEY to 245?

Reference from the original code.
https://github.com/His-Holy-Noodliness/noodlyappendagecoin/blob/1393e84397788417500a49349f1d41f7bc40759d/src/base58.h#L275-L278

[number435398]

Did you set the Main network PUBKEY_ADDRESS in src/chainparams.cpp to 53 and the SECRET_KEY to 181?
Did you set the Test network PUBKEY_ADDRESS in src/chainparams.cpp to 117 and the SECRET_KEY to 245?

Reference from the original code.
https://github.com/His-Holy-Noodliness/noodlyappendagecoin/blob/1393e84397788417500a49349f1d41f7bc40759d/src/base58.h#L275-L278

Yes, but that should not impact actual private key creation, that should only impact what format its in.

Code:

base58Prefixes[PUBKEY_ADDRESS] = std::vector<unsigned char>(1,53);
base58Prefixes[SCRIPT_ADDRESS] = std::vector<unsigned char>(1,5);
base58Prefixes[SCRIPT_ADDRESS2] = std::vector<unsigned char>(1,53);
base58Prefixes[SECRET_KEY] = std::vector<unsigned char>(1,41);

And, yes, I translated them properly.  (1,41) is necessary to produce the private key code that begins with a 7

[DaveF]

Needed to be posted: