Topic: ☑☑☑[ANN][BSD] BitSend - online since 2014 [ Core 0.17++] - page 121. (Read 384726 times)

Thank You! i have receive this week airdrop using my new BSD wallet

BSD   10.00000000   UnConfirmed      
Tx Hash: a84ab445c52496c510e3a0c0cbe663564f261ebac927604b460f9a73435b9db2

No.86 Overview Weekly Airdrop 12/04/17

Total members: 971 |Payout BSD: 10,00| Payout per member total BSD: 5025,85
Airdrop today per member: 9,70 $( total: 9700,00 $)
Airdrop total in Dollar: 1533142,13 $

Info about the Airdrop here: https://bitsend.info/forums/index.php?topic=18.0
Payments will be issued on Mondays until 2019.
Best Regards,
Your Bitsend Team

I've joined on telegram, but it appears empty at the moment.  I'll check back later.  If I wanted to just move the wallet from the laptop that won't connect to the working one, is it just as simple as replacing the wallet.dat file with the backed up one from the bad wallet and then doing a -rescan?

Yea, thats strange, considering you have brand-new wallet installed.
Perhaps, add upnp=0 to bitsend.conf and see how it goes.
If you want to keep trying, join t.me\bsd_bitsend

I tried to run it in "safe mode with networking" and same result, still no connections.  I also rechecked the firewall settings and permissions, everything looks correct (everything involving bitsend is "allowed").  I also tried disabling the firewall completely as well, still no luck.  I cannot, for the life of me, see anything that would prohibit it from connecting...

Thank you for the great info!  I will try loading it in safe mode once I get some time this evening and see what I can find.

guilty by association?  NXT looks like it will do the same think price too low :-D weeee

https://poloniex.com/exchange#btc_nxt

If computers are on the same network, then something blocking UPnP connections from withing program.
You have to look over your firewall rules, it could be default firewall, or may be replaced with something like COMODO AV Firewall.
You can check it by loading PC in "safe mode with networking".

There's should be no problem to run wallet on w8, someone else need to test it. I dont have one.

About debug.log - rename debug.log to debug.log.backup and start wallet until it fully loads up.
Then open debug.log and trace if it contains errors until "GUI: PaymentServer::LoadRootCAs".
After this point wallet should receive messages from bitsend network.
If you dont get what happening, you can post .Log here, or somewhere else, but make sure you clean personal data from it. (like your IP and stuff, you  can use "Replace" feature in notepad)
Also, check if peers present and OK in wallet's settings->debug->peers.
[/quote]

Here is copy/paste of debug.log with personal data removed:

