Bitcoin Forum
October 08, 2024, 10:35:15 PM *
News: Latest Bitcoin Core release: 28.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 ... 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 [75] 76 77 78 79 80 81 82 83 84 »
  Print  
Author Topic: [ANN] NDL - The coin for Pastafarians - Flying Spaghetti Monster Cryptocurrency!  (Read 125287 times)
garmin
Hero Member
*****
Offline Offline

Activity: 550
Merit: 501


View Profile
January 04, 2019, 04:52:00 AM
 #1481

Whats next for NDL?  any exchange prospects?

Once the new forks occur exchange prospects will blow up.  We need the new protocol updates that will occur in February to be added to exchanges.

Please help test the new wallet to assist us in reaching that point:


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

Windows 64-Bit Exe:
https://github.com/number435398/Noodlyappendagecoin-project/blob/master/noodlyappendagecoin-qt%20v%2015.2.exe

Windows 32-bit Exe:
https://github.com/number435398/Noodlyappendagecoin-project/blob/master/noodlyappendagecoin-qt%20v15.2%2032%20bit.exe

Linux Binaries:
https://github.com/number435398/Noodlyappendagecoin-project/blob/master/noodlyappendagecoin%20linux%20binaries.zip


solo mining is working with win wallet
number435398
Jr. Member
*
Offline Offline

Activity: 260
Merit: 6


View Profile
January 04, 2019, 10:12:00 AM
 #1482

Whats next for NDL?  any exchange prospects?

Once the new forks occur exchange prospects will blow up.  We need the new protocol updates that will occur in February to be added to exchanges.

Please help test the new wallet to assist us in reaching that point:


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

Windows 64-Bit Exe:
https://github.com/number435398/Noodlyappendagecoin-project/blob/master/noodlyappendagecoin-qt%20v%2015.2.exe

Windows 32-bit Exe:
https://github.com/number435398/Noodlyappendagecoin-project/blob/master/noodlyappendagecoin-qt%20v15.2%2032%20bit.exe

Linux Binaries:
https://github.com/number435398/Noodlyappendagecoin-project/blob/master/noodlyappendagecoin%20linux%20binaries.zip


solo mining is working with win wallet

Within the wallet or with an external program?
garmin
Hero Member
*****
Offline Offline

Activity: 550
Merit: 501


View Profile
January 04, 2019, 03:43:26 PM
 #1483

Whats next for NDL?  any exchange prospects?

Once the new forks occur exchange prospects will blow up.  We need the new protocol updates that will occur in February to be added to exchanges.

Please help test the new wallet to assist us in reaching that point:


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

Windows 64-Bit Exe:
https://github.com/number435398/Noodlyappendagecoin-project/blob/master/noodlyappendagecoin-qt%20v%2015.2.exe

Windows 32-bit Exe:
https://github.com/number435398/Noodlyappendagecoin-project/blob/master/noodlyappendagecoin-qt%20v15.2%2032%20bit.exe

Linux Binaries:
https://github.com/number435398/Noodlyappendagecoin-project/blob/master/noodlyappendagecoin%20linux%20binaries.zip


solo mining is working with win wallet

Within the wallet or with an external program?

using cpuminer-gw64-corei7
number435398
Jr. Member
*
Offline Offline

Activity: 260
Merit: 6


View Profile
January 04, 2019, 04:26:38 PM
 #1484

Whats next for NDL?  any exchange prospects?

Once the new forks occur exchange prospects will blow up.  We need the new protocol updates that will occur in February to be added to exchanges.

Please help test the new wallet to assist us in reaching that point:


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

Windows 64-Bit Exe:
https://github.com/number435398/Noodlyappendagecoin-project/blob/master/noodlyappendagecoin-qt%20v%2015.2.exe

Windows 32-bit Exe:
https://github.com/number435398/Noodlyappendagecoin-project/blob/master/noodlyappendagecoin-qt%20v15.2%2032%20bit.exe

Linux Binaries:
https://github.com/number435398/Noodlyappendagecoin-project/blob/master/noodlyappendagecoin%20linux%20binaries.zip


solo mining is working with win wallet

Within the wallet or with an external program?

using cpuminer-gw64-corei7

Okay, awesome.  I might be using the same one myself.  Almost thought you were referring to the in wallet miner (which was disabled in the newer versions to avoid false virus detections).
btctrad0r
Member
**
Offline Offline

Activity: 324
Merit: 79


View Profile
January 13, 2019, 06:52:10 AM
 #1485

