☑☑☑[ANN][BSD] BitSend - online since 2014 [ Core 0.21x]

[onnz423]

-snip-

There are many packages that you don't need for the wallet, and which are meant for services only. For example you won't be needing the following packages at all:

Code:

npm nodejs nodejs-legacy redis-server software-properties-common

The wallet is not written on javascript nor java, so what would it really need the nodejs for example? Also reddis is usually used for databases in combination with nodejs, which is why it's not needed at all. I added the software properties common there as well, because i've never had to install that because it's meant for much different things rather than compiling C++ code. Also after compilation i'd run "sudo make install" just because then it adds the PATHS so you can just call bitsend daemon whatever the location on the terminal is.

Hello.
I see message in wallet: Warning: unknown new rules activated (versionbit 7)
What is it?

Bitsend Core version v0.14.0.3-unk (32-bit)

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.

[Rumhurius]

Hello.
I see message in wallet: Warning: unknown new rules activated (versionbit 7)
What is it?

Bitsend Core version v0.14.0.3-unk (32-bit)

https://github.com/LIMXTEC/BitSend/releases
We are on 0.14.0.4

[WhaleHunter]

Will there ever be any initiative to enlarge the user base of Bitsend? I feel adoption base is rising too slow and in the end this is what gives value to a currency.

[bspus]

There are many packages that you don't need for the wallet, and which are meant for services only. For example you won't be needing the following packages at all:

Code:

npm nodejs nodejs-legacy redis-server software-properties-common

The wallet is not written on javascript nor java, so what would it really need the nodejs for example? Also reddis is usually used for databases in combination with nodejs, which is why it's not needed at all. I added the software properties common there as well, because i've never had to install that because it's meant for much different things rather than compiling C++ code. Also after compilation i'd run "sudo make install" just because then it adds the PATHS so you can just call bitsend daemon whatever the location on the terminal is.

Thanks. I'll edit my post and remove them. They were included on the script I copied them from but it is supposed to do more than just compile the wallet.

[Limx Dev]

-snip-

There are many packages that you don't need for the wallet, and which are meant for services only. For example you won't be needing the following packages at all:

Code:

npm nodejs nodejs-legacy redis-server software-properties-common

The wallet is not written on javascript nor java, so what would it really need the nodejs for example? Also reddis is usually used for databases in combination with nodejs, which is why it's not needed at all. I added the software properties common there as well, because i've never had to install that because it's meant for much different things rather than compiling C++ code. Also after compilation i'd run "sudo make install" just because then it adds the PATHS so you can just call bitsend daemon whatever the location on the terminal is.

Hello.
I see message in wallet: Warning: unknown new rules activated (versionbit 7)
What is it?

Bitsend Core version v0.14.0.3-unk (32-bit)

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.

We change it in the next version.

Kind Regards Christian

[bobq]

What are the exact differences between Bitsend and Bitcore? The question is legitimate since the devs are the same, and BTX is getting a lor more of attention from the markets right now. I own both coins, but i am trying to understand if it makes a sense to keep them both or if there is some redundancy.

BitCore has many parameters similar to Bitcoin. 21 Million coin supply, 10 min block time, same halving interval. The distribution is also different from Bitsend. The airdop is based on stake (compounding interest), and there are also BTX airdropped to BTC holders.

Bitsend is a Masternode coin, which is the primary distinction. This changes the economic model, although both BSD and BTX incentivize people to hold coins rather than sell them for short term profit. 210,000,000 BSD and 180-second block time -- very fast.

Clearly more energy has been put into BitCore lately with the recent BTC airdrop and addition to HitBTC. The pendulum will swing back. Working product, competent developers, not over-hyped. Both of these coins have bright futures. Take the lack of hype as an opportunity.

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?

[driller99]

-snip-

There are many packages that you don't need for the wallet, and which are meant for services only. For example you won't be needing the following packages at all:

Code:

npm nodejs nodejs-legacy redis-server software-properties-common

The wallet is not written on javascript nor java, so what would it really need the nodejs for example? Also reddis is usually used for databases in combination with nodejs, which is why it's not needed at all. I added the software properties common there as well, because i've never had to install that because it's meant for much different things rather than compiling C++ code. Also after compilation i'd run "sudo make install" just because then it adds the PATHS so you can just call bitsend daemon whatever the location on the terminal is.

Hello.
I see message in wallet: Warning: unknown new rules activated (versionbit 7)
What is it?

Bitsend Core version v0.14.0.3-unk (32-bit)

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.

We change it in the next version.

Kind Regards Christian

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

[binary0x01]

-snip-

There are many packages that you don't need for the wallet, and which are meant for services only. For example you won't be needing the following packages at all:

Code:

npm nodejs nodejs-legacy redis-server software-properties-common

The wallet is not written on javascript nor java, so what would it really need the nodejs for example? Also reddis is usually used for databases in combination with nodejs, which is why it's not needed at all. I added the software properties common there as well, because i've never had to install that because it's meant for much different things rather than compiling C++ code. Also after compilation i'd run "sudo make install" just because then it adds the PATHS so you can just call bitsend daemon whatever the location on the terminal is.

Hello.
I see message in wallet: Warning: unknown new rules activated (versionbit 7)
What is it?

Bitsend Core version v0.14.0.3-unk (32-bit)

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.

We change it in the next version.

Kind Regards Christian

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

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

[driller99]

Hello.
I see message in wallet: Warning: unknown new rules activated (versionbit 7)
What is it?

Bitsend Core version v0.14.0.3-unk (32-bit)

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!

[wlefever]

I have to retract (and apologize for) the "compiled binaries" part. You're right, the instructions must be clear for everyone and working. The release notes should contain a warning about known big issues like this one ("not available for Linux" -- WTF?).
I hope that BSD code will regain the qualities that attracted so many supporters. That's a pretty thick "glitch".
BTW, I tested dArkjON's script. It doesn't work on last version of BSD and the culprit seems to be related to a boost component... or a misplaced backslash

Apology accepted 
I'll give it a shot during the weekend anyway to see for myself where it breaks. Hopefully the devs will fix it soon enough.

Still waiting for an official answer on this. Can I use 14.0.3 for a masternode in the meantime or not? I can't believe all the current masternodes are upgraded.

Please use 0.14.0.4 for your masternode.
https://github.com/LIMXTEC/BitSend/releases

Kind Regards Christian

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.

[CntryBoy]

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?

[wfthkttn]

Any idea why this would happen?  What would cause it not to communicate with the network?

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

[CntryBoy]

Any idea why this would happen?  What would cause it not to communicate with the network?

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

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.

[wfthkttn]

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.

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.

[gembitz]

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?

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

[CntryBoy]

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.

[wfthkttn]

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

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".

[gembitz]

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

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".

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

https://poloniex.com/exchange#btc_nxt

[CntryBoy]

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

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".

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.

[CntryBoy]

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...