what Cryptopia any progress ??  Cryptopia will do nothing until we give them new code and pay back the coins that were lost one way or another. That is the same situation with dozens of other coins there also. Fortunately, we have new code in work that should be complete next week and have hopes that this will solve the situation with Cryptopia and then get GUN moving again there. yup, cryptopia's incompetence has led to them blackmailing other coins. consider other exchanges like tradesatoshi or southxchange, i'm also cool with novaexchange but they dont allow USA users. heh heh... |
|
|
|
i'm seeing a lot of these in the debug.log (and my sync is stuck after block 296759 way back on sep.23rd 11:33:33)
trying connection 79.26.107.46:8777 lastseen=3.6hrs
received block 419fb08fa5452e83442f
Misbehaving: 140.82.40.161:8777 (0 -> 100) DISCONNECTING
disconnecting node 140.82.40.161:8777
ERROR: ProcessBlock() : block with too little proof-of-stake
received block 419fb08fa5452e83442f
Misbehaving: 94.130.220.2:8777 (0 -> 100) DISCONNECTING
disconnecting node 94.130.220.2:8777
ERROR: ProcessBlock() : block with too little proof-of-stake
is this why many are having troubles syncing? by the way, added the following to checkpoints.cpp using info from https://prohashing.com/explorer/Bitbar/ ( 200000, uint256("0x0000000001fc2837a93e688d504032a9d7a230fc99c7dcaa638fdc4adabc89f7"))
( 225000, uint256("0x000000000014b09367533fb2367b0d912ce6a46a397e240f1458838978f436ce"))
( 250000, uint256("0x000000000013f978b8a8c5527bd5ae32e7d7208cc4e5795747f2b032aa8d6610"))
( 275000, uint256("0x00000000000881db3d71ae6849df642221a3c2086860b240a602abad73b43051"))
( 300000, uint256("0x000000000011ebd21945b69b21ec2817b83aa1a241adc715947c90a1366363fc"))
|
|
|
|
I don't think that has ever been changed - lol
must have been like that for a long time.
I'll fix that for the next update
there are several minor changes in init.cpp compared to v0.7.5.1 did an exceptionally old version get rolled forward into the git repository somehow? (a really old checkout checked back in?) |
|
|
|
default port is 8777
you can check your wallet using
getpeerinfo
on closer examination of the source i see the port has not actually changed. however, the usage/help message *has*, and that threw me off.. diff -r bitbar-0.7.5.1/src/init.cpp bitbar-0.7.6.2/src/init.cpp
234c234
< " -port=<port> " + _("Listen for connections on <port> (default: 8777 or testnet: 18777)") + "\n" +
---
> " -port=<port> " + _("Listen for connections on <port> (default: 7777 or testnet: 17777)") + "\n" +
242d241
< " -irc " + _("Find peers using internet relay chat (default: 0)") + "\n" +
276c275
< " -rpcport=<port> " + _("Listen for JSON-RPC connections on <port> (default: 9344 or testnet: 19344)") + "\n" +
---
> " -rpcport=<port> " + _("Listen for JSON-RPC connections on <port> (default: 8344 or testnet: 18344)") + "\n" +
|
|
|
|
some people do have problems with it syncing, not sure why. for most people it only takes an hour or so. Did I mention that there is a new Bitbar wallet out? I added themes, and fixed the stake reward display in the transactions list. http://bitbar.cowhy was the default p2p port changed from 8777 to 7777 ? 7777 clashes with Novacoin people may also have firewalls and routers previously configured for 8777 and not 7777 and perhaps contributing to syncing problems. |
|
|
|
Hemos pospuesto el evento para realizar la promocion del CCC para Abril. Buscando el nodo màs actualizado del CCC. Del resto trabajo de hormiga y en solitario.
explorer http://coins.dognose.net:3002/my network provider has been unreliable lately, if you cannot connect, try again later. |
|
|
|
I have also given people time to verify this themselves or bring up any concerns.
time? too funny ...less than a week. |
|
|
|
Yes, I do see the word mingw, but didn't see it in the same context as mingw for windows. Perhaps I should clarify; the only formal training I have in programming is for QBasic. You know...for DOS...that was used in the 90's. No one else took up the mantle to update the wallet, so I did. No, I obviously don't know what you know.
My code works with the instructions provided by the Litecoin developers. Their instructions obviously include Mingw. It works in that context; I can't speak to other contexts.
okay then, 'trust me'  I'm not distrusting you at all. I am just very inexperienced in this kind of thing and, at the very least, can only confirm it will work in the same environment I have setup. I will definitely consider updating that uint thing. With those variables aside were you able to compile it? yes, but wont be able to run and play with it for some unknown time this week, my usual couple free hours per week is basically weekends. i go to bed now, up in 5.5 hours for work. |
|
|
|
Yes, I do see the word mingw, but didn't see it in the same context as mingw for windows. Perhaps I should clarify; the only formal training I have in programming is for QBasic. You know...for DOS...that was used in the 90's. No one else took up the mantle to update the wallet, so I did. No, I obviously don't know what you know.
My code works with the instructions provided by the Litecoin developers. Their instructions obviously include Mingw. It works in that context; I can't speak to other contexts.
okay then, 'trust me' |
|
|
|
yes, use uint64_t, do not use u_int64.
it will NOT compile in a non-Mingw environment (both linux and Mac)
the cd in the copy of trythis i got from github occurs AFTER the call to 'sudo make -j4 HOST=x86_64-w64-mingw32'. (ie: make is line 7, cd is line 8, another make without args on line 11
I don't use Mingw. There must be a number of crazy variations on Linux then. Because it compiles for me in Linux just fine (with regards to the u_int64). the text for my "trythis" is as follows: cd depends
PATH=$(echo "$PATH" | sed -e 's/:\/mnt.*//g')
sudo apt get libevent
sudo chmod +x config.guess
sudo chmod +x config.site.in
sudo chmod +x config.sub
sudo make -j4 HOST=x86_64-w64-mingw32
cd ..
./autogen.sh
CONFIG_SITE=$PWD/depends/x86_64-w64-mingw32/share/config.site ./configure --prefix=/
make
There are two "make"'s. The purpose of the first "make" is...well...I don't really know for sure. Its what the Litecoin devs required and its worked so far for me. Perhaps my trythis file won't work for everyone. I have compiled this code countless times in "Ubuntu 18.04.1 LTS". you are cross-building for windows, arent you? and dont you even see the word mingw in that script you just posted above? Mingw exists on linux and on windows systems. it's basially GCC trying to use the microsoft runtime API in a native sort of fashion. and every coin wallet i've seen chooses this path. personally i prefer the Cygwin gcc environmnet on windows -- it attempts valiantly to hide the perverse quirks of microsoft Visual C code and library implementations by putting a posix compliant layer on top of the microsoft mess. if for on other reason, be consistent with what the rest of the litecoin package uses, even within the same validation.cpp file they use uint64_t consistency is important for group projects. |
|
|
|
I have had no problems with the source I uploaded with regards to the validation.cpp. Are you suggesting I establish that as a "uint64_t" as a general rule or are you having problems? Block 1 will not validate if that is not accepted, and I have experienced no problems therewith. To confirm, you are concerned about the following code: static const u_int64 TOTAL_GENERATION = MAX_MONEY;
static const double FSM_FUNDS = 0.03;
u_int64 nSubsidy = 10000 * COIN;
Yes, you're right on the 'apt get', I meant to remove that. Line 8 is "cd .." which takes one out of the depends folder for "make". yes, use uint64_t, do not use u_int64. it will NOT compile in a non-Mingw environment (both linux and Mac) the cd in the copy of trythis i got from github occurs AFTER the call to 'sudo make -j4 HOST=x86_64-w64-mingw32'. (ie: make is line 7, cd is line 8, another make without args on line 11 |
|
|
|
in src/validation.cpp you added a type reference "u_int64" in a couple places this is not a standard type. this particular source package uses uint64_t everywhere else, even within validation.cpp and if you do need to reference a non-basic type for a new variable, make sure the configure script has a recipe to test for its existence, and if not exists, unleash a sutiable definition in a .h file somewhere. your 'trythis' script mentions doing a make while in the 'depends' folder. there is no Makefile in that folder. it also does an 'apt' get. not all versions of linux or bsd support apt as a package manager (mine does not), if you want to make sure a certain package is installed the configure script is the appropriate place to put a test recipe and a message to the user to fetch the damn thing themselves if the library and/or headers are missing. (or perhaps simply state the package is missing -- with less colourful language than i am prone to.) by the way, i was not doing a Mingw type build but a native linux non-gui daemon build. i find debugging is much easier without GUI api stuff getting in the way. i'm guessing u_int64 is a Mingw-ism ? (aka Micorsoft-ism?) |
|
|
|
The only thing I can see that is keeping the new wallet from being fully deployable is the address problem. Anyone who has any ideas, even if its one I will simply shoot down, may be of help. Once the address problem is addressed and the wallet is deployed, we can implement the appropriate BIPs so that we can be traded.
i wont have real free time until the end of november, but i can probably fit 1 or 2 hours a week until then. so, should be able to solve the problem within a week  lol... [dammit EGO, get back in your box!] where can i download your current source version? where can i download the LTC base source that you used? give a clear description of the problem, please avoid short forms and slang since we are probably not of the same generation or country. |
|
|
|
I try this guys to provide with liquidity, and he interprets the many limit orders as "... in the future please do not double, tripple click on the buttons, click it once and let the page load, if not we will be speaking again soon.". The dev "Chad" is a really unfriendly person, behaves like a terminator.
well at least he communicates. better than the 'major' exchanges by far. |
|
|
|
I would like to mine, i have a 1080ti is there a any tutorial how to mine SXC?
Welcome to out little corner of the crypto universe, I'm sure Lava won't mind me saying that once we implement the merged mining the benefits will be two fold in that you'll be mining SexCoin, but if you are mining through one of the pools that has adopted the SXC-MM you will also be mining on the litcoin block chain. merge mine that sexy Doge too? |
|
|
|
That's my cluster of noodles....anyone have any ideas as to the cause?
no actual clue, but with encryption type stuff in general perhaps there is a salt/seed/initial value somewhere used by the base58 routines that is different for LTC than for NDL. i also seem to have a fuzzy recollection that LTC supported a legacy address that started with "3" instead of "L" perhaps that legacy code is influencing things somehow? |
|
|
|
That's my cluster of noodles....anyone have any ideas as to the cause?
no actual clue, but with encryption type stuff in general perhaps there is a salt/seed/initial value somewhere used by the base58 routines that is different for LTC than for NDL. |
|
|
|
THIS IS A BETA! BE CAREFUL!
side issue: have you modified the messages from this new code to use various permutations of Priate Talk and FSM references? the FUN aspect in the coin, imho, is critical to its acceptance. No, I haven't. Though I am open to any contributions you may have to offer. look at the old code |
|
|
|
THIS IS A BETA! BE CAREFUL!
side issue: have you modified the messages from this new code to use various permutations of Priate Talk and FSM references? the FUN aspect in the coin, imho, is critical to its acceptance. |
|
|
|
It just means you have to use a miner that supports longpolling. Cpuminer is one of the ones that can do that. Its possible your current external mining program likely supports longpolling, so you aren't losing that mining method. Which miner are you using?
i use in-wallet cpu mining for NDL to avoid overwhelming the network. i have a stratum-only daemon providing interface to all the altcoins i support at coins.dognose.com i do not run external standalone mining software, my asic boxes talk to the stratum daemon ports using the software their manufacturer provides internally to the box. i'm already using nearly 19gig of a 24gig linux system supporting all the various mining tools, daemons, explorers, database interfaces, etc. i dont intend on running more software just to support NDL, i still want to support several other older altcoins. my system cannot support more crap running. i also simply do not have the time to do this sort of juggling act. coins.dognose.net will have to cease NDL support. |
|
|
|
|
Show Posts