2017-12-03 17:51:56 bitsend version v0.14.0.4-unk
2017-12-03 17:51:56 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1
2017-12-03 17:51:57 Assuming ancestors of block 00000000000000000013176bf8d7dfeab4e1db31dc93bc311b436e82ab226b90 have valid signatures.
2017-12-03 17:51:57 GUI: "registerShutdownBlockReason: Successfully registered: bitsend Core didn't yet exit safely..."
2017-12-03 17:51:58 Default data directory (personal file)
2017-12-03 17:51:58 Using data directory (personal file)
2017-12-03 17:51:58 Using config file (personal file)
2017-12-03 17:51:58 Using at most 125 automatic connections (2048 file descriptors available)
2017-12-03 17:51:58 Using 32 MiB out of 32 requested for signature cache, able to store 1048576 elements
2017-12-03 17:51:58 Using 2 threads for script verification
2017-12-03 17:51:58 scheduler thread start
2017-12-03 17:51:58 Creating backup of (personal file)
2017-12-03 17:51:58 Old backup deleted: (personal file)
2017-12-03 17:51:58 Using BerkeleyDB version Berkeley DB 4.8.30: (April  9, 2010)
2017-12-03 17:51:58 Using wallet wallet.dat
2017-12-03 17:51:58 init message: Verifying wallet...
2017-12-03 17:51:58 CDBEnv::Open: LogDir=C:(personal file)
2017-12-03 17:51:58 Bound to [::]:8886
2017-12-03 17:51:58 Bound to 0.0.0.0:8886
2017-12-03 17:51:58 Cache configuration:
2017-12-03 17:51:58 * Using 2.0MiB for block index database
2017-12-03 17:51:58 * Using 8.0MiB for chain state database
2017-12-03 17:51:58 * Using 290.0MiB for in-memory UTXO set (plus up to 286.1MiB of unused mempool space)
2017-12-03 17:51:58 init message: Loading block index...
2017-12-03 17:51:58 Opening LevelDB in C:(personal file)
2017-12-03 17:51:59 Opened LevelDB successfully
2017-12-03 17:51:59 Using obfuscation key for C:(personal file)\AppData\Roaming\Bitsend\blocks\index: 0000000000000000
2017-12-03 17:51:59 Opening LevelDB in C:(personal file)\AppData\Roaming\Bitsend\chainstate
2017-12-03 17:52:00 Opened LevelDB successfully
2017-12-03 17:52:00 Using obfuscation key for C:(personal file)\AppData\Roaming\Bitsend\chainstate: 00a48f162216a133
2017-12-03 17:57:29 LoadBlockIndexDB: last block file = 2
2017-12-03 17:57:29 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=37363, size=51750463, heights=363655...401017, time=2017-09-07...2017-11-28)
2017-12-03 17:57:29 Checking all blk files are present...
2017-12-03 17:57:29 LoadBlockIndexDB: transaction index disabled
2017-12-03 17:57:30 LoadBlockIndexDB: hashBestChain=0000000001e22e91623dbc0e6b484c6ac82987336a2b2e6a1d4963e27f544033 height=401017 date=2017-11-28 00:22:19 progress=1.000000
2017-12-03 17:57:30 init message: Rewinding blocks...
2017-12-03 17:57:35 init message: Verifying blocks...
2017-12-03 17:57:35 Verifying last 6 blocks at level 3
2017-12-03 17:57:35 [0%]...CheckBlock() : Skipping masternode payment check - nHeight 401018 Hash 0000000001e22e91623dbc0e6b484c6ac82987336a2b2e6a1d4963e27f544033
2017-12-03 17:57:35 [16%]...CheckBlock() : Skipping masternode payment check - nHeight 401018 Hash 0000000001587d02210aa673bed01626cf4f03936447fb3df87042fb158f718d
2017-12-03 17:57:35 [33%]...CheckBlock() : Skipping masternode payment check - nHeight 401018 Hash 00000000004359a3b9627f654095885fea7808cbab5a51039e6ee5c76814dd32
2017-12-03 17:57:35 [50%]...CheckBlock() : Skipping masternode payment check - nHeight 401018 Hash 000000000021dc8d2fcce4497b4591d9b66b36a41768871f74d218dae8c51310
2017-12-03 17:57:35 [66%]...CheckBlock() : Skipping masternode payment check - nHeight 401018 Hash 0000000001bef8d426192ae7de407b85e484379db63543fb95e8556774e46344
2017-12-03 17:57:35 [83%]...CheckBlock() : Skipping masternode payment check - nHeight 401018 Hash 00000000016867fa4fba5729067244dff7f2f7b854a4ddea02d3f512c2a21f53
2017-12-03 17:57:35 [99%]...CheckBlock() : Skipping masternode payment check - nHeight 401018 Hash 00000000031a701dac3a25f107644cbcb73192d0027f16bc29738388db7aa9af
2017-12-03 17:57:35 [DONE].
2017-12-03 17:57:35 No coin database inconsistencies in last 7 blocks (13 transactions)
2017-12-03 17:57:35  block index          337175ms
2017-12-03 17:57:35 init message: Loading wallet...
2017-12-03 17:57:36 nFileVersion = 140004
2017-12-03 17:57:36 Keys: 2933 plaintext, 0 encrypted, 1001 w/ metadata, 2933 total
2017-12-03 17:57:36  wallet                  545ms
2017-12-03 17:57:36 setKeyPool.size() = 1000
2017-12-03 17:57:36 mapWallet.size() = 2
2017-12-03 17:57:36 mapAddressBook.size() = 1
2017-12-03 17:57:36 init message: Loading masternode cache...
2017-12-03 17:57:36 Loaded info from mncache.dat  0ms
2017-12-03 17:57:36   Masternodes: 0, peers who asked us for Masternode list: 0, peers we asked for Masternode list: 0, entries in Masternode list we asked for: 0, nDsqCount: 0
2017-12-03 17:57:36 Locking Masternodes:
2017-12-03 17:57:36 fProUserModeDarksendInstantX -promode 0 # fProUserModeDarksendInstantX2 -disable_Darksend_InstantX  0  #mapBlockIndex.size() = 401018
2017-12-03 17:57:36 nBestHeight = 401017
2017-12-03 17:57:36 AddLocal(personal IP)
2017-12-03 17:57:36 Discover: (personal IP)
2017-12-03 17:57:36 AddLocal(personal IP)
2017-12-03 17:57:36 Discover: (personal IP)
2017-12-03 17:57:36 AddLocal(personal IP):8886,1)
2017-12-03 17:57:36 Discover: (personal IP)
2017-12-03 17:57:36 AddLocal(personal IP):8886,1)
2017-12-03 17:57:36 Discover: (personal IP)
2017-12-03 17:57:36 init message: Loading addresses...
2017-12-03 17:57:36 Loaded 924 addresses from peers.dat  13ms
2017-12-03 17:57:36 init message: Loading banlist...
2017-12-03 17:57:36 init message: Starting network threads...
2017-12-03 17:57:36 torcontrol thread start
2017-12-03 17:57:36 upnp thread start
2017-12-03 17:57:36 net thread start
2017-12-03 17:57:36 AddToWallet (personal transaction #)  
2017-12-03 17:57:36 Imported mempool transactions from disk: 1 successes, 0 failed, 0 expired
2017-12-03 17:57:36 dnsseed thread start
2017-12-03 17:57:36 addcon thread start
2017-12-03 17:57:36 opencon thread start
2017-12-03 17:57:36 msghand thread start
2017-12-03 17:57:36 init message: Done loading
2017-12-03 17:57:36 GUI: Platform customization: "windows"
2017-12-03 17:57:36 GUI: PaymentServer::LoadRootCAs: Loaded  0  root certificates
2017-12-03 17:57:43 No valid UPnP IGDs found
2017-12-03 17:57:43 upnp thread exit
2017-12-03 17:57:47 Loading addresses from DNS seeds (could take a while)
2017-12-03 17:57:47 0 addresses found from DNS seeds
2017-12-03 17:57:47 dnsseed thread exit

When I go to: settings->debug->peers, there is nothing listed there at all.  I'm probably overlooking something simple, but I've looked at it so many times, I'm going cross-eyed.. lol.

dead coin is hard for you to understand? :\ you new here?<<<

There's should be no problem to run wallet on w8, someone else need to test it. I dont have one.

About debug.log - rename debug.log to debug.log.backup and start wallet until it fully loads up.
Then open debug.log and trace if it contains errors until "GUI: PaymentServer::LoadRootCAs".
After this point wallet should receive messages from bitsend network.
If you dont get what happening, you can post .Log here, or somewhere else, but make sure you clean personal data from it. (like your IP and stuff, you  can use "Replace" feature in notepad)
Also, check if peers present and OK in wallet's settings->debug->peers.

As far as I can tell, all Firewall and other rules are the same on both.  The only difference is that the laptop with the connecting wallet is running Windows 10, the one that won't connect to the Bitsend network is running Windows 8 (everything else works fine except the Bitsend wallet).  What am I looking for in debug.log?  It's very long... I apologize, but I'm not very "tech savvy" with this kind of thing.  I just figured I could download it and run it without issue like I did on the other laptop.

Must be a local problem.
Check if firewall, AV and other rules are the same.
What debug.log tells you?

I have downloaded the wallet on 2 different laptops.  On one I just downloaded the Windows .zip file, extracted it and ran the -qt.exe file, it installed and opened and runs no problem.  On the second laptop, I did everything the same way (also Windows), but it always shows 0 connections to the Bitsend network.  It synced up properly from the downloaded files, but is stuck and will not sync the last 2 days worth of blocks (which is obvious, since it will not connect to the network).  Any idea why this would happen?  What would cause it not to communicate with the network?

Masternode running great on 0.14.0.4!  Great work.

Should update the subject and OP to hopefully lessen the release questions in the thread.

That's normal. I think that the wallet thinks that the segwit activation does not belong there, however it does and atleast for me transfers work normally so you don't have to worry about that warning at all.

[/quote]

We change it in the next version.

Kind Regards Christian
[/quote]


Sorry, I am confused. Current version is 0.14.0.2 on github? It's less than v0.14.0.3.
[/quote]

I don't think that is true, I've been running 14.0.4 since Chris uploaded it, built from source on linux.

Here's the link: https://github.com/LIMXTEC/BitSend/releases/tag/v0.14.0.4
[/quote]
Sorry, I looked here: https://github.com/LIMXTEC/BitSend ,
not here: https://github.com/LIMXTEC/BitSend/releases
Thanks!

I don't think that is true, I've been running 14.0.4 since Chris uploaded it, built from source on linux.

Here's the link: https://github.com/LIMXTEC/BitSend/releases/tag/v0.14.0.4

Sorry, I am confused. Current version is 0.14.0.2 on github? It's less than v0.14.0.3.

Thank you very much. And I guess your are right, the lack of hype is an advantage for buying. But to buy enough for a masterminded is very expensive already. Did anyone calculate if the revenues of running a masterminded have any chances to ROI the investment completely?

We change it in the next version.

Kind Regards Christian