Author

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

newbie
Activity: 12
Merit: 0
There is a bug in Bitsend regarding masternode outputs and remote starting of masternodes.
If you have "mnconflock=1" in your bitsend.conf, masternode outputs are locked so that you can't spend them inadvertently, which is good. Unfortunately, this also prevents you from starting your masternode remotely, because the wallet can't find the 25000 BSD VIN anymore, which can be seen as a bug.
So, to start your masternode remotely, temporarily set mnconflock to 0 in your bitsend.conf, restart wallet and start your masternode.


I didn't have the mnconflock linein my conf file, but so I added mnconflock=0, and restarted the wallet. I still can't allocate VIN and the 25k balance is still locked in the Inputs section. How do I unlock it?

Strange. Are you sure you changed the right bitsend.conf? Also make sure that the wallet is not started with the command line parameter "-mnconflock".
You can unlock an input manually in the wallet: In Coin Control, select the locked transaction with right mouse button and unlock it via popup menue. This is a temporary solution until next wallet start.
newbie
Activity: 61
Merit: 0
Successfully updated to v1.1.0.2, how long do I keep temporary connect in bitsend.conf instead of addnodes?

T.
newbie
Activity: 61
Merit: 0
I was slowly getting towards buying up 5000 BSD, oh well keep going to 25000! I guess the change is good for Bitsend.
I really want a masternode!
I did enjoy seeing my first giveaway deposits  Smiley Thankyou.

T.
hero member
Activity: 525
Merit: 500
There is a bug in Bitsend regarding masternode outputs and remote starting of masternodes.
If you have "mnconflock=1" in your bitsend.conf, masternode outputs are locked so that you can't spend them inadvertently, which is good. Unfortunately, this also prevents you from starting your masternode remotely, because the wallet can't find the 25000 BSD VIN anymore, which can be seen as a bug.
So, to start your masternode remotely, temporarily set mnconflock to 0 in your bitsend.conf, restart wallet and start your masternode.


I didn't have the mnconflock linein my conf file, but so I added mnconflock=0, and restarted the wallet. I still can't allocate VIN and the 25k balance is still locked in the Inputs section. How do I unlock it?
copper member
Activity: 2324
Merit: 1348

The next day for our giveaway is tommorrow (So 28.08.2016). We pay tommorrow 250 Bitsend per Member. The paymentday on 05.09.2016 is cancelled. The next normal paymentday is then on 12.09.2016.


Weekly Payments 28.08.16 - Giveaways and Supporter

Today was paid for giveaways 24500 BSD and supporter 3510 BSD.That is is 33,3 % from the total generated coins of the week.
We have paid a total of  244339,9 BSD this year! (1270,57 Dollar ).

