[ANN] LINDA-PoW/PoS-99% APR- MASTERNODE-MULTI-WALLET ( NEW THREAD)

[kellog9000]

hello! lol LINDA to 130 sat

LOL


https://www.cryptopia.co.nz/Exchange/?market=LINDA_BTC

[kellog9000]

Sad :/

[teukka79]

How to edit linda.conf for multiple masternodes?

[BlockRopes]

Just to clarify, only 2M MN's are supported in V2. You will have to split your 30m masternode into multiple MN's.

We have a great user-compiled guide of setting up masternodes here: https://lindacoinfaq.wordpress.com/2mn/

We also have official telegram and discord for instances you might need support.

[teukka79]

wasn't able to get multiple mn in same wallet so now running 1 masternode and staking on my second pc

[baistan]

Is there any movement for yobit exchange wallet i'm still not be able to withdrawal linda and no response from yobit when will be possible?

[Digital D]

Linda should be eliminated !!! Want to lose your ass? Invest in this shit coin ! A lot of talk, but the coin has absolutely no purpose and solves no issues...down 90% from the high..one of the very worst performers ..do not be fooled !!!!

[anneke2001]

When there's blood in the streets, the successfull will buy.

Lol, I don't have to spoonfeed you but that lambo won't come in a day.
Great dollars come with great wait.
Buying in the lower lows is very healthy, wish you luck.

[anneke2001]

I smell newbie accounts fudding this thread.

[anneke2001]

I updated the VPS to v2 Lindad.  After about a minute, Linda starts spitting out errors:

Code:

EXCEPTION: St9bad_alloc
std::bad_alloc
Linda in ProcessMessages()

The VPS has 2GB of RAM plus 2GB of Swap.  And plenty of diskspace.

When browsing your last posts you seem to have issues everywhere with other coins as well.
Check here and fix what's up for you.
https://github.com/bitcoin/bitcoin/issues/9857

You do not have enough memory. Lindacoin is a working product.
What's eating your memory? Lindacoin doesn't ask that much.

[crackfoo]

I can't get the chain to download at all now that I've updated to 2, is there a bootstrap?

All I get for days now is:

ProcessBlock: ORPHAN BLOCK 751, prev=1d23dc1f131a0d677d0123423049ebc366740db42c9ccf3bfcb85159659dff35
ProcessBlock: ORPHAN BLOCK 751, prev=4fb0e6463dbd360266626199e8d2fdf23170f7c8dc4e3ab96e135b4f409395b6
ProcessBlock: ORPHAN BLOCK 751, prev=4e6c766c3a4902c6ac8b1b8967ec25f940d575c9f39d03b44dd7aba70fdecbad
ProcessBlock: ORPHAN BLOCK 751, prev=ede9d7bcf62d82cdb54799634d70503c2a79d57d444e641170628f68d403ce93
ProcessBlock: ORPHAN BLOCK 751, prev=582425ec066f4d34e906d6a982440ebbd55fe10619a761c325f757e8fb7913af
ProcessBlock: ORPHAN BLOCK 751, prev=352486049cf44c03af3f3ef1de4372c3d9ce8186c9edb20f929b0c4f138f6c07

.....

[anneke2001]

The latest bootstrap is here:
https://www.dropbox.com/s/90d3qxu72syb5et/bootstrap_latest.zip?dl=1

I got it from the Staking Tutorial document at:
https://www.dropbox.com/s/g64zj9iy7163n3c

If you have problems, don't update but uninstall completely, then reinstall the new version of Linda.

But backup your wallet, you should be good to go. If not, call Houston.

Here's a user facing the same problem on another coin, it's solved that way I just described above:
http://forum.feathercoin.com/topic/9435/problems-moving-my-old-wallet/5

[anneke2001]

This sort of information I gave you now should be included within LindaCoin's main website. It will solve all problems.

1 - Backup wallet.dat to somewhere safe (very important for your coins!)
2 - Wipe out your old Linda installation
3 - Reinstall the new version of Linda
4 - Put your wallet.dat from Step 1 in place
5 - Download latest bootstrap and put it in place
6 - Put a lindacoin.conf in place (get the addnodes from Cryptopia)

Or else, you'll end up with mixed up Linda versions on your harddisk.
This is the way to do it.

[jtnresale]

horrible community.... wish I never bought any.. was excited but EXTREMELY RUDE COMMUNLTY quickly shot down any chance of me wanting to be ANY part of this. WOW is all I have to say.. DONT WASTE YOUR TIME

[anneke2001]

Yes, it's a hell of a volume coming down. But Lindacoin works.
I get my stakes and I will not panic, and sell with profit. As usual.
Crypto done right is, a goldmine.

[anneke2001]

horrible community.... wish I never bought any.. was excited but EXTREMELY RUDE COMMUNLTY quickly shot down any chance of me wanting to be ANY part of this. WOW is all I have to say.. DONT WASTE YOUR TIME

Don't feel uncomfy, my friend. Lindacoin will have it's time in the sun. It's a normal cycle.
Hold on.

[quetadadown]

What is the minimum investment?

[handsomerat]

horrible community.... wish I never bought any.. was excited but EXTREMELY RUDE COMMUNLTY quickly shot down any chance of me wanting to be ANY part of this. WOW is all I have to say.. DONT WASTE YOUR TIME

Don't feel uncomfy, my friend. Lindacoin will have it's time in the sun. It's a normal cycle.
Hold on.

I also feel scare when Linda down. Afraid that invested to wrong coin. But.. ya, Linda have a good road map, a good team who hard working. Wait and wait, then Linda coin become Golden coin

[tothetop]

What is the minimum investment?

I think you can stake any amount at your wallet, and you must have 2M Lindas for masternode

[size_m]

for me the new wallet doesn't work on win10.
i did everything like in annekes instruction but it just doesn't connect to the linda network.
the thing with the bootstrap worked so i have only 11 days left for syncing but no matter which and how many nodes i add into the linda.conf i don't get one single connection to the network.
anybody else with this problem?
or anybody knows a solution to this problem?
otherwise i would need to install the older version of the wallet again because that one worked just fine with lots of connections.

edit:
by the way, does it matter which linda.conf you use?
i have noticed that the linda.conf contains a rpcuser number and a rpcpassword.
now should i use the linda.conf from the fresh installation or the one inside the bottstrap (or even my old one from the older wallet)?

i have also noticed that there is a strange file called .lock (0 kb) in the roaming folder.
maybe this one has anything to do with not connecting to the network?