could you help me to information of project ?
In this current version, block times, block rewards, transaction fee, and blockchain database format have changed.
Launch date: September 18th, 2017
Premine: 9365 blocks
POW/POS: Proof-of-Work (POW)
Block times: changed from 240 to 540 seconds
Currency ticker: B1T
Block rewards: changed from ~15 B1T to ~100 BIT
Algorithm: CryptoNight-Lite - hash-based Proof-of-Work (PoW) algorithm
Max supply: ~18.4 million B1T
Difficulty: retargets at every block
Transaction fee: changed from 0.000001 to 0.01
Seed nodes: 138.68.115.86; 159.65.213.51
P2P port = 50805;
RPC port = 50904;
The blockchain database format has been changed from raw memory to LMDB.
Link to Bitcash GUI's source code and instructions on how to build B1tcash GUI on Linux, Windows and IOS:
https://github.com/b1tcash/b1tcash-guiLink to Bitcash source code and with instructions on how to build B1tcash on Linux, Windows and IOS:
https://github.com/b1tcash/b1tLink to B1tcash's Blockchain explorer:
http://b1t.cashAdditionally, below are specifications of changes that have been adopted from Monero in this current version. These specifications can also be accessed at:
https://github.com/aeonix/aeon/releases/tag/v0.12.0.0 The following changes have been adopted:
Per-kb fees: PR-184
Allow miners to claim less money than allowed: PR-410
Claim a quantized reward in coinbase & all outputs must be decomposed: PR-425
Require miner tx to have well behaved outs: PR-763
Reject invalid pubkeys: PR-1386
Use new block filling algorithm: PR-1902
Forbid duplicate ring members: PR-2188
Checks for top block hard fork version: PR-2269
Reject unsorted ins and outs: PR-2440
CryptoNight variant 1: PR-3253
This is adapted to CryptoNight-Lite, making it CryptoNight-Lite-variant1
The following are Aeon's own changes deviating from Monero:
Transactions of ring size 1 (i.e. with no decoy outputs, called non-private txes henceforth) are allowed to occupy up to ~10% of all transactions in each block. Specifically, for a block containing N txes (excluding coinbase), M non-private txes are allowed to exist as long as 10*(M-1) does not exceed N.
The implication of non-private txes is the same as before: you can use them wisely to make transactions smaller and thus save in fees, but if you do so when there's a backlog of non-private txes in the transaction pool, your non-private txes will likely take very long time to confirm. You're advised to use normal transactions if you want timely confirmation.
Normal transactions must have at least ring size 3. In other words, transactions with ring size 2 are entirely forbidden.
Multisig is disabled (but will be enabled again once Aeon adopts RingCT with Bulletproofs).