The giveaway in this week was per member 30 BSD + 220 Bonus (192500 SAT/BTC( p. Member) and has now 98 member.
Everyone can join our giveaway! Info about the giveaway here: http://bitsend.info/forums/index.php?topic=18.0
The next paymentday is the 12.09.2016.


Best Regards Christian


newbie
Activity: 12
Merit: 0
There is a bug in Bitsend regarding masternode outputs and remote starting of masternodes.
If you have "mnconflock=1" in your bitsend.conf, masternode outputs are locked so that you can't spend them inadvertently, which is good. Unfortunately, this also prevents you from starting your masternode remotely, because the wallet can't find the 25000 BSD VIN anymore, which can be seen as a bug.
So, to start your masternode remotely, temporarily set mnconflock to 0 in your bitsend.conf, restart wallet and start your masternode.
hero member
Activity: 525
Merit: 500
Okay so I'm trying to set up a Masternode. I have the control wallet on this rig, and the daemon has already been started on my VPS.

 I'm getting the following error from my control wallet:

 "overall" : "Successfully started 0 masternodes, failed to start 1, total 1",
    "detail" : {
        "status" : {
            "alias" : "MasternodeD01",
            "result" : "failed",
            "errorMessage" : "could not allocate vin"

Can someone help me?


PS: Why do my masternode outputs keep getting deleted?


21:24:25

masternode outputs


21:24:25

{
}

All blank.
hero member
Activity: 525
Merit: 500
The collateral is now 25,000 and not 5,000 right?
legendary
Activity: 2576
Merit: 1073
Doesn't allow me to use another port. It says port must be 8886 for mainnet. This basically means I'm limited to one Masternode per IP address, right?

Look at my post above - there are definitely people who run many masternodes on a single machine. Port is shown to be the same, but that is not true - actually masternodes are running on different ports, just "masternode list" shows them incorrectly (@Christian, you might want to look into this - as the output is actually misleading - ports should be different).
legendary
Activity: 2576
Merit: 1073
Code:
bitsendd masternode list
{
    "37.120.190.76:8886" : "ENABLED",
    "37.120.190.76:8886" : "ENABLED",
    "37.120.190.76:8886" : "ENABLED",
    "37.120.190.76:8886" : "ENABLED",
    "37.120.190.76:8886" : "ENABLED",
    "37.120.190.76:8886" : "ENABLED",
    "37.120.190.76:8886" : "ENABLED",
    "37.120.190.76:8886" : "ENABLED",
    "37.120.190.76:8886" : "ENABLED",
    "37.120.190.76:8886" : "ENABLED",
    "37.120.190.76:8886" : "ENABLED",
    "85.214.68.75:8886" : "ENABLED",
    "85.214.68.75:8886" : "ENABLED",
    "37.120.190.76:8886" : "ENABLED",
    "37.120.190.76:8886" : "ENABLED",
    "85.214.68.75:8886" : "ENABLED",
    "37.120.190.76:8886" : "ENABLED",
    "37.120.190.76:8886" : "ENABLED",
    "85.214.68.75:8886" : "ENABLED",
    "85.214.68.75:8886" : "ENABLED",
    "85.214.68.75:8886" : "ENABLED",
    "85.214.68.75:8886" : "ENABLED",
    "85.214.68.75:8886" : "ENABLED",
    "37.120.190.76:8886" : "ENABLED",
    "37.120.190.76:8886" : "ENABLED",
    "37.120.190.76:8886" : "ENABLED",
    "37.120.190.76:8886" : "ENABLED",
    "37.120.190.76:8886" : "ENABLED",
    "37.120.190.76:8886" : "ENABLED",
    "37.120.190.76:8886" : "ENABLED",
    "37.120.190.76:8886" : "ENABLED",
    "37.120.190.76:8886" : "ENABLED",
    "85.214.68.75:8886" : "ENABLED",
    "85.214.68.75:8886" : "ENABLED",
    "85.214.68.75:8886" : "ENABLED",
    "104.207.131.249:8886" : "ENABLED",
    "[2a02:c207:3001:4465::b001]:8886" : "ENABLED",
    "[2a02:c207:3001:4465::b002]:8886" : "ENABLED",
    "[2a02:c207:3001:4465::b003]:8886" : "ENABLED",
    "[2a02:c207:3001:4465::b004]:8886" : "ENABLED",
    "[2a02:c207:3001:4465::b005]:8886" : "ENABLED",
    "[2a02:c207:3001:4465::b006]:8886" : "ENABLED",
    "[2a02:c207:3001:4465::b007]:8886" : "ENABLED",
    "[2a02:c207:3001:4465::b008]:8886" : "ENABLED",
    "[2a02:c207:3001:4465::b009]:8886" : "ENABLED",
    "[2a02:c207:3001:4465::b010]:8886" : "ENABLED",
    "[2a02:c207:3001:4465::b011]:8886" : "ENABLED",
    "[2a02:c207:3001:4465::b012]:8886" : "ENABLED",
    "[2a02:c207:3001:4465::b013]:8886" : "ENABLED",
    "[2a02:c207:3001:4465::b014]:8886" : "ENABLED",
    "[2a02:c207:3001:4465::b015]:8886" : "ENABLED",
    "[2a02:c207:3001:4465::b016]:8886" : "ENABLED",
    "[2a02:c207:3001:4465::b017]:8886" : "ENABLED",
    "[2a02:c207:3001:4465::b018]:8886" : "ENABLED",
    "[2a02:c207:3001:4465::b019]:8886" : "ENABLED",
    "[2a02:c207:3001:4465::b020]:8886" : "ENABLED",
    "[2a02:c207:3001:4465::b021]:8886" : "ENABLED",
    "[2a02:c207:3001:4465::b022]:8886" : "ENABLED",
    "[2a02:c207:3001:4465::b023]:8886" : "ENABLED",
    "[2a02:c207:3001:4465::b024]:8886" : "ENABLED",
    "[2a02:c207:3001:4465::b025]:8886" : "ENABLED",
    "[2a02:c207:3001:4465::b026]:8886" : "ENABLED",
    "[2a02:c207:3001:4465::b027]:8886" : "ENABLED",
    "[2a02:c207:3001:4465::b028]:8886" : "ENABLED",
    "[2a02:c207:3001:4465::b029]:8886" : "ENABLED",
    "[2a02:c207:3001:4465::b030]:8886" : "ENABLED",
    "37.120.190.76:8886" : "ENABLED"
}

Hmm, we have a funny list above - looks like there are just max 4 people having masternodes here: three whales with huge amount of masternodes accumulating as much BSD as they can, and just one normal BSD user with a single masternode.. guess who is that..? Smiley
full member
Activity: 168
Merit: 100
Secured & Trusted Crypto Trade Platform
hero member
Activity: 525
Merit: 500
Can I run more than one masternode per IP address?

one masternode per port

set up multiple wallets with different datadir and use different ports

the only limit is system memory

edit: my knowledge is from from other masternode coins
in case chris did change the code in that area he have to explain the differences

even if the network now after a lets say less than optimal hardfork is a bot chaotic

i see big possibilities in the future for bitsend

the fedchain europecoin cooperation
wher also dmd diamond is a project supporter
looks to me like a pond that can grow some big fishes

Doesn't allow me to use another port. It says port must be 8886 for mainnet. This basically means I'm limited to one Masternode per IP address, right?
copper member
Activity: 2324
Merit: 1348
Bittex is currently under Wallet Maintenance but Livecoin.net, Cryptopia, southxchange.com  is complete online.

The next day for our giveaway is tommorrow (So 28.08.2016). We pay tommorrow 250 Bitsend per Member. The paymentday on 05.09.2016 is cancelled. The next normal paymentday is then on 12.09.2016.
sr. member
Activity: 518
Merit: 250
Hello Mates,

the new version 1.1.0.2 is online.

-disconnect wrong versions
-little fixes in Dual KGW3

https://github.com/LIMXTEC/BitSend/releases/tag/BSD1102

Currently only windows and source.

Best Regards Christian
Dear friend
With new vesion,
I have to sync all or not?
legendary
Activity: 2576
Merit: 1073
Is there a problem with the chain? Trying to withdraw from Bittrex and getting this: "The last block update occurred 176 minutes ago."

The chain moves well. All of my wallets on different machines, as well as CrypoId block explorer are at block 213187, which is just 6 minutes old.

Bittrex might be at a wrong fork, and it would be better to refrain from withdrawals for now.
hero member
Activity: 525
Merit: 500
Is there a problem with the chain? Trying to withdraw from Bittrex and getting this: "The last block update occurred 176 minutes ago."
copper member
Activity: 2324
Merit: 1348
Hello Mates,

the new version 1.1.0.2 is online.

-disconnect wrong versions
-little fixes in Dual KGW3

https://github.com/LIMXTEC/BitSend/releases/tag/BSD1102

Currently only windows and source.

Best Regards Christian
legendary
Activity: 3052
Merit: 1053
bit.diamonds | uNiq.diamonds
Can I run more than one masternode per IP address?

one masternode per port

set up multiple wallets with different datadir and use different ports

the only limit is system memory

edit: my knowledge is from from other masternode coins
in case chris did change the code in that area he have to explain the differences

even if the network now after a lets say less than optimal hardfork is a bot chaotic

i see big possibilities in the future for bitsend

the fedchain europecoin cooperation
wher also dmd diamond is a project supporter
looks to me like a pond that can grow some big fishes
hero member
Activity: 525
Merit: 500
Can I run more than one masternode per IP address?
sr. member
Activity: 518
Merit: 250
A little extra giveaway for all member. 10 BSD today ^^

8a7a6dfc589f9e72ff66f54e898f447efa8f97522dba37beb8aad62cb1574612

Best Regards Christian
Thanks! I have received
Jump to: