Yes, you should start it via usual "masternode start-<smth>" command only for now and wait for DIP0003 to register it as a deterministic one. This post above https://www.dash.org/forum/threads/dash-core-v0-13-on-mainnet.43130/#post-205630 outlines the migration process pretty good.
There is no special rules for this case, will require 101 confirmations like any other coinbase outputs. That's a network-wide rule and I believe all exchanges and wallets handle this properly (they don't even have to care if this is a MN payment or a miner reward, what matters is that it's...
Let me correct this ^^^ a bit. These entries are derived from pubKeyMasternode which is a part of masternode announcement message (mnb). But yes, they are not used until spork15, so you can ignore them for now.
You can use "getblockchaininfo" which should produce output like
...
"dip0003": {
"status": "started",
"bit": 3,
"period": 4032,
"threshold": 3226,
"windowStart": 1003968,
"windowBlocks": 0,
"windowProgress": 0,
"startTime": 1546300800...
Great job!
Small correction:
"A" has actually 2 phases for 0.13 masternodes:
A1. Before DIP3 activation: Start MN as usual via "start". You won't be able to send ProRegTx yet.
A2. After DIP3 activation: Start MN as usual via "start" if you haven't already, if it's already started, skip to...
Make sure "Options -> Network -> Allow incoming connections" checkbox is on.
Number of outgoing connections going above 8 and down again is ok - it's your wallet asking some masternodes to confirm the state of some another masternode, nothing to worry about.
Only the Owner can set the percentage. I don't see an issue with that because even now operators can charge in Dash. IF it's not what the Operator wants, he can simply charge as usual (i.e. the Owner gets 100% and pays X USD at the end of the month or in any other way the Owner and the Operator...
There is no additional trust in operator, that's not the case - the only special tx operator can sign to update any mn data is ProUpServTx.
i.e. operator can only update node IP and an address he would like to get his share of the reward to and that's it.
Pls see...
2018-12-01 08:01:39 ERROR: ReadBlockFromDisk: Errors in block header at CBlockDiskPos(nFile=0, nPos=39907952)
2018-12-01 08:01:39 *** Failed to read block
i.e. the last block data file is broken. Since you already tried to disable/remove AVs I guess it could be some disk or file system issue...
Yep, this is expected - IS locks are held for 6 blocks on testnet https://github.com/dashpay/dash/blob/master/src/chainparams.cpp#L283 (24 on mainnet https://github.com/dashpay/dash/blob/master/src/chainparams.cpp#L130).
Translations should be fixed by https://github.com/dashpay/dash/pull/2451
Re sync issues: there are a lot of different versions on testnet, things will get better once we rebuild our testnet mn cluster.
To answer every your question specifically:
No.
No. No. No.
:D
In general, DIP3 was modified recently https://github.com/dashpay/dips/pull/21 and @codablock already implemented these changes in https://github.com/dashpay/dash/pull/2412 and https://github.com/dashpay/dash/pull/2427 exactly to...
Dash Core 0.12.3.3 is a critical bugfix release of the Dash Core 0.12.3.x series.
There was a serious vulnerability discovered in Bitcoin Core's codebase recently which
can cause node receiving a specially crafted block to crash https://github.com/bitcoin/bitcoin/pull/14247
We encourage all...
You are trying to spend ~1002 tDASH but you only specified 1 single output for ~80 tDASH. You must specify a change output too because otherwise 922 tDASH (1002 - 80) are going to be mined as a fee.
FYI: Moved this thread out of Dash Foundation subforum, not sure why we had it there in the first place...
Maybe it's not the best place for this thread either but I can't find a better one, any suggestions are welcome.
@tungfa