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

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

            

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.

has anyone successfully used pywallet.py (version 1.1) on a hobonickels wallet.dat ?
if so, what are the magic options i need to feed it?
currently i'm getting a fault

Code:

%./pywallet.py --dumpwallet --dumpwithbalance --wallet=hobo.dat --datadir=.

Traceback (most recent call last):
  File "./pywallet.py", line 2062, in parse_wallet
    d['txIn'].append(parse_TxIn(vds))
  File "./pywallet.py", line 2031, in parse_TxIn
    d['sequence'] = vds.read_uint32()
  File "./pywallet.py", line 1945, in read_uint32
    def read_uint32(self): return self._read_num('<I')
  File "./pywallet.py", line 1984, in _read_num
    (i,) = struct.unpack_from(format, self.input, self.read_cursor)
error: unpack_from requires a buffer of at least 4 bytes
ERROR parsing wallet.dat, type tx

has anyone successfully used pywallet.py (version 1.1) on a bottlecaps wallet.dat ?
if so, what are the magic options i need to feed it?
currently i'm getting a fault

i admire your optimism

from a discussion specific to the cryptopia situation: https://bitcointalk.org/index.php?topic=5097916.0

"given there is a police investigation, could be months if not years for the NZ Police to establish what was taken and by whom.  Firstly there is the theft in January 2019 of Crypto to investigate, then there is the issue of potentially trading while insolvent due to Cryptopia being unable to repay to depositors funds that had been stolen via 51% attacks in the second half of 2018. Then there are the class actions to recover funds by depositors to be considered. In all likely-hood an administrator would be likely be appointed to forensically examine which accounts owned what and seek a determination from a Judge how best to distribute to the masses funds from both hot and cold wallets which is why I am trying to gather together in this thread proof of what crypto was stolen and what hot and cold wallets have been left intact (not to mention any class actions & news articles on the Police's investigation and the NZ Crown's DPP potentially laying charges ( and the time frames those proceedings might take) ).

Get yourself a pen and paper and write down as many details as you can about your own account.

user name, password, email address - any 2FA and any recovery codes. Deposits. Withdrawls. What coins were up for sale (or buy). Even your Karma score.

Given that it could be years - put that sheet of paper in a safe place. Memories, Hard Drives and Mobile phones come and go, a sheet of paper in a safe place can be the key to recovering your funds in a few years time."

bleutrade.com been around quite a while and has a nice clean/concise interface.

well, the exchange has been running a month now, and except for the initial Frist! transaction, there has been ZERO trading activity.

use it or lose it folks.

sex coin appears to be on a fork.
a new wallet was released at the end of 2018

have the pools

hash-to-coins.com
ispace.co.uk
prohashing.com (they run an explorer too)

been informed?

does it block v1.5.2 clients too?
because until/when cryptopia and otherplaces like prohashing.com update from 1.5.2 the new wallet wont be able to receive from them.

fixed.
if either the ndl wallet daemon isnt running, or the iquidus update process get killed for any reason, a lock-file is left behind.

that lockfile then needs to be manually deleted before things start moving again.

there is now a report/feedback link at the bottom of the explorer page since i'm not realiably reading this forum. (well, i'm reliable, just not frequent. ]

until i get a replacement power supply, is it safe to run the L3+ with a smaller supply just connected to
the controller and a couple of the mining boards?
ie: will leaving some of the mining boards unpowered cause damage to the controller or anything? or will the L3+
   merrily operate with what it has?

i assume you are referring to cryptopia having reopened Gun for trading last night?

so, should PoS be seriously considered to keep a moving network?

i think i recall an altcoin (42coin perhaps?) that continues to mine zero value blocks with the finder getting
transaction fees only as a reward. doesnt sound motivating, but perhaps it's success should be looked into.
do most coins default to 0 blocks with just fees when they reach their maximum proof of work? can't say i've thought
about that end of things.

it looks like Novaexchange as of Dec.10 has listed SciFi coin (trade with Doge or Moon)

Novaexchange does not support USA residents and citizens however

quick! mine it !

https://www.cnn.com/2018/12/12/europe/chocolate-covered-street-grm-scli-intl/index.html

i was very busy in november when the new client was released, and had not included its new client name in the 'whitelist' my own node uses to allow connections.

(my quick and dirty solution to all those other altcoin connects was to create a list of allowed client names)

i have now added the new client name to my whitelist and connections should once again work for those new client users to my node at coins.dognose.net

i also maintain an iquidus explorer at coins.dognose.net:3001
but please do NOT consider it the primary or main explorer to use because HTTP type network connections to my site are often blocked by border networks thinking that home users should not be having incoming http connections (ie: they think they are protecting innocent home users from themselves and trojans/backdoors/etc.)

remember to specify 'coins.dognose.net' with addnodes and do NOT use my internet ip# --as a home user my ip# could change at random times without warning. admitidly not frequent, but it does happen.

is there a development team??



well the above image rendered okay in the 'preview' before posting...

try
http:/dognose.com/g/mega.png

He works in mysterioius ways.

the following email i got last night sounds a lot like a de-listing notice, even though they didn't use those words.

Dear Cryptopian,

You are receiving this email because we recognise you as a holder of: 

    GoldCoin(GLD)
    MegaCoin(MEC)

The above coin(s) has suffered from a 51% attack.
We will be enabling withdrawals from 02:00:00 AM (UTC) on 20 December 2018 in
order for users to reclaim their funds.

Withdrawals will operate on a first-in, first-served basis because of the 51% attack,
meaning users who withdraw later may not be able to do so. If you do not take
action you will risk losing your funds.