 Show Posts
|
|
Pages: [1]
|
|
Basicly this coin needs first some more miners, with NO MORE then diff=64 (C=THOR,d=64) set to all pools.
Pool Operators should STOP to overwrite users neoscrypt difficulty back to > 512 or generaly greater > 128!
- This works only for GH/s coins, but NOT for coins with Hashrates < 80 MH/s.
The optimal diff for low hashrate coins on neoscrypt IS diff=64 and maximum should be diff=128 set.
With a hashrate under 1,8 MH/s itīs no wonder, when chain, PoW and all MNīs stucks for many hours :-)
|
|
|
|
After original dev never registered the domain "gaon.network", neighter presented a working blockexplorer for the coin... I made this today: https://explorer.gaon.networkHave fun ;-) BTW: When someone need support for MN or by mining this coin, come to our new BanKitt Discord Chan: https://discord.gg/edksx9y |
|
|
|
|
There was one of the typical dash-fork netsplits - now on this coin.
One of the 5er ips is buggy and needs to be removed from your config!
addnode=5.23.52.56
addnode=5.23.54.111
addnode=176.57.208.60
addnode=176.57.208.151
addnode=188.225.86.206
THIS is the list of nodes, which are on the right chain.
I have a few stable nodes more:
80.64.131.241
80.64.131.242
80.64.131.243
Many nodes are stuck on Block 19002 - which is wrong.
At time of writing actual running chain is on block 19123+
Graviex is on the right chain right now.
|
|
|
|
|
Hey Dev.
Double your Blocktime to 300 and double the reward for compensation of less blocks.
...and the nicehash guys lost... :-)
|
|
|
|
Possible yes, but i prefer the correct place for them: -> on the devs original github! i noted today a few version errors with some sentinels from other coins, so the CTF-one have one "dash" edit left, which let them still timeout and shows no correct version in debug mode. This way windows wallets shows "expired" or "need restart" after one day, but linux wallets still says "enabled". I checked today latest dash code and use now there latest code and made the edits for bankitt the right way from the start. Now the sentinel works with correct data for windows and Linux and the version number is 1.1.0 - and not 1.0.1 as a few users have at the moment  |
|
|
|
....and.... as usualy with many dash based coins these days.... we had a netsplit....  Here are some nodes, which are on the right chain: addnode=159.65.4.213 addnode=159.65.4.238 addnode=46.149.182.41 addnode=54.36.126.197 addnode=87.229.103.131 addnode=89.47.160.41 addnode=93.82.27.19 addnode=94.177.235.56 addnode=95.65.39.101 addnode=136.243.24.2 addnode=188.6.168.185 addnode=194.67.217.145 the actual chain have this block (56760) at 15:12 UTC (13. March 2018): Blockhash: 0000000061e98f93e003ebeffc4ff2637823e011f3500591d60a8551376b09b6 Confirmations: 4 Height: 56760 Time: 2018-03-13 15:10:16 (1520953816) Difficulty: 0.960261989538 Bits: 1d010a97 Nonce: 71749 Version: 20000000 Size: 224 bytes Previous Hash: 000000010354b76a7d98ef07329d4e6790cf8099146e75a8e6e3228c98c31a53 Next Hash: 00000000d5e77bf27699c6f53e2c5f9dca28eefad9a882f235857e87aee540d1 Merkle Root: 608e9d47a66a662dd0f938fa806928817bb09e6ac9ffdcc70303a1bd9573f7c3 Transactions: 1 Please resync your MNīs & nodes and check for more reliable basic "addnodes" generally! |
|
|
|
|
just simply go to github and search for coin2fly (CTF). in the root respository is the "sentinel" subfolder. just download it, and edit as i described.
HINT: google points you directly to the github with the right seach words :-)
...and yes... a little work has todo, not all is leech & ready, hrhr
|
|
|
|
|
Here is a minimal list of static/vps-nodes, which are on the latest working chain:
addnode=18.218.76.227
addnode=45.76.15.162
addnode=45.77.72.229
addnode=104.156.246.74
addnode=178.62.222.184
addnode=185.65.245.181
addnode=188.166.43.45
addnode=188.166.67.20
addnode=188.166.68.141
addnode=188.166.77.58
addnode=209.250.247.175
addnode=217.61.107.94
Before use this addresses delete the "peers.dat" file,
or better delete the entire blockchain, except wallet.dat + salen.conf in the data folder and let the wallet completly resync.
|
|
|
|
|
This coin needs definitly the DOGE market and/or a 2nd exchange!
On coinexchange there are only huge sell orders by 1sat.
I see with 10 BTC sell orders on 1sat and 2sat positions no growing and volatility at all... :-(
|
|
|
|
|
For all which have problems with "WATCHDOG_EXPIRED":
a.) Took a sentinel from SAROS, CTF or another coin, which is based on the same codebase-fork.
b.) Unpack the source to a temp. working folder, but donīt install the scripts yet!
c.) search & replace in ALL the scripts the "oldcoinname" (i.e. "saros") and replace it with "bankitt"
d.) rename all files, which contains in partly the old coinname and rename the files partly to bankitt
(sample: saros_config.py becomes bankitt_config.py, etc.)
e.) after renaming all things, one more edit: in the file "bankitt_config.py" search for the old "default_port" number in Line 37 and change it to 6116
f.) install this scripts in the final location, and donīt use any git-commands from the readme-files - because, you work with the local modified scripts now :-)
I used the SAROS-sentinel for this, it was a quick and dirty hack, but finaly it works and i have no more WATCHDOG_EXPIRED ;-)
BTW: For general instructions, how to install under linux the sentinel, please consult one of the many MN sentinel install guides out there.
The procedure for bankitt is the same as for many other coins, which uses sentinel as watchdog.
|
|
|
|
|
This have todo with staking overflow mostly!
When you have more then 90.000.000 coins in one part and the next stake comes in, it can go over 99 Million and wallet is crashing.
it is very simple: Divide ALL your stakes by make smaller 50.000.000 parts and stake many. when you reached 85.000.000 in some parts, just divide again to 50 Million.
As long as every part is under 90.000.000 Coins you usualy become no problems.
Another way to finaly clean up this messes is to create a clean new empty wallet, and transfer all your variable coins in 50.000.000 parts to the new wallet and then delete the
old wallet. This way i stake without any problems since many months ;-)
Same when you transfer coins to exchange wallets: NO more then 99.000.000 coin in each send!
When one single part is bigger then > 99.999.999 you have a problem and canīt send from this part this way. For getting coins out
from a part which is bigger, there needs other tricks, like "half-syncing" the blockchain and stop at a point where not all inputs on this part in the wallet.
So you can send a part from this coins out, before it goes over 99.999.999 which ocurs, when blockchain is completly sync.
Crappy ways, boring, i know, but it works so far so save your actual coins until a real fixed wallet comes out.
|
|
|
|
|
Where is the LATEST (modified) source code on github ?
i see 5 forks there are just 1:1 copys of the code from 2016 and the only commits
i saw was editing a readme-url...
Where are the first codesnippets from the last tryings of fixxing the wallet for the known bugs ?
I saw for a while some pull-requests with a lot of small fixxings - but this requests disapeared,
so i asume that a reworked version is somewhere in a hidden github-account...
It make really sense, not just include a binary.zip to the new homepage without a
link to exactly the code, where this version is build from.
|
|
|
|
|
Guys, why the hell is an old wallet recompiled with a shitload of useless .dll files ?
It is really easy to cross-compile the original code with qt-5.7.x completly static by using
MXE on linux ;-)
...finaly fixing the int/uint/long variables make really more sence
|
|
|
|
|
I can confirm this.
The links on mega from the thread are replaced and contains a rarfile with an exe dated to 11 April 2017.
(Which is to young and no longer the original old 2016er wallet!)
The .exe installs an file "explorer.exe" in C:\Program Files (x86)\WindowsClient\explorer.exe - which is a fake.
To activate them, it created an autostart entry in the registry that points directly after boot to this file.
When try to kill the process, the process is spawned many times and restarting in endless loop.
At this point a immidiate power-cut from the machine is best what you can make at this moment.
For me it looks like an replacement for the regulary explorer - which contains keylogger and all the usual
things we know.
I had the chance to remove all instances fast enough, before the usual "download actions" begans.
Antivirus has not detected any activity - only the long starting time and nearly doing "nothing" for
about 30 Seconds makes me fast checking all running processes and shutdown the machine asap.
By the way: On the old website the other download-link is dead to mega, further more, most google
searches to the forum opening post - so this thread needs immidiatly disabled or edited by an admin.
|
|
|
|
|
The NAT Problem with lost connections is still not fixed.
I still lost all few minutes the connections behind a NAT-Router in a reconnect-loop.
|
|
|
|
|
In last version the NAT changes are not really works.
i got all few minutes lost connections in and endless loop.
my regulary NAT timeout ist 360 or 600 seconds - that is enough for
a router.
Can you please check your keepalive (tcp based!) coding,
and verify that the miner is working with general settings on natted router ?
|
|
|
|
|
I have a "load-problem" under ubuntu 14.04 with 4 Nvidia Cards on CUDA9:
(used latest 0.52 Version)
2121 root 20 0 51,978g 396036 351052 S 23,4 9,8 0:56.68 ./zm --server .....
compared with the older ewbf-miner 23,4% nearly continous load on a quad-cpu is huge.
I costs nearly 8 Watts extra energy. Can you please check, why the cpu-usage is so high ?
my used commandline:
./zm --server luckpool.org --port 3057 --user xxx.yyy --pass x --time
Tested with --api and without --time i have the same results with the cpu-load
|
|
|
|
|
