Good news. Spacecoin on cryptopia has 8 connections and is back in business! 17 nodes running the wallets. We are still looking for a new exchange. Any ideas where there is a reputable exchange we can get listed at?

No. But you can get some idea by comparing the posting frequency.

On here there's typically what, half a dozen posts per day ... at best? The Linda Discord channel frequently receives more than that in a minute.

Not sure why the nodes dropped off.
Mine where down yesterday but it is usually attributed to spectrums internet service going down or just acting flaky.

received block 00000000023f27205c86
SetBestChain: new best=00000000023f27205c86  height=1405731  trust=29474282056660516  blocktrust=466087502913  date=09/01/18 03:27:08
ProcessBlock: ACCEPTED

<quite a few linefeeds and then my watchdog restarted the wallets:>

SpaceCoin version v1.0.1.4 (Jun  7 2018, 19:26:38)
Using OpenSSL version OpenSSL 1.0.1t  3 May 2016
Startup time: 09/01/18 03:30:06
...

Times change.

It's not just Linda that has moved to Discord, many have. Bitcointalk is old and clunky. It's just not practical to discuss all the separate elements of Linda (wallets, staking, masternodes, trading, etc, etc) here in a single thread, while providing support and keeping people up-to-date on developments. Discord provides a much more modern, organised interface that makes it easy for the developers to be more involved with the community.

Personally I think Discord was a good choice. It keeps all of the discussions about each crypto development conveniently organised in one place, while making it easy to add more 'servers' to switch between the discussions of all the different crypto development that you might be following with just a single sign-up. And you can access it in a browser on a desktop computer just as easily as you can from a mobile device.

When you buy a product that requires support, you wouldn't expect the manufacturer to participate in every related forum on the internet -- in most cases they would have their own forums, which you would be required to subscribe to if you wished to be kept up-to-date on developments. At least with Discord you only have to register once, yet each development team has its own 'forum'.

Linda's Discord channel has around 7000 members presently and typically over 600 online at any one time. Compare that to this place. It would be difficult for the developers to justify spending time maintaining and supporting this thread when it reaches so few people.

I am seeing this issue even after downloading with the Boostrap and starting over.

Anyone know if / how this can be fixed? I see it back even years ago with Bitcoin and Doge same ORPHAN BLOCK 751 issue

I mean since the mandatory v3.0.0.0 update .....

Are there any more requirements? In terms of CPU capability, traffic or harddisk?
And are there any specific regions that the server should be in? I mean if someone does US I could do Europe and/or Asia.

And may I ask how you are involved with the project?

Hi,

I would be willing to set up a node and carry the costs for one or two small server for this. I am not heavily involved as an investor, but I see this as an opportunity to learn. Not very tech savvy though (i can compile and run stuff on Linux though ). If you give me a helping hand, I'd be glad to help out.

Kind regards

coin related news doesnt seem to get announced on this thread...for those who don't know v3.0 of the wallet is out, and will be a mandatory upgrade as of block 585200..after that block, lower versions will be disconnected from the network.

you can get it at https://github.com/TheLindaProjectInc/Linda/releases

below are the notes from the github post

Linda 3.0.0.0g
This is a mandatory upgrade. Please upgrade by August 21st to avoid any interruptions


