Dear Colleagues,
I want to inform you that the development of client 0.8.0 is almost completed, and
The process is in the testing phase.
Who wants to join the process - you can download the current version from
my personal website: http://olegh.ftp.sh/emercoin/0.8.0-dirty/
If you just hold coins, then the transition to the new version is off,
wait for the full release.
If you develop projects using Emer technologies, then
I recommend taking a new client into development and working with him.
Then you won't have to redesign the interface in the future.
I also ask for feedback that you will see "wrong", how you can improve and
etc. I must say right away that I will postpone requests that are difficult to implement,
but bugs - I'll try to fix it.
Before using - I recommend renaming the current working
directory of the old Emer-client, create a new one,
copy wallet.dat and emercoin.conf there, and use the new one
client. At the same time, the blockchain is redownloaded, but in the directory exactly
there will be no "tails" from the old client. Or at least keep a backup.
for wallet.dat.
So what's in the new version:
Core (Wallet):
Emercoin has been ported to Bitcoin Core 0.19.1. This core contains a number
improvements in terms of performance.
Together with our optimizations, this greatly improved efficiency.
CPU usage. So, when working in PoS mode,
I previously used ~20% CPU, now ~4%.
If the 0.7.X releases introduced SetWit support in the kernel, then this
version of SegWit is used by default,
including - for the address of change, generation of a new address for payment or
name.
If you need a legacy address of the old format (say, to receive
coins from an old client or from the exchange), then when
creating an address in the "Receive" menu, deselect the default flag "Generate
native segwit (Bech32) address".
If you need to create a name for a new legacy-address, then in the address bar for
name "New address" enter the word "legacy".
That is, if there is an empty string, a new beech32 address will be created, and
if the word is "legacy", then the address of the old format will be created.
Added dynamic balancing of download queues, which speeded up
blockchain download.
Downloading a full blockchain with a good network takes less than an hour.
Added mechanism for sending own transactions from mempool upon receipt
block that does not contain these transactions.
This helps to propagate stuck transactions in the mempool faster.
Added the ability to sign messages with signmessage addresses
beech32 (by the way, Bitcoin can't do that).
Increased detail information in JSON responses. So getinfo returns
both difficulty, and name_show/name_history - shows the vout for the name.
Randpay (Probabilistic payment system):
The interface to the Randpay subsystem has been completely changed, it has become more
higher level and simpler.
Now there are commands:
randpay_mkchap - set a riddle from the server to the client
randpay_mktx - create a transaction, the answer to the puzzle
randpay_accept - accept the answer, and get money if you're lucky.
See the help for these functions for options.
Moved to segwit beech32 by default, still able to generate
legacy addresses by specifying a flag when requested.
See help randpay_mktx for details.
NVS (Named record store):
Prepared but not activated (activation will occur at 90%
updating the network to a new version, including PoW miners)
the ability to include multiple operations with names in one transaction.
While working with names as before, only the default addresses have become
beech32. But even after the activation of the new functionality
the old name operations will continue to work. But now the team
"decoderawtransaction" returns the names in
information about the UTXO, and not in the information about the transaction, as in the new
format will be possible multiple UTXO with names in one transaction.
Added config parameter "-nametxoutamount", which allows you to add to
name-UTXO amount greater than the default subcent.
This is useful when sending a name whose recipient does not have coins, and
he will need to do nam_update, for example
in blockchain voting systems.
EmerDNS (Alternative domain system):
Added a filter to block DGA requests from botnets.
Added support for SRV, CAA, TLSA records
STUN (Wallet IP detection mechanism):
Added periodic request for external IP address via STUN. It may
be useful when changing the network configuration,
such as enabling or disabling the VPN.
Added config parameter "-stuntimio", indicating the initial interval
between stun requests, which increases by ~1% after each request.
By default, 15 min. Special values: 0 - prompt once, when
start (as the current 0.7.X does), -1 - don't use STUN.
ENUMER (for IP Telephony):
Added the ability to declare enum zones without checking signatures
verifiers.
Servicing only requests of type NAPTR, the rest are ignored.
Known bugs and bugs:
When downloading the blockchain at the time of the transition from the synchronization of headers to
while downloading blocks, the deserialization of messages from some
feast.
Currently, the client simply disconnects from that peer, and continues
work. The bug is not fundamental, it has a low priority.
Not assembled in BIP70 portable assembly, which requires
protobuf, but it is not in the depend libraries.
Since BIP70 is just a purchase from sites through a URI like "bitcoin://"
which is rarely used even for bitcoin, then for Emer it is still
not relevant.
Therefore, the imperfection is also not fundamental.
Block Explorer:
The explorer does not understand segwit addresses, and they are displayed as "N/A" there.
The problem is in the explorer, not in Emer. Ignore this bug, we
explorer will be redesigned later.