Whats next for NDL?  any exchange prospects?

Once the new forks occur exchange prospects will blow up.  We need the new protocol updates that will occur in February to be added to exchanges.

Please help test the new wallet to assist us in reaching that point:


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

Windows 64-Bit Exe:
https://github.com/number435398/Noodlyappendagecoin-project/blob/master/noodlyappendagecoin-qt%20v%2015.2.exe

Windows 32-bit Exe:
https://github.com/number435398/Noodlyappendagecoin-project/blob/master/noodlyappendagecoin-qt%20v15.2%2032%20bit.exe

Linux Binaries:
https://github.com/number435398/Noodlyappendagecoin-project/blob/master/noodlyappendagecoin%20linux%20binaries.zip


cool downloaded this one for testing.
btw please keep the old splash screen it was quite cool.
number435398
Jr. Member
*
Offline Offline

Activity: 260
Merit: 6


View Profile
January 18, 2019, 12:07:52 AM
 #1486

Noodlyappendagecoin Wallet Release v 0.15.2

I have just released version 0.15.2 of the Noodlyappendagecoin Wallet!

Periodically backup your wallet.dat file!  Especially when changing wallet programs!

This version is meant to be the full usable version, however, it will not fully take hold until February 1st, 2019.  In the interim it will fully function as your wallet and will sync with the network and explorer.  So if you have any concerns, or notice any bugs, this version is not considered to be “Official” until then.

The old wallet will work for mining until that point.  This wallet does not mine unto itself, however you can use a newer version of cpuminer to mine to the wallet using long-polling, though you must specify a specific address to mine to.

When this wallet is opened after 12:01am on February 1st, 2019, it will shift to a new pchmessage code.  This means all other wallets not hardcoded to the new code (“NDLY”) will no longer connect to the network.  If you open this wallet before that date and time, it will use the old code.  You will have to close it and reopen it to have it initiate with the new code (as it only checks the date and the code each time you open the wallet).

On February 1st, later in the day, the network will fork to apply BIP34. Then it will fork again on February 2nd for BIP65, then again on February 2nd for BIP66.  On February 8th, it will fork for BIP68, BIP112, and BIP113.  Then on February 12th, it will fork for BIP141, BIP143, and BIP147.  

Once these forks are completed we will be so up to date we will be eligible to be added to exchanges.

Previous wallets will no longer function at that point.   Even if an older wallet is coded with the new pchmessage, all blocks generated by it will be rejected and a small percentage of its sent transactions will actually be accepted (due to DER encoding).

If you wish to compile the code yourself, please refer to the build text files located in the docs folder for instructions.

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

Windows 64-Bit Exe:
https://github.com/number435398/Noodlyappendagecoin-project/blob/master/noodlyappendagecoin-qt%20v%2015.2.exe

Windows 32-bit Exe:
https://github.com/number435398/Noodlyappendagecoin-project/blob/master/noodlyappendagecoin-qt%20v15.2%2032%20bit.exe

Linux Binaries:
https://github.com/number435398/Noodlyappendagecoin-project/blob/master/noodlyappendagecoin%20linux%20binaries.zip


EDIT:  Clarified that this wallet is fully usable right now and is full replacement for existing wallets!

Two weeks everyone!  Please update your wallets or provide feedback if you've found a glitch to require that we postpone this new wallet!  Old wallets will no longer connect to the new wallets after this point unless you change the pchmessage in the code itself!  Even then it won't be able to create blocks or mine.
btctrad0r
Member
**
Offline Offline

Activity: 324
Merit: 79


View Profile
January 20, 2019, 11:13:32 PM
 #1487

always nice to come back and see some more development in this project has been done!
in nomini spaghetti sancti
ramen.
nxtraordinary
Jr. Member
*
Offline Offline

Activity: 100
Merit: 1

Pool for Future-Airdrops already at 9.000.000 NDL


View Profile
January 27, 2019, 06:40:46 PM
 #1488

always nice to come back and see some more development in this project has been done!
in nomini spaghetti sancti
ramen.

I am still not sure, unfortunately, if that isn't naive somehow.

Greez.

n.

Before we begin, we should take a hard look at ourselves first.

(galgitron)

~

NDL Donations for future Airdrops: Ngo2somW9pLj4QC8cyHWKjrpTRYm
nxtraordinary
Jr. Member
*
Offline Offline

Activity: 100
Merit: 1

Pool for Future-Airdrops already at 9.000.000 NDL


View Profile
January 27, 2019, 06:58:55 PM
 #1489


