Topic: ☑☑☑[ANN][BSD] BitSend - online since 2014 [ Core 0.17++] - page 122. (Read 384637 times)
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.
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)
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
-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)
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.
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)
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)
Getting the same
Warning: unknown new rules activated (versionbit 28)
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)
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)
dump this silly fork and get your DOGE on the devs at bittrex will pump DOGE
weeeeehttps://poloniex.com/exchange#btc_doge
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)
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)
legendary
Activity: 2422
Merit: 1083
Leading Crypto Sports Betting & Casino Platform
Segwit is now active on BitSend, confirmed working by my transaction here: https://chainz.cryptoid.info/bsd/tx.dws?561529.htm
Thank you, yes it is true. We are now the first masternode coin with newest coinbase and segwit. I am very happy about that.
Code:
{
"chain": "main",
"blocks": 402644,
"headers": 402644,
"bestblockhash": "0000000001a33e036076deb621daf300849dd3f4f9f4a38078c8a1b05c633e3d",
"difficulty": 54.12132082532227,
"mediantime": 1512141149,
"verificationprogress": 1,
"chainwork": "000000000000000000000000000000000000000000000000009dd9582469bab9",
"pruned": false,
"softforks": [
{
"id": "bip34",
"version": 2,
"reject": {
"status": true
}
},
{
"id": "bip66",
"version": 3,
"reject": {
"status": true
}
},
{
"id": "bip65",
"version": 4,
"reject": {
"status": true
}
}
],
"bip9_softforks": {
"csv": {
"status": "active",
"startTime": 1503255158,
"timeout": 1607990400,
"since": 366336
},
"segwit": {
"status": "active",
"startTime": 1503255158,
"timeout": 1607990400,
"since": 402624
}
}
}Segwit with Core 0.14.x
The Segwit opens up new possibilities like the Lightning Network, Tumblebit, Schnorr Signatures, Confidential Transactions, Cross-chain atomic swaps, and so on.
We are already exploring all these new functions, and testing the water. We expect the first implementations as fast as possible.
Kind Regards Christian
next year, bsd to the moon like btx I unfortunately got wind of BitSend only allowing Legendary members in from here on out and that kinda sucked. I wish that I could have made it for next year but that seems like it won't happen now. Is there any chance of increasing the members from 1k to 2k in the future or is that going to be capped until the distribution is done?
Also I know about Bitcore project a little bit how does BitSend differ from that one? I know it is run by same people but I am no tech guy could somebody try explaining it to me like I am 5 (ELI5 for those of you who reddit
). Thanks 
Also I know about Bitcore project a little bit how does BitSend differ from that one? I know it is run by same people but I am no tech guy could somebody try explaining it to me like I am 5 (ELI5 for those of you who reddit
). Thanks what do you mean only legendary sockpuppets invited..? :\ hmmm
Segwit is now active on BitSend, confirmed working by my transaction here: https://chainz.cryptoid.info/bsd/tx.dws?561529.htm
Thank you, yes it is true. We are now the first masternode coin with newest coinbase and segwit. I am very happy about that.
Code:
{
"chain": "main",
"blocks": 402644,
"headers": 402644,
"bestblockhash": "0000000001a33e036076deb621daf300849dd3f4f9f4a38078c8a1b05c633e3d",
"difficulty": 54.12132082532227,
"mediantime": 1512141149,
"verificationprogress": 1,
"chainwork": "000000000000000000000000000000000000000000000000009dd9582469bab9",
"pruned": false,
"softforks": [
{
"id": "bip34",
"version": 2,
"reject": {
"status": true
}
},
{
"id": "bip66",
"version": 3,
"reject": {
"status": true
}
},
{
"id": "bip65",
"version": 4,
"reject": {
"status": true
}
}
],
"bip9_softforks": {
"csv": {
"status": "active",
"startTime": 1503255158,
"timeout": 1607990400,
"since": 366336
},
"segwit": {
"status": "active",
"startTime": 1503255158,
"timeout": 1607990400,
"since": 402624
}
}
}Segwit with Core 0.14.x
The Segwit opens up new possibilities like the Lightning Network, Tumblebit, Schnorr Signatures, Confidential Transactions, Cross-chain atomic swaps, and so on.
We are already exploring all these new functions, and testing the water. We expect the first implementations as fast as possible.
Kind Regards Christian
Congratulations! I've been nervously waiting for activation. It seems everything is working smoothly!
I agree, however there are so many distros that it is not just worth the time writing guides for all of the different varitions of distributions.
Ubuntu 16.04 happens to be really common (not sure if the most used version of ubuntu), so of course it provides the most support.
However problem solving is kind of a important part of the GNU/Linux experience
Ubuntu 16.04 happens to be really common (not sure if the most used version of ubuntu), so of course it provides the most support.
However problem solving is kind of a important part of the GNU/Linux experience
Well the easiest way to "solve" the problem is to have a Ubuntu 16.04 VM or whatever is the standard for the current year.
So that's where I do all my linux stuff now, particularly when it comes to compiling and crypto.
So, my take on that would be to run a VM with Ubuntu 14.04 and set up a masternode with it. The masternode setup script (https://github.com/dArkjON/BSD-Masternode-Setup-1404) should work well.
Just my2 cents, but... have fun
Actually, I just finished compiling it on my lubuntu 16.04 VM without problems. I used the only the necessary steps from that script and added a few for the qt part. I expect this process to work for most similar wallets now.
I'll try the masternode next week, as by then I should have the collateral amount
Here are the compilation steps for anyone interested. Note that the files produced were quite large . bitsend-qt alone was about 170mb. There's probably a way to compress them but I haven't tried.
This worked on lubuntu 16.04 as root user. If you are not root, all commands need a sudo in front.
First, do an update
Code:
apt-get update
Then, install essential packages
Code:
apt-get install build-essential libtool autotools-dev autoconf pkg-config libssl-dev
apt-get install libboost-all-dev git libminiupnpc-dev libevent-dev
Add bitcoin repository, update again and install a few more
Code:
add-apt-repository ppa:bitcoin/bitcoin
apt-get update
apt-get install libdb4.8-dev libdb4.8++-dev
If you want a GUI binary as well, you need to install the following
Code:
apt-get install libqt5gui5 libqt5core5a libqt5dbus5 qttools5-dev qttools5-dev-tools libprotobuf-dev protobuf-compiler
Download source, configure and compile
Code:
git clone https://github.com/LIMXTEC/BitSend
cd BitSend
./autogen.sh
./configure
make
Done. If you started the proces in your home dir, binaries should be in ~/BitSend/src
bitsend-qt will be in ~/BitSend/src/qt
BitSend didn't drop a lot in BTC since spring, that's unusual. What's the reason behind that?
Are you referring to the exchange rate of BSD vs BTC?
I unfortunately got wind of BitSend only allowing Legendary members in from here on out and that kinda sucked. I wish that I could have made it for next year but that seems like it won't happen now. Is there any chance of increasing the members from 1k to 2k in the future or is that going to be capped until the distribution is done?
Also I know about Bitcore project a little bit how does BitSend differ from that one? I know it is run by same people but I am no tech guy could somebody try explaining it to me like I am 5 (ELI5 for those of you who reddit). Thanks
Also I know about Bitcore project a little bit how does BitSend differ from that one? I know it is run by same people but I am no tech guy could somebody try explaining it to me like I am 5 (ELI5 for those of you who reddit
). Thanks
Nice project , dev , succes for you , don't late send Token , i hopefully your project go to the moon!
BitSend didn't drop a lot in BTC since spring, that's unusual. What's the reason behind that?
Segwit is now active on BitSend, confirmed working by my transaction here: https://chainz.cryptoid.info/bsd/tx.dws?561529.htm
Thank you, yes it is true. We are now the first masternode coin with newest coinbase and segwit. I am very happy about that.
Code:
{
"chain": "main",
"blocks": 402644,
"headers": 402644,
"bestblockhash": "0000000001a33e036076deb621daf300849dd3f4f9f4a38078c8a1b05c633e3d",
"difficulty": 54.12132082532227,
"mediantime": 1512141149,
"verificationprogress": 1,
"chainwork": "000000000000000000000000000000000000000000000000009dd9582469bab9",
"pruned": false,
"softforks": [
{
"id": "bip34",
"version": 2,
"reject": {
"status": true
}
},
{
"id": "bip66",
"version": 3,
"reject": {
"status": true
}
},
{
"id": "bip65",
"version": 4,
"reject": {
"status": true
}
}
],
"bip9_softforks": {
"csv": {
"status": "active",
"startTime": 1503255158,
"timeout": 1607990400,
"since": 366336
},
"segwit": {
"status": "active",
"startTime": 1503255158,
"timeout": 1607990400,
"since": 402624
}
}
}Segwit with Core 0.14.x
The Segwit opens up new possibilities like the Lightning Network, Tumblebit, Schnorr Signatures, Confidential Transactions, Cross-chain atomic swaps, and so on.
We are already exploring all these new functions, and testing the water. We expect the first implementations as fast as possible.
Kind Regards Christian
Chris, that's really awesome
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
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
Segwit is now active on BitSend, confirmed working by my transaction here: https://chainz.cryptoid.info/bsd/tx.dws?561529.htm
Thank you, yes it is true. We are now the first masternode coin with newest coinbase and segwit. I am very happy about that.
Code:
{
"chain": "main",
"blocks": 402644,
"headers": 402644,
"bestblockhash": "0000000001a33e036076deb621daf300849dd3f4f9f4a38078c8a1b05c633e3d",
"difficulty": 54.12132082532227,
"mediantime": 1512141149,
"verificationprogress": 1,
"chainwork": "000000000000000000000000000000000000000000000000009dd9582469bab9",
"pruned": false,
"softforks": [
{
"id": "bip34",
"version": 2,
"reject": {
"status": true
}
},
{
"id": "bip66",
"version": 3,
"reject": {
"status": true
}
},
{
"id": "bip65",
"version": 4,
"reject": {
"status": true
}
}
],
"bip9_softforks": {
"csv": {
"status": "active",
"startTime": 1503255158,
"timeout": 1607990400,
"since": 366336
},
"segwit": {
"status": "active",
"startTime": 1503255158,
"timeout": 1607990400,
"since": 402624
}
}
}Segwit with Core 0.14.x
The Segwit opens up new possibilities like the Lightning Network, Tumblebit, Schnorr Signatures, Confidential Transactions, Cross-chain atomic swaps, and so on.
We are already exploring all these new functions, and testing the water. We expect the first implementations as fast as possible.
Kind Regards Christian
I agree, however there are so many distros that it is not just worth the time writing guides for all of the different varitions of distributions.
Ubuntu 16.04 happens to be really common (not sure if the most used version of ubuntu), so of course it provides the most support.
However problem solving is kind of a important part of the GNU/Linux experience
Ubuntu 16.04 happens to be really common (not sure if the most used version of ubuntu), so of course it provides the most support.
However problem solving is kind of a important part of the GNU/Linux experience
Well the easiest way to "solve" the problem is to have a Ubuntu 16.04 VM or whatever is the standard for the current year.
So that's where I do all my linux stuff now, particularly when it comes to compiling and crypto.
So, my take on that would be to run a VM with Ubuntu 14.04 and set up a masternode with it. The masternode setup script (https://github.com/dArkjON/BSD-Masternode-Setup-1404) should work well.
Just my2 cents, but... have fun
Segwit is now active on BitSend, confirmed working by my transaction here: https://chainz.cryptoid.info/bsd/tx.dws?561529.htm
I agree, however there are so many distros that it is not just worth the time writing guides for all of the different varitions of distributions.
Ubuntu 16.04 happens to be really common (not sure if the most used version of ubuntu), so of course it provides the most support.
However problem solving is kind of a important part of the GNU/Linux experience
Ubuntu 16.04 happens to be really common (not sure if the most used version of ubuntu), so of course it provides the most support.
However problem solving is kind of a important part of the GNU/Linux experience
Well the easiest way to "solve" the problem is to have a Ubuntu 16.04 VM or whatever is the standard for the current year.
So that's where I do all my linux stuff now, particularly when it comes to compiling and crypto.
Jump to: