Good evening.
Thanx a lot for explanation, but still I have questions.
If nethash changes and it is a cause of blocks-per-day fluctuations,
why thereis so big and stable difference between declared (960)
and calculated (1650+) blocks per day? Is it only problem of difficulty's function or
there are some other problems?
MAGs have mined alot, in whitepaper about 35 millions for 1'st year and now
we have almost half of this quantity.
Will see what explanations will give us the dev.
Hope soon and will be fixed if it is mistake.
Can somebody epxplain what happens with MAG specifications?
In whitepaper says:
Block Time: 90 secs per block.
Block Reward: 200
Block Reward Halving: every 360 000 blocks
So, it is 24*3600/90=960 blocks per 24h
I put command "getinfo" in the console of debug window of the latest magnet wallet
and it says for now 10.02.2018/20:16:
{
"version" : "v1.3.0.0-61403",
"protocolversion" : 61403,
"walletversion" : 60000,
"darksend_balance" : 0.00000000,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"blocks" : 151856,
"timeoffset" : 1,
"moneysupply" : 14718352.13753063,
"connections" : 13,
"proxy" : "",
"difficulty" : 47615.84673888,
"testnet" : false,
"keypoololdest" : 1511982826,
"keypoolsize" : 1001,
"paytxfee" : 0.00010000,
"mininput" : 0.00000000,
"unlocked_until" : 0,
"errors" : ""
}
We are at block #151856
151856/960=151.18 days or more than 5 months BUT the project was started in November of 2017,
about 3 months before, not 5 months.
And finally i do some researches.
I open my transactions and take two points:
1. txid: 46615bd7d579ed98b9ae8ab1e85d4a15bda3a2dff7564fc3d6860f10fc4bc502 at 02.12.2017, 14:01 / 115814 confirmations
2. txid: 67fb03fa05ea16f2c3d470bb926209228c7d508fe73742bd98d7fba746380fd5 at 20.12.2017, 13:51 / 86227 confirmations
So, from 1 to 2 was 115814-86227=29587 blocks
29587/(20-2)=1644 blocks per day which is greater than specified 960 blocks/day
Lets take some other points:
3. txid: 95dfb03afec12ddf0f1a64b59077bb04236ff228e5b806922db1d050d1b2775e at 19.12.2017, 10:00 / 88129 confirmations
4. txid: 6d4afb499e3eafa0b3076ca03c5607347aa9fd0baf973a563141fba606db53d5 at 03.02.2018, 10:08 / 12092 confirmations
So, from 3 to 4 was 88129-12092=76037 blocks
76037/46=1652 blocks per day, almost the same like from 1'st case
Could somebody explain all this?
It is include POS Block.
Block time seem only count for POW block
First of all sorry for not being able to check here as much as in the beginning of the network. Growing network needs more attention than ever before.
Lets go with the explanations!
I quickly resolve another message here on the forum, before answering the quoted one.
Whoever posted here that we "raped" the chain before going public.
No, we did not. Here -
https://bitcointalksearch.org/topic/annmag-magnet-goes-stellar-more-in-description-magnetworkio-2402932 - on page 32 there is an explanation and if You need more - feel free to read through the whole ANN thread to get even better picture. We fight the FUD a lot and give out many explanations on the topic.
Next about the blocktime info.
If You check our explorer here -
http://explorer.magnetwork.io/ You can see easily that often 2-3 blocks are found within a minutes time.
We are still a small growing network and the hashrate fluctuations create this effect so blocks are found faster.
This is no scam or anything particular happening actually. When we gain more momentum after releasing some of our main features in 4-5 months time, the hashrate stability will improve and blocks will be found in a more stable rate. Blocktime in specs always refers to the numeric value in the source code that is the basis for algorithm when re-targeting difficulty, but this is almost never consistent with the real-time results.
So it all depends what difficulty adjust algo chain is using.
We are a fork of Transfercoin and chose to inherit their custom algo for difficulty adjust. We use exponential moving for re-targeting (very similar to Kimoto).
The other classic way to go is to use re-target "family" of simply taking the average and adjusting it by X, but in case of a big hashrate spike, it would take forever to even out the difficulty.
Our algo re-targets in 6 blocks, doesn't matter the size of the spike. This solution may bring faster blocks at the start of the chain when smaller hashrates and more fluctuations, but does not get the chain stuck in case of hashrate spikes (that we have had a lot actually).
So suggesting that we have done anything to manipulate the code in our favor (chain "raping" accusation etc.) is simply ignorant. If You check our GitHub, You can see that we have been forked 14 times and starred by other developers 18 times at the time of writing this. If there was any trouble with the code, any backdoor or malicious entries - developers would have found those fairly quickly and our story would have ended. Instead we have 1000+ MNs on the network and very supportive community of 500-1000 users on slack/Discord.
In conclusion - if we are not here answering every day, we are working on the chain. Lot of FUD often comes from not knowing all the pieces to the puzzle. One way to stay in the loop is to follow our developers blog.
Last post there will share some light on whats to come in near future -
http://magnetwork.io/2018/02/04/developer-diaries-from-the-trenches/Best way is actually to join our Discord channel for live help and info. We (dev team / support / community) are 24/7 there to answer questions and help out -
https://discord.gg/EtEGyEn