(...)

Previous wallets will no longer function at that point.   Even if an older wallet is coded with the new pchmessage, all blocks generated by it will be rejected and a small percentage of its sent transactions will actually be accepted (due to DER encoding).

(...)


I am still not sure what truely happens here. To everyone here: The old members do get more and more quiet, as there is heavy (and plausible) uncertainty, what will happen to existing funds (despite that ones of one person) in the future.

Shortly: Just why should ANYONE ELSE look at this inception as it would be an improvement?

I only am citing from the above:

Quote
"Previous wallets will no longer function at that point.   Even if an older wallet is coded with the new pchmessage, all blocks generated by it will be rejected and a small percentage of its sent transactions will actually be accepted (due to DER encoding)."

Now: What is the implication that should be a benefit to NDL-Holders, is this a win-win case or another robbery?
So far there has not been a single positive argument for the less negative cases, so I still don't know what to think about it, - and because of that: Please everyone do your own dd.


Greez.

n.


PPS: By the way, my announcement of sending 30 Million NDL to someone who creates an up to date wallet for this coin is still alive. It only should be a benefit for everyone involved benefitely ... so, perhaps we will have two chains in near future.

Before we begin, we should take a hard look at ourselves first.

(galgitron)

~

NDL Donations for future Airdrops: Ngo2somW9pLj4QC8cyHWKjrpTRYm
DaveF
Legendary
*
Offline Offline

Activity: 3626
Merit: 6611


Crypto Swap Exchange


View Profile WWW
January 27, 2019, 07:08:08 PM
 #1490


(...)

Previous wallets will no longer function at that point.   Even if an older wallet is coded with the new pchmessage, all blocks generated by it will be rejected and a small percentage of its sent transactions will actually be accepted (due to DER encoding).

(...)


I am still not sure what truely happens here. To everyone here: The old members do get more and more quiet, as there is heavy (and plausible) uncertainty, what will happen to existing funds (despite that ones of one person) in the future.

Shortly: Just why should ANYONE ELSE look at this inception as it would be an improvement?

I only am citing from the above:

Quote
"Previous wallets will no longer function at that point.   Even if an older wallet is coded with the new pchmessage, all blocks generated by it will be rejected and a small percentage of its sent transactions will actually be accepted (due to DER encoding)."

Now: What is the implication that should be a benefit to NDL-Holders, is this a win-win case or another robbery?
So far there has not been a single positive argument for the less negative cases, so I still don't know what to think about it, - and because of that: Please everyone do your own dd.


Greez.

n.


PPS: By the way, my announcement of sending 30 Million NDL to someone who creates an up to date wallet for this coin is still alive. It only should be a benefit for everyone involved benefitely ... so, perhaps we will have two chains in near future.

The only difference is that if you are mining you have to mine with the new wallet. If you have funds in an old wallet they are safe.
If you want to CPU mine now instead of just dropping to the console and typing setgenerate true, you have to put in a conf file and run a CPU miner.
If you were mining with a video card nothing has changed.

-Dave

█▀▀▀











█▄▄▄
▀▀▀▀▀▀▀▀▀▀▀
e
▄▄▄▄▄▄▄▄▄▄▄
█████████████
████████████▄███
██▐███████▄█████▀
█████████▄████▀
███▐████▄███▀
████▐██████▀
█████▀█████
███████████▄
████████████▄
██▄█████▀█████▄
▄█████████▀█████▀
███████████▀██▀
████▀█████████
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
c.h.
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
▀▀▀█











▄▄▄█
▄██████▄▄▄
█████████████▄▄
███████████████
███████████████
███████████████
███████████████
███░░█████████
███▌▐█████████
█████████████
███████████▀
██████████▀
████████▀
▀██▀▀
number435398
Jr. Member
*
Offline Offline

Activity: 260
Merit: 6


View Profile
January 29, 2019, 09:39:16 AM
 #1491


(...)

Previous wallets will no longer function at that point.   Even if an older wallet is coded with the new pchmessage, all blocks generated by it will be rejected and a small percentage of its sent transactions will actually be accepted (due to DER encoding).

(...)


I am still not sure what truely happens here. To everyone here: The old members do get more and more quiet, as there is heavy (and plausible) uncertainty, what will happen to existing funds (despite that ones of one person) in the future.


I will explain what happens.  All wallets have a "pchmessage" code.  This code is generally used to keep wallets from other coins from interacting with wallets of other coins.

Currently, we have the same "pchmessage" code as Litecoin (you can see this discussion in previous posts).  

