Due to recent events, I've been dismissed from my position as Lead Tech - Core Developer at Lucent.

Thank you to the community who've supported me along the way.

It's been a while since I've posted on here, so here's the rundown in the period since I've last posted:

• The deployment of v0.13.x.x was a stunning success with most of the masternodes, mining pools, and exchanges updated! So far from what we can all observe, DGW has reduced the time to readjust the difficulty of the network while maintaining the target block time, which as a result, will help us alleviate any sudden surges in network hash.
  
• We got listed on another exchange at AltMarkets with a trading pair of LCNT/BTC
  
• Development transparency:
  
  • So, as you may (or may not) already know, I'm working on the implementation and idea of a Lucent Smart/Conditional Contract, unique to the Lucent network by building it entirely from scratch.
    
    With the DGW Upgrade (v0.13), which by the way if you haven't updated already, you totally should otherwise you're gonna be on the wrong side, brings a faster difficulty readjustment to handle the current hash rate miners provide us and to prevent an expensive pump and dump of difficulty like we experienced last November/December.
    
    The DGW Upgrade honestly is weird since we changed a static variable that relies on the block height, and was only theoretically tested to compile, run and accept old blocks.
    
    With future updates, I want to make it clear that this type of deployment is just possibly slow, out of the convention and possibly dangerous if not used with discretion.
    
    So before anything goes through, the new testing methodology works as follows:
    
    1.) Theoretically trace the way the new code affects the network, and use integrated deployment types like BIP9 deployments.
    2.) Compile and deploy on regression and or testnet to connect to
    3.) Receive a code audit prior to deploying to the official repository.

If there are any other questions, feel free to ask in here, or communicate with the community and developers at the official Discord Server.

- Amethyst C. aka AlphaSerpentis (Lead Tech @ Lucent Core)

We've officially released Lucent Core v0.13.0.0!

The following change(s) have been made:

• Updated versioning
  
• Updated difficulty readjustment algorithm to DarkGravityWave (DGW) which is backward compatible to sync with old blocks.
  

Masternode operators, pool operators, exchanges, and users should all update as soon as possible! Backup your keys before updating!

https://github.com/LucentCoin/Lucent/releases/tag/v0.13.0.0

Good day to all!

I'd like to inform all users of Lucent that we are collecting a consensus if we should switch to the "DGW" algorithm for the difficulty readjustment.

This is important because it'll determine if Lucent Core will update to v0.13.0.0 as a result.

Please vote here now!

Quick update on this:

1. We're still in the process of exploring and fixing the difficulty issue.
2. The whitepaper is on hold at the moment, but it exists!
3. Easy Install script for Debian has been updated to help masternode operators, but no other scripts have been made since.
4. WE GOT LISTED ON COINGECKO!

I use MiningRigRentals (MRR) to sell my hashing power when I'm not actively experimenting/using it, but I keep getting segmentation faults when MRR points to a new pool while the MLD is mining.

As a temporary fix to this, I made a bash script so that it'll restart the program if it doesn't exit with code 0 which worked BARELY 50% of the time. I've been trying to figure out why this is happening by checking the CP210x drivers, reinstalling BFGMiner and rebooting my RPI, trying different configurations, clocking down, but what I noticed is that if I don't use MRR and instead mine directly to a pool myself, there's no problem when I tell BFGMiner to mine in a different pool.

I tried using NiceHash even to see if it was just MRR, but the instant BFGMiner tries to initialize MLD, it seg faults.

May someone please point me to the right direction as to where things could be going wrong?

Thanks in advance.

Hello all!

I'm honored to be a part of the Lucent Core Development Team as the Lead Tech!

So far, I've contributed via assisting members of the Lucent community, fixing documents, developing a Debian installation guide and script, and soon-to-be the official whitepaper for Lucent!

Anyways, if you wish to contribute, remember to take a look at https://github.com/LucentCoin/Lucent for any issues, pull requests, or releases.

Additionally, I've created my own repository to store the "Easy Install" scripts that include the implementation of Masternodes and Lucent Core at https://github.com/AlphaSerpentis/Lucent-Core-Easy-Install.

So here's what is on the agenda so far:

1. Fix the difficulty issue on the Lucent network
2. Write the whitepaper and receive approval by both the community and other core developers
3. Create more "Easy Install" scripts
4. List on CoinGecko/CoinStats!

If you wish to contact me, join the Official Lucent Community Discord! or DM me via AlphaSerpentis#3203.