Changelog
Critical Fix
- fixed issue where wallet was stuck on syncing block 0 when syncing a new blockchain
- Beginning from block 555000, consecutive blocks created through PoW will be rejected by the network. This is to address a potential security concern if an attacker has a vast amount of hash power at their disposal.
Sync Improvements
- track peer block downloads to auto remove stalled peers
- disconnect peer when reached ban threshold (needs proper ban logic implemented)
- disallows access to nodes running wallets less than 2.0.0.0
- nodes running wallets less than 3.0.0.0 will be disconnected from the network starting after block 585200
- dump orphan blocks from peer when disconnected (prevents filling orphan block list with unusable blocks)
- add maxorphantx startup flag to cap orphan transactions held in memory for running on lightweight machines
General Improvements
- masternode should ignore if wallet is unlocked for staking only
- locked masternode coins will be ignored when staking
- masternode start will check all possible coin inputs instead of just the first
General RPC improvements
- updates listreceivedbyaddress RPC command to return only your addresses when running with minconf=0 and includeempty=true instead of returning all addresses including send addresses from your address book
- fix GetAccountAddress not committing the new account to the walletdb causing duplicates to be made when running the command again
- setaccount no longer can create new addresses. This was a confusing feature and gave no way to change account names without creating new addresses
- setaccount returns error if trying to change the account of an address that doesn't exist in your wallet - listreceived now returns (change) addresses
- added RPC commands for masternodes
- masternode status dumps your masternode status. includes your active time and status to determine if your masternode is running correctly
-masternode status-all dumps the above info for all masternodes on the network (only your masternode will include status field)
- masternode init ip:port allows you to initialise your masternode without editing the linda.conf or masternode.conf files and or restarting the program. Running masternode start will then start your masternode
- masternode addremote ip:port - adds the info to your masternode.conf file (no need to restart Linda-qt or Lindad) running start-many or start-alias will start the appropriate remote masternodes
- masternode removeremote - removes the related account from your masternode.conf file (no need to restart Linda-qt or Lindad) you will need to run the masternode stop to stop these masternodes
- masternode isInit - returns boolean if masternode is enabled and capable of running
- masternode kill - disables masternode. can be re-enable by running init command
- Masternode tab performance improvement.
Thanks to @Tumba24
- fixed the masternodes UI tab uses a lot of resources when it refreshes
. - added sorting to the masternodes UI tab

Thanks for the clarification @psycodad. And this is what was happening. Nobody but Mr./Ms. Selfish mined Bitmark until they left, and shortly thereafter we switched to 8mPoW with DGWv3 anyway.  

 IIUC, this selfish-mining is possible (at least in part) because a larger chain can appear out of the blue and is accepted by all the nodes, because it is the longest, most-work chain, although the "honest" nodes had not seen the selfish node before at all.
Thus, the "selfish" part: The Selfish Miner did not share their work (and thus allow possible competition) until they were sure they hade a stronger chain to show.   Can you shed some more light on this ?

Those large wallets almost certainly belong to the "selfish miner" which mined from the Fall of 2016 until perhaps early 2018, the exact period with the highest emission rate. You can read about this problem, and how we as a community have dealt with it here:    Hard Fork #1 Criteria and Motivation.   The selfish miner did not attack the chain _per se_, that is, they did not double-spend or anything like that, they merely employed their superior hashing power (certainly above 51%) to mine the chain, and they are almost certainly the holders of the large sums as detailed above.

After early 2018, there is a much less pronounced emission rate from a relatively short period of honest, native SCrypt-only mining, and, now, once again, much higher emission from honest, distributed mining on the 8mPoW algos, dominated by merge-mining. Honest merge-mining, yes, but very cheap to produce merge-mining, which is driving the price down.

 I do believe that there must be a reward policy which accounts for the production cost differential of pure native mining from near zero-cost merge-mining. I think it's unwise to foster a complete reliance on foreign chains for our mining.   I do believe the best way to maintain balance, retain dedicated native Bitmark miners and still benefit from the security of a measure of merge-mining is simply to account for that production cost differential in the subsidy.

And yes, certainly that selfish-mining period was centralized mining, and it is for that very reason that we went from a primitive diffalgo with single PoW SCrypt  to  8mPoW with DGWv3 diffalgo.

The PoS went back up again.
Did you re-started the stacking on your node ?

86% for the last 100 blocks. What is the point to keep this. It would be nice to shut it completely or to share the code (for a implantation in a new wallet version).

K.

i looked into the crashing, it has nothing to do with Power. both my hubs can provide enough power, i have stress tested it with plugging 3 Moonlanders 2s into 1 Hub, this ran fine without any speed drop. I now have 2 Hubs running 2 moonlanders each.

i wanted to know if anyone has managed to write a Crontab script that restarts the SH file every 1 or 2 hours? if so how did you do it! any help would be great.



Regards

Paul

while true; do timeout 7200 /path/to/your/script-executable; sleep 3; done

If there is going to be a swap then I need to get my wallet to sync up.
A couple months ago it wouldn't sync, then it finally did.
Now, 2 months later, its stuck in "out of sync" again with my whole total of coins "staking".  Been like this for 2 weeks now...
I guess I can always delete everything and reinstall it, but this is getting annoying.
I do have the newest wallet that they released recently that changed all of the staking value.