As a result, if we added the ip address of a node to the NDL wallet that was the ip address for a node of a Litecoin wallet, both that Litecoin wallet and our wallet will think they're talking to a wallet of the same coin.  This is why our network is inundated with alt-coin wallet nodes.  Because as soon as those two wallets confirm they've got the same "pchmessage" code, they'll start sending each other their list of other nodes.  So a single Litecoin node added to our wallets will result in our wallets asking that Litecoin wallet for all of its nodes regardless of whether the blockchain is our chain or not.  Our wallet just wants to know the nodes.  Only after our wallet gets the nodes will it begin to check the blockchains on those nodes and confirm that they are not on our blockchain.  So one Litecoin ip address added to our wallets will result in our wallets getting inundated with the hundreds, if not thousands, of other nodes that have the same "pchmessage" code, including Litecoin and other alt-coin wallets.  Eventually our wallets will reject all of them because they're not on the same blockchain, but it still takes up a lot of processing time and power and is ultimately just messy.  

The original Dev for Noodlyappendagecoin forgot to change the pchmessage code to something other than the one used by Litecoin.  By changing that code, our wallets will only interact with other nodes with the same pchmessage.  Since old Noodlyappendagecoin wallets will have the old pchmessage code (the same as litecoin) they will stop connecting to the new wallets.

This was not an issue previously because no one had input an ip address for a Litecoin node until recently.  That's when our network started to get messy.  As explained; all it takes is a single Litecoin node to cause a cascade of disruption.

Regarding the new DER encoding.  All transactions have an R and and S value in them, used for the signature verification.  With the new encoding, it was decided that the "S" value couldn't be less than or higher than some specified value  (I don't recall the exact specifics).  The theory was this would eliminate some problems with people tweaking the transactions as technically there are normally 2 valid "S" values for every transaction and changing this mitigated it to some extent.  Its been a while since I've looked it up.  The result is that a wallet that doesn't take into consideration the new "valid" values of the "S" value will send transactions that don't conform to this rule and the new wallets will therefor reject those transactions.  Some may still make it through since the S value correlates with a random number and can change each time you try to send a transaction.

The application of DER encoding is standard at this point in cryptocurrencies.  Bitcoin uses and Litecoin uses it and they both had to transition to the DER encoding thereby effectively disabling old wallets.  This transition is not some arbitrary decision on my part, its normal.

Additionally, as a result of the aforementioned dynamics, old wallets will try to submit blocks to the blockchain that have the now-determined-to-be invalid S values, which would result in that block being rejected.  This would prevent old wallets from being able to mine once the fork goes into effect.  This is the same set of "growing pains" that Bitcoin and Litecoin experienced when adding the DER encoding; its nothing new.


To reference your insinuation of my funds:

There is no code to change existing wallets' funds.

There's no modification of funds of any wallet.  There's only one hard coded allocation of funds and that's the original address for the first block that the original dev setup.  You can see it at:

https://github.com/number435398/Noodlyappendagecoin-project/blob/a4e384415428af9747ba569871e8366880919c13/src/validation.cpp#L1041-L1052

Code:
static const uint64_t TOTAL_GENERATION = MAX_MONEY;
static const double FSM_FUNDS = 0.03;
uint64_t nSubsidy = 10000 * COIN;


