We have confirmed the normal operation of BLOCK_HASH_MODIFIER.
We have completed the implementation of the main codes and the operation check in v3.
autogen.sh is ready to build SorachanCoind.
and … it needs “libtool”, “autoconf” and “unzip”.
yum install libtool
yum install autoconf
yum install unzip
sudo apt-get libtool
sudo apt-get autoconf
sudo apt-get unzip
The funds for the development of this system were missing,
but we simply confirmed that the funds had not yet been withdrawn from the Exchange (Finexbox).
Therefore, we have confirmed the conservation of funds and will resume development.
In this case, I had made to manage some coins to our project someone.
That points, I deeply apologize.
From now on, I will manage the funds “myself”.
Thank you so much.
Due to various reasons, finexDriveChain development has been cancelled.
More details will be posted here and on Twitter as soon as the detail is decided.
We should be added that this is NOT a technical issue.
Before that, we will integrate the implement in benchmark feature into Qt.
We will collect various drive failure information and apply them to recovery services.
We have completed the verification of the hard-fork.
The mainnet aim to change have a block height of 550,000.
In line with this,
we will implement features related to failure prediction at once.
As a result of the verification, we found that the block hash switching fails when PoS crosses the block switching boundary.
Therefore, we will implement by changing only the PoW mining without changing the block version.
We will check the withdrawal status of each Exchange
where SORA is listed, every few days.
After actually sending coins, it becomes “ok” for the first time after confirming the withdrawal TO MY WALLET.
Unnamed Exchange https://www.unnamed.exchange/
BTC ok?, LTC no, ETH no, DOGE no, USDT no, TRX no, BELL ok, SORA ok
Dogecoin may be under maintenance in the short term!!
BTC ok, LTC ok, ETH ok, DOGE no, MONA ok, TRX ok, BELL ok, SORA ok
There is no problem.
ETH ok, USDT ok, SORA ok
Today, we will do hard fork in testnet.
Switching in block will be Lyra2REv2 from block height 1495000.
We will intend to replace hash from Scrypt to Lyra2REv2.
We are currently in the process of verification.
As soon as it is completed, we will officially inform including the date and time of the hard fork.
We had implemented by checkpoints to judge of bip66.
For Windows and Linux versions, we have returned to the LevelDB + SQLite configuration.
The mobile version currently under development will consist of SQLite only.
using Blockchain DB: replace from LevelDB to latest SQLite (SQLite v3.35.0 Mar-2021)
We have created a database of peers_sql.dat from peers.dat and we enabled automatic checkpoints on a trial basis.
We have succeeded in unifying the database in SQLite.
Therefore, we were going to be able to provide an automatic build version that can utilize the latest environment.
We are currently checking performance of the blockchain that has migrated from LevelDB to SQLite.
In the case of LevelDB, in order to retrieve data using the sorted records arranged in a tree structure, it is necessary to deserialize unnecessary key data in order to apply conditions for exiting the search.
For example, if blockchain has 500,000 blocks, the key will be deserialized 500,000 times.
Then, since memcpy is called several times internally, it is a heavy process.
Furthermore, it will be strcmp in the comparison process. It’s heavy.
On the other hand, in the case of SQLite, the key can be specified in advance by the condition, so they only need to get the value.