Luxcore Weekly Report: August 10, 2018

MARKETING AND BUSINESS UPDATES

Our First AMA Video Update is coming soon!

Earlier this week, our team opened up a channel in the official Luxcore Discord for community questions to be answered in our first AMA video going live on August 15th! Continuing our transparency efforts, this is just one more initiative our team feels will better help educate and inform the community with ongoing updates to our business.

Lux is now online at Investing.com.

Make your way over to check out the great content covering Luxcore!

https://www.investing.com/indices/investing.com-lux-btc

We all want more!

And yes, so do we. There are some behind-the-scenes strategic moves in-process we can't disclose just yet. As you may have noticed, though, the editorial efforts are starting to roll out, interviews are being scheduled and our team is working full force on marketing, advertising and ongoing social strategy. Stay tuned for more of these improvements in the coming weeks. There are some incredible things happening.

DEVELOPMENT UPDATES

Smart Contracts:

• Fully activated at the block 350K.
• Fully compatible with other ecosystems like Bitcoin and Ethereum.
• Produce a Virtual Machine compatible with both Bitcoin and Ethereum.
• Compatible with Mobile devices, which allows Luxcore to promote the use of the blockchain technology to many Internet users.
• This is a revolutionary concept that could impact global finance, traditional contracts and almost every industry in real world.

"Now that's an amazing network, by the way, with parallel nodes, with privacy, the Lux Gate, and they are coming out with a decentralized exchange, and I think it will be one of the first distributed exchanges that actually functions using the atomic swap feature."  - John McAfee

Web3 JavaScript app API:

• In order to make your app work on Luxcore, the web3 object provided by the web3.js library can be used.
• Under the hood, it communicates to a local node through RPC calls.
• web3.js works with any Luxcore node, which exposes an RPC layer.
• This feature is still in on-going development. More updates to come…

Log rotation:

• Finished matching log file size and log file count between option menu and lux.conf.
• When log file size is reached, lux-qt/luxd will create the new log file automatically.
• When log file count is reached, lux-qt/luxd will delete the oldest log file.
• Therefore, we are no longer concerned about disk space for long-running wallets.
• We can use it for Pool, MN owner, Mobile wallet, Web wallet and QT wallet now.

Wallet backup:

• The number of wallet.dat backups can be configured in lux.conf and QT option menu.
• By default, we will have 10 days' worth of backups.
• lux-qt/luxd will not back itself up if the wallet.dat file has become corrupted.
• Can perform automatic daily backups when lux-qt or luxd has been running for a long time.
• Together with private key and manual wallet.dat backup, the Lux wallet.dat file will be safer than ever.

Security improvement:

• The coin will provide 2 new functions: Transparent and Privacy.
• Transparency uses the normal protocol, while Privacy uses the i2p protocol.
• If people use the Transparency protocol, everything will show (tx in/out, ipaddress, etc.)
• If people use the Privacy protocol, everything will be hidden but conditions will be applied.
• The backend is finished and we are doing some GUIs on QT.
• This feature is still on-going development. Will update in next weekly update.

Luxtre wallet development:

• Implementing backup/restore wallet feature.
• Added lsr_token tab in luxtre.
• Adding features to manage state of lsr_token

Explorer:

• Added LUX value in BTC and USD.
• Added masternodes pages (map overview and server list).
• Added Stats (Block extraction and explicit PoS extraction).
• Added CSV download of addresses.
• Search bar now on top instead of popup.
• Added Network tab.
• Added Richlist.

Web wallet:

• Updated all slaves to 5.2.0.
• Updated all slaves to 5.2.1.
• Deployed new slaves to increase capacity.
• Fixed the stuck dashboard.
• Improved dashboard loading speed.
• Load transactions only from last 10000 blocks instead of from all blocks
• Co-operating with core developers to fix SegWit address sending issue.
   
  - -

Thanks for reading and, as always, check back next week for more updates!