CAmount GetBlockSubsidy(int nHeight, const Consensus::Params& consensusParams)
{
    if(nHeight == 1)
    {
   nSubsidy = TOTAL_GENERATION * FSM_FUNDS;
// return nSubsidy + nFees;
        return nSubsidy;
    }

The original code shows the same:

https://github.com/His-Holy-Noodliness/noodlyappendagecoin/blob/1393e84397788417500a49349f1d41f7bc40759d/src/main.cpp#L1067-L1076

Code:
int64 static GetBlockValue(int nHeight, int64 nFees)
{
// standard block payouts are 10000 coins
    int64 nSubsidy = 10000 * COIN;


      if(nHeight == 1)
      {
nSubsidy = TOTAL_GENERATION * FSM_FUNDS;
return nSubsidy + nFees;
      }

This can be further confirmed at http://explorer.noodlyappendagecoin.net/block/a7d3e05f3f9e39a4676ea3e58a41718027786a4e05f37201e55c7f9b5713b706

If I had tried to change that it would alter the entire blockchain and the entire block chain would get rejected.  I actually had that problem early on when I hadn't set Block 1 to the proper amount that was already in the blockchain; the new wallet would reject the entire blockchain beginning with Block 1.

Quote

Shortly: Just why should ANYONE ELSE look at this inception as it would be an improvement?



According to standard exchanges, NDL is "worthless".  If we upgrade it to the new protocols it can then be traded and therefor will be considered to have worth.  I'd say that's quite valuable.  Your 30 million NDL is currently worth $0.00.  If there are no bugs with the new wallet, then that 30 million NDL becomes worth $1050 if NDL trades for 1 satoshi each.  For every satoshi of value that an NDL increases it multiplies that $1050 by the number of satoshi.  

I don't know what uncertainty there could be.  The code is available for perusal, and has been for months, but its just a mod of the Litecoin wallet, which is standard.  I have also consistently advocated people backup their wallets.  I, myself, have multiple old folders that are time and date stamped for the purpose of archiving old variations on the blockchain if it is needed for subsequent reference.  If there's some massive bug we've overlooked; we'll roll it back.  But we can't just sit around and refuse to go outside because something might happen to us; we have to grow.


Quote
I only am citing from the above:

Quote
"Previous wallets will no longer function at that point.   Even if an older wallet is coded with the new pchmessage, all blocks generated by it will be rejected and a small percentage of its sent transactions will actually be accepted (due to DER encoding)."

Now: What is the implication that should be a benefit to NDL-Holders, is this a win-win case or another robbery?
So far there has not been a single positive argument for the less negative cases, so I still don't know what to think about it, - and because of that: Please everyone do your own dd.



So, because there is "no positive argument for the less negative case" people should be running for the hills?  I don't even know what statement, that hasn't already been made, would fit your criteria.  The repository is there if you want to go over it.  If you're so concerned that I'm making some irreversible, malicious, and or inappropriate changes, then go through the code, and or keep a backup copy of the current chain and your current wallet.  I've always advocated backing up one's wallet.

Then you're accusing me of robbery?  You're accusing me of spending around a year of being in this forum and months of programming in an attempt to try to rip off a very small community of a coin that doesn't even have value, that is also, by some, considered to be "dead" and that may still end up being worth nothing even after all this effort on my part and DaveF's part.  The last time this coin was traded, I think it was worth around 5 NDL per 1 satoshi, so your 30 million would be worth a mere $210 and the entire current coin supply would be worth around $75,000, assuming someone would be willing to buy the whole coin supply.

You're accusing me of similar plans to Jon Stewart's hypothetical terrorist in this video: http://www.cc.com/video-clips/gn2sjr/the-daily-show-with-jon-stewart-friends-without-benefits---9-11-responders
Its from the Zadroga Bill; the bill to help pay 9/11 first responders' medical bills.  This was necessary since so many of them were dying from strange cancers and even selling off their homes and all their possessions just to be able to afford to pay their medical bills for their cancers that were caused by them helping people and helping clean up on 9/11.  Someone wanted to add an amendment to the bill that stated that terrorists couldn't receive payments to cover their medical bills from 9/11, but, that doesn't make sense because no terrorist would have helped save people and clean up on 9/11 to get lung cancer just to take advantage of medical benefits from the federal government.  Its not worth it nor is it realistic to assume anyone would do such.  The same thing applies here.  When you consider the hundreds of hours I've spent (yes, hundreds when you consider programming, compiling dozens of exes for testing, etc) versus what the coin is worth, I'd be a freaking moron to do that.  It wouldn't be worth it.  

I now have the knowledge and the experience to program a brand new wallet for a brand new coin if that's what I really wanted; I don't need Noodlyappendagecoin.  I want Noodlyappendagecoin.  

You're like the homeless guy claiming I want to steal your old ratty blanket as I drive up in a brand new BMW.  I'm not asking you to give me your blanket and such paranoia is really weird.  And unlike your ratty old blanket, with Noodlyappendagecoin you can always roll it back if it got bad enough.

I haven't changed the algorithm, I haven't changed the difficulty adjustment equation, I haven't changed the encryption, I haven't changed the block times, I haven't changed the difficulty change time.  I think I did add some light transaction fees (its been like 2-3 months since I released this version so I'd have to go back and double check to be exact).  I felt that making a change to the difficulty algorithm (as some suggested) was going too far for this version upgrade AND was not necessary for the growth of the coin at this time AND there was no consensus as to what to change it to.  Everything else was already programmed for me by the Bitcoin Developers, that was then modified by the Litecoin developers, which I then modified.  My changes are standard for the "industry" if you will.

Quote
PPS: By the way, my announcement of sending 30 Million NDL to someone who creates an up to date wallet for this coin is still alive. It only should be a benefit for everyone involved benefitely ... so, perhaps we will have two chains in near future.

Besides your grammer/syntax being a bit odd; I don't even remotely understand how that would result in two chains or why you would try to break this community apart for a mere wallet upgrade.  Admittedly I wanted to increase the block size, but I didn't, as I was concerned that might be too much for me to arbitrarily do that didn't conform to the criteria of "necessary".  If there's a specific thing that actually and truly harms things, then point it out.  Right now its as if you're just trying to be a doomsayer without evidence.  If you want to be a doomsayer, that's fine, go for it.  But show evidence.  If you're claiming Planet X is about to collide with the earth, then tell us the coordinates of your observations in the sky so we can confirm your suspicions.  

If you've been burned before with regards to other coins and you're apprehensive, fine, I totally get that, but explain that.  Keep a backup of your current chain and wallet; just make a copy the Noodlyappendagecoin folder in your Users> (insert user here) > AppData > Roaming folder and rename it to reference the date that you're copying it.  That way if there's a need to roll it back, you have it ready.

I've put hundreds of hours into this trying several different versions of the wallets to find which one works best etc.

I find your evidence-lacking-anti-my-new-wallet perspective to be insulting.  I've put substantial amounts of time into this project without compensation and so has DaveF.  Maybe you're comfortable with sitting around with this project not having any exchange value for 4 years and, frankly, going nowhere, but I know I'm not and I doubt DaveF is okay with that either.  I'm moving the project forward without any attack on anyone who's been involved in the project.  I even offered the original dev a substantial stake if he'd come back and remake the wallet (before I did).  He didn't respond.  

I've put tons of work into this coin.  It should be moving forward and adapting, not sitting around gathering dust.  You saw me offering 100 million NDL for someone to make the wallet.  No one took the offer.  So I did it.  We need to move forward.  Sans any major issues, I don't plan a lot of changes after this particular update either; this is the minimum necessary to garner value for this project and get traded.  We can't even fund anything regarding this project because NDL isn't worth anything so we can't even trade it or sell it to fund itself.

If you want to say you don't trust me or you're just not convinced of trust, fine, then say that.  At least clearly preface your doom-saying so that others don't think you're privy to something that you're not.

I also wonder and ask, if you're going to dismiss me as you have for all the work I've put into this, even if I disappeared, how would you treat anyone else who tried to get involved in the project, would you treat them the same way?  If you did, how long do you think they'd stay?

PS.  If I was going to steal people's NDL, then why have I been, and continue to mine to wallet address NLfFUfsgBB5GsriyzFrSAdhpT4VhGBqLgs?  Info located at http://explorer.noodlyappendagecoin.net/address/NLfFUfsgBB5GsriyzFrSAdhpT4VhGBqLgs

Going at least as far back as block 1351264 (http://explorer.noodlyappendagecoin.net/block/f98250c84982d0458217b34d84d996790e89848329966e8c8c251044ac5b690b), with hash f98250c84982d0458217b34d84d996790e89848329966e8c8c251044ac5b690b with the tx hash of 578c196cd4d42a9d6750905e1b93e5d5912179f96f29e85e1382929a27431155 (http://explorer.noodlyappendagecoin.net/tx/578c196cd4d42a9d6750905e1b93e5d5912179f96f29e85e1382929a27431155).  Why would I do that?  It'd be a waste of my time and computing power to do that if I was going to scam everyone out of their coins.
dnp
Full Member
***
Offline Offline

Activity: 401
Merit: 110


View Profile WWW
January 31, 2019, 01:38:53 AM
 #1492

of course ndl never had any intrinsic or planned value other than novelty.

that novelty comes from the spaghetti monster graphics and 'pirate talk' wallet messages.

without those in a new wallet, there is now zero instead of next-to-zero attraction to this coin.


Explorer and full node hosting at explorer.dognose.net
number435398
Jr. Member
*
Offline Offline

Activity: 260
Merit: 6


View Profile
January 31, 2019, 02:06:50 AM
 #1493

of course ndl never had any intrinsic or planned value other than novelty.

that novelty comes from the spaghetti monster graphics and 'pirate talk' wallet messages.

without those in a new wallet, there is now zero instead of next-to-zero attraction to this coin.



You have a point.  I wasn't particularly drawn due to those dynamics, but they did help with the theme.  The images are supposed to be all the same as were in the previous wallet, I copied those directly over.  I have asked for assistance regarding the msg's but haven't received any help.  Coming up with those messages are not my strong point.  As far as I could find, when looking for it, there were only a few messages that were customized.  I can update that in a new version of the wallet that doesn't require the same drama as this new one as it won't have to do with a hard fork of any sort. 

The "value" of this coin (sans actual traded value) is definitely something to think about.  Its something a lot of coins have to grapple with.  Its something that we need to grapple with.  I've been trying to wrack my brain around it for months.  Yes, we could be seen as a fun coin or a novelty coin, but we're also a religious coin.  Probably one of the first.  Most religions would likely be inclined to view a coin based upon them as offensive but I think The Church of the Flying Spaghetti Monster wouldn't begrudge us.  Its even possible we might be able to work with them too.  Thoughts? 
dnp
Full Member
***
Offline Offline

Activity: 401
Merit: 110


View Profile WWW
January 31, 2019, 03:30:33 AM
Last edit: February 02, 2019, 10:52:17 AM by dnp
 #1494

well, looks like i wont have the luxury of a 'quck install'
and, no, i will not use a premade binary - besides trust issues, i need to move over some source
mods necessary for my own internal sysadmin functions.

i did a ./autogen.sh, then a ./configure, then make

i'll eventually get around to making it work, but i will be out of town all day jan.31st
so i guess my node goes offline, probably for the best i avoid the instability of the first day anyway Smiley


root@carpdiem:/usr/local/src/_coins/ndl/noodly-0.15.2# gcc --version
gcc (GCC) 5.5.0
Copyright (C) 2015 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

root@carpdiem:/usr/local/src/_coins/ndl/noodly-0.15.2# uname -a
Linux carpdiem 4.4.14 #2 SMP Fri Jun 24 13:38:27 CDT 2016 x86_64 AMD FX(tm)-8320 Eight-Core Processor AuthenticAMD GNU/Linux

root@carpdiem:/usr/local/src/_coins/ndl/noodly-0.15.2# cat /etc/os-release
NAME=Slackware
VERSION="14.2"
ID=slackware
VERSION_ID=14.2
PRETTY_NAME="Slackware 14.2"
ANSI_COLOR="0;34"
CPE_NAME="cpe:/o:slackware:slackware_linux:14.2"
HOME_URL="http://slackware.com/"
SUPPORT_URL="http://www.linuxquestions.org/questions/slackware-14/"
BUG_REPORT_URL="http://www.linuxquestions.org/questions/slackware-14/"

root@carpdiem:/usr/local/src/_coins/ndl/noodly-0.15.2# make
...
  CXX      rpc/libbitcoin_server_a-net.o
  CXX      rpc/libbitcoin_server_a-rawtransaction.o
  CXX      rpc/libbitcoin_server_a-server.o
rpc/server.cpp: In function 'void RPCTypeCheckArgument(const UniValue&, UniValue::VType)':
rpc/server.cpp:80:132: error: 'strprintf' was not declared in this scope
         throw JSONRPCError(RPC_TYPE_ERROR, strprintf("Expected type %s, got %s", uvTypeName(typeExpected), uvTypeName(value.type())));
                                                                                                                                    ^
rpc/server.cpp: In function 'void RPCTypeCheckObj(const UniValue&, const std::map<std::basic_string<char>, UniValueType>&, bool, bool)':
rpc/server.cpp:92:79: error: 'strprintf' was not declared in this scope
             throw JSONRPCError(RPC_TYPE_ERROR, strprintf("Missing %s", t.first));
                                                                               ^
rpc/server.cpp:96:73: error: 'strprintf' was not declared in this scope
                 uvTypeName(t.second.type), t.first, uvTypeName(v.type()));
                                                                         ^
rpc/server.cpp:107:67: error: 'strprintf' was not declared in this scope
                 std::string err = strprintf("Unexpected key %s", k);
                                                                   ^
rpc/server.cpp: In function 'uint256 ParseHashV(const UniValue&, std::string)':
rpc/server.cpp:134:125: error: 'strprintf' was not declared in this scope
         throw JSONRPCError(RPC_INVALID_PARAMETER, strprintf("%s must be of length %d (not %d)", strName, 64, strHex.length()));
                                                                                                                             ^
...blah blah blah

Makefile:5833: recipe for target 'rpc/libbitcoin_server_a-server.o' failed
make[2]: *** [rpc/libbitcoin_server_a-server.o] Error 1
make[2]: Leaving directory '/usr/local/src/_coins/ndl/noodly-0.15.2/src'
Makefile:9345: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/usr/local/src/_coins/ndl/noodly-0.15.2/src'
Makefile:746: recipe for target 'all-recursive' failed
make: *** [all-recursive] Error 1

            

Explorer and full node hosting at explorer.dognose.net
number435398
Jr. Member
*
Offline Offline

Activity: 260
Merit: 6


View Profile
January 31, 2019, 12:02:56 PM
 #1495

well, looks like i wont have the luxury of a 'quck install'
and, no, i will not use a premade binary - besides trust issues, i need to move over some source
mods necessary for my own internal sysadmin functions.

i did a ./autogen.sh, then a ./configure, then make

i'll eventually get around to making it work, but i will be out of town all day jan.31st
so i guess my node goes offline, probably for the best i avoid the instability of the first day anyway Smiley


            

Totally understand. 

Regarding compiling you may just need the additional dependencies at:

https://github.com/number435398/Noodlyappendagecoin-project/blob/master/doc/build-unix.md#dependency-build-instructions-ubuntu--debian

such as
Code:
sudo apt-get install libqt5gui5 libqt5core5a libqt5dbus5 qttools5-dev qttools5-dev-tools libprotobuf-dev protobuf-compiler
sudo apt-get install libqrencode-dev
sudo apt-get install libdb4.8-dev libdb4.8++-dev
sudo apt-get install software-properties-common
sudo apt-get repository ppa:bitcoin/bitcoin
sudo apt-get update
dnp
Full Member
***
Offline Offline

Activity: 401
Merit: 110


View Profile WWW
January 31, 2019, 04:02:51 PM
 #1496


Regarding compiling you may just need the additional dependencies at:


the configure step is suppose to catch missing dependencies.

i built the current dogecoin (based on recent litecoin) in the fall without problem, so i suspect dependencies arent really the problem.
unless an obscure one has been introduced into the code base.

oh, and no apt-get on Slackware linux Smiley it has its own package manager...

Explorer and full node hosting at explorer.dognose.net
number435398
Jr. Member
*
Offline Offline

Activity: 260
Merit: 6


View Profile
January 31, 2019, 09:34:31 PM
 #1497


Regarding compiling you may just need the additional dependencies at:


the configure step is suppose to catch missing dependencies.

i built the current dogecoin (based on recent litecoin) in the fall without problem, so i suspect dependencies arent really the problem.
unless an obscure one has been introduced into the code base.

oh, and no apt-get on Slackware linux Smiley it has its own package manager...


Yeah, probably an obscure one.  To find those commands I listed I fired up the Linux VM I used to compile the linux binaries and those were the commands I used prior to the ./autogen and ./configure commands and the subsequent successful make.  So, for better or for worse, those were the packages I had to install myself to achieve success.
number435398
Jr. Member
*
Offline Offline

Activity: 260
Merit: 6


View Profile
February 01, 2019, 08:54:14 AM
 #1498

Alright guys, time to switch to the new wallet.  If you have the new wallet, its time to turn it off and turn it back on so it switches to the appropriate pch message code!  If you run into any issues, let me know!
dnp
Full Member
***
Offline Offline

Activity: 401
Merit: 110


View Profile WWW
February 02, 2019, 01:19:20 AM
Last edit: February 02, 2019, 11:23:03 AM by dnp
 #1499

i strongly suspect the source on github is not *precisely* the source use to build the binaries.
i had to make a minor edit to #include directives in three source files to get a clean build.

i'm also thinking there are brain-dead litecoin developers who set up a source boobytrap.

but i have it built and it appears to be functioning.

Explorer and full node hosting at explorer.dognose.net
number435398
Jr. Member
*
Offline Offline

Activity: 260
Merit: 6


View Profile
February 02, 2019, 03:20:01 AM
 #1500

i strongly suspect the source on github is not *precisely* the source use to build the binaries.
i had to make a minor edit to #include directives in three source files to get a clean build.
Hrmmm...I'll have to test it on my machine.  I do recall having to add some includes, but I think that was with the version 16.3 that I ended up abandoning

Quote
i'm also thinking there are brain-dead litecoin developers who set up a source boobytrap.

I actually think that's why I wasn't able to get version 16.3 working; they added something that you have to look for really really hard to find and if you don't it glitches out and won't work properly.

Quote
but i have it built and it appears to be functioning at addnode=coins.dognose.net

I see that, awesome!

Both explorers are showing up on the network!
Pages: « 1 ... 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 [75] 76 77 78 79 80 81 82 83 84 »
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!